dotnet/reactive
This system is a .NET library providing asynchronous extensions for LINQ and Reactive programming. It implements `IAsyncEnumerable`-based operators for both queryable and enumerable data streams, alongside a comprehensive Reactive Extensions (Rx) implementation featuring async observables, schedulers, and disposable management. The codebase includes tooling for API comparison and performance benchmarking, while maintaining backward compatibility through deprecation facades and extensive xUnit test coverage.
47.5
Weak · 5 August 2026
20k
lines of production code
C#
primary language
2
bus factor · 100 authors in all
4
measurements over time
How it got here
2012–2016 · Modernization and platform expansion
This period focused on modernizing the build infrastructure and expanding cross-platform test coverage for the Interactive Extensions library. Key changes included removing legacy async LINQ implementations, restructuring the project with modern .NET tooling, and adding integration tests for a wide range of .NET platforms and frameworks.
11 changes
2017 · Async LINQ and test modernization
This period focused on modernizing the codebase by migrating the test suite to xUnit and refactoring async LINQ operators to use ValueTask and cancellation tokens for improved performance. The work also involved reorganizing the code structure into individual files, adding new operators like MaxByWithTies, and introducing tooling to compare synchronous and asynchronous APIs.
26 changes
2018–2026 · Async Rx and LINQ modernization
This period focused on introducing comprehensive async support for Reactive Extensions and enhancing LINQ performance measurement. The codebase expanded with new async types, schedulers, and disposable patterns, while simultaneously refactoring source generators and updating API approvals to reflect modernized, backward-compatible interfaces.
5 changes
Survey your own repository
dotnet/reactive was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 5 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 94b5d5ab91 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.