Public report of dotnet/reactive, published 23 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 23 October 2026, 11:37 UTC · Survey ID cd_4465001c7f3a414a97312eb6de75df2d
dotnet/reactive
Measured 23 October 2026, 11:32 UTC, at code version 89e05b8
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Code coverage is not measured: No coverage collector is wired up.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreProvisionalUp 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 178,710 lines of product code in 183 projects, tests not counted · Estimated rebuild effort: about 2.9 person-years · Weakest lens: Production Readiness, 45
Findings by how serious they are
68 critical764 serious713 minor
5 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 11:32 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 121 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS8630: Invalid 'nullable' value: 'Enable' for C# 7.3. Please use language version '8.0' or greater.; CS9202: Feature 'unbound generic types in nameof operator' is not available in C# 12.0. Please use language version 14.0 or greater.; MSB3644: The reference assemblies for UAP,Version=v10.0.18362 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks; CS0234: The type or namespace name 'Reactive' does not exist in the namespace 'System' (are you missing an assembly reference?); CS0246: The type or namespace name 'Timestamped<>' could not be found (are you missing a using directive or an assembly reference?); MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.0/Microsoft.Portable.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.0/Microsoft.Portable.CSharp.targets", is correct, and that the file exists on disk.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Silverlight/v4.0/Microsoft.Silverlight.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Silverlight/$(SilverlightVersion)/Microsoft.Silverlight.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Silverlight/v4.0/Microsoft.Silverlight.CSharp.targets", is correct, and that the file exists on disk.; MSB3073: The command "mono --runtime=v4.0.30319 Rx.NET/Samples/Portable/.nuget/NuGet.exe install "packages.config" -source "" -RequireConsent -solutionDir "Rx.NET/Samples/Portable/"" exited with code 127.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets", is correct, and that the file exists on disk.; CS0246: The type or namespace name 'CommonCodeInPcl' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Subject<>' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'Kinect' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
68of 74 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
1529of 1545 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
74dimensions across 6 lenses, read from 178,710 lines of product code in 183 projects.
dotnet/reactive scores 55 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 45 and is rated Weak. Its Secret Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 3 Leaked secret finding(s) in Secret Scanning and to add a CI workflow that builds and runs the test suite on every push/PR, and if Production Readiness rose to 70, the score would rise from 55 to about 64.
68 findings are critical: 57 in Explicit Debt, four in Secrets (history), three in Secret Scanning, two in Project dependency cycles, one in Static Analysis (SAST) and one in Test Quality.
Watchdog couldn't measure Dependency Hygiene, IL Efficiency and Runtime evidence locked — no reproducible boot in this code, so those dimensions are left out of the score. The product code is 178,710 lines, which would take an estimated 2.9 person-years, around €420,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 83 findings
These 83 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.
Code Duplication · Edited copy of a member (52 corresponding lines) Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs
Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs
Code Duplication · Members sharing a duplicated core (13 members, 50+ identical tokens) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs
Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs
Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs
Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs
Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) Rx.NET/Samples/HOL/CS/Excercise2/Start/Program.cs
Coupling · Off the main sequence: System.Reactive.MakeRefAssemblies(netstandard2.0)
Coupling · Off the main sequence: System.Reactive.Async(netstandard2.0)
Cancellation propagation · Async method without CancellationToken: SkipAndCountAsync Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerablePartition.cs
Cancellation propagation · Async method without CancellationToken: LoadFromEnumeratorAsync Ix.NET/Source/System.Linq.Async/System/Linq/Operators/AppendPrepend.cs
Cancellation propagation · Async method without CancellationToken: ToArray Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs
Cancellation propagation · Async method without CancellationToken: ToList Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs
Cancellation propagation · Async method without CancellationToken: SetEnumeratorAsync Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Union.cs
Cancellation propagation · Async method without CancellationToken: GetNextAsync Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Union.cs
Cancellation propagation · Async method without CancellationToken: Experiment Ix.NET/Source/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: AsyncLinq Ix.NET/Source/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: AsyncLinqQueryable Ix.NET/Source/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: AsyncIx Ix.NET/Source/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: AsyncIxQueryable Ix.NET/Source/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: Async1 Ix.NET/Source/FasterLinq/Program.cs
Cancellation propagation · Async method without CancellationToken: Async2 Ix.NET/Source/FasterLinq/Program.cs
Cancellation propagation · Async method without CancellationToken: Aggregate Ix.NET/Source/FasterLinq/Program.cs
Cancellation propagation · Async method without CancellationToken: Aggregate Ix.NET/Source/FasterLinq/Program.cs
Cancellation propagation · Async method without CancellationToken: ForEachAsync Ix.NET/Source/FasterLinq/Program.cs
Cancellation propagation · Async method without CancellationToken: Aggregate Ix.NET/Source/FasterLinq/Program.cs
Cancellation propagation · Async method without CancellationToken: Aggregate Ix.NET/Source/FasterLinq/Program.cs
Cancellation propagation · Async method without CancellationToken: ForEachAsync Ix.NET/Source/FasterLinq/Program.cs
Cancellation propagation · Async method without CancellationToken: AssignAsync AsyncRx.NET/System.Reactive.Async/AsyncObservableBase.cs
Cancellation propagation · Async method without CancellationToken: AddAsync AsyncRx.NET/System.Reactive.Async/Disposables/CompositeAsyncDisposable.cs
Cancellation propagation · Async method without CancellationToken: RemoveAsync AsyncRx.NET/System.Reactive.Async/Disposables/CompositeAsyncDisposable.cs
Cancellation propagation · Async method without CancellationToken: GetDisposableAsync AsyncRx.NET/System.Reactive.Async/Disposables/RefCountAsyncDisposable.cs
Cancellation propagation · Async method without CancellationToken: ReleaseAsync AsyncRx.NET/System.Reactive.Async/Disposables/RefCountAsyncDisposable.cs
Cancellation propagation · Async method without CancellationToken: AssignAsync AsyncRx.NET/System.Reactive.Async/Disposables/SerialAsyncDisposable.cs
Cancellation propagation · Async method without CancellationToken: AssignAsync AsyncRx.NET/System.Reactive.Async/Disposables/SingleAssignmentAsyncDisposable.cs
Cancellation propagation · Async method without CancellationToken: RemoveActivePlan AsyncRx.NET/System.Reactive.Async/Joins/AsyncJoinObserver.cs
Cancellation propagation · Async method without CancellationToken: GroupByCore AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs
Cancellation propagation · Async method without CancellationToken: GroupByUntilCore AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs
Cancellation propagation · Async method without CancellationToken: WindowCore AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs
Cancellation propagation · Async method without CancellationToken: WindowAsyncCore AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs
Cancellation propagation · Async method without CancellationToken: AcceptAsync AsyncRx.NET/System.Reactive.Async/NotificationAsyncExtensions.cs
Cancellation propagation · Async method without CancellationToken: Wait AsyncRx.NET/System.Reactive.Async/NotificationAsyncExtensions.cs
Cancellation propagation · Async method without CancellationToken: SetResult AsyncRx.NET/System.Reactive.Async/Runtime/CompilerServices/AsyncObservableMethodBuilder.cs
Cancellation propagation · Async method without CancellationToken: EnsureActive AsyncRx.NET/System.Reactive.Async/Subjects/ReplayAsyncSubject.cs
Cancellation propagation · Async method without CancellationToken: UnsubscribeAsync AsyncRx.NET/System.Reactive.Async/Subjects/ReplayAsyncSubject.cs
Cancellation propagation · Async method without CancellationToken: WaitAsync AsyncRx.NET/System.Reactive.Async/Threading/AsyncQueueLock.cs
Cancellation propagation · Async method without CancellationToken: AggregateAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: AllAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: AnyAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: AppendAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: AwaitAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: BufferTimeHoppingAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: BufferTimeSlidingAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: CombineLatestAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: ConcatAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: DelayAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: GroupByAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: GroupBySelectManyAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: MergeAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: PrependAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: RangeAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: ReplaySubjectAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: SelectManyAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: SubjectAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: TakeUntilAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: TimerAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: WhileAsync AsyncRx.NET/Playground/Program.cs
Cancellation propagation · Async method without CancellationToken: DeliverAsync AsyncRx.NET/Microsoft.Reactive.Testing.Async/ColdAsyncObservable.cs
Cancellation propagation · Async method without CancellationToken: RecordAsync AsyncRx.NET/Microsoft.Reactive.Testing.Async/MockAsyncObserver.cs
Rebuild cost: about €420,000 · Estimate
Cost to rebuild
€140,000 to €700,000, for 2,302 to 7,396 hours of work, about 2.9 person-years for 1 to 6 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 178,710 lines of product code, of which 30% is declarations and boilerplate, 27% straight logic and 44% logic with branches
Comment lines
The estimate prices 141,138 lines. Comment lines count towards the size of 178,710 lines but aren't priced as work.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3).
Raises the score by about 10 points · Low effort · Secret Scanning
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 8 points · Medium effort · CI/CD gates
3
Resolve the 1 Tests excluded from compilation finding(s) in Test Quality — start with LicenseHeaderTest.cs.
Raises the score by about 3 points · Low effort · Test Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS8630: Invalid 'nullable' value: 'Enable' for C# 7.3. Please use language version '8.0' or greater.; CS9202: Feature 'unbound generic types in nameof operator' is not available in C# 12.0. Please use language version 14.0 or greater.; MSB3644: The reference assemblies for UAP,Version=v10.0.18362 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks; CS0234: The type or namespace name 'Reactive' does not exist in the namespace 'System' (are you missing an assembly reference?); CS0246: The type or namespace name 'Timestamped<>' could not be found (are you missing a using directive or an assembly reference?); MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.0/Microsoft.Portable.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.0/Microsoft.Portable.CSharp.targets", is correct, and that the file exists on disk.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Silverlight/v4.0/Microsoft.Silverlight.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Silverlight/$(SilverlightVersion)/Microsoft.Silverlight.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Silverlight/v4.0/Microsoft.Silverlight.CSharp.targets", is correct, and that the file exists on disk.; MSB3073: The command "mono --runtime=v4.0.30319 Rx.NET/Samples/Portable/.nuget/NuGet.exe install "packages.config" -source "" -RequireConsent -solutionDir "Rx.NET/Samples/Portable/"" exited with code 127.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets", is correct, and that the file exists on disk.; CS0246: The type or namespace name 'CommonCodeInPcl' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Subject<>' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'Kinect' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €420,000 to build again, about 2.9 person-years of work. Its weakest lens is Production Readiness, at 45 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
44 modules, with 59 dependencies between them. 2 loops run through 11 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 4 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
System.Linq.Internal uses System.Linq, so a change to System.Linq can break System.Linq.Internal, while a change to System.Linq.Internal can't break System.Linq.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→26 System.Linq.Internal uses System.Collections.Genericpart of a loop✕
Connections
5 pairs of types, where a type in System.Linq.Internal uses a type in System.Collections.Generic.
System.Linq.Internal uses System.Collections.Generic, so a change to System.Collections.Generic can break System.Linq.Internal, while a change to System.Linq.Internal can't break System.Collections.Generic.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
System.Linq uses System.Linq.Internal, so a change to System.Linq.Internal can break System.Linq, while a change to System.Linq can't break System.Linq.Internal.
Position
Below the diagonal: System.Linq uses a module listed above it, which is the healthy direction.
24→26 System.Linq uses System.Collections.Genericpart of a loop✕
Connections
87 pairs of types, where a type in System.Linq uses a type in System.Collections.Generic. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
System.Linq uses System.Collections.Generic, so a change to System.Collections.Generic can break System.Linq, while a change to System.Linq can't break System.Collections.Generic.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
System.Reactive.Disposables uses System, so a change to System can break System.Reactive.Disposables, while a change to System.Reactive.Disposables can't break System.
Position
Below the diagonal: System.Reactive.Disposables uses a module listed above it, which is the healthy direction.
System.Reactive.Disposables uses System.Threading, so a change to System.Threading can break System.Reactive.Disposables, while a change to System.Reactive.Disposables can't break System.Threading.
Position
Below the diagonal: System.Reactive.Disposables uses a module listed above it, which is the healthy direction.
25→32 System.Reactive.Disposables uses System.Reactive.Concurrencypart of a loop✕
Connections
1 pair of types, where a type in System.Reactive.Disposables uses a type in System.Reactive.Concurrency.
System.Reactive.Disposables uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Reactive.Disposables, while a change to System.Reactive.Disposables can't break System.Reactive.Concurrency.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
System.Collections.Generic uses System, so a change to System can break System.Collections.Generic, while a change to System.Collections.Generic can't break System.
Position
Below the diagonal: System.Collections.Generic uses a module listed above it, which is the healthy direction.
System.Collections.Generic uses System.Linq, so a change to System.Linq can break System.Collections.Generic, while a change to System.Collections.Generic can't break System.Linq.
Position
Below the diagonal: System.Collections.Generic uses a module listed above it, which is the healthy direction.
System.Reactive.Disposables.Fluent uses System.Reactive.Disposables, so a change to System.Reactive.Disposables can break System.Reactive.Disposables.Fluent, while a change to System.Reactive.Disposables.Fluent can't break System.Reactive.Disposables.
Position
Below the diagonal: System.Reactive.Disposables.Fluent uses a module listed above it, which is the healthy direction.
System.Reactive.Joins uses System.Threading, so a change to System.Threading can break System.Reactive.Joins, while a change to System.Reactive.Joins can't break System.Threading.
Position
Below the diagonal: System.Reactive.Joins uses a module listed above it, which is the healthy direction.
System.Reactive.Joins uses System.Reactive.Disposables, so a change to System.Reactive.Disposables can break System.Reactive.Joins, while a change to System.Reactive.Joins can't break System.Reactive.Disposables.
Position
Below the diagonal: System.Reactive.Joins uses a module listed above it, which is the healthy direction.
28→36 System.Reactive.Joins uses System.Reactivepart of a loop✕
Connections
4 pairs of types, where a type in System.Reactive.Joins uses a type in System.Reactive.
System.Reactive.Joins uses System.Reactive, so a change to System.Reactive can break System.Reactive.Joins, while a change to System.Reactive.Joins can't break System.Reactive.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
System.Reactive.PlatformServices uses System.Reactive.Disposables, so a change to System.Reactive.Disposables can break System.Reactive.PlatformServices, while a change to System.Reactive.PlatformServices can't break System.Reactive.Disposables.
Position
Below the diagonal: System.Reactive.PlatformServices uses a module listed above it, which is the healthy direction.
29→32 System.Reactive.PlatformServices uses System.Reactive.Concurrencypart of a loop✕
Connections
1 pair of types, where a type in System.Reactive.PlatformServices uses a type in System.Reactive.Concurrency.
System.Reactive.PlatformServices uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Reactive.PlatformServices, while a change to System.Reactive.PlatformServices can't break System.Reactive.Concurrency.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28 pairs of types, where a type in System.Labs.Linq uses a type in System.Collections.Generic. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
System.Labs.Linq uses System.Collections.Generic, so a change to System.Collections.Generic can break System.Labs.Linq, while a change to System.Labs.Linq can't break System.Collections.Generic.
Position
Below the diagonal: System.Labs.Linq uses a module listed above it, which is the healthy direction.
System.Threading.Tasks uses System, so a change to System can break System.Threading.Tasks, while a change to System.Threading.Tasks can't break System.
Position
Below the diagonal: System.Threading.Tasks uses a module listed above it, which is the healthy direction.
System.Threading.Tasks uses System.Collections.Generic, so a change to System.Collections.Generic can break System.Threading.Tasks, while a change to System.Threading.Tasks can't break System.Collections.Generic.
Position
Below the diagonal: System.Threading.Tasks uses a module listed above it, which is the healthy direction.
31→32 System.Threading.Tasks uses System.Reactive.Concurrencypart of a loop✕
Connections
6 pairs of types, where a type in System.Threading.Tasks uses a type in System.Reactive.Concurrency.
System.Threading.Tasks uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Threading.Tasks, while a change to System.Threading.Tasks can't break System.Reactive.Concurrency.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→36 System.Threading.Tasks uses System.Reactivepart of a loop✕
Connections
1 pair of types, where a type in System.Threading.Tasks uses a type in System.Reactive.
System.Threading.Tasks uses System.Reactive, so a change to System.Reactive can break System.Threading.Tasks, while a change to System.Threading.Tasks can't break System.Reactive.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
System.Reactive.Concurrency uses System, so a change to System can break System.Reactive.Concurrency, while a change to System.Reactive.Concurrency can't break System.
Position
Below the diagonal: System.Reactive.Concurrency uses a module listed above it, which is the healthy direction.
System.Reactive.Concurrency uses System.Reactive.Disposables, so a change to System.Reactive.Disposables can break System.Reactive.Concurrency, while a change to System.Reactive.Concurrency can't break System.Reactive.Disposables.
Position
Below the diagonal: System.Reactive.Concurrency uses a module listed above it, which is the healthy direction.
System.Reactive.Concurrency uses System.Reactive.PlatformServices, so a change to System.Reactive.PlatformServices can break System.Reactive.Concurrency, while a change to System.Reactive.Concurrency can't break System.Reactive.PlatformServices.
Position
Below the diagonal: System.Reactive.Concurrency uses a module listed above it, which is the healthy direction.
System.Reactive.Concurrency uses System.Threading.Tasks, so a change to System.Threading.Tasks can break System.Reactive.Concurrency, while a change to System.Reactive.Concurrency can't break System.Threading.Tasks.
Position
Below the diagonal: System.Reactive.Concurrency uses a module listed above it, which is the healthy direction.
32→36 System.Reactive.Concurrency uses System.Reactivepart of a loop✕
Connections
9 pairs of types, where a type in System.Reactive.Concurrency uses a type in System.Reactive.
System.Reactive.Concurrency uses System.Reactive, so a change to System.Reactive can break System.Reactive.Concurrency, while a change to System.Reactive.Concurrency can't break System.Reactive.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
System.Reactive.Subjects uses System, so a change to System can break System.Reactive.Subjects, while a change to System.Reactive.Subjects can't break System.
Position
Below the diagonal: System.Reactive.Subjects uses a module listed above it, which is the healthy direction.
System.Reactive.Subjects uses System.Threading, so a change to System.Threading can break System.Reactive.Subjects, while a change to System.Reactive.Subjects can't break System.Threading.
Position
Below the diagonal: System.Reactive.Subjects uses a module listed above it, which is the healthy direction.
System.Reactive.Subjects uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Reactive.Subjects, while a change to System.Reactive.Subjects can't break System.Reactive.Concurrency.
Position
Below the diagonal: System.Reactive.Subjects uses a module listed above it, which is the healthy direction.
33→36 System.Reactive.Subjects uses System.Reactivepart of a loop✕
Connections
10 pairs of types, where a type in System.Reactive.Subjects uses a type in System.Reactive.
System.Reactive.Subjects uses System.Reactive, so a change to System.Reactive can break System.Reactive.Subjects, while a change to System.Reactive.Subjects can't break System.Reactive.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
System.Reactive.Uwp uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Reactive.Uwp, while a change to System.Reactive.Uwp can't break System.Reactive.Concurrency.
Position
Below the diagonal: System.Reactive.Uwp uses a module listed above it, which is the healthy direction.
System.Reactive.Linq uses System.Threading, so a change to System.Threading can break System.Reactive.Linq, while a change to System.Reactive.Linq can't break System.Threading.
Position
Below the diagonal: System.Reactive.Linq uses a module listed above it, which is the healthy direction.
System.Reactive.Linq uses System.Reactive.Disposables, so a change to System.Reactive.Disposables can break System.Reactive.Linq, while a change to System.Reactive.Linq can't break System.Reactive.Disposables.
Position
Below the diagonal: System.Reactive.Linq uses a module listed above it, which is the healthy direction.
System.Reactive.Linq uses System.Reactive.Joins, so a change to System.Reactive.Joins can break System.Reactive.Linq, while a change to System.Reactive.Linq can't break System.Reactive.Joins.
Position
Below the diagonal: System.Reactive.Linq uses a module listed above it, which is the healthy direction.
System.Reactive.Linq uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Reactive.Linq, while a change to System.Reactive.Linq can't break System.Reactive.Concurrency.
Position
Below the diagonal: System.Reactive.Linq uses a module listed above it, which is the healthy direction.
System.Reactive.Linq uses System.Reactive.Subjects, so a change to System.Reactive.Subjects can break System.Reactive.Linq, while a change to System.Reactive.Linq can't break System.Reactive.Subjects.
Position
Below the diagonal: System.Reactive.Linq uses a module listed above it, which is the healthy direction.
35→36 System.Reactive.Linq uses System.Reactivepart of a loop✕
Connections
67 pairs of types, where a type in System.Reactive.Linq uses a type in System.Reactive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
System.Reactive.Linq uses System.Reactive, so a change to System.Reactive can break System.Reactive.Linq, while a change to System.Reactive.Linq can't break System.Reactive.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
System.Reactive uses System.Threading, so a change to System.Threading can break System.Reactive, while a change to System.Reactive can't break System.Threading.
Position
Below the diagonal: System.Reactive uses a module listed above it, which is the healthy direction.
System.Reactive uses System.Reactive.Disposables, so a change to System.Reactive.Disposables can break System.Reactive, while a change to System.Reactive can't break System.Reactive.Disposables.
Position
Below the diagonal: System.Reactive uses a module listed above it, which is the healthy direction.
System.Reactive uses System.Reactive.PlatformServices, so a change to System.Reactive.PlatformServices can break System.Reactive, while a change to System.Reactive can't break System.Reactive.PlatformServices.
Position
Below the diagonal: System.Reactive uses a module listed above it, which is the healthy direction.
System.Reactive uses System.Threading.Tasks, so a change to System.Threading.Tasks can break System.Reactive, while a change to System.Reactive can't break System.Threading.Tasks.
Position
Below the diagonal: System.Reactive uses a module listed above it, which is the healthy direction.
System.Reactive uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Reactive, while a change to System.Reactive can't break System.Reactive.Concurrency.
Position
Below the diagonal: System.Reactive uses a module listed above it, which is the healthy direction.
System.Reactive uses System.Reactive.Subjects, so a change to System.Reactive.Subjects can break System.Reactive, while a change to System.Reactive can't break System.Reactive.Subjects.
Position
Below the diagonal: System.Reactive uses a module listed above it, which is the healthy direction.
System.Reactive uses System.Reactive.Linq, so a change to System.Reactive.Linq can break System.Reactive, while a change to System.Reactive can't break System.Reactive.Linq.
Position
Below the diagonal: System.Reactive uses a module listed above it, which is the healthy direction.
System.Reactive.Linq.ObservableImpl uses System.Reactive.Disposables, so a change to System.Reactive.Disposables can break System.Reactive.Linq.ObservableImpl, while a change to System.Reactive.Linq.ObservableImpl can't break System.Reactive.Disposables.
Position
Below the diagonal: System.Reactive.Linq.ObservableImpl uses a module listed above it, which is the healthy direction.
39 pairs of types, where a type in System.Reactive.Linq.ObservableImpl uses a type in System.Reactive.Concurrency. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
System.Reactive.Linq.ObservableImpl uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Reactive.Linq.ObservableImpl, while a change to System.Reactive.Linq.ObservableImpl can't break System.Reactive.Concurrency.
Position
Below the diagonal: System.Reactive.Linq.ObservableImpl uses a module listed above it, which is the healthy direction.
System.Reactive.Linq.ObservableImpl uses System.Reactive.Subjects, so a change to System.Reactive.Subjects can break System.Reactive.Linq.ObservableImpl, while a change to System.Reactive.Linq.ObservableImpl can't break System.Reactive.Subjects.
Position
Below the diagonal: System.Reactive.Linq.ObservableImpl uses a module listed above it, which is the healthy direction.
System.Reactive.Linq.ObservableImpl uses System.Reactive.Linq, so a change to System.Reactive.Linq can break System.Reactive.Linq.ObservableImpl, while a change to System.Reactive.Linq.ObservableImpl can't break System.Reactive.Linq.
Position
Below the diagonal: System.Reactive.Linq.ObservableImpl uses a module listed above it, which is the healthy direction.
187 pairs of types, where a type in System.Reactive.Linq.ObservableImpl uses a type in System.Reactive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
System.Reactive.Linq.ObservableImpl uses System.Reactive, so a change to System.Reactive can break System.Reactive.Linq.ObservableImpl, while a change to System.Reactive.Linq.ObservableImpl can't break System.Reactive.
Position
Below the diagonal: System.Reactive.Linq.ObservableImpl uses a module listed above it, which is the healthy direction.
System.Reactive.Threading.Tasks uses System.Reactive.Concurrency, so a change to System.Reactive.Concurrency can break System.Reactive.Threading.Tasks, while a change to System.Reactive.Threading.Tasks can't break System.Reactive.Concurrency.
Position
Below the diagonal: System.Reactive.Threading.Tasks uses a module listed above it, which is the healthy direction.
System.Reactive.Threading.Tasks uses System.Reactive, so a change to System.Reactive can break System.Reactive.Threading.Tasks, while a change to System.Reactive.Threading.Tasks can't break System.Reactive.
Position
Below the diagonal: System.Reactive.Threading.Tasks uses a module listed above it, which is the healthy direction.
System.Reactive.WindowsRuntime uses System.Reactive.Subjects, so a change to System.Reactive.Subjects can break System.Reactive.WindowsRuntime, while a change to System.Reactive.WindowsRuntime can't break System.Reactive.Subjects.
Position
Below the diagonal: System.Reactive.WindowsRuntime uses a module listed above it, which is the healthy direction.
System.Reactive.WindowsRuntime uses System.Reactive, so a change to System.Reactive can break System.Reactive.WindowsRuntime, while a change to System.Reactive.WindowsRuntime can't break System.Reactive.
Position
Below the diagonal: System.Reactive.WindowsRuntime uses a module listed above it, which is the healthy direction.
System.Runtime.CompilerServices uses System, so a change to System can break System.Runtime.CompilerServices, while a change to System.Runtime.CompilerServices can't break System.
Position
Below the diagonal: System.Runtime.CompilerServices uses a module listed above it, which is the healthy direction.
System.Runtime.CompilerServices uses System.Reactive.Subjects, so a change to System.Reactive.Subjects can break System.Runtime.CompilerServices, while a change to System.Runtime.CompilerServices can't break System.Reactive.Subjects.
Position
Below the diagonal: System.Runtime.CompilerServices uses a module listed above it, which is the healthy direction.
System.Runtime.CompilerServices uses System.Reactive, so a change to System.Reactive can break System.Runtime.CompilerServices, while a change to System.Runtime.CompilerServices can't break System.Reactive.
Position
Below the diagonal: System.Runtime.CompilerServices uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 59% · Adequate · gated by D18, D17 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A07:2025 — Authentication Failures
8
High / Critical
A05:2025 — Injection
1
High / Critical
Roadmap
Immediately resolve the three leaked secrets, starting with REDACTED, to secure the codebase. Establish a CI workflow to build and test on every push, and fix the excluded LicenseHeaderTest.cs to ensure test coverage is accurate. Finally, remove the 34 NoWarn suppressions in project files to address explicit technical debt, and begin maintaining a changelog to track release history.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3).
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 68
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 764
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 713
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 68 of 74 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 74 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1529 of 1545 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: error: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/WindowsXaml/v18.0/Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath)/Microsoft/WindowsXaml/v$(VisualStudioVersion)/Microsoft.Windows.UI.Xaml.CSh….
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Rx.NET/Source/src/System.Reactive/System.Reactive.csproj' with message: The reference assemblies for UAP,Version=v10.0.18362 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework De….
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (178,710 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Ix.NET/Integration/Uwp/project.json`, `Rx.NET/Integration/Installation/Uwp/project.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (nuget packages.config) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Ix.NET/Source/ApiCompare/Program.cs`, `Ix.NET/Source/Playground/DemoAttribute.cs`, `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Never.cs`, `Ix.NET/Source/System.Interactive/System/Linq/Operators/Create.cs`, `Ix.NET/Source/System.Interactive/System/Linq/Operators/Share.cs`, … (+49 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (Rx.NET/Integration/FacadeTest/MainWindow.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 24 further occurrence(s) are not listed individually; the score already reflects all 64.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 233 further occurrence(s) are not listed individually; the score already reflects all 273.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (6): D19, D20, D21, D24, D25, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
33 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Program.Generate at 73. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ActivePlan.Match at 33 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs (ActivePlan.Match at 33). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with Program.Generate (cyclomatic 73). — Refactoring it lifts Cyclomatic Complexity from 6.3 to about 6.5/10.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 72 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with Program.Generate (cognitive 141). — Refactoring it lifts Cognitive Complexity from 5.7 to about 5.8/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.5 / 10Stronggated by 20 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 9 FileTooLong finding(s) in God Classes — start with Program.cs (2), ActivePlan.cs, QueryLanguage.Async.cs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 7 TooManyMethods finding(s) in God Classes — start with QueryLanguage.Aggregates.cs, FromEventPattern.cs, GroupByUntil.cs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with Program.cs (2), GroupByUntil.cs. — One of this dimension's main actionable groups (3 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
281 duplicated block group(s) detected. A further 23 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 22 of the 304 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 128 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Single.cs (3), Program.cs (2), AsyncSubject.cs (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 12 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with TakeLast.cs (4), MaxBy.cs (3), MinBy.cs (3). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 10 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with GroupBy.cs (2), GroupByUntil.cs (2), SelectMany.cs (2). — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.9 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
Off the main sequence: System.Interactive.Async(net48) (Ix.NET/Source/System.Interactive.Async)Ix.NET/Source/System.Interactive.Async/System.Interactive.Async.csproj:1
Off the main sequence: CommonCodeInPclRx.NET/Integration/BindingRedirects/CommonCodeInPcl/CommonCodeInPcl.csproj:1
What to do
Resolve the 1 Unstable project System.Reactive.Observable.Aliases finding(s) in Coupling — start with System.Reactive.Observable.Aliases.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Off the main sequence finding(s) in Coupling — start with System.Interactive.Async.csproj. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 7 mechanizable ADR(s) are enforced: 6 by analyzers, 1 by tests. Cycles found: 0.
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
40695 test methods: 40695 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 64 zero-assertion, 1 excluded from compilation in 1 file(s), 12 whose failure is swallowed by a catch-all, no mocking-framework packages referenced (hand-written doubles or no mocking) across 7366 tests.
Tests excluded from compilation: Rx.NET/Source/tests/Tests.System.Reactive/Tests/LicenseHeaderTest.csRx.NET/Source/tests/Tests.System.Reactive/Tests/LicenseHeaderTest.cs:29
No assertions: Stopwatch · ×61Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/EventLoopSchedulerTest.cs:298
Test cannot fail: Scheduler_Builtins · ×12Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:215
What to do
Resolve the 1 Tests excluded from compilation finding(s) in Test Quality — start with LicenseHeaderTest.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 61 No assertions finding(s) in Test Quality — start with QbservableTest.cs (48), Program.cs (6), QbservableExTest.cs (2). — One of this dimension's main actionable groups (61 warning-level).
Resolve the 12 Test cannot fail finding(s) in Test Quality — start with ThreadPoolSchedulerTest.cs (4), SchedulerTest.cs (3), DefaultSchedulerTest.cs (2). — One of this dimension's main actionable groups (12 warning-level).
Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 328 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 42 direct `PackageReference`(s), and 200 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
No source file's living knowledge is concentrated in a single author. Counted over 345 of the 808 production source files in this repository: 345 are under the ~2,400-byte size floor this dimension measures over, and the remaining 118 have no attributable history left to measure.
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md.
Do you agree with this assessment?
D17 · Explicit Debt3.7 / 10Weak✓ Tool-verified
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
1230 deducted debt markers + unmeasured dead symbols across 178710 LoC in the .NET projects (3.2/KLoC) → score 3.7. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
NoWarnInCsproj — 6 warning codes suppressed in one element · ×34Ix.NET/Source/FasterLinq/FasterLinq.csproj:8
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 34 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (8), System.Linq.Async.Tests.csproj (4), Directory.build.props (4). — One of this dimension's main actionable groups (34 issue-level).
Resolve the 9 EmptyCatchBlock finding(s) in Explicit Debt — start with ReactiveAssert.cs (2), ColdAsyncObservable.cs, HotAsyncObservable.cs. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 6 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (6). — One of this dimension's main actionable groups (6 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape3.0 / 10Weak✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
183 projects, 7848 source files, 300091 hand-written lines of code (178710 production / 121381 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 68608 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 141 inter-project edges (build failed). Measured across 11 solutions loaded as one workspace: `Rx.NET/Source/System.Reactive.slnx`, `Ix.NET/Source/Ix.NET.sln`, `AsyncRx.NET/AsyncRx.NET.slnx`, `Rx.NET/Samples/HOL/CS/RxHOL.sln`, `Rx.NET/Samples/RxRemoteMouseMoves/RxRemoteMouseMoves.sln`, `Rx.NET/Samples/Portable/Portable.sln`, `Rx.NET/Integration/BindingRedirects/BindingRedirects.sln`, `Rx.NET/Samples/EventCorrelationSample/EventCorrelationSample.sln`, `Rx.NET/Samples/HistoricalScheduling/HistoricalScheduling.sln`, `Rx.NET/Samples/RxKinect/RxKinect.sln`, `Rx.NET/tools/HomoIcon/HomoIcon.slnx`.
Build failed
Thin analysable surface across projects: Android · ×22Ix.NET/Integration/Android/Android.csproj
What to do
Resolve the 22 Thin analysable surface across projects finding(s) in Solution Shape — start with Android.csproj (2), Pcl259.csproj (2), Uwp.csproj (2). — One of this dimension's main actionable groups (22 recommendation-level).
Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README gives an overview of four conceptual libraries (Rx.NET/Async/Interactive/Ix/Linq.Async) and links to a FREE second edition book on Rx, plus a gauntlet testing the packaging design for NuGet. The Gauntlet project itself is well written with background, a detailed problem-detail section, and a repro project file; it documents that directory rather than the repository as a whole. All four libraries are documented in their own READMEs (Rx.NET/Source/, Rx.NET/Test/Gauntlet/, etc.) but none of them appear to be missing installation, usage, or contribution guidance for the repository's root. The XML-doc coverage is high across many namespaces.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR QualityStrong◐ Sampled · advisory
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
Evaluated 13 ADR(s) individually; mean quality 8.0/10 (consistently complete and clear). 0 flagged with a specific gap.
What to do
Improve ADR Quality — currently 8.0/10. — Evaluated 13 ADR(s) individually; mean quality 8.0/10 (consistently complete and clear). 0 flagged with a specific gap.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
ADR not followed: Migration of core `IAsyncEnumerable<T>` LINQ to runtime librariesIx.NET/Documentation/adr/0002-System-Linq-Async-In-Net10.md:51detected by adr-prohibition
✓ On the Gold path — maintain.
Detailed fixes: d25_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
62 % of calls cross a namespace and 4 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. semgrep hit a parse error in 71 file(s) — `AsyncRx.NET/Microsoft.Reactive.Testing.Async/ColdAsyncObservable.cs` (lines 79–80, line 87, line 113), `AsyncRx.NET/Microsoft.Reactive.Testing.Async/HotAsyncObservable.cs` (line 87, line 89), `AsyncRx.NET/Microsoft.Reactive.Testing.Async/MockAsyncObserver.cs` (line 9), `AsyncRx.NET/Microsoft.Reactive.Testing.Async/TestAsyncScheduler.cs` (lines 604–605, line 610, line 621, …), `Ix.NET/Source/ApiCompare/Program.cs` (lines 14–188, line 214, line 241, …), … (+66 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 14 of those file(s) — `AsyncRx.NET/Microsoft.Reactive.Testing.Async/ColdAsyncObservable.cs`, `AsyncRx.NET/Microsoft.Reactive.Testing.Async/HotAsyncObservable.cs`, `AsyncRx.NET/Microsoft.Reactive.Testing.Async/MockAsyncObserver.cs`, `AsyncRx.NET/Microsoft.Reactive.Testing.Async/TestAsyncScheduler.cs`, `Ix.NET/Source/ApiCompare/Program.cs`, … (+9 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 1 of those file(s) — `Ix.NET/Source/ApiCompare/Program.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (nuget packages.config). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget packages.config), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
414 of 463 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Rx.NET/Source/src/System.Reactive/Linq/Observable.Async.cs. Counted over 463 of the 808 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3Rx.NET/Source/src/System.Reactive/Linq/Observable.Aggregates.cs:1
Concentrated knowledge decay
What to do
Resolve the 411 Orphaned file finding(s) in Knowledge Freshness — start with Repeat.cs (5), Buffer.cs (4), Distinct.cs (4). — One of this dimension's main actionable groups (411 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Observable.Aggregates.cs, Observable.Async.cs, Observable.Time.cs. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Change coupling finding(s) in Change Coupling — start with IQueryLanguage.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
2 end-of-life runtime(s) and 0 end-of-life framework(s), read from 59 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with RxGauntlet.csproj, ApiCompare.csproj. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The namespaces System.Collections.Generic ↔ System.Linq ↔ System.Linq.Internal depend on each other. The lightest dependency in the cycle is System.Collections.Generic → System.Linq (System.Collections.Generic.AnonymousAsyncIterator → System.Linq.AsyncIterator, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerator.cs:5
The namespaces System.Reactive ↔ System.Reactive.Concurrency ↔ System.Reactive.Disposables ↔ System.Reactive.Joins ↔ System.Reactive.Linq ↔ System.Reactive.PlatformServices ↔ System.Reactive.Subjects ↔ System.Threading.Tasks depend on each other. The lightest dependency in the cycle is System.Reactive → System.Reactive.PlatformServices (System.Reactive.ExceptionHelpers → System.Reactive.PlatformServices.IExceptionServices, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Rx.NET/Source/src/System.Reactive/Internal/ExceptionServices.cs:7
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×21) — Rx.NET/Samples/HOL/CS/Excercise7/Step02/Service References/DictionarySuggestService/Reference.cs:14, Rx.NET/Samples/HOL/CS/Excercise7/Step03/Service References/DictionarySuggestService/Reference.cs:14, Rx.NET/Samples/HOL/CS/Excercise7/Step04/Service References/DictionarySuggestService/Reference.cs:14, …
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — Rx.NET/Samples/RxRemoteMouseMoves/RxMouseServer/MouseService.cs:47, Rx.NET/Samples/RxRemoteMouseMoves/RxMouseServer/MouseService.cs:52
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`Main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — AsyncRx.NET/Playground/Program.cs:22
`MovedTypeDetails` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Rx.NET/Source/src/System.Reactive.Analyzers/Analyzers/UiFrameworkPackages/UiFrameworkSpecificTypes.cs:56
Control only reaches here when `cancel.IsDisposed` is false, because the guard on line 89 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:111
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×34) — AsyncRx.NET/Playground/Program.cs:24, AsyncRx.NET/Playground/Program.cs:25, AsyncRx.NET/Playground/Program.cs:26, …
`Reset`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. (×3) — Ix.NET/Source/FasterLinq/Program.cs:259, Ix.NET/Source/System.Interactive/System/Linq/Operators/Share.cs:143, Ix.NET/Source/System.Interactive/System/Linq/Yielder.cs:75
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
60 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 124 of 125 project(s) that lack one — worth up to 2 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
Only 26/125 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Rx.NET/Documentation/IntroToRx/02_KeyTypes.md names the project `System.IO.Stream`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Rx.NET/Documentation/IntroToRx/02_KeyTypes.md:223
Rx.NET/Documentation/IntroToRx/A_IoStreams.md names the project `System.IO.Stream`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Rx.NET/Documentation/IntroToRx/A_IoStreams.md:3
Rx.NET/Test/Gauntlet/Checks/Bloat/Readme.md names the project `Microsoft.Desktop.App`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Rx.NET/Test/Gauntlet/Checks/Bloat/Readme.md:43
Rx.NET/Test/Gauntlet/Checks/ExtensionMethods/Readme.md names the project `Microsoft.Desktop.App`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Rx.NET/Test/Gauntlet/Checks/ExtensionMethods/Readme.md:3
Rx.NET/Test/Gauntlet/Checks/PlugIns/Readme.md names .NET 5, but the projects target .NET 3, 6, 8, 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Rx.NET/Test/Gauntlet/Checks/PlugIns/Readme.md:74
What to do
Reconcile the README with reality: Rx.NET/Documentation/IntroToRx/02_KeyTypes.md names the project `System.IO.Stream`, but no project, folder or namespace of that name exists; Rx.NET/Documentation/IntroToRx/A_IoStreams.md names the project `System.IO.Stream`, but no project, folder or namespace of that name exists; Rx.NET/Test/Gauntlet/Checks/Bloat/Readme.md names the project `Microsoft.Desktop.App`, but no project, folder or namespace of that name exists; Rx.NET/Test/Gauntlet/Checks/ExtensionMethods/Readme.md names the project `Microsoft.Desktop.App`, but no project, folder or namespace of that name exists; Rx.NET/Test/Gauntlet/Checks/PlugIns/Readme.md names .NET 5, but the projects target .NET 3, 6, 8, 9, 10.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.
Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 2/3 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 3, 1 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
26 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`_evt.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — Rx.NET/Source/src/System.Reactive/Concurrency/EventLoopScheduler.cs:293, Rx.NET/Source/src/System.Reactive/Concurrency/EventLoopScheduler.cs:305
`.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×3) — Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:87, Rx.NET/Source/src/System.Reactive/Internal/SystemClock.Default.cs:107, Rx.NET/Source/src/System.Reactive/ListObservable.cs:43
`_dispatcherEvent.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:109
`consumer.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×3) — Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:78, Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:166, Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:243
`sink.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:101, Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:113
`e.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:427, AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:165
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×12) — Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:157, Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToEnumerable.cs:67, Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToEnumerable.cs:80, …
`adapter.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — AsyncRx.NET/System.Reactive.Async/NotificationAsyncExtensions.cs:31
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×12) — Rx.NET/Source/src/System.Reactive/Internal/SystemClock.Default.cs:107, Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:154, Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToEnumerable.cs:67, …
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×15) — Rx.NET/Source/src/System.Reactive/Linq/Observable/Merge.cs:318, Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:607, Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:765, …
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — AsyncRx.NET/System.Reactive.Async/Runtime/CompilerServices/AsyncObservableMethodBuilder.cs:259
`Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method. (×2) — Rx.NET/Samples/EventCorrelationSample/EventCorrelationSample/Program.cs:123, Rx.NET/Samples/EventCorrelationSample/EventCorrelationSample/Program.cs:172
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`scheduler` is a `EventLoopScheduler`, which implements `IDisposable`, and it is created here (line 58). Every use of it in `Schedule` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var scheduler = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Source/src/System.Reactive/Concurrency/NewThreadScheduler.cs:58
`spr` is a `SchedulePeriodicStopwatch`, which implements `IDisposable`, and it is created here (line 317). Every use of it in `SchedulePeriodic_` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var spr = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Services.Emulation.cs:317
`ScheduledObserver` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_dispatcherEvent` itself (line 59), which makes that instance its own. But `_dispatcherEvent` is named in none of the methods the disposal search covered: `Dispose` (line 314) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_dispatcherEvent?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:59
`ScheduledObserver` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_dispatcherEventRelease` itself (line 60), which makes that instance its own. But `_dispatcherEventRelease` is named in none of the methods the disposal search covered: `Dispose` (line 314) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_dispatcherEventRelease?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:60
`_` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_bufferGate` itself (line 653), which makes that instance its own. But `_bufferGate` is named in none of the methods the disposal search covered: `Dispose` (line 672) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_bufferGate?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Rx.NET/Source/src/System.Reactive/Linq/Observable/Buffer.cs:653
`L` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_evt` itself (line 265), which makes that instance its own. But `_evt` is named in none of the methods the disposal search covered: `Dispose` (line 281) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_evt?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Rx.NET/Source/src/System.Reactive/Linq/Observable/Delay.cs:265
`e` is a `GetEnumerator`, which implements `IDisposable`, and it is created here (line 125). Every use of it in `GetEnumerator` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var e = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:125
`_subscription` is never created by `Connection` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 69). Its declared type `IDisposable` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Rx.NET/Source/src/System.Reactive/Subjects/ConnectableObservable.cs:69
`_source` is never created by `MemoizedBuffer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 162). Its declared type `IEnumerator` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Ix.NET/Source/System.Interactive/System/Linq/Operators/Memoize.cs:162
`_source` is never created by `PublishedBuffer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 111). Its declared type `IEnumerator` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Ix.NET/Source/System.Interactive/System/Linq/Operators/Publish.cs:111
`_source` is never created by `SharedBuffer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 86). Its declared type `IEnumerator` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Ix.NET/Source/System.Interactive/System/Linq/Operators/Share.cs:86
`_source` is never created by `WithCancellationAsyncEnumerator` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 44). Its declared type `IAsyncEnumerator` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerator.WithCancellation.cs:44
`semaphore` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 77). Every use of it in `Delay` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var semaphore = …;`), which releases it at the end of the scope on every path including a throw. — AsyncRx.NET/System.Reactive.Async/Linq/Operators/Delay.cs:77
`semaphore` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `ObserveOn` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var semaphore = …;`), which releases it at the end of the scope on every path including a throw. — AsyncRx.NET/System.Reactive.Async/Linq/Operators/ObserveOn.cs:45
`queueLock` is a `AsyncQueueLock`, which implements `IDisposable`, and it is created here (line 740). Every use of it in `Window` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var queueLock = …;`), which releases it at the end of the scope on every path including a throw. — AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:740
`e` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 161). Every use of it in `GetResult` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var e = …;`), which releases it at the end of the scope on every path including a throw. — AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:161
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. (×5) — Rx.NET/Samples/HOL/CS/Excercise7/Step03/Program.cs:13, Rx.NET/Samples/HOL/CS/Excercise7/Step04/Program.cs:13, Rx.NET/Samples/HOL/CS/Excercise7/Step05/Program.cs:13, …
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 27). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. (×2) — Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:27, Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:27
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 28). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. (×3) — Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs:28, Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:28, Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:28
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 29). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:29
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. (×2) — Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:31, Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs:31
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:36
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:38
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 49). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:49
`svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 48). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Samples/HOL/CS/Excercise9/Step04/Program.cs:48
`semaphore` is a `Semaphore`, which implements `IDisposable`, and it is created here (line 105). Every use of it in `StartService` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var semaphore = …;`), which releases it at the end of the scope on every path including a throw. — Rx.NET/Samples/EventCorrelationSample/EventCorrelationSample/Program.cs:105
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 526/798 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×14) — Rx.NET/Source/src/System.Reactive/Linq/Observable.Imperative.cs:25, Rx.NET/Source/src/System.Reactive/Linq/Observable.Imperative.cs:75, Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Imperative.cs:19, …
No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×24) — Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Distinct.cs:240, Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Distinct.cs:385, Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Distinct.cs:531, …
Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. — Ix.NET/Source/System.Linq.Async/System/Linq/AsyncListPartition.cs:53
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×7) — Rx.NET/Source/src/System.Reactive/Concurrency/CatchScheduler.cs:89, Rx.NET/Source/src/System.Reactive/Linq/Observable/ResetExceptionDispatchState.cs:44, Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/OnErrorResumeNext.cs:130, …
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — Ix.NET/Source/System.Interactive/System/Linq/Operators/OnErrorResumeNext.cs:74
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
22/25 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~1.8 `!` suppressions per 1k syntax nodes — 957 suppression(s) across the 546395 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 42 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D12 Dependency Hygiene — Dependency hygiene not measured
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 54 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — no CI workflow found
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
NoWarnInCsproj — 6 warning codes suppressed in one element Ix.NET/Source/FasterLinq/FasterLinq.csproj:8— A single <NoWarn> suppresses 6 warning codes (IDE0007;IDE0034;IDE0040;IDE0063;IDE0090;IDE1006) in one stroke — one team-wide decision, not 6 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj — 9 warning codes suppressed in one element Rx.NET/Source/tests/Tests.System.Reactive.Uwp.DeviceRunner/Tests.System.Reactive.Uwp.DeviceRunner.csproj:27— A single <NoWarn> suppresses 9 warning codes (CA1001;CA2213;CA1510;CA1513;CS0618;IDE0056;IDE0057;IDE0290;IDE0305) in one stroke — one team-wide decision, not 9 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj — 9 warning codes suppressed in one element Rx.NET/Source/tests/Tests.System.Reactive.Uwp.DeviceRunner/Tests.System.Reactive.Uwp.DeviceRunner.csproj:38— A single <NoWarn> suppresses 9 warning codes (CA1001;CA2213;CA1510;CA1513;CS0618;IDE0056;IDE0057;IDE0290;IDE0305) in one stroke — one team-wide decision, not 9 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj — 34 warning codes suppressed in one element Rx.NET/Source/tests/Tests.System.Reactive.Uwp.DeviceRunner/Tests.System.Reactive.Uwp.DeviceRunner.csproj:93— A single <NoWarn> suppresses 34 warning codes (IDE0003;IDE0016;IDE0017;IDE0018;IDE0019;IDE0020;IDE0031;IDE0032;IDE0034;IDE0037;IDE0038;IDE0039;IDE0040;IDE0044;IDE0051;IDE0052;IDE0056;IDE0057;IDE0059;IDE0060;IDE0062;IDE0063;IDE0071;IDE0074;IDE0075;IDE0076;IDE0077;IDE0079;IDE0083;IDE0090;IDE0180;IDE1006;IDE1056;MSTEST0049) in one stroke — one team-wide decision, not 34 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj — 27 warning codes suppressed in one element Rx.NET/Source/src/Microsoft.Reactive.Testing/Microsoft.Reactive.Testing.csproj:12— A single <NoWarn> suppresses 27 warning codes (IDE0054;IDE0066;CA1305;CA1307;CA1032;CA1064;CA1704;CA1822;CA1812;CA1820;CA1823;CA1825;CA1845;CA2249;IDE0016;IDE0018;IDE0019;IDE0020;IDE0028;IDE0031;IDE0039;IDE0044;IDE0059;IDE0074;IDE0090;IDE0270;IDE0300) in one stroke — one team-wide decision, not 27 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj Rx.NET/Integration/WindowsDesktopTests/WindowsDesktopTests.csproj:4— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Rx.NET/Integration/LinuxTests/LinuxTests.csproj:4— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Linq.Async.Tests/System.Linq.Async.Tests.csproj:11— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Linq.Async.Queryable.Tests/System.Linq.Async.Queryable.Tests.csproj:5— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Interactive.Tests/System.Interactive.Tests.csproj:10— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Interactive.Async.Tests/System.Interactive.Async.Tests.csproj:11— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Interactive.Async.Providers.Tests/System.Interactive.Async.Providers.Tests.csproj:5— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Rx.NET/Source/tests/Tests.System.Reactive/Tests.System.Reactive.csproj:9— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Rx.NET/Source/tests/Tests.System.Reactive.ApiApprovals/Tests.System.Reactive.ApiApprovals.csproj:5— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Linq.Async.Tests/System.Linq.Async.Tests.csproj:11— CS8603 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Interactive.Tests/System.Interactive.Tests.csproj:10— CS8603 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Interactive.Async.Tests/System.Interactive.Async.Tests.csproj:11— CS8603 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Linq.Async.Tests/System.Linq.Async.Tests.csproj:11— CS8625 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Interactive.Tests/System.Interactive.Tests.csproj:10— CS8625 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Interactive.Async.Tests/System.Interactive.Async.Tests.csproj:11— CS8625 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/System.Linq.Async.Tests/System.Linq.Async.Tests.csproj:11— CA1822 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Rx.NET/Source/benchmarks/Benchmarks.System.Reactive/Benchmarks.System.Reactive.csproj:19— IDE1006 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj AsyncRx.NET/Directory.Build.props:13— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Rx.NET/Source/Directory.build.props:12— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Ix.NET/Source/Directory.Build.props:17— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
EmptyCatchBlock AsyncRx.NET/Microsoft.Reactive.Testing.Async/ColdAsyncObservable.cs:67— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock AsyncRx.NET/Microsoft.Reactive.Testing.Async/HotAsyncObservable.cs:53— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/OnErrorResumeNext.cs:130— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Rx.NET/Samples/Portable/SilverlightApplication/App.xaml.cs:63— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Rx.NET/Source/src/Microsoft.Reactive.Testing/ReactiveAssert.cs:219— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Rx.NET/Source/src/Microsoft.Reactive.Testing/ReactiveAssert.cs:253— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Rx.NET/Source/src/System.Reactive/Concurrency/CatchScheduler.cs:89— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Rx.NET/Source/src/System.Reactive/Linq/Observable/ResetExceptionDispatchState.cs:44— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Rx.NET/tools/HomoIcon/Program.cs:113— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
AnalyzerSeverityNone .editorconfig:262— IDE0290 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone Rx.NET/Test/Gauntlet/.editorconfig:4— IDE0290 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:267— IDE0090 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone Rx.NET/Test/Gauntlet/.editorconfig:10— IDE0028 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone Rx.NET/Test/Gauntlet/.editorconfig:11— IDE0305 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone Rx.NET/Test/Gauntlet/.editorconfig:12— IDE0306 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
FileScopedPragmaDisable Rx.NET/Source/src/System.Reactive/Linq/ObservableEx.cs:17— #pragma warning disable IDE1006 // Naming Styles: 3rd party code is known to reflect for this specific field name — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Rx.NET/Source/src/System.Reactive/Linq/Observable_.cs:12— #pragma warning disable IDE1006 // Naming Styles: 3rd party code is known to reflect for this specific field name — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/ControlSchedulerTest.cs:9— #pragma warning disable IDE0034 // (Simplify 'default'.) Want to be explicit about overload being tested. — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/DispatcherSchedulerTest.cs:8— #pragma warning disable IDE0034 // (Simplify 'default'.) Want to be explicit about overload being tested. — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/Observable/SubscribeTest.cs:5— #pragma warning disable IDE0350 // Use implicitly typed lambda - we want to be explicit here for clarity — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
Namespace dependency cycle Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerator.cs:5— The namespaces System.Collections.Generic ↔ System.Linq ↔ System.Linq.Internal depend on each other. The lightest dependency in the cycle is System.Collections.Generic → System.Linq (System.Collections.Generic.AnonymousAsyncIterator → System.Linq.AsyncIterator, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle Rx.NET/Source/src/System.Reactive/Internal/ExceptionServices.cs:7— The namespaces System.Reactive ↔ System.Reactive.Concurrency ↔ System.Reactive.Disposables ↔ System.Reactive.Joins ↔ System.Reactive.Linq ↔ System.Reactive.PlatformServices ↔ System.Reactive.Subjects ↔ System.Threading.Tasks depend on each other. The lightest dependency in the cycle is System.Reactive → System.Reactive.PlatformServices (System.Reactive.ExceptionHelpers → System.Reactive.PlatformServices.IExceptionServices, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D10 · Test Quality· Tests excluded from compilation · ×1
Tests excluded from compilation: Rx.NET/Source/tests/Tests.System.Reactive/Tests/LicenseHeaderTest.cs Rx.NET/Source/tests/Tests.System.Reactive/Tests/LicenseHeaderTest.cs:29— 1 test method(s) in this file, but `Tests.System.Reactive.Uwp.DeviceRunner.csproj` drops it from the build with `<Compile Remove="..\Tests.System.Reactive\Tests\LicenseHeaderTest.cs" />`. It never compiles, never runs, and never reports as skipped — unlike a `Skip = "..."` attribute, nothing in a green test run says these tests are gone. Restore it to the compilation, or delete the file so the tree stops implying coverage that isn't there.
WriteOnlyPrivateField Rx.NET/Integration/BindingRedirects/CommonCodeInPcl/Class1.cs:14— private IDisposable disposable — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D17 · Explicit Debt· NoWarnInCsproj repeated 42 times in 8 files · ×1
NoWarnInCsproj repeated 42 times in 8 files Ix.NET/Integration/Wpa81/Wpa81.csproj:41— The identical NoWarnInCsproj (`2008`) appears 42 times in 8 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 42 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)
BlanketAnalyzerSeverityNone Rx.NET/Source/tests/.editorconfig:5— dotnet_analyzer_diagnostic.category-Design.severity = none — every rule in the Design category — this is not one rule switched off, it is a whole set the file never lists: every rule the entry covers is silenced for every file the section matches, in every project under this directory, and any rule added to that set by a future analyzer upgrade is silenced too, without anybody deciding so. It reads as narrower than it is — the analyzers still run and the build still looks configured — and because no rule is named there is nothing for a reader to look up and no list that will ever disclose what is covered. Replace it with the rules you actually mean to switch off, each on its own line, so the set is finite, visible and reviewable, and the ones nobody chose keep protecting the tree. If the blanket entry is genuinely right, link the decision from a comment above it: a comment that only restates the entry is what the editor generates when it writes this line, so it is a reference to the decision — an issue or a ticket — that clears this row.
DeadPreprocessorBranch Ix.NET/Source/Playground/Program.cs:84— #if USE_AWAIT_FOREACH — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/Playground/Program.cs:114— #if USE_AWAIT_FOREACH — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/Playground/Program.cs:144— #if USE_AWAIT_FOREACH — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/Playground/Program.cs:163— #if USE_AWAIT_FOREACH — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Interactive.Async/System/Diagnostics/CodeAnalysis/ExcludeFromCodeCoverageAttribute.cs:5— #if NO_CODE_COVERAGE_ATTRIBUTE — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Linq.Async/System/Diagnostics/CodeAnalysis/ExcludeFromCodeCoverageAttribute.cs:5— #if NO_CODE_COVERAGE_ATTRIBUTE — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Merge.cs:28— #if USE_FAIR_AND_CHEAPER_MERGE — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Interactive.Async/TaskExt.cs:22— #if USE_FAIR_AND_CHEAPER_MERGE — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Throw.cs:25— #if NO_TASK_FROMEXCEPTION — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Linq.Async.Tests/System/Linq/AsyncEnumerableTests.cs:73— #if NO_TASK_FROMEXCEPTION — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerablePartition.cs:155— #if NOTYET — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Linq.Async/System/Linq/AsyncListPartition.cs:60— #if NOT_YET — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Ix.NET/Source/System.Linq.Async/System/Linq/EmptyArray.cs:5— #if NO_ARRAY_EMPTY — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:22— #if PRODUCTION — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:22— #if PRODUCTION — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:22— #if PRODUCTION — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Samples/HOL/CS/Excercise9/Step04/Program.cs:22— #if PRODUCTION — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Samples/HOL/CS/Excercise9/Step04/Program.cs:52— #if PRODUCTION — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Source/src/System.Reactive/Internal/PushPullAdapter.cs:5— #if NO_PERF — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Source/tests/Tests.System.Reactive/Stress/Core/Disposables/Composite.cs:5— #if STRESS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Source/tests/Tests.System.Reactive/Stress/Core/Disposables/RefCount.cs:5— #if STRESS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Source/tests/Tests.System.Reactive/Stress/Core/Disposables/Serial.cs:5— #if STRESS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Source/tests/Tests.System.Reactive/Stress/Core/Disposables/SingleAssignment.cs:5— #if STRESS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Source/tests/Tests.System.Reactive/Stress/Core/Schedulers/EventLoop.cs:5— #if STRESS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch Rx.NET/Source/tests/Tests.System.Reactive/Stress/Helpers.cs:5— #if STRESS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
No assertions: Stopwatch Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/EventLoopSchedulerTest.cs:298— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Stopwatch Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/NewThreadSchedulerTest.cs:61— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Stopwatch Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/TaskPoolSchedulerTest.cs:128— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: SingleAssignmentDisposable_SetNull Rx.NET/Source/tests/Tests.System.Reactive/Tests/Disposables/DisposableTests.cs:69— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ForkJoin Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableExTest.cs:33— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Let Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableExTest.cs:64— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Aggregate Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:69— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Amb Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:100— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: And Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:129— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Any Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:143— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Average Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:165— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: BufferWithCount Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:187— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: BufferWithTime Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:205— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Case Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:232— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Cast Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:246— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Catch Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:265— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CombineLatest Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:282— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Count Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:309— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Defer Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:367— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Delay Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:384— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Dematerialize Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:399— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: DistinctUntilChanged Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:418— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: DoWhile Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:467— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Finally Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:495— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: For Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/QbservableTest.cs:509— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TodoComment AsyncRx.NET/Playground/Program.cs:82— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/Playground/Program.cs:93— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/Playground/Program.cs:104— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/Playground/Program.cs:116— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/Playground/Program.cs:127— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/Playground/Program.cs:177— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/Playground/Program.cs:243— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/Playground/Program.cs:248— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/Playground/Program.cs:255— // TODO: Use ForEachAsync. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncSchedulerBase.cs:44— // TODO: Support clock drift and clock changes. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Concurrency/TaskPoolAsyncScheduler.cs:46— // TODO: Call event handler. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:11— // TODO: Implement tail call behavior to flatten Catch chains. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/Concat.cs:11— // TODO: Implement tail call behavior to flatten Concat chains. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/Delay.cs:13— // TODO: Add overloads with DateTimeOffset and with duration selector. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/Delay.cs:73— // TODO: Use stopwatch functionality. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/For.cs:14— // TODO: Add IAsyncEnumerable<T> based overlaod. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/ForEachAsync.cs:69— // TODO: Trace? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:197— // TODO: Trace? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:13— // TODO: Add Merge with max concurrency and IEnumerable<T>-based overloads. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/OnErrorResumeNext.cs:11— // TODO: Implement tail call behavior to flatten OnErrorResumeNext chains. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/SequenceEqual.cs:13— // TODO: Add SequenceEqual<T>(IAsyncObservable<T>, IAsyncEnumerable<T>). — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/Timer.cs:142— // TODO: Compensate for drift by adding stopwatch functionality. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/Timer.cs:171— // TODO: Compensate for drift by adding stopwatch functionality. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Linq/Operators/Zip.cs:15— // TODO: Add Zip<T>(IAsyncObservable<T>, IAsyncEnumerable<T>) overload when we have reference to IAsyncEnumerable<T>. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment AsyncRx.NET/System.Reactive.Async/Subjects/BehaviorAsyncSubject.cs:42— // TODO: support for disposal — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Sync-over-async blocking — 26 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Concurrency/EventLoopScheduler.cs:293— `_evt.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Concurrency/EventLoopScheduler.cs:305— `_evt.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:87— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:109— `_dispatcherEvent.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Internal/SystemClock.Default.cs:107— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:78— `consumer.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:101— `sink.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:113— `sink.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:166— `consumer.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:243— `consumer.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/ListObservable.cs:43— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:427— `e.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:157— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToEnumerable.cs:67— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToEnumerable.cs:80— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Ix.NET/Source/Playground/Program.cs:255— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:76— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:123— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs:49— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs:94— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking AsyncRx.NET/System.Reactive.Async/Linq/Operators/ToAsyncObservable.cs:89— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking AsyncRx.NET/System.Reactive.Async/Linq/Operators/ToAsyncObservable.cs:91— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking AsyncRx.NET/System.Reactive.Async/Linq/Operators/ToAsyncObservable.cs:93— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking AsyncRx.NET/System.Reactive.Async/NotificationAsyncExtensions.cs:31— `adapter.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
+ 2 more in this group — see findings.md.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×25
Disposable created and abandoned in the method that made it Rx.NET/Source/src/System.Reactive/Concurrency/NewThreadScheduler.cs:58— `scheduler` is a `EventLoopScheduler`, which implements `IDisposable`, and it is created here (line 58). Every use of it in `Schedule` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var scheduler = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Services.Emulation.cs:317— `spr` is a `SchedulePeriodicStopwatch`, which implements `IDisposable`, and it is created here (line 317). Every use of it in `SchedulePeriodic_` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var spr = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Blocking.cs:125— `e` is a `GetEnumerator`, which implements `IDisposable`, and it is created here (line 125). Every use of it in `GetEnumerator` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var e = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it AsyncRx.NET/System.Reactive.Async/Linq/Operators/Delay.cs:77— `semaphore` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 77). Every use of it in `Delay` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var semaphore = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it AsyncRx.NET/System.Reactive.Async/Linq/Operators/ObserveOn.cs:45— `semaphore` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `ObserveOn` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var semaphore = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:740— `queueLock` is a `AsyncQueueLock`, which implements `IDisposable`, and it is created here (line 740). Every use of it in `Window` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var queueLock = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:161— `e` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 161). Every use of it in `GetResult` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var e = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise7/Step03/Program.cs:13— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise7/Step04/Program.cs:13— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise7/Step05/Program.cs:13— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise7/Step06/Program.cs:13— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise7/Step07/Program.cs:13— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:27— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 27). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:27— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 27). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs:28— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 28). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:28— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 28). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:28— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 28). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:29— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 29). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:31— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs:31— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:36— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:38— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:49— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 49). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/HOL/CS/Excercise9/Step04/Program.cs:48— `svc` is a `DictServiceSoapClient`, which implements `IDisposable`, and it is created here (line 48). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var svc = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Rx.NET/Samples/EventCorrelationSample/EventCorrelationSample/Program.cs:105— `semaphore` is a `Semaphore`, which implements `IDisposable`, and it is created here (line 105). Every use of it in `StartService` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var semaphore = …;`), which releases it at the end of the scope on every path including a throw.
Sync-over-async (deadlock risk) through `.Result` Rx.NET/Source/src/System.Reactive/Linq/Observable/Merge.cs:318— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:607— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:765— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1548— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1683— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Rx.NET/Source/src/System.Reactive/Threading/Tasks/TaskObservableExtensions.cs:329— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Rx.NET/Source/src/System.Reactive/Threading/Tasks/TaskObservableExtensions.cs:504— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Ix.NET/Source/FasterLinq/Program.cs:98— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Ix.NET/Source/FasterLinq/Program.cs:99— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Ix.NET/Source/FasterLinq/Program.cs:100— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Ix.NET/Source/FasterLinq/Program.cs:148— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Ix.NET/Source/FasterLinq/Program.cs:149— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Ix.NET/Source/FasterLinq/Program.cs:150— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` AsyncRx.NET/System.Reactive.Async/Linq/Operators/Zip.cs:39— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` AsyncRx.NET/System.Reactive.Async/Threading/Tasks/TaskAsyncObservableExtensions.cs:141— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
X2 · Cancellation propagation· Async method without CancellationToken · ×14
Async method without CancellationToken: ForEachAsync Rx.NET/Source/src/System.Reactive/Linq/Observable.Imperative.cs:25— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ForEachAsync Rx.NET/Source/src/System.Reactive/Linq/Observable.Imperative.cs:75— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ForEachAsync Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Imperative.cs:19— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ForEachAsync Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Imperative.cs:29— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ToTask Rx.NET/Source/src/System.Reactive/Threading/Tasks/TaskObservableExtensions.cs:409— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: MoveNextCore Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:51— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SkipBeforeAsync Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerablePartition.cs:358— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SkipAndCountAsync Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerablePartition.cs:364— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: MoveNextCore Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerator.cs:94— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Sort Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:545— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Sort Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:554— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ElementAt Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:563— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ComputeMap Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:572— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ComputeKeys Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:785— No CancellationToken parameter — this work can't be stopped early once started.
Test cannot fail: Scheduler_Builtins Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:215— This test's act runs inside `Schedule` at line 933 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. Adding an assertion inside that region does not fix it: the assertion throws, and the same catch swallows it exactly like the exception it replaced. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: Catch_Builtin_Swallow_Shallow Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:704— This test's act runs inside `Schedule` at line 933 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. Adding an assertion inside that region does not fix it: the assertion throws, and the same catch swallows it exactly like the exception it replaced. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: Catch_Builtin_Swallow_Recursive Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:719— This test's act runs inside `Schedule` at line 933 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. Adding an assertion inside that region does not fix it: the assertion throws, and the same catch swallows it exactly like the exception it replaced. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: ScheduleAction Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/DefaultSchedulerTest.cs:35— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: ScheduleActionDue Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/DefaultSchedulerTest.cs:45— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: Immediate_ArgumentChecking_More Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/ImmediateSchedulerTest.cs:115— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 6 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: NewThread_ScheduleAction Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/NewThreadSchedulerTest.cs:40— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: NewThread_ScheduleActionDue Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/NewThreadSchedulerTest.cs:50— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: ScheduleAction Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/ThreadPoolSchedulerTest.cs:35— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: ScheduleActionDueRelative Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/ThreadPoolSchedulerTest.cs:100— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: ScheduleActionDue0 Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/ThreadPoolSchedulerTest.cs:110— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: ScheduleActionDueAbsolute Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/ThreadPoolSchedulerTest.cs:120— This test's act runs inside `Schedule` at Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/SchedulerTest.cs:933, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Duplicated block (9 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Buffer.cs:88— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Buffer.cs:88-96 | Ix.NET/Source/System.Interactive/System/Linq/Operators/Buffer.cs:60-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:112— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:112-120 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:154-162 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `innerKeySelector` to `Func<TInner, ValueTask<TKey>>` in one and `Func<TInner, CancellationToken, ValueTask<TKey>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) Rx.NET/tools/HomoIcon/Program.cs:629— Rx.NET/tools/HomoIcon/Program.cs:629-637 | Rx.NET/tools/HomoIcon/Program.cs:757-765 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:89— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:89-97 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SingleOrDefault.cs:90-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:138— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:138-146 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SingleOrDefault.cs:139-147 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:177— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:177-185 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SingleOrDefault.cs:178-186 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Single.cs:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:500— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:500-508 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:522-530 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:500` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/GroupedAsyncObservable.cs:27— AsyncRx.NET/System.Reactive.Async/Linq/GroupedAsyncObservable.cs:27-35 | AsyncRx.NET/System.Reactive.Async/Linq/WindowAsyncObservable.cs:24-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `observer` to `IAsyncObserver<TElement>` in one and `IAsyncObserver<TSource>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:311— Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:311-319 | Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs:272-280 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs` and `Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:326` calls `ThrowDisposed`, `ObjectDisposedException` and `Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs:290` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:311— Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:311-319 | Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs:272-280 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs` and `Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:326` calls `ThrowDisposed`, `ObjectDisposedException` and `Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs:290` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:90— AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:90-98 | AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs:69-77 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs` and `AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:33— Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:33-41 | Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:35-43 — `Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 54 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:131— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:131-135 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:166-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:131` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:70— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:70-74 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:70-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:173— Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:173-177 | Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLastBuffer.cs:103-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:181` calls `DisposeUpstream` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLastBuffer.cs:113` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:237— Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:237-241 | Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLastBuffer.cs:129-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:173— Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:173-177 | Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLastBuffer.cs:103-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:181` calls `DisposeUpstream` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLastBuffer.cs:113` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:237— Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:237-241 | Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLastBuffer.cs:129-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs:148— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs:148-152 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxByWithTies.cs:147-151 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs` and `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxByWithTies.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs:155— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs:155-159 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxByWithTies.cs:154-158 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs` and `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxByWithTies.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs:163— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs:163-167 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxByWithTies.cs:162-166 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxBy.cs` and `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MaxByWithTies.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs:148— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs:148-152 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinByWithTies.cs:147-151 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs` and `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinByWithTies.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs:155— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs:155-159 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinByWithTies.cs:154-158 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs` and `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinByWithTies.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs:163— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs:163-167 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinByWithTies.cs:162-166 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinBy.cs` and `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinByWithTies.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Sync-over-async (deadlock risk) Rx.NET/Source/src/System.Reactive/Internal/SystemClock.Default.cs:107— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:154— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToEnumerable.cs:67— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToEnumerable.cs:80— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) Ix.NET/Source/Playground/Program.cs:255— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:72— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:123— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs:45— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs:94— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) AsyncRx.NET/System.Reactive.Async/Linq/Operators/ToAsyncObservable.cs:89— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) AsyncRx.NET/System.Reactive.Async/Linq/Operators/ToAsyncObservable.cs:91— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) AsyncRx.NET/System.Reactive.Async/Linq/Operators/ToAsyncObservable.cs:93— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
BarePragmaDisable Rx.NET/Source/src/System.Reactive/Notification.cs:14— #pragma warning disable CS0661 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Concurrency/ScheduledItemTest.cs:93— #pragma warning disable 1718 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/Observable/CombineLatestTest.cs:16— #pragma warning disable IDE0039 // Use local function — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/Observable/FromAsyncPatternTest.cs:17— #pragma warning disable IDE0039 // Use local function — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/Observable/ManySelectTest.cs:16— #pragma warning disable IDE0039 // Use local function — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/Observable/ZipTest.cs:22— #pragma warning disable IDE0039 // Use local function — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/Observable/FromEventPatternTest.cs:877— #pragma warning disable 67 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/Linq/Observable/FromEventPatternTest.cs:889— #pragma warning disable 67 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/TaskLikeSupportTest.cs:25— #pragma warning disable 1998 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Rx.NET/Source/tests/Tests.System.Reactive/Tests/TaskLikeSupportTest.cs:38— #pragma warning disable 1998 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×10
Members sharing a duplicated core (4 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:419— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:419-440 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:509-530 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:692-713 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:784-805 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:110— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:110-126 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:152-168 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:128-160 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:186-218 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:239— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:239-263 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:300-324 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:362-386 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:427-451 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:38— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:38-47 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:74-83 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:112-121 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:138-147 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:90— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:90-104 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:107-121 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:218-232 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:235-249 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:32— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:32-46 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:49-63 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:176-190 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:193-207 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:102— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:102-118 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:121-137 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:246-262 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:265-281 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:14— AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:14-31 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:34-51 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:98-115 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:118-135 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:54— AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:54-73 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:76-95 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:138-157 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:160-179 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:14— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:14-57 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:61-104 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:108-159 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:163-214 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
FileTooLong: Joins/ActivePlan.cs Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs— FileTooLong — 1133 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 633 over it, 2.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Linq/QueryLanguage.Async.cs Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs— FileTooLong — 897 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 397 over it, 1.79× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Joins/Plan.cs Rx.NET/Source/src/System.Reactive/Joins/Plan.cs— FileTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 317 over it, 1.63× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FasterLinq/Program.cs Ix.NET/Source/FasterLinq/Program.cs— FileTooLong — 802 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 302 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Observable/SelectMany.cs Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs— FileTooLong — 783 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 283 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Operators/GroupBy.cs Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs— FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 149 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: HomoIcon/Program.cs Rx.NET/tools/HomoIcon/Program.cs— FileTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 120 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Operators/OrderedAsyncEnumerable.cs Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs— FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 76 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Operators/GroupByUntil.cs AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs— FileTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 44 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (19 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1520— Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1520-1538 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1655-1673 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1520` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:201— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:201-219 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:204-222 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/DoWhile.cs:16— AsyncRx.NET/System.Reactive.Async/Linq/Operators/DoWhile.cs:16-34 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/DoWhile.cs:77-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/DoWhile.cs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:82— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:82-100 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:82-101 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19 lines × 2) AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncScheduler.cs:125— AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncScheduler.cs:125-143 | AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncScheduler.cs:152-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncScheduler.cs:125` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `dueTime` to `TimeSpan` in one and `DateTimeOffset` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:535— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:535-570 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:642-660 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:535` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:151— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:151-169 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:239-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:151` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Task.cs:27— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Task.cs:27-45 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Task.cs:33-51 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Task.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Task.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Task.cs:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:57— AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:57-75 | AsyncRx.NET/System.Reactive.Async/Subjects/SimpleAsyncSubject.cs:41-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:26— AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:26-37 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:78-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:26` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:565— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:565-576 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:736-747 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:565` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:735` calls `Clear` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:564` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:91— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:91-102 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:155-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:29— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:29-40 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:157-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:44— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:44-55 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:172-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:76— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:76-87 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:204-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:18— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:18-29 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:162-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) Rx.NET/Samples/HOL/CS/Excercise4/Step03/Program.cs:12— Rx.NET/Samples/HOL/CS/Excercise4/Step03/Program.cs:12-23 | Rx.NET/Samples/HOL/CS/Excercise4/Step04/Program.cs:12-23 — `Rx.NET/Samples/HOL/CS/Excercise4/Step03/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise4/Step04/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 12 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 2) Rx.NET/Samples/HOL/CS/Excercise6/Step02/Program.cs:12— Rx.NET/Samples/HOL/CS/Excercise6/Step02/Program.cs:12-23 | Rx.NET/Samples/HOL/CS/Excercise6/Step03/Program.cs:12-23 — `Rx.NET/Samples/HOL/CS/Excercise6/Step02/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise6/Step03/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 12 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:375— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:375-384 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs:375-384 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:375` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:401— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:401-410 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs:401-410 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:401` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncScheduler.cs:189— AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncScheduler.cs:189-198 | AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncScheduler.cs:240-249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Concurrency/AsyncScheduler.cs:189` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) AsyncRx.NET/Microsoft.Reactive.Testing.Async/ColdAsyncObservable.cs:91— AsyncRx.NET/Microsoft.Reactive.Testing.Async/ColdAsyncObservable.cs:91-100 | AsyncRx.NET/Microsoft.Reactive.Testing.Async/HotAsyncObservable.cs:91-100 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:398— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:398-407 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:457-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:398` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) Rx.NET/Source/src/System.Reactive/EventPatternSourceBase.cs:121— Rx.NET/Source/src/System.Reactive/EventPatternSourceBase.cs:121-130 | Rx.NET/Source/src/System.Reactive/EventSource.cs:71-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SkipUntil.cs:45— Rx.NET/Source/src/System.Reactive/Linq/Observable/SkipUntil.cs:45-54 | Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeUntil.cs:44-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) Rx.NET/Source/src/System.Reactive/EventPatternSourceBase.cs:121— Rx.NET/Source/src/System.Reactive/EventPatternSourceBase.cs:121-130 | Rx.NET/Source/src/System.Reactive/EventSource.cs:71-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:52— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:52-61 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:239-248 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:45— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:45-66 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:45-66 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:137— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:137-158 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:138-159 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:228— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:228-249 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:230-251 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:228` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:310— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:310-331 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:312-333 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:310` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:199— AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:199-220 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:236-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:199` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs:52— Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs:52-73 | Rx.NET/Source/src/System.Reactive/Platforms/Desktop/Concurrency/ControlScheduler.cs:46-67 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/Desktop/Concurrency/ControlScheduler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/WithLatestFrom.cs:38— AsyncRx.NET/System.Reactive.Async/Linq/Operators/WithLatestFrom.cs:38-59 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/WithLatestFrom.cs:63-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) Rx.NET/Source/src/System.Reactive.Windows.Forms/System.Reactive.Linq/ControlObservable.cs:46— Rx.NET/Source/src/System.Reactive.Windows.Forms/System.Reactive.Linq/ControlObservable.cs:46-67 | Rx.NET/Source/src/System.Reactive/Platforms/Desktop/Linq/ControlObservable.cs:42-63 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.Windows.Forms/System.Reactive.Linq/ControlObservable.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/Desktop/Linq/ControlObservable.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:199— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:199-213 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Concat.cs:104-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `observer` to `IAsyncDisposable) Catch<TSource>(IAsyncObserver<TSource>` in one and `IAsyncDisposable) Concat<TSource>(IAsyncObserver<TSource>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:266— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:266-280 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:294-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:266` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SequenceEqual.cs:84— Rx.NET/Source/src/System.Reactive/Linq/Observable/SequenceEqual.cs:84-98 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SequenceEqual.cs:158-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/SequenceEqual.cs:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:125— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:125-139 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:253-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:67— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:67-81 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:211-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs:108— Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs:108-123 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs:233-247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs:108` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `TLeft` in one and `TRight` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/Count.cs:82— Rx.NET/Source/src/System.Reactive/Linq/Observable/Count.cs:82-96 | Rx.NET/Source/src/System.Reactive/Linq/Observable/LongCount.cs:82-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) Rx.NET/Samples/HOL/CS/Excercise3/Step06/Program.cs:22— Rx.NET/Samples/HOL/CS/Excercise3/Step06/Program.cs:22-36 | Rx.NET/Samples/HOL/CS/Excercise4/Start/Program.cs:22-36 — before extracting anything, compare `Rx.NET/Samples/HOL/CS/Excercise3/Step06/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise4/Start/Program.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Samples/HOL/CS/Excercise3/Step06/Program.cs:22` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
TooManyMethods: QueryLanguage Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Aggregates.cs— TooManyMethods — 2257 significant lines (blank, comment-only and punctuation-only lines excluded), 719 methods, declared across 16 files: Linq/QueryLanguage.Aggregates.cs (133), Linq/QueryLanguage.Async.cs (122), Linq/QueryLanguage.Time.cs (104), Linq/QueryLanguage.StandardSequenceOperators.cs (67), +12 more file(s). The bar is 30 methods; this is 689 over it, 23.97× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: AsyncObservable AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs— TooManyMethods — 4027 significant lines (blank, comment-only and punctuation-only lines excluded), 452 methods, declared across 101 files: Operators/FromEventPattern.cs (25), Operators/Replay.cs (24), Operators/GroupBy.cs (17), Operators/GroupByUntil.cs (17), +97 more file(s). The bar is 30 methods; this is 422 over it, 15.07× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: AsyncObserver AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs— TooManyMethods — 4688 significant lines (blank, comment-only and punctuation-only lines excluded), 300 methods, declared across 66 files: Operators/GroupBy.cs (16), Operators/GroupByUntil.cs (16), Operators/Generate.cs (12), Operators/Max.cs (12), +62 more file(s). The bar is 30 methods; this is 270 over it, 10.00× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Observable Rx.NET/Source/src/System.Reactive/Linq/Observable.Creation.cs— TooManyMethods — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 78 methods, declared across 3 files: Linq/Observable.Creation.cs (35), Linq/Observable.Events.cs (30), Linq/Observable.Imperative.cs (13). The bar is 30 methods; this is 48 over it, 2.60× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: EnumerableEx Ix.NET/Source/System.Interactive/System/Linq/Operators/Catch.cs— TooManyMethods — 315 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods, declared across 20 files: Operators/Catch.cs (6), Operators/Repeat.cs (6), Operators/OnErrorResumeNext.cs (4), Operators/Scan.cs (4), +16 more file(s). The bar is 30 methods; this is 21 over it, 1.70× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: TestAsyncScheduler AsyncRx.NET/Microsoft.Reactive.Testing.Async/TestAsyncScheduler.cs— TooManyMethods — 269 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods, declared across 3 files: Microsoft.Reactive.Testing.Async/TestAsyncScheduler.cs (23), Microsoft.Reactive.Testing.Async/TestAsyncScheduler.Harness.cs (6), Microsoft.Reactive.Testing.Async/TestAsyncScheduler.Factories.cs (4). The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AsyncEnumerableEx Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/MinByWithTies.cs— TooManyMethods — 297 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods, declared across 10 files: Operators/MinByWithTies.cs (12), Operators/Amb.cs (4), Operators/OnErrorResumeNext.cs (4), Operators/Defer.cs (3), +6 more file(s). The bar is 30 methods; this is 1 over it, 1.03× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Duplicated block (23 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:116— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:116-138 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs:116-138 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:158— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:158-180 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs:158-180 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:200— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:200-222 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs:200-222 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:242— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:242-264 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs:242-264 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:242` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:284— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:284-306 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs:284-306 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:130— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:130-152 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:188-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `innerKeySelector` to `Func<TInner, ValueTask<TKey>>` in one and `Func<TInner, CancellationToken, ValueTask<TKey>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (23 lines × 2) Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:14— Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:14-36 | Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs:14-36 — `Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (16 lines × 2) Ix.NET/Source/FasterLinq/Program.cs:1075— Ix.NET/Source/FasterLinq/Program.cs:1075-1090 | Ix.NET/Source/FasterLinq/Program.cs:1106-1121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/FasterLinq/Program.cs:1075` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:1126— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:1126-1141 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:1201-1216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:1126` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:253— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:253-268 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:612-627 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Last.cs:69— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Last.cs:69-84 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Single.cs:71-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Last.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/While.cs:16— AsyncRx.NET/System.Reactive.Async/Linq/Operators/While.cs:16-31 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/While.cs:69-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/While.cs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/Delay.cs:177— Rx.NET/Source/src/System.Reactive/Linq/Observable/Delay.cs:177-192 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Delay.cs:356-371 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/Delay.cs:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SingleAsync.cs:34— Rx.NET/Source/src/System.Reactive/Linq/Observable/SingleAsync.cs:34-49 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SingleOrDefaultAsync.cs:34-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:11— Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:11-17 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs:10-16 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs:93— Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs:93-99 | Rx.NET/Source/src/System.Reactive/Linq/QbservableEx.cs:22-28 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs` and `Rx.NET/Source/src/System.Reactive/Linq/QbservableEx.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs:103— Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs:103-109 | Rx.NET/Source/src/System.Reactive/Linq/QbservableEx.cs:32-38 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs` and `Rx.NET/Source/src/System.Reactive/Linq/QbservableEx.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs:93— Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs:93-99 | Rx.NET/Source/src/System.Reactive/Linq/QbservableEx.cs:22-28 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs` and `Rx.NET/Source/src/System.Reactive/Linq/QbservableEx.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs:103— Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs:103-109 | Rx.NET/Source/src/System.Reactive/Linq/QbservableEx.cs:32-38 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Qbservable.cs` and `Rx.NET/Source/src/System.Reactive/Linq/QbservableEx.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) Ix.NET/Source/System.Interactive.Async.Providers/System/Linq/AsyncQueryableEx.cs:18— Ix.NET/Source/System.Interactive.Async.Providers/System/Linq/AsyncQueryableEx.cs:18-24 | Ix.NET/Source/System.Linq.Async.Queryable/System/Linq/AsyncQueryable.cs:39-45 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async.Providers/System/Linq/AsyncQueryableEx.cs` and `Ix.NET/Source/System.Linq.Async.Queryable/System/Linq/AsyncQueryable.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:224— AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:224-230 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLastBuffer.cs:124-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:220` calls `SingleAssignmentAsyncDisposable` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLastBuffer.cs:120` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Swallowed exception (empty catch) Rx.NET/Source/src/System.Reactive/Concurrency/CatchScheduler.cs:89— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Rx.NET/Source/src/System.Reactive/Linq/Observable/ResetExceptionDispatchState.cs:44— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/OnErrorResumeNext.cs:130— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsyncRx.NET/Microsoft.Reactive.Testing.Async/ColdAsyncObservable.cs:67— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) AsyncRx.NET/Microsoft.Reactive.Testing.Async/HotAsyncObservable.cs:53— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Rx.NET/Samples/Portable/SilverlightApplication/App.xaml.cs:63— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Rx.NET/tools/HomoIcon/Program.cs:113— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
BareSuppressMessage Rx.NET/Source/src/Microsoft.Reactive.Testing/GlobalSuppressions.cs:16— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage Rx.NET/Source/src/Microsoft.Reactive.Testing/GlobalSuppressions.cs:17— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage Rx.NET/Source/src/Microsoft.Reactive.Testing/GlobalSuppressions.cs:18— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage Rx.NET/Source/src/Microsoft.Reactive.Testing/GlobalSuppressions.cs:19— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage Rx.NET/Source/src/Microsoft.Reactive.Testing/GlobalSuppressions.cs:20— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage Rx.NET/Source/src/System.Reactive/GlobalSuppressions.cs:39— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
Duplicated block (24 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:174— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:174-197 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:177-200 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:68— AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:68-91 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Where.cs:68-91 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Where.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:104— AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:104-127 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Where.cs:100-123 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Where.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Concat.cs:102— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Concat.cs:102-125 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/OnErrorResumeNext.cs:103-126 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (24 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:80— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:80-103 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:291-314 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:80` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Take.cs:128— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Take.cs:128-151 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeUntil.cs:148-171 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:244— Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:244-256 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs:238-250 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:244` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:225— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:225-237 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:584-596 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:240— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:240-252 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:428-440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:240` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:86— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:86-98 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:230-242 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) Rx.NET/Source/src/System.Reactive/Disposables/Disposable.Utils.cs:74— Rx.NET/Source/src/System.Reactive/Disposables/Disposable.Utils.cs:74-92 | Rx.NET/Source/src/System.Reactive/Disposables/Disposable.Utils.cs:108-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Disposables/Disposable.Utils.cs:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Disposables/Disposable.Utils.cs:121` calls `Dispose` and `Rx.NET/Source/src/System.Reactive/Disposables/Disposable.Utils.cs:93` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/WindowsRuntimeThreadPoolScheduler.cs:106— Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/WindowsRuntimeThreadPoolScheduler.cs:106-118 | Rx.NET/Source/src/System.Reactive/Concurrency/TaskPoolScheduler.cs:227-240 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (26 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1012— Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1012-1037 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1248-1273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:116— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:116-141 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:180-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (26 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:140— AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:140-165 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Where.cs:132-157 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Where.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:178— AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:178-203 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Where.cs:166-191 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Where.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeWhile.cs:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) AsyncRx.NET/System.Reactive.Async/Threading/Tasks/TaskAsyncObservableExtensions.cs:63— AsyncRx.NET/System.Reactive.Async/Threading/Tasks/TaskAsyncObservableExtensions.cs:63-88 | AsyncRx.NET/System.Reactive.Async/Threading/Tasks/TaskAsyncObservableExtensions.cs:127-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:132— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:132-152 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:187-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:139— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:139-159 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:142-162 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Single.cs:54— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Single.cs:54-74 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SingleOrDefault.cs:54-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Single.cs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:105— AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:105-125 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeUntil.cs:101-121 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) Ix.NET/Source/System.Interactive.Providers/System/Linq/QueryableEx.cs:130— Ix.NET/Source/System.Interactive.Providers/System/Linq/QueryableEx.cs:130-150 | Rx.NET/Source/src/System.Reactive/ObservableQuery.cs:468-488 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Interactive.Providers/System/Linq/QueryableEx.cs:130` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) Rx.NET/Source/src/System.Reactive/Threading/Tasks/TaskObservableExtensions.cs:46— Rx.NET/Source/src/System.Reactive/Threading/Tasks/TaskObservableExtensions.cs:46-63 | Rx.NET/Source/src/System.Reactive/Threading/Tasks/TaskObservableExtensions.cs:93-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Threading/Tasks/TaskObservableExtensions.cs:46` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `observer` to `IObserver<Unit>` in one and `IObserver<TResult>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:265— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:265-282 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:267-284 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:265` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:677— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:677-694 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:703-720 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:677` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:70— Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:70-87 | Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs:62-79 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs` and `Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs:55` calls `ThrowDisposed`, `ObjectDisposedException` and `Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:57` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:272— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:272-289 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:631-648 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:226— Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:226-242 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs:220-236 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/Join.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/GroupJoin.cs:226` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:335— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:335-351 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:606-622 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:335` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:602— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:602-618 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:629-645 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:602` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:141— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:141-157 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:285-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs:74— Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs:74-90 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Min.cs:79-95 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/Min.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) Ix.NET/Source/FasterLinq/Program.cs:82— Ix.NET/Source/FasterLinq/Program.cs:82-92 | Ix.NET/Source/FasterLinq/Program.cs:132-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:70— Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:70-80 | Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:186-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:70` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:184` calls `Trim` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs:68` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:28— AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:28-38 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeUntil.cs:28-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:28` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) AsyncRx.NET/System.Reactive.Async/AsyncObserver.cs:16— AsyncRx.NET/System.Reactive.Async/AsyncObserver.cs:16-26 | AsyncRx.NET/System.Reactive.Async/Internal/UnsafeAsyncObserver.cs:16-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) Ix.NET/Source/System.Interactive/System/Linq/Operators/Memoize.cs:158— Ix.NET/Source/System.Interactive/System/Linq/Operators/Memoize.cs:158-168 | Ix.NET/Source/System.Interactive/System/Linq/Operators/Publish.cs:107-117 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
X18 · Disposal-pattern correctness· Disposes a dependency it does not own · ×5
Disposes a dependency it does not own Rx.NET/Source/src/System.Reactive/Subjects/ConnectableObservable.cs:69— `_subscription` is never created by `Connection` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 69). Its declared type `IDisposable` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own Ix.NET/Source/System.Interactive/System/Linq/Operators/Memoize.cs:162— `_source` is never created by `MemoizedBuffer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 162). Its declared type `IEnumerator` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own Ix.NET/Source/System.Interactive/System/Linq/Operators/Publish.cs:111— `_source` is never created by `PublishedBuffer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 111). Its declared type `IEnumerator` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own Ix.NET/Source/System.Interactive/System/Linq/Operators/Share.cs:86— `_source` is never created by `SharedBuffer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 86). Its declared type `IEnumerator` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerator.WithCancellation.cs:44— `_source` is never created by `WithCancellationAsyncEnumerator` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 44). Its declared type `IAsyncEnumerator` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Duplicated block (36 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1542— Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1542-1577 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1677-1712 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36 lines × 2) Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:189— Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:189-224 | Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs:179-214 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36 lines × 2) Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:238— Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:238-273 | Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs:228-263 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToObservable.cs:39— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToObservable.cs:39-74 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToObservable.cs:45-80 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToObservable.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToObservable.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:153— Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:153-160 | Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs:143-150 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:153` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Recursive.cs:234— Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Recursive.cs:234-241 | Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Recursive.cs:262-269 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:184— AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:184-191 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:223-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:193` calls `default` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:232` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Retry.cs:58— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Retry.cs:58-65 | Ix.NET/Source/System.Interactive/System/Linq/Operators/Repeat.cs:84-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 4) Rx.NET/Source/src/System.Reactive.WindowsRuntime/StableUncheckedCompositeDisposable.cs:54— Rx.NET/Source/src/System.Reactive.WindowsRuntime/StableUncheckedCompositeDisposable.cs:54-62 | Rx.NET/Source/src/System.Reactive/Disposables/StableCompositeDisposable.cs:133-141 | Rx.NET/Source/src/System.Reactive/Disposables/StableCompositeDisposable.cs:167-175 | Rx.NET/Source/src/System.Reactive/Disposables/StableCompositeDisposable.cs:195-203 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Rx.NET/Source/src/System.Reactive/Disposables/StableCompositeDisposable.cs:163` calls `Read` and `Rx.NET/Source/src/System.Reactive.WindowsRuntime/StableUncheckedCompositeDisposable.cs:50` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:408— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:408-416 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:498-506 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:681-689 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:773-781 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:408— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:408-416 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:498-506 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:681-689 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:773-781 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 4) Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:28— Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:28-36 | Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs:28-36 | Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:32-41 | Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:34-43 — `Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:28` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:32` calls `ToObservable` and `Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:28` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:463— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:463-468 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:553-558 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1272-1277 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1360-1365 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:736— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:736-741 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:828-833 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1007-1012 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1097-1102 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:463— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:463-468 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:553-558 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1272-1277 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1360-1365 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:736— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:736-741 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:828-833 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1007-1012 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1097-1102 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×4
Owned disposable field is never released Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:59— `ScheduledObserver` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_dispatcherEvent` itself (line 59), which makes that instance its own. But `_dispatcherEvent` is named in none of the methods the disposal search covered: `Dispose` (line 314) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_dispatcherEvent?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:60— `ScheduledObserver` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_dispatcherEventRelease` itself (line 60), which makes that instance its own. But `_dispatcherEventRelease` is named in none of the methods the disposal search covered: `Dispose` (line 314) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_dispatcherEventRelease?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released Rx.NET/Source/src/System.Reactive/Linq/Observable/Buffer.cs:653— `_` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_bufferGate` itself (line 653), which makes that instance its own. But `_bufferGate` is named in none of the methods the disposal search covered: `Dispose` (line 672) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_bufferGate?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released Rx.NET/Source/src/System.Reactive/Linq/Observable/Delay.cs:265— `L` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_evt` itself (line 265), which makes that instance its own. But `_evt` is named in none of the methods the disposal search covered: `Dispose` (line 281) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_evt?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
MethodTooLong: Program.Generate Rx.NET/tools/HomoIcon/Program.cs:148— MethodTooLong — Generate runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Program.GenerateAsync Rx.NET/tools/HomoIcon/Program.cs:539— MethodTooLong — GenerateAsync runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AsyncObserver.GroupByUntil AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:571— MethodTooLong — GroupByUntil runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (32 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/MaxBy.cs:43— Rx.NET/Source/src/System.Reactive/Linq/Observable/MaxBy.cs:43-74 | Rx.NET/Source/src/System.Reactive/Linq/Observable/MinBy.cs:43-74 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Observable/MaxBy.cs` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/MinBy.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (32 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/Buffer.cs:319— Rx.NET/Source/src/System.Reactive/Linq/Observable/Buffer.cs:319-350 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Window.cs:181-212 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/Buffer.cs:319` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (32 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:65— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:65-96 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs:65-96 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Max.cs:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SingleAsync.cs:102— Rx.NET/Source/src/System.Reactive/Linq/Observable/SingleAsync.cs:102-132 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SingleOrDefaultAsync.cs:88-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (31 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/Zip.cs:105— Rx.NET/Source/src/System.Reactive/Linq/Observable/Zip.cs:105-135 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Zip.cs:188-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `TFirst` in one and `TSecond` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (31 lines × 2) Rx.NET/Samples/Portable/Net40ConsoleApp_NuGet/Program.cs:14— Rx.NET/Samples/Portable/Net40ConsoleApp_NuGet/Program.cs:14-44 | Rx.NET/Samples/Portable/Net40ConsoleApplication/Program.cs:14-44 — `Rx.NET/Samples/Portable/Net40ConsoleApp_NuGet/Program.cs` and `Rx.NET/Samples/Portable/Net40ConsoleApplication/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 31 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (30 lines × 2) Ix.NET/Source/FasterLinq/Program.cs:98— Ix.NET/Source/FasterLinq/Program.cs:98-127 | Ix.NET/Source/FasterLinq/Program.cs:148-177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/FasterLinq/Program.cs:98` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:70— Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:70-99 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:115-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:145` calls `recurse` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:100` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (30 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:148— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:148-177 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Lookup.cs:461-490 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (25 lines × 2) Ix.NET/Source/Playground/Program.cs:82— Ix.NET/Source/Playground/Program.cs:82-106 | Ix.NET/Source/Playground/Program.cs:112-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/Playground/Program.cs:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:15— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:15-39 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:109-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:62— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:62-86 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:164-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:38— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:38-57 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:85-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Using.cs:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) Rx.NET/tools/HomoIcon/Program.cs:641— Rx.NET/tools/HomoIcon/Program.cs:641-660 | Rx.NET/tools/HomoIcon/Program.cs:768-787 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/tools/HomoIcon/Program.cs:641` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Rx.NET/tools/HomoIcon/Program.cs:638` calls `WriteLine` and `Rx.NET/tools/HomoIcon/Program.cs:766` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:132— AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:132-151 | AsyncRx.NET/System.Reactive.Async/Subjects/BehaviorAsyncSubject.cs:150-169 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Subjects/AsyncAsyncSubject.cs:132` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:133— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:133-149 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:90-106 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:157-173 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:126` calls `CoreAsync` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:88` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 3) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:879— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:879-895 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:968-984 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1058-1074 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:879` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 3) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1146— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1146-1162 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1233-1249 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1321-1337 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1146` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:199— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:199-213 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Concat.cs:104-118 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/OnErrorResumeNext.cs:105-119 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `observer` to `IAsyncDisposable) Catch<TSource>(IAsyncObserver<TSource>` in one and `IAsyncDisposable) Concat<TSource>(IAsyncObserver<TSource>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 3) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1060— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1060-1074 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1191-1205 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1329-1343 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 3) Ix.NET/Source/ApiCompare/Program.cs:77— Ix.NET/Source/ApiCompare/Program.cs:77-91 | Ix.NET/Source/ApiCompare/Program.cs:116-130 | Ix.NET/Source/ApiCompare/Program.cs:182-196 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:91— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:91-101 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:108-118 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:219-229 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:236-246 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 4) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:33— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:33-43 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:50-60 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:177-187 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:194-204 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:240— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:240-250 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:301-311 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:363-373 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:428-438 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:240` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 11) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:305— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:305-312 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:378-385 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:459-466 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:548-556 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:645-653 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:749-757 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:861-869 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:980-988 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1106-1114 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1240-1248 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1381-1389 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:305` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:386` calls `Peek` and `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:314` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 11) Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerablePartition.cs:56— Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerablePartition.cs:56-63 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/AppendPrepend.cs:105-112 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Concat.cs:139-146 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/DefaultIfEmpty.cs:65-72 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:211-218 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:382-389 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:441-448 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:219-226 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:285-292 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:347-354 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:412-419 — there are 11 copies across 6 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 11 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 11) Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:25— Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:25-32 | Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:25-32 | Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs:26-33 | Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:26-33 | Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:26-33 | Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:27-34 | Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:28-36 | Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs:28-36 | Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:32-41 | Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:34-43 | Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:45-54 — `Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:35` calls `matchInWordNetByPrefix` and `Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:34` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
AsyncObserver.Generate (cognitive 18) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Generate.cs:347— AsyncObserver.Generate has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 362). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This shape REPEATS in the file: one other method here (AsyncObserver.Generate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncObserver.Generate (cognitive 18) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Generate.cs:469— AsyncObserver.Generate has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 484). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This shape REPEATS in the file: one other method here (AsyncObserver.Generate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Duplicated block (37 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:224— Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:224-260 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:333-369 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/Generate.cs:224` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (37 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:288— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:288-324 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Prepend.cs:258-294 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:288` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (33 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:90— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:90-122 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:87-119 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (33 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:431— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:431-463 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:400-432 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (28 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Aggregate.cs:98— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Aggregate.cs:98-125 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Scan.cs:68-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Aggregate.cs:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Scan.cs:97` calls `OnNextAsync`, `ConfigureAwait` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Aggregate.cs:126` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (28 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Aggregate.cs:145— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Aggregate.cs:145-172 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Scan.cs:106-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Aggregate.cs:145` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Scan.cs:135` calls `OnNextAsync`, `ConfigureAwait` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Aggregate.cs:173` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:23— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:23-34 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:44-55 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:64-75 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Catch.cs:23` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:560— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:560-571 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:148-159 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:172-183 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:560` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:572` calls `OnNextAsync`, `ConfigureAwait` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:160` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:230— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:230-241 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:312-323 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:232-243 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:314-325 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 4) AsyncRx.NET/System.Reactive.Async/Threading/Tasks/TaskAwaitable.cs:51— AsyncRx.NET/System.Reactive.Async/Threading/Tasks/TaskAwaitable.cs:51-62 | AsyncRx.NET/System.Reactive.Async/Threading/Tasks/TaskAwaitable.cs:107-118 | AsyncRx.NET/System.Reactive.Async/Threading/Tasks/ValueTaskAwaitable.cs:51-62 | AsyncRx.NET/System.Reactive.Async/Threading/Tasks/ValueTaskAwaitable.cs:107-118 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 4) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:103— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:103-115 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:122-134 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:247-259 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:266-278 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 4) Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:172— Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:172-185 | Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/WindowsRuntimeThreadPoolScheduler.cs:106-118 | Rx.NET/Source/src/System.Reactive/Concurrency/TaskPoolScheduler.cs:227-240 | Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs:162-175 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:213— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:213-226 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:126-139 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:214-227 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:213` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 3) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:456— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:456-469 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:592-605 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:731-744 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Max.cs:31— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Max.cs:31-44 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Min.cs:31-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Max.cs:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:59— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:59-72 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:187-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 3) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:82— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:82-92 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:210-220 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:251-261 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SkipWhile.cs:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Scan.cs:37— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Scan.cs:37-47 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Scan.cs:108-118 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Scan.cs:147-157 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Scan.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/DistinctUntilChanged.cs:208— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/DistinctUntilChanged.cs:208-215 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/DistinctUntilChanged.cs:247-254 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/DistinctUntilChanged.cs:287-294 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Expand.cs:31— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Expand.cs:31-38 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Expand.cs:65-72 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Expand.cs:100-107 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Expand.cs:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 9) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:470— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:470-477 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:561-568 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:659-666 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:764-771 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:877-884 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:997-1004 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1124-1131 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1259-1266 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1401-1408 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:470` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 9) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:417— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:417-424 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:502-509 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:595-602 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:695-702 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:802-809 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:917-924 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1039-1046 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1168-1175 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1305-1312 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 10) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:388— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:388-393 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:470-475 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:561-566 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:659-664 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:764-769 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:877-882 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:997-1002 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1124-1129 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1259-1264 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1401-1406 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:388` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 10) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1077— Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1077-1082 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1106-1111 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1135-1140 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1164-1169 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1193-1198 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1222-1227 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1251-1256 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1280-1285 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1309-1314 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1338-1343 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1077` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:40— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:40-44 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:76-80 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:114-118 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:140-144 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Zip.cs:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:112— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:112-116 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:154-158 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:130-134 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:188-192 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupJoin.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `innerKeySelector` to `Func<TInner, ValueTask<TKey>>` in one and `Func<TInner, CancellationToken, ValueTask<TKey>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:576— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:576-581 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:667-672 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:759-764 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `elementSelector` to `Func<TSource, TElement>` in one and `Func<TSource, ValueTask<TElement>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) Rx.NET/Samples/HOL/CS/Excercise7/Step05/Program.cs:13— Rx.NET/Samples/HOL/CS/Excercise7/Step05/Program.cs:13-18 | Rx.NET/Samples/HOL/CS/Excercise7/Step06/Program.cs:13-18 | Rx.NET/Samples/HOL/CS/Excercise7/Step07/Program.cs:13-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (6 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:184— AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:184-189 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:250-255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:248` calls `Trim` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs:183` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) Rx.NET/Samples/Portable/PortableClassLibrary/PortableClass.cs:21— Rx.NET/Samples/Portable/PortableClassLibrary/PortableClass.cs:21-26 | Rx.NET/Samples/Portable/PortableClassLibrary_NuGet/PortableClass.cs:21-26 — `Rx.NET/Samples/Portable/PortableClassLibrary/PortableClass.cs` and `Rx.NET/Samples/Portable/PortableClassLibrary_NuGet/PortableClass.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 6 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 5) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Distinct.cs:230— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Distinct.cs:230-238 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Distinct.cs:375-383 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Distinct.cs:521-529 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Distinct.cs:98-106 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Union.cs:73-81 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 5) Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:28— Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:28-36 | Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs:29-37 | Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:29-37 | Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:29-37 | Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:30-38 — `Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 65 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 8) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:319— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:319-327 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:590-598 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:863-871 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:952-960 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1042-1050 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1130-1138 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1217-1225 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1305-1313 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 8) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:319— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:319-327 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:590-598 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:863-871 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:952-960 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1042-1050 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1130-1138 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1217-1225 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1305-1313 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
End-of-life runtime: .NET net9.0 Rx.NET/Test/Gauntlet/RxGauntlet/RxGauntlet.csproj:5— Rx.NET/Test/Gauntlet/RxGauntlet/RxGauntlet.csproj declares .NET net9.0 as this project's target framework, and .NET 9 STS, support ended 2026-05-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-05-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET netcoreapp3.1 AsyncRx.NET/ApiCompare/ApiCompare.csproj:5— AsyncRx.NET/ApiCompare/ApiCompare.csproj declares .NET netcoreapp3.1 as this project's target framework, and .NET Core 3.1 LTS, support ended 2022-12-13. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-12-13 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Unfinished stub — throws NotImplementedException Rx.NET/Samples/RxRemoteMouseMoves/RxMouseServer/MouseService.cs:47— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Rx.NET/Samples/RxRemoteMouseMoves/RxMouseServer/MouseService.cs:52— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Blocking `Thread.Sleep` inside an `async` method Rx.NET/Samples/EventCorrelationSample/EventCorrelationSample/Program.cs:123— `Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method.
Blocking `Thread.Sleep` inside an `async` method Rx.NET/Samples/EventCorrelationSample/EventCorrelationSample/Program.cs:172— `Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method.
Program.Generate (cyclomatic 73) Rx.NET/tools/HomoIcon/Program.cs:148— Program.Generate has cyclomatic complexity 73 (threshold 15). Of this number, 69 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Rx.NET/tools/HomoIcon/Program.cs holds 3 of the 33 methods over the threshold — including the worst — and 105 of the 253 points over it (42%), 2.9× the next-largest file (/root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/EqualityAsserts.cs at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Program.GenerateAsync (cyclomatic 43) Rx.NET/tools/HomoIcon/Program.cs:539— Program.GenerateAsync has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Rx.NET/tools/HomoIcon/Program.cs holds 3 of the 33 methods over the threshold — including the worst — and 105 of the 253 points over it (42%), 2.9× the next-largest file (/root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/EqualityAsserts.cs at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Program.ToString2 (cyclomatic 34) Rx.NET/tools/HomoIcon/Program.cs:831— Program.ToString2 has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Rx.NET/tools/HomoIcon/Program.cs holds 3 of the 33 methods over the threshold — including the worst — and 105 of the 253 points over it (42%), 2.9× the next-largest file (/root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/EqualityAsserts.cs at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
AsyncObserver.GroupByUntil (cyclomatic 25) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:571— AsyncObserver.GroupByUntil has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 646, 777). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
UiFrameworkSpecificTypes.Check (cyclomatic 24) Rx.NET/Source/src/System.Reactive.Analyzers/Analyzers/UiFrameworkPackages/UiFrameworkSpecificTypes.cs:93— UiFrameworkSpecificTypes.Check has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AsyncObserver.Join (cyclomatic 24) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:49— AsyncObserver.Join has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 85, 173, 116, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TailRecursiveSink.Drain (cyclomatic 19) Rx.NET/Source/src/System.Reactive/Internal/TailRecursiveSink.cs:47— TailRecursiveSink.Drain has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AsyncEnumerableRewriter.ArgsMatch (cyclomatic 19) Ix.NET/Source/System.Linq.Async.Queryable/System/Linq/AsyncEnumerableRewriter.cs:147— AsyncEnumerableRewriter.ArgsMatch has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AsyncObserver.GroupBy (cyclomatic 19) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:507— AsyncObserver.GroupBy has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Observable.CombineLatest (cyclomatic 18) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.CombineLatest.cs:1104— Observable.CombineLatest has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Observable.Zip (cyclomatic 18) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.Zip.cs:1090— Observable.Zip has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Observable.CombineLatest (cyclomatic 17) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.CombineLatest.cs:979— Observable.CombineLatest has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ObservableEx.CombineLatest) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ObservableEx.CombineLatest (cyclomatic 17) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.CombineLatest.cs:1867— ObservableEx.CombineLatest has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Observable.CombineLatest) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Observable.Zip (cyclomatic 17) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.Zip.cs:966— Observable.Zip has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ObservableEx.Zip) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ObservableEx.Zip (cyclomatic 17) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.Zip.cs:1853— ObservableEx.Zip has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Observable.Zip) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DeprecatedDuplicateBuilder.BuildDuplicatesIfRequired (cyclomatic 17) Ix.NET/Source/System.Linq.Async.SourceGenerator/DeprecatedDuplicateBuilder.cs:84— DeprecatedDuplicateBuilder.BuildDuplicatesIfRequired has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AsyncObserver.Buffer (cyclomatic 17) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:366— AsyncObserver.Buffer has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AsyncObserver.SequenceEqual (cyclomatic 17) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SequenceEqual.cs:80— AsyncObserver.SequenceEqual has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 97, 163, 140, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AsyncObserver.Window (cyclomatic 17) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:372— AsyncObserver.Window has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EventLoopScheduler.Run (cyclomatic 16) Rx.NET/Source/src/System.Reactive/Concurrency/EventLoopScheduler.cs:289— EventLoopScheduler.Run has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Observable.CombineLatest (cyclomatic 16) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.CombineLatest.cs:861— Observable.CombineLatest has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ObservableEx.CombineLatest) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ObservableEx.CombineLatest (cyclomatic 16) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.CombineLatest.cs:1794— ObservableEx.CombineLatest has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Observable.CombineLatest) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Observable.Zip (cyclomatic 16) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.Zip.cs:849— Observable.Zip has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ObservableEx.Zip) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ObservableEx.Zip (cyclomatic 16) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.Zip.cs:1780— ObservableEx.Zip has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Observable.Zip) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncObserver.Amb (cyclomatic 16) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Amb.cs:77— AsyncObserver.Amb has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 93, 109, 125, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CoverageExclusion Ix.NET/Source/System.Linq.Async/System/Linq/Set.cs:13— class Set — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
HackComment Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.cs:18— // HACK: Causes race condition with Locks in DefaultScheduler's static ctor chain — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
Build failed — The target solution did not build cleanly (errors: 121), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS8630: Invalid 'nullable' value: 'Enable' for C# 7.3. Please use language version '8.0' or greater.; CS9202: Feature 'unbound generic types in nameof operator' is not available in C# 12.0. Please use language version 14.0 or greater.; MSB3644: The reference assemblies for UAP,Version=v10.0.18362 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks; CS0234: The type or namespace name 'Reactive' does not exist in the namespace 'System' (are you missing an assembly reference?); CS0246: The type or namespace name 'Timestamped<>' could not be found (are you missing a using directive or an assembly reference?); MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.0/Microsoft.Portable.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.0/Microsoft.Portable.CSharp.targets", is correct, and that the file exists on disk.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Silverlight/v4.0/Microsoft.Silverlight.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Silverlight/$(SilverlightVersion)/Microsoft.Silverlight.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Silverlight/v4.0/Microsoft.Silverlight.CSharp.targets", is correct, and that the file exists on disk.; MSB3073: The command "mono --runtime=v4.0.30319 Rx.NET/Samples/Portable/.nuget/NuGet.exe install "packages.config" -source "" -RequireConsent -solutionDir "Rx.NET/Samples/Portable/"" exited with code 127.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets", is correct, and that the file exists on disk.; CS0246: The type or namespace name 'CommonCodeInPcl' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Subject<>' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'Kinect' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?).
Program.Generate (cognitive 141) Rx.NET/tools/HomoIcon/Program.cs:148— Program.Generate has cognitive complexity 141 (threshold 15). Of this number, 136 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.GenerateAsync (cognitive 112) Rx.NET/tools/HomoIcon/Program.cs:539— Program.GenerateAsync has cognitive complexity 112 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TailRecursiveSink.Drain (cognitive 69) Rx.NET/Source/src/System.Reactive/Internal/TailRecursiveSink.cs:47— TailRecursiveSink.Drain has cognitive complexity 69 (threshold 15). Of this number, 66 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Program.ToString2 (cognitive 62) Rx.NET/tools/HomoIcon/Program.cs:831— Program.ToString2 has cognitive complexity 62 (threshold 15). Of this number, 58 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UiFrameworkSpecificTypes.Check (cognitive 43) Rx.NET/Source/src/System.Reactive.Analyzers/Analyzers/UiFrameworkPackages/UiFrameworkSpecificTypes.cs:93— UiFrameworkSpecificTypes.Check has cognitive complexity 43 (threshold 15). Of this number, 41 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UiFrameworkSpecificExtensionMethods.ReportDiagnosticIfAppropriate (cognitive 42) Rx.NET/Source/src/System.Reactive.Analyzers/Analyzers/UiFrameworkPackages/UiFrameworkSpecificExtensionMethods.cs:154— UiFrameworkSpecificExtensionMethods.ReportDiagnosticIfAppropriate has cognitive complexity 42 (threshold 15). Of this number, 30 points are the body's own statements and 12 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeprecatedDuplicateBuilder.BuildDuplicatesIfRequired (cognitive 41) Ix.NET/Source/System.Linq.Async.SourceGenerator/DeprecatedDuplicateBuilder.cs:84— DeprecatedDuplicateBuilder.BuildDuplicatesIfRequired has cognitive complexity 41 (threshold 15). Of this number, 40 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncObserver.GroupByUntil (cognitive 38) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:571— AsyncObserver.GroupByUntil has cognitive complexity 38 (threshold 15). Most of this is not in the body itself: 11 of the 38 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 646, 777). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EventLoopScheduler.Run (cognitive 35) Rx.NET/Source/src/System.Reactive/Concurrency/EventLoopScheduler.cs:289— EventLoopScheduler.Run has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConcatManyOuterObserver.Drain (cognitive 35) Rx.NET/Source/src/System.Reactive/Linq/Observable/ConcatMany.cs:123— ConcatManyOuterObserver.Drain has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
QueryProviderShim.Redir (cognitive 32) Ix.NET/Source/System.Interactive.Providers/System/Linq/QueryableEx.cs:48— QueryProviderShim.Redir has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MemoizedBuffer.GetEnumerator_ (cognitive 31) Ix.NET/Source/System.Interactive/System/Linq/Operators/Memoize.cs:170— MemoizedBuffer.GetEnumerator_ has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PublishedBuffer.GetEnumeratorCore (cognitive 31) Ix.NET/Source/System.Interactive/System/Linq/Operators/Publish.cs:119— PublishedBuffer.GetEnumeratorCore has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
S.DrainQueue (cognitive 30) Rx.NET/Source/src/System.Reactive/Linq/Observable/Delay.cs:152— S.DrainQueue has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
L.DrainQueue (cognitive 30) Rx.NET/Source/src/System.Reactive/Linq/Observable/Delay.cs:342— L.DrainQueue has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FastImmediateObserver.EnsureActive (cognitive 30) Rx.NET/Source/src/System.Reactive/Subjects/ReplaySubject.cs:774— FastImmediateObserver.EnsureActive has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ObserveOnObserverLongRunning.Drain (cognitive 29) Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:696— ObserveOnObserverLongRunning.Drain has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncEnumerableSorterBase.PartialQuickSort (cognitive 29) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:627— AsyncEnumerableSorterBase.PartialQuickSort has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncEnumerableSorterBase.QuickSelect (cognitive 29) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:692— AsyncEnumerableSorterBase.QuickSelect has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncObserver.Join (cognitive 27) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:49— AsyncObserver.Join has cognitive complexity 27 (threshold 15). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 85, 173, 116, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AsyncEnumerableRewriter.ArgsMatch (cognitive 25) Ix.NET/Source/System.Linq.Async.Queryable/System/Linq/AsyncEnumerableRewriter.cs:147— AsyncEnumerableRewriter.ArgsMatch has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryLanguageEx.ForkJoin (cognitive 24) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguageEx.cs:237— QueryLanguageEx.ForkJoin has cognitive complexity 24 (threshold 15). None of this is in the body itself: all 24 points belong to 2 function literals inside it that branch (lines 249, 292). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AsyncSubject.OnCompleted (cognitive 24) Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:68— AsyncSubject.OnCompleted has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncEnumerableHelpers.ToArrayWithLength (cognitive 24) Ix.NET/Source/System.Linq.Async/System/Linq/AsyncEnumerableHelpers.cs:21— AsyncEnumerableHelpers.ToArrayWithLength has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AsyncObserver.SequenceEqual (cognitive 24) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SequenceEqual.cs:80— AsyncObserver.SequenceEqual has cognitive complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 97, 163, 140, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Program.RunDemos (cognitive 23) Ix.NET/Source/Playground/Program.cs:176— Program.RunDemos has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AsyncObserver.GroupBy (cognitive 23) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:507— AsyncObserver.GroupBy has cognitive complexity 23 (threshold 15). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 556, 622). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AsyncEnumerable.MaxAsync (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:125— AsyncEnumerable.MaxAsync has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerableDeprecated.MaxAsync, AsyncEnumerable.MaxAwaitAsyncCore, AsyncEnumerableDeprecated.MaxAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerable.MaxAwaitAsyncCore (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:215— AsyncEnumerable.MaxAwaitAsyncCore has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MaxAsync, AsyncEnumerableDeprecated.MaxAsync, AsyncEnumerableDeprecated.MaxAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerable.MaxAwaitWithCancellationAsyncCore (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:297— AsyncEnumerable.MaxAwaitWithCancellationAsyncCore has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MaxAsync, AsyncEnumerableDeprecated.MaxAsync, AsyncEnumerable.MaxAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerable.MinAsync (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:126— AsyncEnumerable.MinAsync has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerableDeprecated.MinAsync, AsyncEnumerable.MinAwaitAsyncCore, AsyncEnumerableDeprecated.MinAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerable.MinAwaitAsyncCore (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:217— AsyncEnumerable.MinAwaitAsyncCore has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MinAsync, AsyncEnumerableDeprecated.MinAsync, AsyncEnumerableDeprecated.MinAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerable.MinAwaitWithCancellationAsyncCore (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:299— AsyncEnumerable.MinAwaitWithCancellationAsyncCore has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MinAsync, AsyncEnumerableDeprecated.MinAsync, AsyncEnumerable.MinAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerableDeprecated.MaxAsync (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:125— AsyncEnumerableDeprecated.MaxAsync has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MaxAsync, AsyncEnumerable.MaxAwaitAsyncCore, AsyncEnumerableDeprecated.MaxAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerableDeprecated.MaxAwaitAsyncCore (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:215— AsyncEnumerableDeprecated.MaxAwaitAsyncCore has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MaxAsync, AsyncEnumerableDeprecated.MaxAsync, AsyncEnumerable.MaxAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerableDeprecated.MaxAwaitWithCancellationAsyncCore (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:297— AsyncEnumerableDeprecated.MaxAwaitWithCancellationAsyncCore has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MaxAsync, AsyncEnumerableDeprecated.MaxAsync, AsyncEnumerable.MaxAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerableDeprecated.MinAsync (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:126— AsyncEnumerableDeprecated.MinAsync has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MinAsync, AsyncEnumerable.MinAwaitAsyncCore, AsyncEnumerableDeprecated.MinAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerableDeprecated.MinAwaitAsyncCore (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:217— AsyncEnumerableDeprecated.MinAwaitAsyncCore has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MinAsync, AsyncEnumerableDeprecated.MinAsync, AsyncEnumerable.MinAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerableDeprecated.MinAwaitWithCancellationAsyncCore (cognitive 22) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:299— AsyncEnumerableDeprecated.MinAwaitWithCancellationAsyncCore has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 5 other methods here (AsyncEnumerable.MinAsync, AsyncEnumerableDeprecated.MinAsync, AsyncEnumerable.MinAwaitAsyncCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncObserver.Buffer (cognitive 22) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:366— AsyncObserver.Buffer has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 465, 405, 388). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CompositeDisposable.Remove (cognitive 21) Rx.NET/Source/src/System.Reactive/Disposables/CompositeDisposable.cs:221— CompositeDisposable.Remove has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncEnumerable.MaxAsync (cognitive 21) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:36— AsyncEnumerable.MaxAsync has cognitive complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
AsyncEnumerable.MinAsync (cognitive 21) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:36— AsyncEnumerable.MinAsync has cognitive complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ScheduledAsyncObserverBase.RunAsync (cognitive 21) AsyncRx.NET/System.Reactive.Async/Internal/ScheduledAsyncObserverBase.cs:51— ScheduledAsyncObserverBase.RunAsync has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncEnumerable.Join (cognitive 20) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:53— AsyncEnumerable.Join has cognitive complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 4 other methods here (AsyncEnumerable.JoinAwaitCore, AsyncEnumerableDeprecated.JoinAwaitCore, AsyncEnumerable.JoinAwaitWithCancellationCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerable.JoinAwaitCore (cognitive 20) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:111— AsyncEnumerable.JoinAwaitCore has cognitive complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 4 other methods here (AsyncEnumerable.Join, AsyncEnumerableDeprecated.JoinAwaitCore, AsyncEnumerable.JoinAwaitWithCancellationCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerable.JoinAwaitWithCancellationCore (cognitive 20) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:169— AsyncEnumerable.JoinAwaitWithCancellationCore has cognitive complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 4 other methods here (AsyncEnumerable.Join, AsyncEnumerable.JoinAwaitCore, AsyncEnumerableDeprecated.JoinAwaitCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerable.SequenceEqualAsync (cognitive 20) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SequenceEqual.cs:41— AsyncEnumerable.SequenceEqualAsync has cognitive complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.CompareAggregateOverloads (cognitive 20) Ix.NET/Source/ApiCompare/Program.cs:179— Program.CompareAggregateOverloads has cognitive complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AsyncEnumerableDeprecated.JoinAwaitCore (cognitive 20) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:111— AsyncEnumerableDeprecated.JoinAwaitCore has cognitive complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 4 other methods here (AsyncEnumerable.Join, AsyncEnumerable.JoinAwaitCore, AsyncEnumerable.JoinAwaitWithCancellationCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AsyncEnumerableDeprecated.JoinAwaitWithCancellationCore (cognitive 20) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Join.cs:169— AsyncEnumerableDeprecated.JoinAwaitWithCancellationCore has cognitive complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: 4 other methods here (AsyncEnumerable.Join, AsyncEnumerable.JoinAwaitCore, AsyncEnumerableDeprecated.JoinAwaitCore, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ScheduledObserver.Dispatch (cognitive 19) Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:83— ScheduledObserver.Dispatch has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ObservableRewriter.VisitMethodCall (cognitive 19) Rx.NET/Source/src/System.Reactive/ObservableQuery.cs:193— ObservableRewriter.VisitMethodCall has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AsyncObserver.Window (cognitive 19) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:372— AsyncObserver.Window has cognitive complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AsyncObserver.Zip (cognitive 19) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Zip.cs:46— AsyncObserver.Zip has cognitive complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 61, 105). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CombineLatestSink.Next (cognitive 18) Rx.NET/Source/src/System.Reactive/Linq/Observable/CombineLatest.cs:244— CombineLatestSink.Next has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RedoSerializedObserver.Drain (cognitive 18) Rx.NET/Source/src/System.Reactive/Linq/Observable/RetryWhen.cs:211— RedoSerializedObserver.Drain has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CompositeDisposable.Add (cognitive 17) Rx.NET/Source/src/System.Reactive/Disposables/CompositeDisposable.cs:161— CompositeDisposable.Add has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CompositeDisposable.CopyTo (cognitive 17) Rx.NET/Source/src/System.Reactive/Disposables/CompositeDisposable.cs:423— CompositeDisposable.CopyTo has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScheduledObserver.Run (cognitive 17) Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:205— ScheduledObserver.Run has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Observable.CombineLatest (cognitive 17) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.CombineLatest.cs:1104— Observable.CombineLatest has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Observable.Zip (cognitive 17) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.Zip.cs:1090— Observable.Zip has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AsyncEnumerable.ElementAtOrDefaultAsync::Core (cognitive 17) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ElementAtOrDefault.cs:37— AsyncEnumerable.ElementAtOrDefaultAsync::Core has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncObservable.GetEventMethods (cognitive 17) AsyncRx.NET/System.Reactive.Async/Linq/Operators/FromEventPattern.cs:262— AsyncObservable.GetEventMethods has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AsyncObserver.Generate (cognitive 17) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Generate.cs:231— AsyncObserver.Generate has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 244). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Observable.CombineLatest (cognitive 16) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.CombineLatest.cs:979— Observable.CombineLatest has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ObservableEx.CombineLatest) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ObservableEx.CombineLatest (cognitive 16) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.CombineLatest.cs:1867— ObservableEx.CombineLatest has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Observable.CombineLatest) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Observable.Zip (cognitive 16) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.Zip.cs:966— Observable.Zip has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ObservableEx.Zip) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ObservableEx.Zip (cognitive 16) Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.Zip.cs:1853— ObservableEx.Zip has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Observable.Zip) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ForkJoinObservable.SubscribeCore (cognitive 16) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguageEx.cs:357— ForkJoinObservable.SubscribeCore has cognitive complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 404, 384). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AsyncSubject.Subscribe (cognitive 16) Rx.NET/Source/src/System.Reactive/Subjects/AsyncSubject.cs:193— AsyncSubject.Subscribe has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OnErrorResumeNextAsyncIterator.MoveNextCore (cognitive 16) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/OnErrorResumeNext.cs:99— OnErrorResumeNextAsyncIterator.MoveNextCore has cognitive complexity 16 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AsyncEnumerable.ElementAtAsync (cognitive 16) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ElementAt.cs:31— AsyncEnumerable.ElementAtAsync has cognitive complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function item inside it that branches (Core). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
AsyncEnumerableRewriter.FixupQuotedExpression (cognitive 16) Ix.NET/Source/System.Linq.Async.Queryable/System/Linq/AsyncEnumerableRewriter.cs:309— AsyncEnumerableRewriter.FixupQuotedExpression has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WhereFastIteratorWithTask.WaitForNextAsync (cognitive 16) Ix.NET/Source/FasterLinq/Program.cs:1528— WhereFastIteratorWithTask.WaitForNextAsync has cognitive complexity 16 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AsyncObserver.GroupJoin (cognitive 16) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:47— AsyncObserver.GroupJoin has cognitive complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 86, 175, 119). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassTooLong: Program Rx.NET/tools/HomoIcon/Program.cs— ClassTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 210 over it, 1.53× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Change coupling: IQueryLanguage.cs ↔ Observable.StandardSequenceOperators.cs Rx.NET/Source/src/System.Reactive/Linq/IQueryLanguage.cs:1— `Rx.NET/Source/src/System.Reactive/Linq/IQueryLanguage.cs` and `Rx.NET/Source/src/System.Reactive/Linq/Observable.StandardSequenceOperators.cs` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `0aa0a009` Modify OfType to accept nullable input element type (#2260); `7d8ee678` Change signature of Observable.DefaultIfEmpty to a IObservable<TSourc…; `62753954` Adding IScheduler overloads for ToObservable on Task. (at that commit the files were still `Rx.NET/Source/System.Reactive.Linq/Reactive/Linq/IQueryLanguage.cs` and `Rx.NET/Source/System.Reactive.Linq/Reactive/Linq/Observable.StandardSequenceOperators.cs`) — run `git show` on any of them.
D4 · Code Duplication· Near-duplicate member family (13 members, 25 shared lines) · ×1
Near-duplicate member family (13 members, 25 shared lines) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:201— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:201-238 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:256-296 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:314-358 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:376-423 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:441-491 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:509-562 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:580-636 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:654-714 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:732-796 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:815-882 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:901-975 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:993-1070 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1087-1168 — These 13 members are variants of one another: a block of 25 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
Near-duplicate member pair (93 shared lines) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:48— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:48-237 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:50-260 — These two members are variants of one another: 93 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (40 shared lines) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:34— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:34-103 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:217-314 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (52 corresponding lines) · ×1
Edited copy of a member (52 corresponding lines) Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:599— Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:599-651 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:757-808 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (15 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (15 members, 50+ identical tokens) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:21— Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:21-54 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:57-86 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:89-118 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:121-150 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:153-182 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:185-214 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:217-246 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:249-278 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:281-310 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:313-342 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:345-374 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:377-406 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:409-438 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:441-470 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:473-502 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication· Members sharing a duplicated core (13 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (13 members, 50+ identical tokens) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:177— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:177-205 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:234-266 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:299-335 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:371-411 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:451-496 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:539-589 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:635-689 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:738-796 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:849-911 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:967-1033 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1092-1162 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1225-1299 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1365-1443 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1073— Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1073-1094 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1102-1123 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1131-1152 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1160-1181 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1189-1210 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1218-1239 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1247-1268 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1276-1297 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1305-1326 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1334-1355 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1592— Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1592-1612 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1620-1640 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1648-1668 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1676-1696 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1704-1724 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1732-1752 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1760-1780 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1788-1808 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1816-1836 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:307— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:307-361 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:379-492 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:510-581 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:659-752 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:128-174 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:86-139 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:152-198 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeUntil.cs:86-135 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:228— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:228-259 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:310-341 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:347-374 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:230-261 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:312-343 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:349-374 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (66 lines × 2) Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs:86— Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs:86-151 | Rx.NET/Source/src/System.Reactive/Platforms/Desktop/Concurrency/ControlScheduler.cs:80-145 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/Desktop/Concurrency/ControlScheduler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (65 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SequenceEqual.cs:96— AsyncRx.NET/System.Reactive.Async/Linq/Operators/SequenceEqual.cs:96-160 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SequenceEqual.cs:162-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SequenceEqual.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (52 lines × 2) Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs:165— Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs:165-216 | Rx.NET/Source/src/System.Reactive/Platforms/Desktop/Concurrency/ControlScheduler.cs:159-210 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.Windows.Forms/ControlScheduler.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/Desktop/Concurrency/ControlScheduler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (48 lines × 2) Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:91— Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs:91-138 | Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs:81-128 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Concurrency/CoreDispatcherScheduler.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Concurrency/CoreDispatcherScheduler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (32–48 lines × 9) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:460— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:460-491 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:529-562 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:601-636 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:677-714 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:757-796 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:841-882 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:932-975 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1025-1070 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1121-1168 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:460` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (46 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1334— Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1334-1379 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1417-1462 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1334` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (44 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/MaxBy.cs:105— AsyncRx.NET/System.Reactive.Async/Linq/Operators/MaxBy.cs:105-148 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/MinBy.cs:105-148 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/MaxBy.cs:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (47 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:128— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs:128-174 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs:152-198 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Skip.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipUntil.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (44 lines × 3) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:521— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:521-564 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:659-702 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:798-841 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (44–45 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:607— Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:607-651 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:765-808 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:607` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (43 lines × 2) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguageEx.cs:249— Rx.NET/Source/src/System.Reactive/Linq/QueryLanguageEx.cs:249-291 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguageEx.cs:292-334 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/QueryLanguageEx.cs:292` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (42 lines × 2) Ix.NET/Source/ApiCompare/Program.cs:116— Ix.NET/Source/ApiCompare/Program.cs:116-157 | Ix.NET/Source/ApiCompare/Program.cs:182-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (41 lines × 2) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:53— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:53-93 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:61-101 — before extracting anything, compare `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/ToAsyncEnumerable.Observable.cs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (39 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:171— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:171-209 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:169-207 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:171` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 2) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:114— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:114-142 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:202-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:114` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (24–29 lines × 2) AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:48— AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:48-76 | AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs:26-49 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs` and `AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24–28 lines × 15) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:27— Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:27-54 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:63-86 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:95-118 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:127-150 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:159-182 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:191-214 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:223-246 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:255-278 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:287-310 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:319-342 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:351-374 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:383-406 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:415-438 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:447-470 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:479-502 — all 15 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:27` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 3) Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Catch.cs:40— Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Catch.cs:40-63 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Catch.cs:103-126 | Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Catch.cs:167-190 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Catch.cs:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `handler` to `Func<TException, IAsyncEnumerable<TSource>>` in one and `Func<TException, ValueTask<IAsyncEnumerable<TSource>>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (23 lines × 3) Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:387— Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:387-409 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1341-1363 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1424-1446 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:387` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–24 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:311— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:311-331 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:385-408 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:548-571 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:311` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 9) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:478— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:478-491 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:570-583 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:669-682 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:775-788 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:889-902 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1010-1023 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1138-1151 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1274-1287 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1417-1430 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:478` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 10) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:388— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:388-407 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:471-491 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:563-583 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:662-682 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:768-788 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:882-902 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1003-1023 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1131-1151 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1267-1287 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1410-1430 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:388` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20 lines × 3) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.cs:61— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.cs:61-80 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.cs:134-153 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.cs:239-258 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 4) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:55— AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:55-73 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:77-95 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:139-157 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:161-179 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/For.cs:61— AsyncRx.NET/System.Reactive.Async/Linq/Operators/For.cs:61-79 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/While.cs:41-59 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/While.cs:94-112 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/For.cs:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:174— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:174-192 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:175-194 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:174` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–20 lines × 2) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:347— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:347-366 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:349-366 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:347` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–19 lines × 11) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:314— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:314-331 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:389-406 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:472-490 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:564-582 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:663-681 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:769-787 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:883-901 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1004-1022 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1132-1150 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1268-1286 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1411-1429 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:314` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 10) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:396— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:396-411 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:462-477 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:531-546 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:603-618 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:679-694 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:759-774 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:843-858 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:934-949 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1027-1042 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1123-1138 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:396` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:478` calls `RemoveActivePlan` and `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:412` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16–19 lines × 2) AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:106— AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs:106-124 | AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs:80-95 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Internal/EventPatternSourceBaseInternal.cs` and `AsyncRx.NET/System.Reactive.Async/Internal/EventSource.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 11) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:333— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:333-347 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:396-410 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:462-476 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:531-545 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:603-617 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:679-693 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:759-773 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:843-857 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:934-948 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1027-1041 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1123-1137 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:333` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:411` calls `RemoveActivePlan` and `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:348` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 4) AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:15— AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:15-31 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:35-51 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:99-115 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:119-135 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:152— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:152-169 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:208-227 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:267-286 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `values` to `params TSource[]` in one and `IEnumerable<TSource>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17–18 lines × 2) Rx.NET/tools/HomoIcon/Program.cs:545— Rx.NET/tools/HomoIcon/Program.cs:545-561 | Rx.NET/tools/HomoIcon/Program.cs:666-683 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/tools/HomoIcon/Program.cs:545` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–17 lines × 12) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:247— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:247-262 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:315-330 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:390-405 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:473-489 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:565-581 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:664-680 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:770-786 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:884-900 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1005-1021 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1133-1149 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1269-1285 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1412-1428 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 12) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:273— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:273-286 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:333-346 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:396-409 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:462-475 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:531-544 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:603-616 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:679-692 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:759-772 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:843-856 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:934-947 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1027-1040 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1123-1136 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:273` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:347` calls `RemoveActivePlan` and `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:287` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 10) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:412— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:412-421 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:479-488 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:549-558 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:622-631 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:699-708 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:780-789 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:865-874 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:957-966 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1051-1060 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1148-1157 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:412` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:489` calls `AddActivePlan` and `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:422` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:425— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:425-440 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:515-530 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:698-713 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:790-805 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:425` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 13) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:217— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:217-229 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:273-285 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:333-345 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:396-408 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:462-474 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:531-543 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:603-615 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:679-691 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:759-771 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:843-855 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:934-946 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1027-1039 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1123-1135 — all 13 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:217` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:286` calls `RemoveActivePlan` and `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:230` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 2) Rx.NET/tools/HomoIcon/Program.cs:588— Rx.NET/tools/HomoIcon/Program.cs:588-603 | Rx.NET/tools/HomoIcon/Program.cs:716-730 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Rx.NET/tools/HomoIcon/Program.cs:586` calls `Join` and `Rx.NET/tools/HomoIcon/Program.cs:714` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 11) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:348— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:348-356 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:412-420 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:479-487 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:549-557 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:622-630 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:699-707 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:780-788 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:865-873 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:957-965 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1051-1059 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1148-1156 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:348` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:421` calls `AddActivePlan` and `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:357` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 13) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:188— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:188-201 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:248-261 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:316-329 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:391-404 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:474-488 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:566-580 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:665-679 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:771-785 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:885-899 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1006-1020 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1134-1148 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1270-1284 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1413-1427 — all 13 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:188` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 12) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:287— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:287-294 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:348-355 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:412-419 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:479-486 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:549-556 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:622-629 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:699-706 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:780-787 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:865-872 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:957-964 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1051-1058 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1148-1155 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:287` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:356` calls `AddActivePlan` and `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:295` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:129— AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:129-135 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:126-132 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:214-220 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupJoin.cs:129` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 13) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:230— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:230-236 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:287-293 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:348-354 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:412-418 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:479-485 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:549-555 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:622-628 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:699-705 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:780-786 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:865-871 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:957-963 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1051-1057 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1148-1154 — all 13 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:230` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:294` calls `AddActivePlan` and `Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:237` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Prepend.cs:130— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Prepend.cs:130-139 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Prepend.cs:187-196 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Prepend.cs:247-256 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Prepend.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 9) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:452— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:452-458 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:540-546 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:636-642 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:739-745 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:850-856 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:968-974 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1093-1099 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1226-1232 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1366-1372 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:452` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 10) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:470— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:470-477 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:561-568 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:659-666 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:764-771 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:877-884 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:997-1004 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1124-1131 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1259-1266 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1401-1408 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1409-1416 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:470` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:310— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:310-317 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:347-354 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:312-319 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs:349-356 — before extracting anything, compare `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs` and `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Min.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Max.cs:310` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 12) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:239— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:239-245 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:305-311 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:378-384 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:459-465 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:548-555 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:645-652 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:749-756 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:861-868 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:980-987 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1106-1113 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1240-1247 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1381-1388 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:239` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:312` calls `Peek` and `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:247` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 4) Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:989— Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:989-995 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1115-1121 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1249-1255 | Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1390-1396 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1122` calls `Peek` and `Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:997` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 13) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:202— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:202-206 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:257-261 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:315-319 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:377-381 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:442-446 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:510-514 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:581-585 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:655-659 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:733-737 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:816-820 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:902-906 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:994-998 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1088-1092 — all 13 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 7) Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:586— Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:586-591 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:660-665 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:738-743 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:821-826 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:907-912 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:999-1004 | Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1093-1098 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 9) Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1596— Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1596-1600 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1624-1628 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1652-1656 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1680-1684 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1708-1712 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1736-1740 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1764-1768 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1792-1796 | Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1820-1824 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1596` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) AsyncRx.NET/System.Reactive.Async/Subjects/ConcurrentAsyncAsyncSubject.cs:13— AsyncRx.NET/System.Reactive.Async/Subjects/ConcurrentAsyncAsyncSubject.cs:13-17 | AsyncRx.NET/System.Reactive.Async/Subjects/ConcurrentBehaviorAsyncSubject.cs:15-22 | AsyncRx.NET/System.Reactive.Async/Subjects/ConcurrentSimpleAsyncSubject.cs:13-17 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Subjects/ConcurrentAsyncAsyncSubject.cs` and `AsyncRx.NET/System.Reactive.Async/Subjects/ConcurrentBehaviorAsyncSubject.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 3) AsyncRx.NET/System.Reactive.Async/Subjects/SequentialAsyncAsyncSubject.cs:13— AsyncRx.NET/System.Reactive.Async/Subjects/SequentialAsyncAsyncSubject.cs:13-34 | AsyncRx.NET/System.Reactive.Async/Subjects/SequentialBehaviorAsyncSubject.cs:14-39 | AsyncRx.NET/System.Reactive.Async/Subjects/SequentialSimpleAsyncSubject.cs:13-34 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Subjects/SequentialAsyncAsyncSubject.cs` and `AsyncRx.NET/System.Reactive.Async/Subjects/SequentialBehaviorAsyncSubject.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (174 lines × 2) Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Linq/CoreDispatcherObservable.cs:31— Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Linq/CoreDispatcherObservable.cs:31-204 | Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Linq/CoreDispatcherObservable.cs:32-310 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive.WindowsRuntime/System.Reactive.Linq/CoreDispatcherObservable.cs` and `Rx.NET/Source/src/System.Reactive/Platforms/WinRT/Linq/CoreDispatcherObservable.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) Rx.NET/Source/src/System.Reactive.WindowsRuntime/StableUncheckedCompositeDisposable.cs:54— Rx.NET/Source/src/System.Reactive.WindowsRuntime/StableUncheckedCompositeDisposable.cs:54-62 | Rx.NET/Source/src/System.Reactive/Disposables/StableCompositeDisposable.cs:167-175 | Rx.NET/Source/src/System.Reactive/Disposables/StableCompositeDisposable.cs:195-203 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Rx.NET/Source/src/System.Reactive/Disposables/StableCompositeDisposable.cs:163` calls `Read` and `Rx.NET/Source/src/System.Reactive.WindowsRuntime/StableUncheckedCompositeDisposable.cs:50` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 10) Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs:185— Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs:185-201 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs:246-262 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs:307-323 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs:368-384 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs:429-445 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Min.cs:185-201 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Min.cs:246-262 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Min.cs:307-323 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Min.cs:368-384 | Rx.NET/Source/src/System.Reactive/Linq/Observable/Min.cs:429-445 — before extracting anything, compare `Rx.NET/Source/src/System.Reactive/Linq/Observable/Max.cs` and `Rx.NET/Source/src/System.Reactive/Linq/Observable/Min.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 5) Rx.NET/Source/src/System.Reactive/Linq/Observable/Merge.cs:194— Rx.NET/Source/src/System.Reactive/Linq/Observable/Merge.cs:194-213 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:81-100 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:245-264 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:908-927 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1142-1161 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 5) Rx.NET/Source/src/System.Reactive/Linq/Observable/Merge.cs:252— Rx.NET/Source/src/System.Reactive/Linq/Observable/Merge.cs:252-267 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:156-171 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:324-339 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:964-979 | Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1198-1213 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 6) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:268— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:268-275 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:504-511 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:623-630 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.cs:50-57 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.cs:123-130 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToAsyncEnumerable.cs:228-235 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 8) Ix.NET/Source/System.Linq.Async/System/Linq/Operators/AppendPrepend.cs:105— Ix.NET/Source/System.Linq.Async/System/Linq/Operators/AppendPrepend.cs:105-112 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:211-218 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:382-389 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:441-448 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:219-226 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:285-292 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:347-354 | Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Where.cs:412-419 — there are 8 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 5) AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:75— AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:75-80 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:44-49 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs:231-236 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/WithLatestFrom.cs:108-113 | AsyncRx.NET/System.Reactive.Async/Linq/Operators/WithLatestFrom.cs:175-180 — before extracting anything, compare `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/SelectMany.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Join.cs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AsyncRx.NET/System.Reactive.Async/Linq/Operators/Merge.cs:42` calls `CompositeAsyncDisposable` and `AsyncRx.NET/System.Reactive.Async/Linq/Operators/WithLatestFrom.cs:106` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication· Near-duplicate member family (7 members, 26 shared lines) · ×1
Near-duplicate member family (7 members, 26 shared lines) Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:13— Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:13-54 | Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:13-55 | Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:13-61 | Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs:13-59 | Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:13-64 | Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:13-66 | Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:13-77 — These 7 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) Rx.NET/Samples/HOL/CS/Excercise2/Start/Program.cs:10— Rx.NET/Samples/HOL/CS/Excercise2/Start/Program.cs:10-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step03/Program.cs:10-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step04/Program.cs:10-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step05/Program.cs:10-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step06/Program.cs:10-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step07/Program.cs:10-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step08/Program.cs:10-23 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Duplicated block (42–45 lines × 2) Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:13— Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:13-54 | Rx.NET/Samples/HOL/CS/Excercise9/Step04/Program.cs:13-57 — `Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise9/Step04/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 64 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–19 lines × 8) Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:37— Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:37-54 | Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:38-55 | Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:43-61 | Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs:41-59 | Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:46-64 | Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:48-66 | Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:59-77 | Rx.NET/Samples/HOL/CS/Excercise9/Step04/Program.cs:68-86 — `Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 70 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:37` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:42` calls `TakeUntil` and `Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:36` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 5) Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:16— Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:16-32 | Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:16-32 | Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs:17-33 | Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:17-33 | Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:17-33 — `Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:35` calls `matchInWordNetByPrefix` and `Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:34` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 3) Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:29— Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:29-43 | Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:29-44 | Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:30-45 — `Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 81 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 6) Rx.NET/Samples/HOL/CS/Excercise8/Step02/Program.cs:12— Rx.NET/Samples/HOL/CS/Excercise8/Step02/Program.cs:12-24 | Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:13-25 | Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:13-25 | Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs:14-26 | Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:14-26 | Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:14-26 — `Rx.NET/Samples/HOL/CS/Excercise8/Step02/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 13 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13–14 lines × 2) Rx.NET/Samples/HOL/CS/Excercise7/Step05/Program.cs:13— Rx.NET/Samples/HOL/CS/Excercise7/Step05/Program.cs:13-25 | Rx.NET/Samples/HOL/CS/Excercise7/Step06/Program.cs:13-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Samples/HOL/CS/Excercise7/Step06/Program.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 7) Rx.NET/Samples/HOL/CS/Excercise2/Start/Program.cs:13— Rx.NET/Samples/HOL/CS/Excercise2/Start/Program.cs:13-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step03/Program.cs:13-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step04/Program.cs:13-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step05/Program.cs:13-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step06/Program.cs:13-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step07/Program.cs:13-23 | Rx.NET/Samples/HOL/CS/Excercise2/Step08/Program.cs:13-23 — `Rx.NET/Samples/HOL/CS/Excercise2/Start/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise2/Step03/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 11 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Rx.NET/Samples/HOL/CS/Excercise2/Start/Program.cs:13` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 6) Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:27— Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:27-35 | Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs:28-36 | Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:28-36 | Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:28-36 | Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:29-37 | Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:31-40 — `Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 65 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:42` calls `TakeUntil` and `Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:37` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 14) Rx.NET/Samples/HOL/CS/Excercise7/Step05/Program.cs:13— Rx.NET/Samples/HOL/CS/Excercise7/Step05/Program.cs:13-18 | Rx.NET/Samples/HOL/CS/Excercise7/Step06/Program.cs:13-18 | Rx.NET/Samples/HOL/CS/Excercise7/Step07/Program.cs:13-18 | Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:27-32 | Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:27-32 | Rx.NET/Samples/HOL/CS/Excercise8/Step06/Program.cs:28-33 | Rx.NET/Samples/HOL/CS/Excercise8/Step07/Program.cs:28-33 | Rx.NET/Samples/HOL/CS/Excercise8/Step08/Program.cs:28-33 | Rx.NET/Samples/HOL/CS/Excercise8/Step09/Program.cs:29-34 | Rx.NET/Samples/HOL/CS/Excercise8/Step10/Program.cs:31-36 | Rx.NET/Samples/HOL/CS/Excercise8/Step11/Program.cs:31-36 | Rx.NET/Samples/HOL/CS/Excercise9/Step01/Program.cs:36-41 | Rx.NET/Samples/HOL/CS/Excercise9/Step02/Program.cs:38-43 | Rx.NET/Samples/HOL/CS/Excercise9/Step03/Program.cs:49-54 — `Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs` and `Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Rx.NET/Samples/HOL/CS/Excercise8/Step05/Program.cs:35` calls `matchInWordNetByPrefix` and `Rx.NET/Samples/HOL/CS/Excercise8/Step03/Program.cs:34` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Off the main sequence: System.Interactive.Async(net48) (Ix.NET/Source/System.Interactive.Async) Ix.NET/Source/System.Interactive.Async/System.Interactive.Async.csproj:1— System.Interactive.Async(net48) (Ix.NET/Source/System.Interactive.Async): abstractness 0.12, instability 0.00, distance 0.88 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
Fake-async — async method never awaits AsyncRx.NET/Playground/Program.cs:22— `Main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body — does nothing with its inputs Rx.NET/Source/src/System.Reactive.Analyzers/Analyzers/UiFrameworkPackages/UiFrameworkSpecificTypes.cs:56— `MovedTypeDetails` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Condition was already decided — an earlier guard makes this test constant Rx.NET/Source/src/System.Reactive/Internal/ScheduledObserver.cs:111— Control only reaches here when `cancel.IsDisposed` is false, because the guard on line 89 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 60 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
async void method: SetResult AsyncRx.NET/System.Reactive.Async/Runtime/CompilerServices/AsyncObservableMethodBuilder.cs:259— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
X2 · Cancellation propagation· Async local function without CancellationToken · ×1
Async local function without CancellationToken: Core Ix.NET/Source/System.Linq.Async/System/Linq/AsyncListPartition.cs:53— Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Swallowed exception (caught, then discarded) Ix.NET/Source/System.Interactive/System/Linq/Operators/OnErrorResumeNext.cs:74— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.StandardSequenceOperators.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.Events.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Ix.NET/Source/System.Linq.Async/System/Linq/Operators/GroupBy.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/IQueryLanguage.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Async.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.Multiple.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Joins/Plan.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.Binding.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Joins/ActivePlan.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.Single.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Ix.NET/Source/FasterLinq/Program.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupByUntil.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Ix.NET/Source/System.Linq.Async/System/Linq/Operators/SelectMany.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Ix.NET/Source/System.Linq.Async/System/Linq/Operators/OrderedAsyncEnumerable.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.Creation.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/tools/HomoIcon/Program.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive.Observable.Aliases/Observable.Aliases.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file AsyncRx.NET/System.Reactive.Async/Linq/Operators/Window.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file AsyncRx.NET/System.Reactive.Async/Linq/Operators/GroupBy.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Services.Emulation.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Subjects/ReplaySubject.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file AsyncRx.NET/System.Reactive.Async/Linq/Operators/Buffer.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Rx.NET/Source/src/System.Reactive/Notification.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Ix.NET/Source/System.Linq.Async/System/Linq/Operators/Select.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Commented-out code AsyncRx.NET/Playground/Program.cs:24— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:25— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:26— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:27— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:28— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:29— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:30— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:31— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:32— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:33— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:34— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:35— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:36— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:37— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:38— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:39— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:40— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:41— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:42— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:43— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:44— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/Playground/Program.cs:45— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncRx.NET/System.Reactive.Async/AsyncObservableBase.cs:105— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Ix.NET/Source/System.Linq.Async.Queryable/System/Linq/AsyncEnumerableRewriter.cs:141— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Rx.NET/Source/src/System.Reactive/Concurrency/ConcurrencyAbstractionLayerImpl.cs:87— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Thin analysable surface across projects: Android Ix.NET/Integration/Android/Android.csproj— 22 project(s) carry only a thin slice of real code; `Android` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Pcl259 Ix.NET/Integration/Pcl259/Pcl259.csproj— 22 project(s) carry only a thin slice of real code; `Pcl259` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Uwp Ix.NET/Integration/Uwp/Uwp.csproj— 22 project(s) carry only a thin slice of real code; `Uwp` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Win81 Ix.NET/Integration/Win81/Win81.csproj— 22 project(s) carry only a thin slice of real code; `Win81` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Win81Wpa81 Ix.NET/Integration/Win81Wpa81/Win81Wpa81.csproj— 22 project(s) carry only a thin slice of real code; `Win81Wpa81` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Wpa81 Ix.NET/Integration/Wpa81/Wpa81.csproj— 22 project(s) carry only a thin slice of real code; `Wpa81` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: iOS Ix.NET/Integration/iOS/iOS.csproj— 22 project(s) carry only a thin slice of real code; `iOS` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: tvOS Ix.NET/Integration/tvOS/tvOS.csproj— 22 project(s) carry only a thin slice of real code; `tvOS` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Android Rx.NET/Integration/Installation/Android/Android.csproj— 22 project(s) carry only a thin slice of real code; `Android` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Pcl259 Rx.NET/Integration/Installation/Pcl259/Pcl259.csproj— 22 project(s) carry only a thin slice of real code; `Pcl259` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Uwp Rx.NET/Integration/Installation/Uwp/Uwp.csproj— 22 project(s) carry only a thin slice of real code; `Uwp` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Win81 Rx.NET/Integration/Installation/Win81/Win81.csproj— 22 project(s) carry only a thin slice of real code; `Win81` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Win81Wpa81 Rx.NET/Integration/Installation/Win81Wpa81/Win81Wpa81.csproj— 22 project(s) carry only a thin slice of real code; `Win81Wpa81` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Wpa81 Rx.NET/Integration/Installation/Wpa81/Wpa81.csproj— 22 project(s) carry only a thin slice of real code; `Wpa81` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: iOS Rx.NET/Integration/Installation/iOS/iOS.csproj— 22 project(s) carry only a thin slice of real code; `iOS` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: tvOS Rx.NET/Integration/Installation/tvOS/tvOS.csproj— 22 project(s) carry only a thin slice of real code; `tvOS` has 25 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Net45 Ix.NET/Integration/Net45/Net45.csproj— 22 project(s) carry only a thin slice of real code; `Net45` has 26 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.04 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Net461 Ix.NET/Integration/Net461/Net461.csproj— 22 project(s) carry only a thin slice of real code; `Net461` has 26 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.04 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Net45 Rx.NET/Integration/Installation/Net45/Net45.csproj— 22 project(s) carry only a thin slice of real code; `Net45` has 26 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.04 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Net461 Rx.NET/Integration/Installation/Net461/Net461.csproj— 22 project(s) carry only a thin slice of real code; `Net461` has 26 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.04 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Wp8 Ix.NET/Integration/Wp8/Wp8.csproj— 22 project(s) carry only a thin slice of real code; `Wp8` has 33 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.03 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Wp8 Rx.NET/Integration/Installation/Wp8/Wp8.csproj— 22 project(s) carry only a thin slice of real code; `Wp8` has 33 significant line(s). The mean analysable-surface weight is 88 %; this project lowers Solution Shape by about 0.03 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise7/Step02/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise7/Step03/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise7/Step04/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise7/Step05/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise7/Step06/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise7/Step07/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Start/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step01/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step02/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step03/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step05/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step06/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step07/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step08/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step09/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step10/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise8/Step11/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise9/Step01/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise9/Step02/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise9/Step03/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DictServiceSoap (27 members) Rx.NET/Samples/HOL/CS/Excercise9/Step04/Service References/DictionarySuggestService/Reference.cs:14— `DictServiceSoap` declares 27 members: `ServerInfo`, `BeginServerInfo`, `EndServerInfo`, `DictionaryList`, `BeginDictionaryList`, `EndDictionaryList`, `DictionaryListExtended`, `BeginDictionaryListExtended`, `EndDictionaryListExtended`, `DictionaryInfo`, `BeginDictionaryInfo`, `EndDictionaryInfo`, `Define`, `BeginDefine`, `EndDefine`, `DefineInDict`, `BeginDefineInDict`, `EndDefineInDict`, `StrategyList`, `BeginStrategyList`, `EndStrategyList`, `Match`, `BeginMatch`, `EndMatch`, `MatchInDict`, `BeginMatchInDict`, `EndMatchInDict`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Duplicated predicate Rx.NET/Source/src/System.Reactive/ObservableQuery.cs:448— `!method.IsGenericMethod && typeArgs != null && typeArgs.Length > 0` appears character-identically in 2 files — Ix.NET/Source/System.Interactive.Providers/System/Linq/QueryableEx.cs, Rx.NET/Source/src/System.Reactive/ObservableQuery.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Ix.NET/Source/System.Linq.Async/System/Linq/Operators/AppendPrepend.cs:282— `!onlyIfCheap || _source is ICollection<TSource> || _source is ICollection` appears character-identically in 2 files — Ix.NET/Source/System.Linq.Async/System/Linq/Operators/AppendPrepend.cs, Ix.NET/Source/System.Linq.Async/System/Linq/Operators/DefaultIfEmpty.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Rx.NET/Source/src/Microsoft.Reactive.Testing/Recorded.cs:50— `Time == other.Time && EqualityComparer<T>.Default.Equals(Value, other.Value)` appears character-identically in 2 files — AsyncRx.NET/Microsoft.Reactive.Testing.Async/AsyncRecorded.cs, Rx.NET/Source/src/Microsoft.Reactive.Testing/Recorded.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Rx.NET/Source/src/System.Reactive/Linq/Observable/Merge.cs:253— `_parent._isStopped && _parent._group.Count == 0` appears character-identically in 2 files — Rx.NET/Source/src/System.Reactive/Linq/Observable/Merge.cs, Rx.NET/Source/src/System.Reactive/Linq/Observable/SelectMany.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Rx.NET/Source/src/System.Reactive/Linq/Observable/SkipLast.cs:95— `_queue.Count > 0 && now - _queue.Peek().Interval >= _duration` appears character-identically in 3 files — Rx.NET/Source/src/System.Reactive/Linq/Observable/SkipLast.cs, Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLast.cs, Rx.NET/Source/src/System.Reactive/Linq/Observable/TakeLastBuffer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/EqualException.cs:125— `actualPointer.HasValue && mismatchedIndex.HasValue` appears character-identically in 2 files — ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/EqualException.cs, ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/NotEqualException.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Ix.NET/Source/System.Interactive/System/Linq/Operators/Buffer.cs:65— `buffers.Count > 0 && buffers.Peek().Count == count` appears character-identically in 2 files — Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Buffer.cs, Ix.NET/Source/System.Interactive/System/Linq/Operators/Buffer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Rx.NET/Source/src/Microsoft.Reactive.Testing/TestScheduler.cs:95— `disposed < created || disposed < subscribed` appears character-identically in 2 files — AsyncRx.NET/Microsoft.Reactive.Testing.Async/TestAsyncScheduler.Harness.cs, Rx.NET/Source/src/Microsoft.Reactive.Testing/TestScheduler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/EqualException.cs:120— `expectedPointer.HasValue && mismatchedIndex.HasValue` appears character-identically in 2 files — ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/EqualException.cs, ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/NotEqualException.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/EqualException.cs:117— `expectedType != null && actualType != null && expectedType != actualType` appears character-identically in 2 files — ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/EqualException.cs, ../../root/.nuget/packages/xunit.v3.assert.source/3.2.2/contentFiles/cs/netstandard2.0/Asserts/Sdk/Exceptions/NotEqualException.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs:229— `i < values.Length && !ct.IsCancellationRequested` appears character-identically in 2 files — AsyncRx.NET/System.Reactive.Async/Linq/Operators/Append.cs, AsyncRx.NET/System.Reactive.Async/Linq/Operators/Prepend.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipLast.cs:112— `queue.Count > 0 && now - queue.Peek().Timestamp >= duration` appears character-identically in 3 files — AsyncRx.NET/System.Reactive.Async/Linq/Operators/SkipLast.cs, AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLast.cs, AsyncRx.NET/System.Reactive.Async/Linq/Operators/TakeLastBuffer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Pass-through layer Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Async.cs:483— CancelableScheduler: all 3 public methods forward their arguments unchanged to _scheduler and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _scheduler directly, or give the layer a job.
Pass-through layer Rx.NET/Source/src/System.Reactive/Concurrency/SchedulerQueue.cs:13— SchedulerQueue: all 4 public methods forward their arguments unchanged to _queue and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _queue directly, or give the layer a job.
Pass-through layer Rx.NET/Source/src/System.Reactive/Internal/Sink.cs:100— _: all 3 public methods forward their arguments unchanged to _forward and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _forward directly, or give the layer a job.
Pass-through layer Rx.NET/Source/src/System.Reactive/Linq/Observable/RepeatWhen.cs:144— HandlerObserver: all 3 public methods forward their arguments unchanged to _main and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _main directly, or give the layer a job.
Pass-through layer Rx.NET/Source/src/System.Reactive/Linq/Observable/RetryWhen.cs:137— HandlerObserver: all 3 public methods forward their arguments unchanged to _main and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _main directly, or give the layer a job.
Pass-through layer Rx.NET/Source/src/System.Reactive/Linq/QueryLanguage.Concurrency.cs:10— QueryLanguage: all 6 public methods forward their arguments unchanged to Synchronization and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call Synchronization directly, or give the layer a job.
Pass-through layer Rx.NET/Source/benchmarks/Benchmarks.System.Reactive/CombineLatestBenchmark.cs:11— CombineLatestBenchmark: all 15 public methods forward their arguments unchanged to _zipTest and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _zipTest directly, or give the layer a job.
Pass-through layer Rx.NET/Source/benchmarks/Benchmarks.System.Reactive/ZipBenchmark.cs:11— ZipBenchmark: all 20 public methods forward their arguments unchanged to _zipTest and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _zipTest directly, or give the layer a job.
README/code drift Rx.NET/Documentation/IntroToRx/02_KeyTypes.md:223— Rx.NET/Documentation/IntroToRx/02_KeyTypes.md names the project `System.IO.Stream`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Rx.NET/Documentation/IntroToRx/A_IoStreams.md:3— Rx.NET/Documentation/IntroToRx/A_IoStreams.md names the project `System.IO.Stream`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Rx.NET/Test/Gauntlet/Checks/Bloat/Readme.md:43— Rx.NET/Test/Gauntlet/Checks/Bloat/Readme.md names the project `Microsoft.Desktop.App`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Rx.NET/Test/Gauntlet/Checks/ExtensionMethods/Readme.md:3— Rx.NET/Test/Gauntlet/Checks/ExtensionMethods/Readme.md names the project `Microsoft.Desktop.App`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Rx.NET/Test/Gauntlet/Checks/PlugIns/Readme.md:74— Rx.NET/Test/Gauntlet/Checks/PlugIns/Readme.md names .NET 5, but the projects target .NET 3, 6, 8, 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.Aggregates.cs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.Async.cs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file Rx.NET/Source/src/System.Reactive/Linq/Observable.Time.cs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
IC1 · Incompleteness & stubs· Member throws NotSupportedException · ×3
Member throws NotSupportedException Ix.NET/Source/FasterLinq/Program.cs:259— `Reset`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional.
Member throws NotSupportedException Ix.NET/Source/System.Interactive/System/Linq/Operators/Share.cs:143— `Reset`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional.
Member throws NotSupportedException Ix.NET/Source/System.Interactive/System/Linq/Yielder.cs:75— `Reset`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional.
DuplicateAnalyzerSeverity .editorconfig:258— IDE0290 severity is assigned none twice in the same [*.cs] section — here and again at line 262. The later assignment is the one that applies; this one is a duplicate to remove. — both lines say the same thing, so nothing about the build changes either way, but the repetition is what makes the next edit dangerous: whoever changes one of them will believe the change took effect, and the surviving copy will silently keep the old behaviour. Delete this one and leave a single entry for the rule.
ADR not followed: Migration of core `IAsyncEnumerable<T>` LINQ to runtime libraries Ix.NET/Documentation/adr/0002-System-Linq-Async-In-Net10.md:51— Ix.NET/Documentation/adr/0002-System-Linq-Async-In-Net10.md:51 rules out `System.Linq.Async` in methods, Async, but production code uses it: Ix.NET/Source/System.Linq.Async.SourceGenerator/SyntaxReceiver.cs:6, Ix.NET/Source/System.Linq.Async.SourceGenerator/GenerationOptions.cs:1, Ix.NET/Source/System.Linq.Async.SourceGenerator/DeprecatedDuplicateBuilder.cs:9, Ix.NET/Source/System.Linq.Async.SourceGenerator/AsyncOverloadsGenerator.cs:14, Ix.NET/Source/System.Linq.Async.SourceGenerator/AsyncMethodGrouping.cs:5 (+1 more)
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 125 project(s) overshoot their size bounds, lowering Project Cohesion to 9.7/10. The most over is `System.Reactive(netstandard2.0)` (86976 LoC, 116 public types across 12 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Concentrated knowledge decay — 414 of 463 significant files have no living knowledge, while the repository is still being changed at a low rate (1 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 414 separate risks. Counted over 463 of the 808 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
Logging is not universal — Only 2/3 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 3, 1 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 526/798 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Nullable reference types not enabled everywhere — 22/25 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.8 `!` suppressions per 1k syntax nodes — 957 suppression(s) across the 546395 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Silent fallback default in catch Rx.NET/Source/src/System.Reactive/Concurrency/CatchScheduler.cs:29— `Wrap` swallows `TException` into `return Disposable.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Off the main sequence: CommonCodeInPcl Rx.NET/Integration/BindingRedirects/CommonCodeInPcl/CommonCodeInPcl.csproj:1— CommonCodeInPcl: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 54 file(s) — `Ix.NET/Source/ApiCompare/Program.cs`, `Ix.NET/Source/Playground/DemoAttribute.cs`, `Ix.NET/Source/System.Interactive.Async/System/Linq/Operators/Never.cs`, `Ix.NET/Source/System.Interactive/System/Linq/Operators/Create.cs`, `Ix.NET/Source/System.Interactive/System/Linq/Operators/Share.cs`, … (+49 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a16889-181c-774a-93c4-cbeb0ba2f5f3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 68 · Warnings: 764 · Recommendations: 635 · Info: 78 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 11:32 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.