Public report of louthy/language-ext, 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, 12:11 UTC · Survey ID cd_96c76098aa734febaedc1bc0d30dab87
louthy/language-ext
Measured 23 October 2026, 12:07 UTC, at code version 54d27a2
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 scoreWeak
CriticalWeakAdequateStrongExemplary
Down 1 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: 169,637 lines of product code in 23 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Production Readiness, 26
Findings by how serious they are
29 critical837 serious92 minor
9 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, 12:07 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 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 ▸
66of 70 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
937of 958 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
70dimensions across 6 lenses, read from 169,637 lines of product code in 23 projects.
louthy/language-ext scores 43 out of 100 and is rated Weak, while five of its six lenses score higher still: Architecture at 95, rated Exemplary, Performance at 72, rated Strong, and Maturity at 58, Security and Compliance at 55 and Code Health at 54, all rated Adequate.
The score is lower than those five because the weakest lens counts most, and here that is Production Readiness, which scores 26 and is rated Weak. Its CI/CD gates 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 No assertions (empty test) finding(s) in Test Quality 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 43 to about 57.
29 findings are critical: 23 in Explicit Debt, three in Test Quality, two in Data Compliance (PII/GDPR) and one in Project dependency cycles.
Watchdog couldn't measure 4 dimensions in this code, among them Test Reliability, Dependency Hygiene and IL Efficiency, so they are left out of the score. The product code is 169,637 lines, which would take an estimated 0.8 person-years, around €120,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: 33 findings
These 33 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.
Cancellation propagation · Async method without CancellationToken: MapAsync LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.Extensions.cs
Cancellation propagation · Async method without CancellationToken: ApplyAsync LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.Extensions.cs
Cancellation propagation · Async method without CancellationToken: BindAsync LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.Extensions.cs
Cancellation propagation · Async method without CancellationToken: FilterAsync LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.Extensions.cs
Cancellation propagation · Async method without CancellationToken: Select LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs
Cancellation propagation · Async method without CancellationToken: SelectMany LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs
Cancellation propagation · Async method without CancellationToken: SelectMany LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs
Cancellation propagation · Async method without CancellationToken: Where LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs
Cancellation propagation · Async method without CancellationToken: Skip LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs
Cancellation propagation · Async method without CancellationToken: Take LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs
Cancellation propagation · Async method without CancellationToken: RunTransaction LanguageExt.Core/Concurrency/STM/STM.cs
Cancellation propagation · Async method without CancellationToken: choice LanguageExt.Core/Concurrency/Task/Task.Prelude.cs
Cancellation propagation · Async method without CancellationToken: choice LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs
Cancellation propagation · Async method without CancellationToken: One LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Singleton.cs
Cancellation propagation · Async method without CancellationToken: OneAsync LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.SingletonIO.cs
Cancellation propagation · Async method without CancellationToken: TailAsync LanguageExt.Core/Immutable Collections/IteratorAsync/DSL/IteratorAsync.ConsValueEnum.cs
Cancellation propagation · Async method without CancellationToken: Fold LanguageExt.Core/Immutable Collections/IteratorAsync/IteratorAsync.cs
Cancellation propagation · Async method without CancellationToken: Fold LanguageExt.Core/Immutable Collections/IteratorAsync/IteratorAsync.cs
Cancellation propagation · Async method without CancellationToken: FoldWhile LanguageExt.Core/Immutable Collections/IteratorAsync/IteratorAsync.cs
Cancellation propagation · Async method without CancellationToken: FoldWhile LanguageExt.Core/Immutable Collections/IteratorAsync/IteratorAsync.cs
Cancellation propagation · Async method without CancellationToken: FoldUntil LanguageExt.Core/Immutable Collections/IteratorAsync/IteratorAsync.cs
Cancellation propagation · Async method without CancellationToken: FoldUntil LanguageExt.Core/Immutable Collections/IteratorAsync/IteratorAsync.cs
Cancellation propagation · Async method without CancellationToken: matchAsync LanguageExt.Core/Monads/Alternative Monads/Nullable/Nullable.Prelude.cs
Cancellation propagation · Async method without CancellationToken: matchAsync LanguageExt.Core/Monads/Alternative Monads/Nullable/Nullable.Prelude.cs
Cancellation propagation · Async method without CancellationToken: Expect Samples/TestBed/ResourcesDiscussion1366.cs
Cancellation propagation · Async method without CancellationToken: asyncStream Samples/Streams/OptionalItems.cs
Exception handling · Swallowed exception (caught, then discarded) LanguageExt.Core/Concurrency/Task/Task.Extensions.cs
Exception handling · Swallowed exception (caught, then discarded) LanguageExt.Core/Concurrency/ValueTask/ValueTask.Extensions.cs
Exception handling · Swallowed exception (caught, then discarded) LanguageExt.Core/Monads/Alternative Monads/Fin/Fin.cs
Exception handling · Swallowed exception (caught, then discarded) LanguageExt.Core/Prelude/Value parsing/Prelude.Parse.cs
Exception handling · Swallowed exception (caught, then discarded) LanguageExt.Core/Prelude/Value parsing/Prelude.Parse.cs
Exception handling · Swallowed exception (caught, then discarded) LanguageExt.Core/Traits/Resolve/Resolver.cs
Outbound HTTP resilience · Outbound HTTP without resilience
Rebuild cost: about €120,000 · Estimate
Cost to rebuild
€41,000 to €200,000, for 676 to 2,132 hours of work, about 0.8 person-years for 1 to 2 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.7 at a score of 43. 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: 169,637 lines of product code, of which 39% is declarations and boilerplate, 38% straight logic and 23% logic with branches
Comment lines
The estimate prices 101,641 lines. Comment lines count towards the size of 169,637 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 No assertions (empty test) finding(s) in Test Quality — start with ApplicativeLawTests.cs, FunctorLawTests.cs, MonadLawsTest.cs.
Raises the score by about 5 points · Low effort · Test Quality
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 6 points · Medium effort · CI/CD gates
3
Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with LanguageExt.Streaming.csproj, LanguageExt.Rx.csproj, LanguageExt.Parsec.csproj.
Raises the score by about 2 points · Low effort · Explicit Debt
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.
Where the investment is most exposed · Value at risk
This code would cost about €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Production Readiness, at 26 (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.
If you do one thing first · First action
Resolve the 3 No assertions (empty test) finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 3 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
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.
32 modules, with 60 dependencies between them. One loop runs through 6 of the modules, marked above the diagonal.
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.
LanguageExt.Common uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Common, while a change to LanguageExt.Common can't break LanguageExt.Traits.
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.
9→15 LanguageExt.Common uses LanguageExtpart of a loop✕
Connections
16 pairs of types, where a type in LanguageExt.Common uses a type in LanguageExt.
LanguageExt.Common uses LanguageExt, so a change to LanguageExt can break LanguageExt.Common, while a change to LanguageExt.Common can't break LanguageExt.
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.
10→15 LanguageExt.Parsec uses LanguageExtpart of a loop✕
Connections
30 pairs of types, where a type in LanguageExt.Parsec uses a type in LanguageExt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.Parsec uses LanguageExt, so a change to LanguageExt can break LanguageExt.Parsec, while a change to LanguageExt.Parsec can't break LanguageExt.
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.
LanguageExt.Traits uses LanguageExt.Common, so a change to LanguageExt.Common can break LanguageExt.Traits, while a change to LanguageExt.Traits can't break LanguageExt.Common.
Position
Below the diagonal: LanguageExt.Traits uses a module listed above it, which is the healthy direction.
11→15 LanguageExt.Traits uses LanguageExtpart of a loop✕
Connections
88 pairs of types, where a type in LanguageExt.Traits uses a type in LanguageExt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.Traits uses LanguageExt, so a change to LanguageExt can break LanguageExt.Traits, while a change to LanguageExt.Traits can't break LanguageExt.
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.
102 pairs of types, where a type in LanguageExt.ClassInstances uses a type in LanguageExt.Traits. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.ClassInstances uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.ClassInstances, while a change to LanguageExt.ClassInstances can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.ClassInstances uses a module listed above it, which is the healthy direction.
12→15 LanguageExt.ClassInstances uses LanguageExtpart of a loop✕
Connections
94 pairs of types, where a type in LanguageExt.ClassInstances uses a type in LanguageExt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.ClassInstances uses LanguageExt, so a change to LanguageExt can break LanguageExt.ClassInstances, while a change to LanguageExt.ClassInstances can't break LanguageExt.
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.
1 pair of types, where a type in LanguageExt.ContT uses a type in LanguageExt.Traits.
The types involved
LanguageExt.ContT.ContT → LanguageExt.Traits.K
Direction
LanguageExt.ContT uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.ContT, while a change to LanguageExt.ContT can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.ContT uses a module listed above it, which is the healthy direction.
LanguageExt.Pipes uses LanguageExt.Common, so a change to LanguageExt.Common can break LanguageExt.Pipes, while a change to LanguageExt.Pipes can't break LanguageExt.Common.
Position
Below the diagonal: LanguageExt.Pipes uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in LanguageExt.Pipes uses a type in LanguageExt.Traits. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.Pipes uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Pipes, while a change to LanguageExt.Pipes can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Pipes uses a module listed above it, which is the healthy direction.
14→15 LanguageExt.Pipes uses LanguageExtpart of a loop✕
Connections
122 pairs of types, where a type in LanguageExt.Pipes uses a type in LanguageExt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.Pipes uses LanguageExt, so a change to LanguageExt can break LanguageExt.Pipes, while a change to LanguageExt.Pipes can't break LanguageExt.
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.
LanguageExt uses LanguageExt.Effects, so a change to LanguageExt.Effects can break LanguageExt, while a change to LanguageExt can't break LanguageExt.Effects.
Position
Below the diagonal: LanguageExt uses a module listed above it, which is the healthy direction.
LanguageExt uses LanguageExt.Traits.Domain, so a change to LanguageExt.Traits.Domain can break LanguageExt, while a change to LanguageExt can't break LanguageExt.Traits.Domain.
Position
Below the diagonal: LanguageExt uses a module listed above it, which is the healthy direction.
55 pairs of types, where a type in LanguageExt uses a type in LanguageExt.Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt uses LanguageExt.Common, so a change to LanguageExt.Common can break LanguageExt, while a change to LanguageExt can't break LanguageExt.Common.
Position
Below the diagonal: LanguageExt uses a module listed above it, which is the healthy direction.
LanguageExt uses LanguageExt.Parsec, so a change to LanguageExt.Parsec can break LanguageExt, while a change to LanguageExt can't break LanguageExt.Parsec.
Position
Below the diagonal: LanguageExt uses a module listed above it, which is the healthy direction.
305 pairs of types, where a type in LanguageExt uses a type in LanguageExt.Traits. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt, while a change to LanguageExt can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt uses a module listed above it, which is the healthy direction.
LanguageExt uses LanguageExt.ClassInstances, so a change to LanguageExt.ClassInstances can break LanguageExt, while a change to LanguageExt can't break LanguageExt.ClassInstances.
Position
Below the diagonal: LanguageExt uses a module listed above it, which is the healthy direction.
LanguageExt uses LanguageExt.Pipes, so a change to LanguageExt.Pipes can break LanguageExt, while a change to LanguageExt can't break LanguageExt.Pipes.
Position
Below the diagonal: LanguageExt uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in LanguageExt.Async uses a type in LanguageExt.
The types involved
LanguageExt.Async.Async → LanguageExt.ForkIO
Direction
LanguageExt.Async uses LanguageExt, so a change to LanguageExt can break LanguageExt.Async, while a change to LanguageExt.Async can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Async uses a module listed above it, which is the healthy direction.
LanguageExt.Benchmarks uses LanguageExt, so a change to LanguageExt can break LanguageExt.Benchmarks, while a change to LanguageExt.Benchmarks can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Benchmarks uses a module listed above it, which is the healthy direction.
LanguageExt.DSL uses LanguageExt.Common, so a change to LanguageExt.Common can break LanguageExt.DSL, while a change to LanguageExt.DSL can't break LanguageExt.Common.
Position
Below the diagonal: LanguageExt.DSL uses a module listed above it, which is the healthy direction.
65 pairs of types, where a type in LanguageExt.DSL uses a type in LanguageExt.Traits. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.DSL uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.DSL, while a change to LanguageExt.DSL can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.DSL uses a module listed above it, which is the healthy direction.
167 pairs of types, where a type in LanguageExt.DSL uses a type in LanguageExt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
35 pairs of types, where a type in LanguageExt.Megaparsec uses a type in LanguageExt.Traits. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.Megaparsec uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Megaparsec, while a change to LanguageExt.Megaparsec can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Megaparsec uses a module listed above it, which is the healthy direction.
LanguageExt.Megaparsec uses LanguageExt, so a change to LanguageExt can break LanguageExt.Megaparsec, while a change to LanguageExt.Megaparsec can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Megaparsec uses a module listed above it, which is the healthy direction.
LanguageExt.Pretty uses LanguageExt, so a change to LanguageExt can break LanguageExt.Pretty, while a change to LanguageExt.Pretty can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Pretty uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Traits uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Sys.Traits, while a change to LanguageExt.Sys.Traits can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Sys.Traits uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Traits uses LanguageExt, so a change to LanguageExt can break LanguageExt.Sys.Traits, while a change to LanguageExt.Sys.Traits can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Sys.Traits uses a module listed above it, which is the healthy direction.
LanguageExt.Traits.Range uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Traits.Range, while a change to LanguageExt.Traits.Range can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Traits.Range uses a module listed above it, which is the healthy direction.
LanguageExt.Traits.Range uses LanguageExt, so a change to LanguageExt can break LanguageExt.Traits.Range, while a change to LanguageExt.Traits.Range can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Traits.Range uses a module listed above it, which is the healthy direction.
LanguageExt.UnsafeValueAccess uses LanguageExt, so a change to LanguageExt can break LanguageExt.UnsafeValueAccess, while a change to LanguageExt.UnsafeValueAccess can't break LanguageExt.
Position
Below the diagonal: LanguageExt.UnsafeValueAccess uses a module listed above it, which is the healthy direction.
36 pairs of types, where a type in LanguageExt.Megaparsec.DSL uses a type in LanguageExt.Traits. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.Megaparsec.DSL uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Megaparsec.DSL, while a change to LanguageExt.Megaparsec.DSL can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Megaparsec.DSL uses a module listed above it, which is the healthy direction.
LanguageExt.Megaparsec.DSL uses LanguageExt, so a change to LanguageExt can break LanguageExt.Megaparsec.DSL, while a change to LanguageExt.Megaparsec.DSL can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Megaparsec.DSL uses a module listed above it, which is the healthy direction.
222 pairs of types, where a type in LanguageExt.Megaparsec.DSL uses a type in LanguageExt.Megaparsec. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
LanguageExt.Megaparsec.DSL uses LanguageExt.Megaparsec, so a change to LanguageExt.Megaparsec can break LanguageExt.Megaparsec.DSL, while a change to LanguageExt.Megaparsec.DSL can't break LanguageExt.Megaparsec.
Position
Below the diagonal: LanguageExt.Megaparsec.DSL uses a module listed above it, which is the healthy direction.
LanguageExt.Sys uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Sys, while a change to LanguageExt.Sys can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Sys uses a module listed above it, which is the healthy direction.
LanguageExt.Sys uses LanguageExt.Pipes, so a change to LanguageExt.Pipes can break LanguageExt.Sys, while a change to LanguageExt.Sys can't break LanguageExt.Pipes.
Position
Below the diagonal: LanguageExt.Sys uses a module listed above it, which is the healthy direction.
LanguageExt.Sys uses LanguageExt.Sys.Traits, so a change to LanguageExt.Sys.Traits can break LanguageExt.Sys, while a change to LanguageExt.Sys can't break LanguageExt.Sys.Traits.
Position
Below the diagonal: LanguageExt.Sys uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Diag uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Sys.Diag, while a change to LanguageExt.Sys.Diag can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Sys.Diag uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Diag uses LanguageExt, so a change to LanguageExt can break LanguageExt.Sys.Diag, while a change to LanguageExt.Sys.Diag can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Sys.Diag uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Diag uses LanguageExt.Sys.Traits, so a change to LanguageExt.Sys.Traits can break LanguageExt.Sys.Diag, while a change to LanguageExt.Sys.Diag can't break LanguageExt.Sys.Traits.
Position
Below the diagonal: LanguageExt.Sys.Diag uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.IO uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Sys.IO, while a change to LanguageExt.Sys.IO can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Sys.IO uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.IO uses LanguageExt.Pipes, so a change to LanguageExt.Pipes can break LanguageExt.Sys.IO, while a change to LanguageExt.Sys.IO can't break LanguageExt.Pipes.
Position
Below the diagonal: LanguageExt.Sys.IO uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in LanguageExt.Sys.IO uses a type in LanguageExt.
The types involved
LanguageExt.Sys.IO.Directory → LanguageExt.Option
LanguageExt.Sys.IO.Directory → LanguageExt.Seq
LanguageExt.Sys.IO.Directory → LanguageExt.Unit
LanguageExt.Sys.IO.File → LanguageExt.Seq
LanguageExt.Sys.IO.File → LanguageExt.Unit
LanguageExt.Sys.IO.Stream → LanguageExt.SeqLoan
LanguageExt.Sys.IO.Stream → LanguageExt.Unit
LanguageExt.Sys.IO.TextRead → LanguageExt.SeqLoan
LanguageExt.Sys.IO.TextRead → LanguageExt.Unit
Direction
LanguageExt.Sys.IO uses LanguageExt, so a change to LanguageExt can break LanguageExt.Sys.IO, while a change to LanguageExt.Sys.IO can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Sys.IO uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.IO uses LanguageExt.Sys.Traits, so a change to LanguageExt.Sys.Traits can break LanguageExt.Sys.IO, while a change to LanguageExt.Sys.IO can't break LanguageExt.Sys.Traits.
Position
Below the diagonal: LanguageExt.Sys.IO uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Live uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Sys.Live, while a change to LanguageExt.Sys.Live can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Sys.Live uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Live uses LanguageExt, so a change to LanguageExt can break LanguageExt.Sys.Live, while a change to LanguageExt.Sys.Live can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Sys.Live uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Live uses LanguageExt.Sys.Traits, so a change to LanguageExt.Sys.Traits can break LanguageExt.Sys.Live, while a change to LanguageExt.Sys.Live can't break LanguageExt.Sys.Traits.
Position
Below the diagonal: LanguageExt.Sys.Live uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Live.Implementations uses LanguageExt, so a change to LanguageExt can break LanguageExt.Sys.Live.Implementations, while a change to LanguageExt.Sys.Live.Implementations can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Sys.Live.Implementations uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Live.Implementations uses LanguageExt.Sys.Traits, so a change to LanguageExt.Sys.Traits can break LanguageExt.Sys.Live.Implementations, while a change to LanguageExt.Sys.Live.Implementations can't break LanguageExt.Sys.Traits.
Position
Below the diagonal: LanguageExt.Sys.Live.Implementations uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Test.Implementations uses LanguageExt, so a change to LanguageExt can break LanguageExt.Sys.Test.Implementations, while a change to LanguageExt.Sys.Test.Implementations can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Sys.Test.Implementations uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Test.Implementations uses LanguageExt.Sys.Traits, so a change to LanguageExt.Sys.Traits can break LanguageExt.Sys.Test.Implementations, while a change to LanguageExt.Sys.Test.Implementations can't break LanguageExt.Sys.Traits.
Position
Below the diagonal: LanguageExt.Sys.Test.Implementations uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Test.Implementations uses LanguageExt.Sys, so a change to LanguageExt.Sys can break LanguageExt.Sys.Test.Implementations, while a change to LanguageExt.Sys.Test.Implementations can't break LanguageExt.Sys.
Position
Below the diagonal: LanguageExt.Sys.Test.Implementations uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Test uses LanguageExt.Traits, so a change to LanguageExt.Traits can break LanguageExt.Sys.Test, while a change to LanguageExt.Sys.Test can't break LanguageExt.Traits.
Position
Below the diagonal: LanguageExt.Sys.Test uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Test uses LanguageExt, so a change to LanguageExt can break LanguageExt.Sys.Test, while a change to LanguageExt.Sys.Test can't break LanguageExt.
Position
Below the diagonal: LanguageExt.Sys.Test uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Test uses LanguageExt.Sys.Traits, so a change to LanguageExt.Sys.Traits can break LanguageExt.Sys.Test, while a change to LanguageExt.Sys.Test can't break LanguageExt.Sys.Traits.
Position
Below the diagonal: LanguageExt.Sys.Test uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Test uses LanguageExt.Sys, so a change to LanguageExt.Sys can break LanguageExt.Sys.Test, while a change to LanguageExt.Sys.Test can't break LanguageExt.Sys.
Position
Below the diagonal: LanguageExt.Sys.Test uses a module listed above it, which is the healthy direction.
LanguageExt.Sys.Test uses LanguageExt.Sys.Test.Implementations, so a change to LanguageExt.Sys.Test.Implementations can break LanguageExt.Sys.Test, while a change to LanguageExt.Sys.Test can't break LanguageExt.Sys.Test.Implementations.
Position
Below the diagonal: LanguageExt.Sys.Test uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 54% · Adequate · gated by X1 ·
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
A01:2025 — Broken Access Control
2
High / Critical
Roadmap
First, establish a CI workflow to build and test every change, while immediately fixing empty tests in the law verification suites. Next, restrict the public API by making types internal by default to protect against breaking changes. Then, ensure all outbound HTTP calls have explicit timeouts and cancellation tokens to prevent hanging on slow endpoints. Finally, implement encryption for sensitive data at rest and manage keys securely, unless this is already handled by infrastructure.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with ApplicativeLawTests.cs, FunctorLawTests.cs, MonadLawsTest.cs.
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
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 — 29
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 — 837
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 — 92
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
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. 66 of 70 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 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 — 70 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, 937 of 958 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.
D11 Test Reliability — 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. Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 1435 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
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: Samples/TestBed.WPF/TestBed.WPF.csproj : error NU1201: Project LanguageExt.Core is not compatible with net8.0-windows7.0 (.NETCoreApp,Version=v8.0). Project LanguageExt.Core supports: net10.0 (.NETCoreApp,Version=v10.0) [/tmp/codehealth-iso-314717….
D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (102 contributor(s) across 4061 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 101 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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 'LanguageExt.Parsec/LanguageExt.Parsec.csproj' with message: PackageReference System.ValueTuple will not be pruned. This package is automatically available and does not need to be referenced explicitly. Remove the PackageReference item.
D18 Solution Shape — 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 build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
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 (169,637 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"]`.
D32 Data Compliance (PII/GDPR) — 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. `LanguageExt.Core/Catch.cs`, `LanguageExt.Core/Comment Alternatives.cs`, `LanguageExt.Core/Common/ErrorException.cs`, `LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs`, `LanguageExt.Core/Concurrency/STM/STM.cs`, … (+296 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 build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. 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 (Samples/TestBed.WPF/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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for Samples/TestBed.WPF/TestBed.WPF.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
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.
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.
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.
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.
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.
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").
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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.
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 (4): D19, D21, D24, 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.
15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Internal.chaini at 29. A further 10 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 Layout.layout at 26 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: LanguageExt.Core/Pretty/Layout.cs (Layout.layout at 26), LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs (AtomSeq.Concat at 24), LanguageExt.Core/Immutable Collections/Seq/Seq.cs (Seq.Concat at 17), LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs (ValidationExtensions.ApplyI at 17), LanguageExt.Core/Units of Measure/Temperature.cs (Temperature.Equals at 17). 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.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Internal.chaini (cyclomatic 29), InternalIO.chaini (cyclomatic 29), Patch.Combine (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 15 together lifts Cyclomatic Complexity from 8.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cyclomatic Complexity 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: 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.
+ 25 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with Internal.chaini (cognitive 74), InternalIO.chaini (cognitive 74). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Stand up a CI pipeline, then gate Cognitive Complexity 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: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.9 / 10Adequate✓ 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 102 TooManyMethods finding(s) in God Classes — start with Prim.cs (3), Eff.cs (2), Prelude.Collections.cs. — One of this dimension's main actionable groups (102 warning-level).
Resolve the 16 FileTooLong finding(s) in God Classes — start with TrieMap.cs, Map.Internal.cs, AtomHashMap.Eq.cs. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 2 MethodTooLong finding(s) in God Classes — start with Token.cs, Token2.cs. — One of this dimension's main actionable groups (2 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.
303 duplicated block group(s) detected. A further 35 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 9 of the 338 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.
+ 93 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 28 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with AtomHashMap.Eq.cs (12), Map.Internal.cs (3), Foldable.Trait.cs (3). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 23 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Foldable.Trait.cs (4), TrieMap.cs (3), Iterable.Add.cs (2). — One of this dimension's main actionable groups (23 warning-level).
Resolve the 16 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with AtomHashMap.Eq.cs (9), Atom.Metadata.cs, ValueTuple6.Extensions.cs. — One of this dimension's main actionable groups (16 warning-level).
Stand up a CI pipeline, then gate Code Duplication 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 Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.7 / 10Stronggated by 1 serious finding✓ 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: LanguageExt.CoreLanguageExt.Core/LanguageExt.Core.csproj:1
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling — start with LanguageExt.Core.csproj. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Coupling 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: 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.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with SeqLazy.cs. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cohesion (LCOM4) 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 Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.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.
1435 test methods: 1435 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 Quality8.9 / 10Adequategated by 3 critical findings✓ 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, 99 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1435 tests.
No assertions (empty test): StreamT · ×3LanguageExt.Tests/TraitTests/ApplicativeLawTests.cs:57
No assertions: DeriveBluebird · ×96LanguageExt.Tests/CombinatorsTests.cs:24
What to do
Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with ApplicativeLawTests.cs, FunctorLawTests.cs, MonadLawsTest.cs. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 96 No assertions finding(s) in Test Quality — start with FunctorLawTests.cs (17), ApplicativeLawTests.cs (15), MonadLawsTest.cs (15). — One of this dimension's main actionable groups (96 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.
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.
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 210 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 16 direct `PackageReference`(s), and 186 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: 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.
251 deducted debt markers + unmeasured dead symbols across 169637 LoC in the .NET projects (0.7/KLoC) → score 8.6. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
FileScopedPragmaDisable repeated across 24 filesLanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 EmptyCatchBlock finding(s) in Explicit Debt — start with ResourcesDiscussion1366.cs (3), IO.cs (2), Task.Prelude.cs. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 6 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Seq.Enumerable.Tests.cs (2), ListIterationBenchmarks.cs, EnvIO.cs. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with LanguageExt.Streaming.csproj, LanguageExt.Rx.csproj, LanguageExt.Parsec.csproj. — One of this dimension's main actionable groups (5 issue-level).
Stand up a CI pipeline, then gate Explicit Debt 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: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
23 projects, 1755 source files, 189939 hand-written lines of code (169637 production / 20302 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), 50 inter-project edges (build status unknown — did not finish).
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 is a strong overview of the library (C#-based pure functional framework for declarative code) and its author's personal links plus an outline of Contents. The LanguageExt.Core/README.md files document their own directories (Prelude, Concurrency, Immutable Collections), each with focused content on modules like Effects, Pipes, Monads, Traits, and Error; the root README is the only one mentioning installation, usage examples, or contribution guidance. All visible documents are well-structured per an outline, but no single file is flagged as missing any of the standard sections (installation/usage/contributing) for its own directory. The repository's READMEs are well written for their deploy tiers: each one is a directory README documenting what it contains (an EffectsExamples sample, a release notes section, an Atom usage example) and the body explains the feature with examples. The architecture/design docs are absent from this summary, but XML-doc coverage across 37 documents shows high documentation quality (9920/14296 for LanguageExt.Core).
Resolve the 13 Low XML-doc coverage finding(s) in Documentation Quality — start with LanguageExt.Parsec.csproj, TestBed.csproj, LanguageExt.Benchmarks.csproj. — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
2 of 23 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability5.0 / 10Weak✓ Tool-verified
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.
56 % of calls cross a namespace and 3 % go through an interface, but 46 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
Scattered collaborators
What to do
Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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).
semgrep found no security issues. semgrep hit a parse error in 310 file(s) — `LanguageExt.Core/Catch.cs` (line 18, lines 19–21, line 24), `LanguageExt.Core/Comment Alternatives.cs` (line 11), `LanguageExt.Core/Common/ErrorException.cs` (line 186, line 249, line 250, …), `LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs` (lines 9–10, line 73), `LanguageExt.Core/Concurrency/STM/STM.cs` (line 490), … (+305 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 30 of those file(s) — `LanguageExt.Core/Common/ErrorException.cs`, `LanguageExt.Core/Concurrency/Signals/CountdownSignal.cs`, `LanguageExt.Core/Concurrency/Signals/Signal.cs`, `LanguageExt.Core/Extensions/ActionObservable.cs`, `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs`, … (+25 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 119 of those file(s) — `LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs`, `LanguageExt.Core/DataTypes/Fail/Fail.Extensions.cs`, `LanguageExt.Core/DataTypes/Loop/Loop.Extensions.cs`, `LanguageExt.Core/DataTypes/Pure/Pure.Extensions.cs`, `LanguageExt.Core/Effects/Eff/Eff no runtime/Operators/Eff.Operators.Applicative.cs`, … (+114 more) — 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.
✓ On the Gold path — maintain.
Detailed fixes: d29_recommendation.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)5.0 / 10Adequate✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. semgrep could not parse 301 file(s) — `LanguageExt.Core/Catch.cs`, `LanguageExt.Core/Comment Alternatives.cs`, `LanguageExt.Core/Common/ErrorException.cs`, `LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.LINQ.Extensions.cs`, `LanguageExt.Core/Concurrency/STM/STM.cs`, … (+296 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
3 of 602 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is LanguageExt.Core/Effects/Schedule/Duration.cs. Counted over 602 of the 1389 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 2 Change coupling finding(s) in Change Coupling — start with Effect.cs, Consumer.cs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 23 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.
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 LanguageExt ↔ LanguageExt.ClassInstances ↔ LanguageExt.Common ↔ LanguageExt.Parsec ↔ LanguageExt.Pipes ↔ LanguageExt.Traits depend on each other. The lightest dependency in the cycle is LanguageExt → LanguageExt.Parsec (LanguageExt.ParsecPipes → LanguageExt.Parsec.PString, 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. — LanguageExt.Parsec/Pipes.cs:4
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.
`Alternative<F>` declares 22 members: `Empty`, `Choice`, `Choice`, `Some`, `Many`, `EndBy`, `EndBy1`, `Either`, `ManyUntil`, `ManyUntil2`, `SomeUntil`, `SomeUntil2`, `Option`, `SepBy`, `SepBy1`, `SepByEnd`, `SepByEnd1`, `SkipMany`, `SkipSome`, `Skip`, `SkipManyUntil`, `SkipSomeUntil`. 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. Those 22 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — LanguageExt.Core/Traits/Alternative/Alternative.Trait.cs:7
`Applicative<F>` declares 16 members under just 7 distinct name(s): `Pure`, `Apply`, `Apply`, `Apply`, `Apply`, `Action`, `BackAction`, `Action`, `BackAction`, `Action`, `BackAction`, `Action`, `BackAction`, `Actions`, `Between`, `Replicate`. 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. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 7 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — LanguageExt.Core/Traits/Applicative/Applicative.Trait.cs:16
`Floating<A>` declares 18 members: `Pi`, `Exp`, `Sqrt`, `Log`, `Pow`, `LogBase`, `Sin`, `Cos`, `Tan`, `Asin`, `Acos`, `Atan`, `Sinh`, `Cosh`, `Tanh`, `Asinh`, `Acosh`, `Atanh`. 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. — LanguageExt.Core/Traits/Floating/Floating.cs:10
`Foldable<T>` declares 58 members: `FoldStep`, `FoldStepBack`, `FoldWhile`, `FoldBackWhile`, `FoldMaybe`, `FoldBackMaybe`, `FoldWhileM`, `FoldBackWhileM`, `FoldUntil`, `FoldUntilM`, `FoldBackUntil`, `FoldBackUntilM`, `Fold`, `FoldM`, `FoldBack`, `FoldBackM`, `Fold`, `FoldWhile`, `FoldUntil`, `FoldMap`, `FoldMapWhile`, `FoldMapUntil`, `FoldMapBack`, `FoldMapWhileBack`, `FoldMapUntilBack`, `ToSeq`, `ToLst`, `ToArr`, `ToIterable`, `IsEmpty`, `Count`, `Exists`, `ForAll`, `Contains`, `Contains`, `Find`, `FindBack`, `FindAll`, `FindAllBack`, `Sum`, and 18 more. 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. Those 58 declarations carry 45 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 45 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:10
`MonadUnliftIO<M>` declares 73 members: `ToIO`, `MapIO`, `ForkIO`, `Await`, `LocalIO`, `UninterruptibleIO`, `PostIO`, `TimeoutIO`, `BracketIO`, `BracketIO`, `BracketIO`, `RepeatIO`, `RepeatIO`, `RepeatWhileIO`, `RepeatWhileIO`, `RepeatUntilIO`, `RepeatUntilIO`, `RetryIO`, `RetryIO`, `RetryWhileIO`, `RetryWhileIO`, `RetryUntilIO`, `RetryUntilIO`, `FoldIO`, `FoldIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldUntilIO`, `FoldUntilIO`, `FoldUntilIO`, `FoldUntilIO`, `FoldUntilIO`, `FoldUntilIO`, `LanguageExt.Traits.Maybe.MonadUnliftIO<M>.MapIOMaybe`, `LanguageExt.Traits.Maybe.MonadUnliftIO<M>.ToIOMaybe`, `LanguageExt.Traits.Maybe.MonadUnliftIO<M>.ForkIOMaybe`, and 33 more. 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. Those 73 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — LanguageExt.Core/Traits/Monads/MonadUnliftIO/MonadUnliftIO.Trait.cs:19
`DirectoryIO` declares 30 members: `Create`, `Delete`, `GetParent`, `Exists`, `SetCreationTime`, `SetCreationTimeUtc`, `GetCreationTime`, `GetCreationTimeUtc`, `SetLastWriteTime`, `SetLastWriteTimeUtc`, `GetLastWriteTime`, `GetLastWriteTimeUtc`, `SetLastAccessTime`, `SetLastAccessTimeUtc`, `GetLastAccessTime`, `GetLastAccessTimeUtc`, `EnumerateDirectories`, `EnumerateDirectories`, `EnumerateDirectories`, `EnumerateFiles`, `EnumerateFiles`, `EnumerateFiles`, `EnumerateFileSystemEntries`, `EnumerateFileSystemEntries`, `EnumerateFileSystemEntries`, `GetDirectoryRoot`, `GetCurrentDirectory`, `SetCurrentDirectory`, `Move`, `GetLogicalDrives`. 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. Those 30 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — LanguageExt.Sys/Traits/DirectoryIO.cs:6
`EnvironmentIO` declares 34 members: `CommandLine`, `CurrentManagedThreadId`, `Exit`, `ExitCode`, `SetExitCode`, `ExpandEnvironmentVariables`, `FailFast`, `FailFast`, `GetCommandLineArgs`, `GetEnvironmentVariable`, `GetEnvironmentVariable`, `GetEnvironmentVariables`, `GetEnvironmentVariables`, `GetFolderPath`, `GetFolderPath`, `GetLogicalDrives`, `HasShutdownStarted`, `Is64BitOperatingSystem`, `Is64BitProcess`, `MachineName`, `NewLine`, `OSVersion`, `ProcessorCount`, `SetEnvironmentVariable`, `SetEnvironmentVariable`, `StackTrace`, `SystemDirectory`, `SystemPageSize`, `TickCount`, `UserDomainName`, `UserInteractive`, `UserName`, `Version`, `WorkingSet`. 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. Those 34 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — LanguageExt.Sys/Traits/EnvironmentIO.cs:5
`FileIO` declares 19 members: `Copy`, `Move`, `Move`, `AppendAllLines`, `ReadAllLines`, `ReadAllText`, `ReadAllBytes`, `WriteAllText`, `WriteAllLines`, `WriteAllBytes`, `Delete`, `Exists`, `OpenText`, `CreateText`, `AppendText`, `OpenRead`, `Open`, `Open`, `OpenWrite`. 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. Those 19 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — LanguageExt.Sys/Traits/FileIO.cs:7
`MonadParsecT<MP, E, S, T, M>` declares 17 members: `Error`, `Label`, `Hidden`, `Try`, `LookAhead`, `NotFollowedBy`, `WithRecovery`, `EOF`, `Observing`, `Token`, `Tokens`, `OneOf`, `NoneOf`, `TakeWhile`, `TakeWhile1`, `Take`, `Lift`. 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. — LanguageExt.Megaparsec/MonadParsecT/MonadParsecT.cs:21
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
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.
Do you agree with this assessment?
C1 · Data Protection3.0 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
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. (×11) — LanguageExt.Core/Common/ErrorException.cs:471, LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:25, LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:36, …
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.
`Compare` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — LanguageExt.Core/Class Instances/Ord/OrdTrue.cs:10
`Combine` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LanguageExt.Core/Common/ErrorException.cs:471
`SelectMany` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — LanguageExt.Core/DataTypes/Fail/Fail.cs:41
Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 443 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. (×2) — LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:449, LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:457
Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 467 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. (×2) — LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:473, LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:481
Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 506 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. (×2) — LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:512, LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:520
Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 531 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. (×2) — LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:537, LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:545
`CompareTo` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:25, LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:36, LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:46
`TryConvertFromChecked` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LanguageExt.Megaparsec/Pos.cs:137
`TryConvertFromSaturating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LanguageExt.Megaparsec/Pos.cs:140
`TryConvertFromTruncating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LanguageExt.Megaparsec/Pos.cs:143
`TryConvertToChecked` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LanguageExt.Megaparsec/Pos.cs:146
`TryConvertToSaturating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LanguageExt.Megaparsec/Pos.cs:149
`TryConvertToTruncating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LanguageExt.Megaparsec/Pos.cs:152
`TryFormat` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LanguageExt.Megaparsec/Pos.cs:210
The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. (×2) — LanguageExt.Parsec/Parsec.Internal.cs:119, LanguageExt.Parsec/ParsecIO.Internal.cs:113
3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). (×10) — LanguageExt.Core/Class Instances/Monoid/Addition.cs:2, LanguageExt.Core/Class Instances/Monoid/MError.cs:2, LanguageExt.Core/Class Instances/Monoid/Product.cs:2, …
4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — LanguageExt.Core/Deriving/Maybe/MonadUnliftIO.cs:37
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — LanguageExt.Core/Immutable Collections/Arr/Arr.cs:703, LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1312, LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2257, …
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.
What to do
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 21 of 23 project(s) that lack one — worth up to 1.8 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 10/23 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.
README.md names the project `LanguageExt.Prelude`, 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.md:77
Major Version Release Notes/Version 5/README.md names the project `LanguageExt.SysX`, 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. — Major Version Release Notes/Version 5/README.md:89
Major Version Release Notes/Version 5/README.md names the project `LanguageExt.CodeGen`, 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. — Major Version Release Notes/Version 5/README.md:90
Major Version Release Notes/Version 5/README.md names the project `LanguageExt.Transformers`, 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. — Major Version Release Notes/Version 5/README.md:91
Major Version Release Notes/Version 5/README.md names the project `LanguageExt.Prelude`, 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. — Major Version Release Notes/Version 5/README.md:735
Major Version Release Notes/Version 5/README.md names the project `LanguageExt.UnitsOfMeasure`, 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. — Major Version Release Notes/Version 5/README.md:735
What to do
Reconcile the README with reality: README.md names the project `LanguageExt.Prelude`, but no project, folder or namespace of that name exists; Major Version Release Notes/Version 5/README.md names the project `LanguageExt.SysX`, but no project, folder or namespace of that name exists; Major Version Release Notes/Version 5/README.md names the project `LanguageExt.CodeGen`, but no project, folder or namespace of that name exists; Major Version Release Notes/Version 5/README.md names the project `LanguageExt.Transformers`, but no project, folder or namespace of that name exists; Major Version Release Notes/Version 5/README.md names the project `LanguageExt.Prelude`, but no project, folder or namespace of that name exists.
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.
Do you agree with this assessment?
P10 · Library API & versioning2.0 / 10Critical✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
1902/2239 types (85%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
Do you agree with this assessment?
P2 · Observability6.6 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/5 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 5, 4 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.
Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
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.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
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 · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. (×3) — Samples/Newsletter/Newsletter/Effects/Runtime.cs:31, Samples/Newsletter/Newsletter/Effects/Runtime.cs:40, Samples/TestBed.Web.Runner/Program.cs:5
What to do
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
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.
A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way hot code pressures the GC) aren't being measured.
What to do
Add [MemoryDiagnoser] to the benchmarks so allocation regressions are visible, not just time.
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.
What to do
Raise allocation-aware density on the hot paths — currently 658 use(s) across 171,534 production line(s) (~3.8/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
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.
16 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).
`.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). (×16) — LanguageExt.Core/Effects/IO/DSL/IOFold.cs:145, LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:159, LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:168, …
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.
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. (×24) — LanguageExt.Core/Concurrency/Task/Task.Extensions.cs:230, LanguageExt.Core/Concurrency/Task/Task.Extensions.cs:235, LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:167, …
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. (×10) — LanguageExt.Core/Effects/IO/IO.cs:411, LanguageExt.Core/Effects/IO/IO.cs:716, LanguageExt.Core/Effects/IO/IO.cs:744, …
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.
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 26/59 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. (×21) — LanguageExt.Core/Concurrency/ValueTask/ValueTask.Extensions.cs:290, LanguageExt.Core/Effects/Eff/Eff with runtime/Extensions/Eff.Extensions.cs:84, LanguageExt.Core/Effects/Eff/Eff with runtime/Extensions/Eff.Extensions.cs:103, …
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. (×9) — LanguageExt.Core/Effects/IO/DSL/IOFold.cs:66, LanguageExt.Core/Effects/IO/DSL/IOFold.cs:105, LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:70, …
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. (×2) — LanguageExt.Sys/Sys/IO/Stream.cs:22, LanguageExt.Sys/Sys/IO/TextRead.cs:36
This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on. — Samples/TestBed.Web/Program.cs:14
8 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
Holds a CancellationToken but hands `default` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). (×5) — LanguageExt.Core/Concurrency/Task/Tasks.cs:15, LanguageExt.Core/Concurrency/Task/Tasks.cs:22, LanguageExt.Core/Concurrency/Task/Tasks.cs:29, …
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. (×5) — LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:149, LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:146, Samples/TestBed/ResourcesDiscussion1366.cs:37, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×2) — LanguageExt.Core/Effects/IO/IO.cs:1030, LanguageExt.Core/Effects/IO/IO.cs:1031
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.
21/22 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.
~0.5 `!` suppressions per 1k syntax nodes — 394 suppression(s) across the 805290 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 — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
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 — 43 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.
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.
D11 Test Reliability — Test runner surfaced no tests
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
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.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — 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
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.
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 193 value object(s); a Domain/Aggregates/ValueObjects layer
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
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.
EmptyCatchBlock LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:149— 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 LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:146— 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 LanguageExt.Core/Effects/IO/IO.cs:1030— 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 LanguageExt.Core/Effects/IO/IO.cs:1031— 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 Samples/TestBed/ResourcesDiscussion1366.cs:37— 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 Samples/TestBed/ResourcesDiscussion1366.cs:56— 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 Samples/TestBed/ResourcesDiscussion1366.cs:75— 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.
WriteOnlyPrivateField LanguageExt.Benchmarks/ListIterationBenchmarks.cs:18— private T[] values — 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.
WriteOnlyPrivateField LanguageExt.Core/Effects/IO/EnvIO.cs:20— private EnvIO DisposeEnv — 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.
WriteOnlyPrivateField LanguageExt.Tests/OptionUnsafeApply.cs:9— private Func<int, int, int> add — 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.
WriteOnlyPrivateField LanguageExt.Tests/SeqTypes/Seq.Enumerable.Tests.cs:20— private IEnumerable<char> edcbaChars — 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.
WriteOnlyPrivateField LanguageExt.Tests/SeqTypes/Seq.Enumerable.Tests.cs:22— private IEnumerable<string> edcbaStrs — 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.
WriteOnlyPrivateField Samples/TestBed/Issues/Discussion1527.cs:143— private IO<Option<IObservation>> NoObservations — 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.
NoWarnInCsproj — 10 warning codes suppressed in one element LanguageExt.Streaming/LanguageExt.Streaming.csproj:6— A single <NoWarn> suppresses 10 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587) in one stroke — one team-wide decision, not 10 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 — 10 warning codes suppressed in one element LanguageExt.Rx/LanguageExt.Rx.csproj:6— A single <NoWarn> suppresses 10 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587) in one stroke — one team-wide decision, not 10 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 — 10 warning codes suppressed in one element LanguageExt.Parsec/LanguageExt.Parsec.csproj:6— A single <NoWarn> suppresses 10 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587) in one stroke — one team-wide decision, not 10 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 — 10 warning codes suppressed in one element LanguageExt.FSharp/LanguageExt.FSharp.csproj:7— A single <NoWarn> suppresses 10 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587) in one stroke — one team-wide decision, not 10 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 — 11 warning codes suppressed in one element LanguageExt.Core/LanguageExt.Core.csproj:6— A single <NoWarn> suppresses 11 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587;CA2260) in one stroke — one team-wide decision, not 11 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.)
FileScopedPragmaDisable LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Enumerable.cs:1— #pragma warning disable CS1998 — 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 LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Singleton.cs:1— #pragma warning disable CS1998 // Async method lacks 'await' operators and will run synchronously — 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 LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.SingletonIO.cs:1— #pragma warning disable CS1998 // Async method lacks 'await' operators and will run synchronously — 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 LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Strict.cs:1— #pragma warning disable CS1998 // Async method lacks 'await' operators and will run synchronously — 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.
D10 · Test Quality· No assertions (empty test) · ×3
No assertions (empty test): StreamT LanguageExt.Tests/TraitTests/ApplicativeLawTests.cs:57— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): StreamT LanguageExt.Tests/TraitTests/FunctorLawTests.cs:101— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): StreamT LanguageExt.Tests/TraitTests/MonadLawsTest.cs:58— Test method has an empty body — it asserts nothing and exercises no code.
Namespace dependency cycle LanguageExt.Parsec/Pipes.cs:4— The namespaces LanguageExt ↔ LanguageExt.ClassInstances ↔ LanguageExt.Common ↔ LanguageExt.Parsec ↔ LanguageExt.Pipes ↔ LanguageExt.Traits depend on each other. The lightest dependency in the cycle is LanguageExt → LanguageExt.Parsec (LanguageExt.ParsecPipes → LanguageExt.Parsec.PString, 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.
FileScopedPragmaDisable repeated across 24 files LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1— The identical FileScopedPragmaDisable (`#pragma warning disable CS0693 // Type parameter has the same name as the type parameter from outer type`) appears in 24 files (24 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 24 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
TooManyMethods: Prelude LanguageExt.Core/Immutable Collections/Prelude.Collections.cs— TooManyMethods — 4317 significant lines (blank, comment-only and punctuation-only lines excluded), 1158 methods, declared across 90 files: Immutable Collections/Prelude.Collections.cs (143), Currying and Partial Application/Prelude.PartialApplication.cs (91), Lambda function inference/Prelude.Func.cs (63), Value parsing/Prelude.Parse.cs (48), +86 more file(s). The bar is 30 methods; this is 1128 over it, 38.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: TrieMap LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs— TooManyMethods — 1051 significant lines (blank, comment-only and punctuation-only lines excluded), 158 methods. The bar is 30 methods; this is 128 over it, 5.27× 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: Map LanguageExt.Core/Immutable Collections/Map/Map.Module.cs— TooManyMethods — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 156 methods, declared across 2 files: Map/Map.Module.cs (80), Map/Map.Module.Ord.cs (76). The bar is 30 methods; this is 126 over it, 5.20× 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: Map LanguageExt.Core/Immutable Collections/Map/Map.cs— TooManyMethods — 622 significant lines (blank, comment-only and punctuation-only lines excluded), 145 methods. The bar is 30 methods; this is 115 over it, 4.83× 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: TrackingHashMap LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.cs— TooManyMethods — 489 significant lines (blank, comment-only and punctuation-only lines excluded), 135 methods. The bar is 30 methods; this is 105 over it, 4.50× 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: TrackingHashMap LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.cs— TooManyMethods — 488 significant lines (blank, comment-only and punctuation-only lines excluded), 135 methods. The bar is 30 methods; this is 105 over it, 4.50× 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: Map LanguageExt.Core/Immutable Collections/Map/Map.Ord.cs— TooManyMethods — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 134 methods. The bar is 30 methods; this is 104 over it, 4.47× 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: bigint LanguageExt.Core/DataTypes/BigInt/BigInt.cs— TooManyMethods — 287 significant lines (blank, comment-only and punctuation-only lines excluded), 130 methods. The bar is 30 methods; this is 100 over it, 4.33× 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: HashMap LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs— TooManyMethods — 575 significant lines (blank, comment-only and punctuation-only lines excluded), 129 methods. The bar is 30 methods; this is 99 over it, 4.30× 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: HashMap LanguageExt.Core/Immutable Collections/HashMap/HashMap.cs— TooManyMethods — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 123 methods. The bar is 30 methods; this is 93 over it, 4.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: AtomHashMap LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs— TooManyMethods — 955 significant lines (blank, comment-only and punctuation-only lines excluded), 118 methods. The bar is 30 methods; this is 88 over it, 3.93× 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: TrackingHashMap LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Module.Eq.cs— TooManyMethods — 356 significant lines (blank, comment-only and punctuation-only lines excluded), 118 methods, declared across 2 files: TrackingHashMap/TrackingHashMap.Module.Eq.cs (59), TrackingHashMap/TrackingHashMap.Module.cs (59). The bar is 30 methods; this is 88 over it, 3.93× 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: AtomHashMap LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs— TooManyMethods — 962 significant lines (blank, comment-only and punctuation-only lines excluded), 117 methods. The bar is 30 methods; this is 87 over it, 3.90× 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: Applicative LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Apply.cs— TooManyMethods — 618 significant lines (blank, comment-only and punctuation-only lines excluded), 112 methods, declared across 12 files: Module/Applicative.Module.Apply.cs (19), Module/Applicative.Module.Memo.Apply.cs (19), Module/Applicative.Module.Memo.Lift.cs (17), Module/Applicative.Module.ApplyM.cs (9), +8 more file(s). The bar is 30 methods; this is 82 over it, 3.73× 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: HashMap LanguageExt.Core/Immutable Collections/HashMap/HashMap.Module.Eq.cs— TooManyMethods — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 111 methods, declared across 2 files: HashMap/HashMap.Module.Eq.cs (58), HashMap/HashMap.Module.cs (53). The bar is 30 methods; this is 81 over it, 3.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: Iterable LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs— TooManyMethods — 612 significant lines (blank, comment-only and punctuation-only lines excluded), 110 methods. The bar is 30 methods; this is 80 over it, 3.67× 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: EffExtensions LanguageExt.Core/Effects/Eff/Eff no runtime/Operators/Eff.Operators.Applicative.cs— TooManyMethods — 427 significant lines (blank, comment-only and punctuation-only lines excluded), 110 methods, declared across 12 files: Operators/Eff.Operators.Applicative.cs (21), Operators/Eff.Operators.Applicative.cs (21), Operators/Eff.Operators.Functor.cs (20), Operators/Eff.Operators.Functor.cs (20), +8 more file(s). The bar is 30 methods; this is 80 over it, 3.67× 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: Either LanguageExt.Core/Monads/Alternative Monads/Either/Either.cs— TooManyMethods — 318 significant lines (blank, comment-only and punctuation-only lines excluded), 104 methods. The bar is 30 methods; this is 74 over it, 3.47× 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: Validation LanguageExt.Core/Monads/Alternative Monads/Validation/Validation.cs— TooManyMethods — 313 significant lines (blank, comment-only and punctuation-only lines excluded), 96 methods. The bar is 30 methods; this is 66 over it, 3.20× 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: Option LanguageExt.Core/Monads/Alternative Monads/Option/Option.cs— TooManyMethods — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 89 methods. The bar is 30 methods; this is 59 over it, 2.97× 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: Set LanguageExt.Core/Immutable Collections/Set/Set.Ord.Module.cs— TooManyMethods — 303 significant lines (blank, comment-only and punctuation-only lines excluded), 89 methods, declared across 3 files: Set/Set.Ord.Module.cs (33), Set/Set.Module.cs (32), Trait/Set.TraitImpl.cs (24). The bar is 30 methods; this is 59 over it, 2.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: MapInternal LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs— TooManyMethods — 829 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× 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: Fin LanguageExt.Core/Monads/Alternative Monads/Fin/Fin.cs— TooManyMethods — 280 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× 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: List LanguageExt.Core/Immutable Collections/List/Lst.Module.cs— TooManyMethods — 376 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 30 methods; this is 53 over it, 2.77× 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: ApplicativeExtensions LanguageExt.Core/Traits/Applicative/Operators/Applicative.Memo.Operators.cs— TooManyMethods — 373 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods, declared across 2 files: Operators/Applicative.Memo.Operators.cs (62), Operators/Applicative.Operators.cs (21). The bar is 30 methods; this is 53 over it, 2.77× 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.
No assertions: DeriveBluebird LanguageExt.Tests/CombinatorsTests.cs:24— 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: DeriveCardinalBird LanguageExt.Tests/CombinatorsTests.cs:30— 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: EitherCoalesce LanguageExt.Tests/EitherTests.cs:124— 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: EitherInfer1 LanguageExt.Tests/EitherTests.cs:130— 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: LambdaInferTests LanguageExt.Tests/FunTests.cs:8— 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: MapAddInOrderTest LanguageExt.Tests/HashMapTests.cs:60— 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: MapAddInReverseOrderTest LanguageExt.Tests/HashMapTests.cs:89— 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: MapAddInMixedOrderTest LanguageExt.Tests/HashMapTests.cs:115— 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: HashSetAddInOrderTest LanguageExt.Tests/HashSetTests.cs:38— 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: HashSetAddInReverseOrderTest LanguageExt.Tests/HashSetTests.cs:67— 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: HashSetAddInMixedOrderTest LanguageExt.Tests/HashSetTests.cs:96— 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: Issue208 LanguageExt.Tests/IssuesTests.cs:51— 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: Issue346 LanguageExt.Tests/IssuesTests.cs:59— 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: Test LanguageExt.Tests/IssuesTests.cs:368— 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: OptionLst1 LanguageExt.Tests/LinqTests.cs:151— 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: OptionNoneTest1 LanguageExt.Tests/LinqTests.cs:163— 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: MapAddInOrderTest LanguageExt.Tests/MapTests.cs:80— 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: MapAddInReverseOrderTest LanguageExt.Tests/MapTests.cs:109— 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: MapAddInMixedOrderTest LanguageExt.Tests/MapTests.cs:135— 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: MultiLineNestedComments LanguageExt.Tests/ParsecTests.cs:23— 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: MultiLineComments LanguageExt.Tests/ParsecTests.cs:34— 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: ParallelCheck LanguageExt.Tests/ParsecTests.cs:617— 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: MergeSynchronousProducersSucceeds LanguageExt.Tests/PipesTests.cs:10— 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: SetAddInOrderTest LanguageExt.Tests/SetTests.cs:52— 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: SetAddInReverseOrderTest LanguageExt.Tests/SetTests.cs:81— 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 LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:504— // TODO: Consider building a monoid wrappers for all numeric values (and strings) — 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 LanguageExt.Core/DataTypes/StringM/OrdString.cs:1— // TODO: Work out where these types should live — 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 LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:1112— // TODO: Replace with FoldIO — 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 LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:1127— // TODO: Replace with FoldIO — 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 LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:1142— // TODO: Replace with FoldIO — 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 LanguageExt.Core/Immutable Collections/IterableNE/Trait/IterableNE.TraitImpl.cs:20— // TODO: We need a way of lifting an IO<IAsyncEnumerable> into IterableNE (knowing it's non-empty) — 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 LanguageExt.Core/Immutable Collections/IteratorAsync/IteratorAsync.cs:319— // TODO: Replace this with a WaitAny tasks for each side, replacing the — 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 LanguageExt.Core/Monads/IdentityT/IdentityT.Monad.cs:24— // TODO: Make a stack-safe version of this — 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 LanguageExt.Core/Traits/Applicative/Applicative.Trait.cs:225— // TODO: Consider ways to make this not be blocking as a sensible default implementation — 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 LanguageExt.Core/Traits/Domain/Locus.cs:1— // TODO: Decide whether you want to develop this idea or not
TodoComment LanguageExt.Core/Traits/Monads/Monad/Monad.Trait.cs:62— // TODO: Check if this implementation is valid — 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 LanguageExt.Megaparsec/Reach.cs:21— // TODO: Consider if the maths here are correct — 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 LanguageExt.Megaparsec/Reach.cs:104— // TODO: Consider if the maths here are correct — 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 LanguageExt.Megaparsec/Reach.cs:22— // TODO: Probably TokenStream should support Split — 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 LanguageExt.Megaparsec/Reach.cs:105— // TODO: Probably TokenStream should support Split — 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 LanguageExt.Parsec/Parsers/Token.cs:329— // : /* TODO - fully implement case insensitive version*/); — 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 LanguageExt.Parsec/Parsers/Token2.cs:318— // : /* TODO - fully implement case insensitive version*/); — 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 LanguageExt.Streaming/ConduitT/Internal/ConduitT.ABC.cs:84— // TODO: Deal with errors? — 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 LanguageExt.Streaming/SourceT/DSL/FoldUntilSourceT.cs:14— // TODO: Schedule — 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 LanguageExt.Streaming/SourceT/DSL/FoldWhileSourceT.cs:14— // TODO: Schedule — 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 LanguageExt.Tests/MonadTests.cs:102— // TODO: Restore when traits are complete — 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 LanguageExt.Tests/OptionTTests.cs:190— // .FilterT(x => x > 2); <-- TODO: Above was this -- should we restore a filter operation? Can we even? — 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 LanguageExt.Tests/OptionUnsafeApply.cs:11— // TODO: Restore — 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 LanguageExt.Tests/TraitTests/ApplicativeLawTests.cs:60— // TODO: Restore — 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 LanguageExt.Tests/TraitTests/FunctorLawTests.cs:104— // TODO: Restore — 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.
Duplicated block (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:403— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:403-422 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:377-396 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:403` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:756— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:756-775 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:730-749 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:786— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:786-805 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:760-779 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:819— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:819-838 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:793-812 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:849— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:849-868 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:823-842 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:941— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:941-960 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:915-934 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:941` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1424— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1424-1443 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1406-1425 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `rhs` to `AtomHashMap<EqK, K, V>` in one and `AtomHashMap<K, V>` 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1447— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1447-1466 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1429-1448 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `rhs` to `HashMap<EqK, K, V>` in one and `HashMap<K, V>` 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1470— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1470-1489 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1452-1471 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `rhs` to `AtomHashMap<EqK, K, V>` in one and `AtomHashMap<K, V>` 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1493— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1493-1512 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1475-1494 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `rhs` to `HashMap<EqK, K, V>` in one and `HashMap<K, V>` 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1591— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1591-1610 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1573-1592 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1790— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1790-1809 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1771-1790 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (20 lines × 2) LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1219— LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1219-1238 | LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1252-1271 — 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 `pred` to `Func<A, bool>` in one and `Func<A, int, bool>` 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1451— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1451-1470 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1507-1526 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1451` 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1563— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1563-1582 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1619-1638 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1563` 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1675— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1675-1694 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1731-1750 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1675` 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 (20 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1155— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1155-1174 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1186-1205 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1155` 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 (20 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1400— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1400-1419 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1562-1581 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1400` 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 (20 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1488— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1488-1507 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1622-1641 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1488` 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 (20 lines × 2) LanguageExt.Core/Effects/Eff/Eff no runtime/Extensions/Eff.Extensions.MapApply.cs:19— LanguageExt.Core/Effects/Eff/Eff no runtime/Extensions/Eff.Extensions.MapApply.cs:19-70 | LanguageExt.Core/Effects/Eff/Eff no runtime/Prelude/Eff.Prelude.mapapply.cs:19-38 — `LanguageExt.Core/Effects/Eff/Eff no runtime/Extensions/Eff.Extensions.MapApply.cs` and `LanguageExt.Core/Effects/Eff/Eff no runtime/Prelude/Eff.Prelude.mapapply.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 52 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/Arr/Extensions/Arr.Extensions.MapApply.cs:19— LanguageExt.Core/Immutable Collections/Arr/Extensions/Arr.Extensions.MapApply.cs:19-70 | LanguageExt.Core/Immutable Collections/Arr/Prelude/Arr.Prelude.mapapply.cs:19-38 — `LanguageExt.Core/Immutable Collections/Arr/Extensions/Arr.Extensions.MapApply.cs` and `LanguageExt.Core/Immutable Collections/Arr/Prelude/Arr.Prelude.mapapply.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 52 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/HashSet/Extensions/HashSet.Extensions.MapApply.cs:19— LanguageExt.Core/Immutable Collections/HashSet/Extensions/HashSet.Extensions.MapApply.cs:19-70 | LanguageExt.Core/Immutable Collections/HashSet/Prelude/HashSet.Prelude.mapapply.cs:19-38 — `LanguageExt.Core/Immutable Collections/HashSet/Extensions/HashSet.Extensions.MapApply.cs` and `LanguageExt.Core/Immutable Collections/HashSet/Prelude/HashSet.Prelude.mapapply.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 52 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/Extensions/Iterable.Extensions.MapApply.cs:19— LanguageExt.Core/Immutable Collections/Iterable/Extensions/Iterable.Extensions.MapApply.cs:19-70 | LanguageExt.Core/Immutable Collections/Iterable/Prelude/Iterable.Prelude.mapapply.cs:19-38 — `LanguageExt.Core/Immutable Collections/Iterable/Extensions/Iterable.Extensions.MapApply.cs` and `LanguageExt.Core/Immutable Collections/Iterable/Prelude/Iterable.Prelude.mapapply.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 52 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/List/Extensions/Lst.Extensions.MapApply.cs:19— LanguageExt.Core/Immutable Collections/List/Extensions/Lst.Extensions.MapApply.cs:19-70 | LanguageExt.Core/Immutable Collections/List/Prelude/Lst.Prelude.mapapply.cs:19-38 — `LanguageExt.Core/Immutable Collections/List/Extensions/Lst.Extensions.MapApply.cs` and `LanguageExt.Core/Immutable Collections/List/Prelude/Lst.Prelude.mapapply.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 52 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/Seq/Extensions/Seq.Extensions.MapApply.cs:19— LanguageExt.Core/Immutable Collections/Seq/Extensions/Seq.Extensions.MapApply.cs:19-70 | LanguageExt.Core/Immutable Collections/Seq/Prelude/Seq.Prelude.mapapply.cs:19-38 — `LanguageExt.Core/Immutable Collections/Seq/Extensions/Seq.Extensions.MapApply.cs` and `LanguageExt.Core/Immutable Collections/Seq/Prelude/Seq.Prelude.mapapply.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 52 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.
Sync-over-async (deadlock risk) through `.Result` LanguageExt.Core/Concurrency/Task/Task.Extensions.cs:230— 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` LanguageExt.Core/Concurrency/Task/Task.Extensions.cs:235— 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` LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:167— 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` LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:191— 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` LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:205— 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` LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:218— 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` LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:241— 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` LanguageExt.Core/Concurrency/ValueTask/ValueTask.Extensions.cs:226— 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` LanguageExt.Core/Concurrency/ValueTask/ValueTask.Extensions.cs:230— 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` LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:164— 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` LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:188— 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` LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:202— 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` LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:215— 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` LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:238— 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` LanguageExt.Core/Effects/IO/DSL/IOApply.cs:26— 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` LanguageExt.Core/Effects/IO/DSL/IOApply.cs:53— 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` LanguageExt.Core/Effects/IO/DSL/IOApply.cs:56— 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` LanguageExt.Core/Effects/IO/DSL/IOApply.cs:59— 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` LanguageExt.Core/Effects/IO/DSL/IOApply.cs:65— 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` LanguageExt.Core/Utility/WaitAsync.cs:14— 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` LanguageExt.Core/Utility/WaitAsync.cs:23— 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` LanguageExt.Core/Utility/WaitAsync.cs:33— 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` LanguageExt.Core/Utility/WaitAsync.cs:44— 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` LanguageExt.Core/Utility/WaitAsync.cs:56— 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.
Duplicated block (11 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:109— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:109-119 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:145-155 — 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. 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 × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:184— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:184-194 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:220-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. 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 × 2) LanguageExt.Parsec/GenTokenParser.cs:329— LanguageExt.Parsec/GenTokenParser.cs:329-339 | LanguageExt.Parsec/GenTokenParser2.cs:343-353 — 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 `LanguageExt.Parsec/GenTokenParser.cs:329` 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) LanguageExt.Core/Class Instances/Eq/EqEnumerable.cs:22— LanguageExt.Core/Class Instances/Eq/EqEnumerable.cs:22-32 | LanguageExt.Core/Class Instances/Eq/EqIterable.cs:22-32 — before extracting anything, compare `LanguageExt.Core/Class Instances/Eq/EqEnumerable.cs` and `LanguageExt.Core/Class Instances/Eq/EqIterable.cs` as WHOLE FILES: 83% 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. 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 `x` to `IEnumerable<A>` in one and `Iterable<A>` 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 (11 lines × 2) LanguageExt.Core/Class Instances/Eq/EqQue.cs:18— LanguageExt.Core/Class Instances/Eq/EqQue.cs:18-28 | LanguageExt.Core/Class Instances/Eq/EqStck.cs:17-27 — 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 `LanguageExt.Core/Class Instances/Eq/EqQue.cs:18` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `x` to `Que<A>` in one and `Stck<A>` 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 (11 lines × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:60— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:60-70 | LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:74-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. Note first that the copies are not typed on the same thing: the declarations holding them bind `items` to `IEnumerable<(K Key, V Value)>` in one and `ReadOnlySpan<(K Key, V Value)>` 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 (11 lines × 2) LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:58— LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:58-68 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:72-82 — 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 `items` to `ReadOnlySpan<K>` in one and `IEnumerable<K>` 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 (11 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:72— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:72-82 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:298-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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:72` 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 × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107-117 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:371-381 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107` 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 × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:600— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:600-610 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:632-642 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:600` 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 × 2) LanguageExt.Core/Traits/Resolve/EqResolver.cs:57— LanguageExt.Core/Traits/Resolve/EqResolver.cs:57-67 | LanguageExt.Core/Traits/Resolve/HashableResolver.cs:34-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 `LanguageExt.Core/Traits/Resolve/EqResolver.cs:57` 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) LanguageExt.Core/Traits/Resolve/Resolver.cs:85— LanguageExt.Core/Traits/Resolve/Resolver.cs:85-95 | LanguageExt.Core/Traits/Resolve/Resolver.cs:101-111 — 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) LanguageExt.Core/Traits/Resolve/Resolver.cs:119— LanguageExt.Core/Traits/Resolve/Resolver.cs:119-129 | LanguageExt.Core/Traits/Resolve/Resolver.cs:135-145 — 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) LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1103— LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1103-1113 | LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1135-1145 — 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 `LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1103` 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 × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:61— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:61-71 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:77-88 — 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 `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:61` 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 × 2) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1008— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1008-1018 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1194-1204 — 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 `LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1008` 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) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:355— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:355-365 | LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:419-429 — 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 `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:355` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `items` to `TrieMap<EqK, K, Change<V>> Changes) TryAddRangeWithLog(IEnumerable<(K Key, V Value)>` in one and `TrieMap<EqK, K, Change<V>> Changes) TryAddRangeWithLog(IEnumerable<KeyValuePair<K, V>>` 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 (11 lines × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:643— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:643-653 | LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:675-685 — 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 `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:643` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `items` to `TrieMap<EqK, K, Change<V>> Changes) TrySetItemsWithLog(IEnumerable<(K Key, V Value)>` in one and `TrieMap<EqK, K, Change<V>> Changes) TrySetItemsWithLog(IEnumerable<KeyValuePair<K, V>>` 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 (11 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:149— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:149-159 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:189-199 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:149` 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 × 2) LanguageExt.Parsec/ParserIOs/Expr.cs:98— LanguageExt.Parsec/ParserIOs/Expr.cs:98-108 | LanguageExt.Parsec/ParserIOs/Expr.cs:113-123 — 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 `LanguageExt.Parsec/ParserIOs/Expr.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. 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) LanguageExt.Parsec/Parsers/Expr.cs:103— LanguageExt.Parsec/Parsers/Expr.cs:103-113 | LanguageExt.Parsec/Parsers/Expr.cs:118-128 — 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 `LanguageExt.Parsec/Parsers/Expr.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. 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) LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldUntilTransducer.cs:48— LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldUntilTransducer.cs:48-58 | LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldWhileTransducer.cs:57-68 — 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 `LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldUntilTransducer.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. 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. 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) LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs:122— LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs:122-132 | LanguageExt.Streaming/SourceT/DSL/MultiListenerSourceT.cs:122-132 — before extracting anything, compare `LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs` and `LanguageExt.Streaming/SourceT/DSL/MultiListenerSourceT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 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.
X2 · Cancellation propagation· Async method without CancellationToken · ×21
Async method without CancellationToken: WindowIter LanguageExt.Core/Concurrency/ValueTask/ValueTask.Extensions.cs:290— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunAsync LanguageExt.Core/Effects/Eff/Eff with runtime/Extensions/Eff.Extensions.cs:84— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunAsync LanguageExt.Core/Effects/Eff/Eff with runtime/Extensions/Eff.Extensions.cs:103— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunUnsafeAsync LanguageExt.Core/Effects/Eff/Eff with runtime/Extensions/Eff.Extensions.cs:123— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Invoke LanguageExt.Core/Effects/IO/DSL/IOActionsAsync.cs:20— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Invoke LanguageExt.Core/Effects/IO/DSL/IOEmpty.cs:144— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Invoke LanguageExt.Core/Effects/IO/DSL/IOFinal.cs:55— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Invoke LanguageExt.Core/Effects/IO/DSL/IOLocal2.cs:18— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Invoke LanguageExt.Core/Effects/IO/DSL/IOLocal2.cs:39— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunAsync LanguageExt.Core/Effects/IO/Extensions/IO.Extensions.cs:50— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunAsync LanguageExt.Core/Effects/IO/IO.cs:763— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunAsyncInternal LanguageExt.Core/Effects/IO/IO.cs:917— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: First LanguageExt.Core/Immutable Collections/IteratorAsync/DSL/IteratorAsync.ConsFirst.cs:32— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WaitOneAsync LanguageExt.Core/Utility/WaitAsync.cs:114— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Run Samples/TestBed/ResourcesDiscussion1366.cs:11— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Case2 Samples/TestBed/ResourcesDiscussion1366.cs:44— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Case3 Samples/TestBed/ResourcesDiscussion1366.cs:62— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Case4 Samples/TestBed/ResourcesDiscussion1366.cs:81— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Case5 Samples/TestBed/ResourcesDiscussion1366.cs:92— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Download Samples/Newsletter/Newsletter/Effects/Impl/Web.cs:9— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: naturalsEnum Samples/Streams/CountForeverAsync.cs:24— No CancellationToken parameter — this work can't be stopped early once started.
D17 · Explicit Debt· Whole file has no live code · ×18
Whole file has no live code — 1 debt marker inside it LanguageExt.Core/Class Instances/Monoid/Addition.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it LanguageExt.Core/Class Instances/Monoid/MError.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it LanguageExt.Core/Class Instances/Monoid/Product.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it LanguageExt.Core/Deriving/Maybe/MonadIO.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 2 debt markers inside it LanguageExt.Core/Deriving/Maybe/MonadUnliftIO.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 2 debt markers (2 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 2 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it LanguageExt.Core/Traits/Fallible/Fallible.Interface.cs:7— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 4 debt markers inside it LanguageExt.Tests/LensTests.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 4 debt markers (3 CommentedOutCode, 1 TodoComment) all sit inside that dead text: one decision to leave the whole file switched off, not 4 independent debts. The first note recorded in it is "TODO: Restore when we have SourceGen" (line 2). Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 14 debt markers inside it LanguageExt.Tests/MemoryFSTests.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 14 debt markers (14 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 14 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 10 debt markers inside it LanguageExt.Tests/OptionLazy.cs:1— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 10 debt markers (10 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 10 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 5 debt markers inside it LanguageExt.Tests/PrismTests.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 5 debt markers (4 CommentedOutCode, 1 TodoComment) all sit inside that dead text: one decision to leave the whole file switched off, not 5 independent debts. The first note recorded in it is "TODO: Restore when SourceGen available" (line 2). Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 5 debt markers inside it LanguageExt.Tests/UnionCustomJsonSerializerTests.cs:3— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 5 debt markers (4 CommentedOutCode, 1 TodoComment) all sit inside that dead text: one decision to leave the whole file switched off, not 5 independent debts. The first note recorded in it is "TODO: Consider restoring when SourceGen arrives" (line 3). Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 5 debt markers inside it LanguageExt.Tests/UnionJsonSerializerTests.cs:3— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 5 debt markers (4 CommentedOutCode, 1 TodoComment) all sit inside that dead text: one decision to leave the whole file switched off, not 5 independent debts. The first note recorded in it is "TODO: Consider restoring when SourceGen arrives" (line 3). Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 7 debt markers inside it LanguageExt.Tests/UnionTests.cs:3— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 7 debt markers (6 CommentedOutCode, 1 TodoComment) all sit inside that dead text: one decision to leave the whole file switched off, not 7 independent debts. The first note recorded in it is "TODO: Consider restoring when SourceGen arrives" (line 3). Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 2 debt markers inside it LanguageExt.Tests/WithTests.cs:3— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 2 debt markers (1 CommentedOutCode, 1 TodoComment) all sit inside that dead text: one decision to leave the whole file switched off, not 2 independent debts. The first note recorded in it is "TODO: Restore when we get SourceGen" (line 3). Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 4 debt markers inside it Samples/Streams/HeadsAndTails.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 4 debt markers (4 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 4 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 2 debt markers inside it Samples/TestBed.WPF/AtomIO.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 2 debt markers (2 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 2 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 3 debt markers inside it Samples/TestBed/RobotExample.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 3 debt markers (2 CommentedOutCode, 1 TodoComment) all sit inside that dead text: one decision to leave the whole file switched off, not 3 independent debts. The first note recorded in it is "TODO: RESTORE WITH NEW CODE-GEN SYSTEM" (line 2). Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 24 debt markers inside it Samples/TestBed/TestCodeGen.cs:2— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 24 debt markers (23 CommentedOutCode, 1 TodoComment) all sit inside that dead text: one decision to leave the whole file switched off, not 24 independent debts. The first note recorded in it is "TODO: RESTORE WITH NEW CODE-GEN SYSTEM" (line 2). Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Sync-over-async blocking — 16 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 LanguageExt.Core/Effects/IO/DSL/IOFold.cs:145— `.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 LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:159— `.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 LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:168— `.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 LanguageExt.Core/Effects/IO/IO.cs:411— `.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 LanguageExt.Core/Effects/IO/IO.cs:716— `.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 LanguageExt.Core/Effects/IO/IO.cs:744— `.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 Samples/TestBed/SequenceParallelTest.cs:13— `.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 LanguageExt.Streaming/ConduitT/Internal/ConduitT.ABC.cs:77— `.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 LanguageExt.Streaming/ConduitT/Internal/ConduitT.ABC.cs:79— `.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 LanguageExt.Streaming/SourceT/DSL/ObservablePureSourceT.cs:21— `.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 LanguageExt.Streaming/SourceT/DSL/ObservableSourceT.cs:21— `.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 LanguageExt.Streaming/SourceT/DSL/Reader2SourceT.cs:29— `.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 LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:34— `.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 LanguageExt.Streaming/SourceT/DSL/Reader4SourceT.cs:37— `.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 LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldUntilTransducer.cs:52— `.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 LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldWhileTransducer.cs:61— `.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).
FileTooLong: TrieMap/TrieMap.cs LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs— FileTooLong — 1321 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 821 over it, 2.64× 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: Map/Map.Internal.cs LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs— FileTooLong — 1233 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 733 over it, 2.47× 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: AtomHashMap/AtomHashMap.Eq.cs LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs— FileTooLong — 974 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 474 over it, 1.95× 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: AtomHashMap/AtomHashMap.cs LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs— FileTooLong — 967 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 467 over it, 1.93× 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: Utility/IL.cs LanguageExt.Core/Utility/IL.cs— FileTooLong — 809 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 309 over it, 1.62× 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: Internal/Set.Internal.cs LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs— FileTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 207 over it, 1.41× 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: Internal/Lst.Internal.cs LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs— FileTooLong — 671 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 171 over it, 1.34× 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: Map/Map.cs LanguageExt.Core/Immutable Collections/Map/Map.cs— FileTooLong — 634 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 134 over it, 1.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: Iterable/Iterable.cs LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs— FileTooLong — 625 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 125 over it, 1.25× 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: AtomSeq/AtomSeq.cs LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs— FileTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 106 over it, 1.21× 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: HashMap/HashMap.Eq.cs LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 87 over it, 1.17× 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: Immutable Collections/Prelude.Collections.cs LanguageExt.Core/Immutable Collections/Prelude.Collections.cs— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 87 over it, 1.17× 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: TrieSet/TrieSet.cs LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs— FileTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 71 over it, 1.14× 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: HashMap/HashMap.cs LanguageExt.Core/Immutable Collections/HashMap/HashMap.cs— FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 64 over it, 1.13× 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: Arr/Arr.cs LanguageExt.Core/Immutable Collections/Arr/Arr.cs— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× 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: Seq/Seq.cs LanguageExt.Core/Immutable Collections/Seq/Seq.cs— FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 16 over it, 1.03× 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×16
Members sharing a duplicated core (4 members, 50+ identical tokens) LanguageExt.Core/Concurrency/Atom/Atom.Metadata.cs:86— LanguageExt.Core/Concurrency/Atom/Atom.Metadata.cs:86-107 | LanguageExt.Core/Concurrency/Atom/Atom.Metadata.cs:125-148 | LanguageExt.Core/Concurrency/Atom/Atom.cs:84-105 | LanguageExt.Core/Concurrency/Atom/Atom.cs:123-146 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:269— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:269-288 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:306-325 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:243-262 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:280-299 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:560— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:560-585 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:595-620 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:534-559 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:569-594 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:755— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:755-775 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:785-805 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:729-749 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:759-779 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:818— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:818-838 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:848-868 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:792-812 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:822-842 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1107— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1107-1128 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1136-1157 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1081-1102 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1110-1131 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1165— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1165-1190 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1198-1223 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1139-1164 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1172-1197 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1590— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1590-1610 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1616-1636 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1572-1592 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1598-1618 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1709— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1709-1729 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1736-1756 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1690-1710 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1717-1737 — 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1763— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1763-1782 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1789-1809 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1744-1763 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1770-1790 — 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) LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:42— LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:42-47 | LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Prelude.cs:43-48 | LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:42-48 | LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Prelude.cs:43-49 — 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) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1856— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1856-1887 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1993-2011 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2059-2077 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2081-2099 — 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) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2256— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2256-2287 | LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2290-2392 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:746-777 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:780-886 — 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:574— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:574-591 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:599-623 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:631-655 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1213-1231 — 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) LanguageExt.Streaming/Transducers/Transducer/DSL/ComposeTransducer.cs:64— LanguageExt.Streaming/Transducers/Transducer/DSL/ComposeTransducer.cs:64-72 | LanguageExt.Streaming/Transducers/Transducer/DSL/ComposeTransducer.cs:91-101 | LanguageExt.Streaming/Transducers/TransducerM/DSL/ComposeTransducer.cs:52-60 | LanguageExt.Streaming/Transducers/TransducerM/DSL/ComposeTransducer.cs:76-86 — 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) LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:14— LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:14-37 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:51-86 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:13-37 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:51-85 — 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.
Duplicated block (6 lines × 2) LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:205— LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:205-210 | LanguageExt.Core/Immutable Collections/Seq/Seq.cs:173-178 — 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.
Duplicated block (6 lines × 2) LanguageExt.Core/Utility/IL.cs:97— LanguageExt.Core/Utility/IL.cs:97-102 | LanguageExt.Core/Utility/IL.cs:336-341 — 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 `LanguageExt.Core/Utility/IL.cs:97` 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 (6 lines × 2) LanguageExt.Parsec/Pipes.cs:45— LanguageExt.Parsec/Pipes.cs:45-50 | LanguageExt.Parsec/Pipes.cs:76-81 — 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 (6 lines × 2) LanguageExt.Core/DataTypes/Compositions/FoldCompositions.cs:12— LanguageExt.Core/DataTypes/Compositions/FoldCompositions.cs:12-17 | LanguageExt.Core/DataTypes/Compositions/FoldCompositions.cs:24-29 — 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 (6 lines × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:1399— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:1399-1404 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:375-380 — `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs` and `LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:1399` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `rhs` to `TrieMap<EqK, K, Change<V>> Changes) SubtractWithLog(TrieMap<EqK, K, V>` in one and `TrieSet<EqK, K>?` 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 × 2) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:656— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:656-661 | LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:674-679 — 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 `LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:656` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1931— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1931-1936 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1949-1954 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1931` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:910— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:910-915 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:927-932 — 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:910` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) LanguageExt.Core/Utility/IL.cs:311— LanguageExt.Core/Utility/IL.cs:311-316 | LanguageExt.Core/Utility/Reflect.cs:257-262 — 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. 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 (6 lines × 2) LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:17— LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:17-22 | LanguageExt.Streaming/SourceT/DSL/Reader4SourceT.cs:18-23 — 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 `LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:17` 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 (6 lines × 2) LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:19— LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:19-24 | LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:26-31 — 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 (6 lines × 2) LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:50— LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:50-55 | LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:57-62 — 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 (6 lines × 2) LanguageExt.Megaparsec/ParsecT/DSL/Bind.cs:19— LanguageExt.Megaparsec/ParsecT/DSL/Bind.cs:19-24 | LanguageExt.Megaparsec/ParsecT/DSL/Bind.cs:26-31 — 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 (6 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:756— LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:756-761 | LanguageExt.Core/Immutable Collections/IterableNE/IterableNE.cs:428-433 — 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 (6 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:774— LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:774-779 | LanguageExt.Core/Immutable Collections/IterableNE/IterableNE.cs:446-451 — 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 (6 lines × 2) LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs:28— LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs:28-33 | LanguageExt.Streaming/SourceT/DSL/MultiListenerSourceT.cs:28-33 — before extracting anything, compare `LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs` and `LanguageExt.Streaming/SourceT/DSL/MultiListenerSourceT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 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 (13 lines × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2582— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2582-2594 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:1071-1083 — `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs` and `LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2582` 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 (13 lines × 2) LanguageExt.Core/Traits/Resolve/EqResolver.cs:46— LanguageExt.Core/Traits/Resolve/EqResolver.cs:46-58 | LanguageExt.Core/Traits/Resolve/OrdResolver.cs:85-97 — 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 `LanguageExt.Core/Traits/Resolve/EqResolver.cs:46` 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) LanguageExt.Parsec/Parsers/Token.cs:166— LanguageExt.Parsec/Parsers/Token.cs:166-178 | LanguageExt.Parsec/Parsers/Token2.cs:154-166 — before extracting anything, compare `LanguageExt.Parsec/Parsers/Token.cs` and `LanguageExt.Parsec/Parsers/Token2.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 240 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 (13 lines × 2) LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:61— LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:61-73 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:64-76 — 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 `LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:61` 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 (13 lines × 2) LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:50— LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:50-62 | LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:69-81 — 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 `LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:50` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 2) LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:444— LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:444-456 | LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:467-479 — 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 `LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:444` 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) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:998— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:998-1010 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1020-1032 — 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:998` 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) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2201— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2201-2213 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:694-706 — `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs` and `LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2201` 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) LanguageExt.Core/Utility/IL.cs:1162— LanguageExt.Core/Utility/IL.cs:1162-1174 | LanguageExt.Core/Utility/IL.cs:1213-1225 — 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 `LanguageExt.Core/Utility/IL.cs:1162` 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) LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:47— LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:47-59 | LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:99-112 — 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 `LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:47` 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 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 × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1448— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1448-1460 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1596-1608 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1448` 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. 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1536— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1536-1548 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1656-1668 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1536` 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. 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) LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:15— LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:15-27 | LanguageExt.Benchmarks/HashMapRandomRemovalBenchmarks.cs:15-27 — 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 `LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.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 (10 lines × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2304— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2304-2313 | LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2493-2502 — 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. 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) LanguageExt.Parsec/Parsec.Internal.cs:101— LanguageExt.Parsec/Parsec.Internal.cs:101-110 | LanguageExt.Parsec/ParsecIO.Internal.cs:95-104 — before extracting anything, compare `LanguageExt.Parsec/Parsec.Internal.cs` and `LanguageExt.Parsec/ParsecIO.Internal.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 `LanguageExt.Parsec/Parsec.Internal.cs:101` 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 (10 lines × 2) LanguageExt.Parsec/Parsers/Prim.cs:354— LanguageExt.Parsec/Parsers/Prim.cs:354-363 | LanguageExt.Parsec/Parsers/Prim.cs:469-478 — 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 `LanguageExt.Parsec/Parsers/Prim.cs:354` 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) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:298— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:298-307 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:737-746 — 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 (10 lines × 2) LanguageExt.Parsec/ParserResult.cs:74— LanguageExt.Parsec/ParserResult.cs:74-83 | LanguageExt.Parsec/ParserResultIO.cs:62-71 — 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) LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs:603— LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs:603-612 | LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs:647-656 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs` and `LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 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 (10 lines × 2) LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs:621— LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs:621-630 | LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs:665-674 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs` and `LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 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 (10 lines × 2) LanguageExt.Core/Immutable Collections/HashSet/Trait/HashSet.TraitImpl.cs:55— LanguageExt.Core/Immutable Collections/HashSet/Trait/HashSet.TraitImpl.cs:55-64 | LanguageExt.Core/Immutable Collections/Set/Trait/Set.TraitImpl.cs:50-59 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `LanguageExt.Core/Immutable Collections/HashSet/Trait/HashSet.TraitImpl.cs:51` calls `As` and `LanguageExt.Core/Immutable Collections/Set/Trait/Set.TraitImpl.cs:48` 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 (10 lines × 2) LanguageExt.Core/Immutable Collections/HashSet/Trait/HashSet.TraitImpl.cs:72— LanguageExt.Core/Immutable Collections/HashSet/Trait/HashSet.TraitImpl.cs:72-81 | LanguageExt.Core/Immutable Collections/Set/Trait/Set.TraitImpl.cs:65-74 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `LanguageExt.Core/Immutable Collections/HashSet/Trait/HashSet.TraitImpl.cs:69` calls `As` and `LanguageExt.Core/Immutable Collections/Set/Trait/Set.TraitImpl.cs:63` 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 (10 lines × 2) LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs:21— LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs:21-30 | LanguageExt.Core/Immutable Collections/Seq/Trait/Seq.TraitImpl.cs:57-66 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs` and `LanguageExt.Core/Immutable Collections/Seq/Trait/Seq.TraitImpl.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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.
Duplicated block (10 lines × 2) LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs:51— LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs:51-60 | LanguageExt.Core/Immutable Collections/Seq/Trait/Seq.TraitImpl.cs:87-96 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs` and `LanguageExt.Core/Immutable Collections/Seq/Trait/Seq.TraitImpl.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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.
Duplicated block (10 lines × 2) LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs:66— LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs:66-75 | LanguageExt.Core/Immutable Collections/Seq/Trait/Seq.TraitImpl.cs:102-111 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs` and `LanguageExt.Core/Immutable Collections/Seq/Trait/Seq.TraitImpl.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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.
Duplicated block (10 lines × 2) LanguageExt.Core/Immutable Collections/Set/Set.Ord.cs:626— LanguageExt.Core/Immutable Collections/Set/Set.Ord.cs:626-635 | LanguageExt.Core/Immutable Collections/Set/Set.cs:712-721 — 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 (22 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:164— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:164-185 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:138-159 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (22 lines × 2) LanguageExt.Core/Immutable Collections/Iterator/DSL/Iterator.ConsValueEnum.cs:67— LanguageExt.Core/Immutable Collections/Iterator/DSL/Iterator.ConsValueEnum.cs:67-88 | LanguageExt.Core/Immutable Collections/IteratorAsync/DSL/IteratorAsync.ConsValueEnum.cs:93-114 — 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 `LanguageExt.Core/Immutable Collections/Iterator/DSL/Iterator.ConsValueEnum.cs:67` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (22 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2363— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2363-2384 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2400-2421 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2363` 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) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2437— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2437-2458 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2473-2494 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2437` 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) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1258— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1258-1279 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1295-1316 — 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1258` 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) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1332— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1332-1353 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1369-1390 — 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1332` 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) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:441— LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:441-462 | LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:465-486 — 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) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:504— LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:504-525 | LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:529-550 — 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) LanguageExt.Core/Immutable Collections/Iterator/DSL/Iterator.ConsValueLazy.cs:56— LanguageExt.Core/Immutable Collections/Iterator/DSL/Iterator.ConsValueLazy.cs:56-77 | LanguageExt.Core/Immutable Collections/IteratorAsync/DSL/IteratorAsync.ConsValueLazy.cs:52-73 — 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 `LanguageExt.Core/Immutable Collections/Iterator/DSL/Iterator.ConsValueLazy.cs:56` 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) LanguageExt.Core/Monads/Alternative Monads/TryT/Extensions/TryT.Extensions.MapApply.cs:20— LanguageExt.Core/Monads/Alternative Monads/TryT/Extensions/TryT.Extensions.MapApply.cs:20-76 | LanguageExt.Core/Monads/Alternative Monads/TryT/Prelude/TryT.Prelude.mapapply.cs:20-41 — `LanguageExt.Core/Monads/Alternative Monads/TryT/Extensions/TryT.Extensions.MapApply.cs` and `LanguageExt.Core/Monads/Alternative Monads/TryT/Prelude/TryT.Prelude.mapapply.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 57 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 (22 lines × 2) LanguageExt.Core/Monads/Free/Extensions/Free.Extensions.MapApply.cs:20— LanguageExt.Core/Monads/Free/Extensions/Free.Extensions.MapApply.cs:20-76 | LanguageExt.Core/Monads/Free/Prelude/Free.Prelude.mapapply.cs:20-41 — `LanguageExt.Core/Monads/Free/Extensions/Free.Extensions.MapApply.cs` and `LanguageExt.Core/Monads/Free/Prelude/Free.Prelude.mapapply.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 57 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 (7 lines × 2) LanguageExt.Core/Class Instances/Ord/OrdQue.cs:50— LanguageExt.Core/Class Instances/Ord/OrdQue.cs:50-56 | LanguageExt.Core/Class Instances/Ord/OrdStck.cs:50-56 — before extracting anything, compare `LanguageExt.Core/Class Instances/Ord/OrdQue.cs` and `LanguageExt.Core/Class Instances/Ord/OrdStck.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Class Instances/Ord/OrdQue.cs:50` 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 (7 lines × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2222— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2222-2228 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:713-719 — `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs` and `LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2222` 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. 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 (7 lines × 2) LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs:84— LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs:84-90 | LanguageExt.Core/Immutable Collections/Set/Set.cs:102-108 — 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 `LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs:84` 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 × 2) LanguageExt.Core/Utility/Reflect.cs:112— LanguageExt.Core/Utility/Reflect.cs:112-118 | LanguageExt.Core/Utility/Reflect.cs:172-178 — 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 `LanguageExt.Core/Utility/Reflect.cs:112` 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 × 2) LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:42— LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:42-48 | LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Prelude.cs:43-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.
Duplicated block (7 lines × 2) LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:191— LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:191-197 | LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:201-209 — 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 (7 lines × 2) LanguageExt.Core/Utility/IL.cs:773— LanguageExt.Core/Utility/IL.cs:773-780 | LanguageExt.Core/Utility/IL.cs:850-856 — 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 (7 lines × 2) LanguageExt.Core/Effects/Eff/Eff with runtime/Eff.Module.cs:76— LanguageExt.Core/Effects/Eff/Eff with runtime/Eff.Module.cs:76-82 | LanguageExt.Core/Effects/Eff/Eff with runtime/Prelude/Eff.Prelude.cs:69-75 — 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.
Duplicated block (7 lines × 2) LanguageExt.Core/Immutable Collections/HashMap/HashMap.Trait.Implementations.cs:16— LanguageExt.Core/Immutable Collections/HashMap/HashMap.Trait.Implementations.cs:16-22 | LanguageExt.Core/Immutable Collections/Map/Map.Trait.Implementations.cs:13-19 — 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.
Duplicated block (7 lines × 2) LanguageExt.Core/Immutable Collections/Seq/DSL/SeqStrict.cs:429— LanguageExt.Core/Immutable Collections/Seq/DSL/SeqStrict.cs:429-435 | LanguageExt.Core/Immutable Collections/Seq/SeqLoan.cs:255-261 — 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 (7 lines × 2) LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs:95— LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs:95-101 | LanguageExt.Streaming/SourceT/DSL/MultiListenerSourceT.cs:95-101 — before extracting anything, compare `LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs` and `LanguageExt.Streaming/SourceT/DSL/MultiListenerSourceT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 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.
Unfinished stub — throws NotImplementedException LanguageExt.Core/Common/ErrorException.cs:471— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:25— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:36— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:46— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:137— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:140— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:143— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:146— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:149— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:152— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:210— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Core/Common/ErrorException.cs:471— `Combine` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:25— `CompareTo` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:36— `CompareTo` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/ErrorItem/ErrorItem.cs:46— `CompareTo` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:137— `TryConvertFromChecked` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:140— `TryConvertFromSaturating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:143— `TryConvertFromTruncating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:146— `TryConvertToChecked` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:149— `TryConvertToSaturating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:152— `TryConvertToTruncating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException LanguageExt.Megaparsec/Pos.cs:210— `TryFormat` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Duplicated block (12 lines × 2) LanguageExt.Core/Class Instances/Eq/EqHashSet.cs:20— LanguageExt.Core/Class Instances/Eq/EqHashSet.cs:20-31 | LanguageExt.Core/Class Instances/Eq/EqSet.cs:20-31 — 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 `x` to `HashSet<A>` in one and `Set<A>` 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 (12 lines × 2) LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1363— LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1363-1374 | LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1388-1399 — 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 `LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:1363` 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 × 2) LanguageExt.Core/Effects/IO/DSL/IOActions.cs:21— LanguageExt.Core/Effects/IO/DSL/IOActions.cs:21-32 | LanguageExt.Core/Effects/IO/DSL/IOActions.cs:48-59 — 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) LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:87— LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:87-98 | LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:129-140 — 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 `LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:87` 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) LanguageExt.Parsec/Parsers/Token.cs:249— LanguageExt.Parsec/Parsers/Token.cs:249-260 | LanguageExt.Parsec/Parsers/Token2.cs:237-248 — before extracting anything, compare `LanguageExt.Parsec/Parsers/Token.cs` and `LanguageExt.Parsec/Parsers/Token2.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 240 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 `LanguageExt.Parsec/Parsers/Token.cs:249` 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 (12 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:479— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:479-490 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:554-565 — 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) LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:26— LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:26-37 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:74-85 — 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 `LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:71` calls `Done` and `LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:25` 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 × 2) LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs:69— LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs:69-80 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.cs:69-80 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs` and `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 (12 lines × 2) LanguageExt.Streaming/SourceT/DSL/ObservablePureSourceT.cs:13— LanguageExt.Streaming/SourceT/DSL/ObservablePureSourceT.cs:13-24 | LanguageExt.Streaming/SourceT/DSL/ObservableSourceT.cs:13-24 — 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) LanguageExt.Benchmarks/HashSetContainsBenchmarks.cs:12— LanguageExt.Benchmarks/HashSetContainsBenchmarks.cs:12-23 | LanguageExt.Benchmarks/HashSetIterationBenchmarks.cs:12-23 — 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 `LanguageExt.Benchmarks/HashSetContainsBenchmarks.cs:12` 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 × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Zip.cs:23— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Zip.cs:23-30 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Zip.cs:78-85 — 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) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1442— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1442-1449 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1498-1505 — 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. 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 × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1554— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1554-1561 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1610-1617 — 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. 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 × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1666— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1666-1673 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1722-1729 — 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. 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 × 2) LanguageExt.Core/Immutable Collections/Seq/Seq.cs:1212— LanguageExt.Core/Immutable Collections/Seq/Seq.cs:1212-1222 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:760-767 — 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 `LanguageExt.Core/Immutable Collections/Seq/Seq.cs:1212` 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 × 2) LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:133— LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:133-140 | LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Prelude.cs:127-134 — 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 (8 lines × 2) LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs:581— LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs:581-588 | LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs:625-632 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs` and `LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `array` to `System.Array` in one and `Array` 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 (8 lines × 2) LanguageExt.Core/Traits/Alternative/Alternative.Laws.cs:114— LanguageExt.Core/Traits/Alternative/Alternative.Laws.cs:114-121 | LanguageExt.Core/Traits/Choice/Choice.Laws.cs:111-118 — `LanguageExt.Core/Traits/Alternative/Alternative.Laws.cs` and `LanguageExt.Core/Traits/Choice/Choice.Laws.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 8 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 (8 lines × 2) LanguageExt.Benchmarks/HashSetContainsBenchmarks.cs:28— LanguageExt.Benchmarks/HashSetContainsBenchmarks.cs:28-35 | LanguageExt.Benchmarks/HashSetIterationBenchmarks.cs:28-35 — 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 (8 lines × 2) Samples/DomainTypesExamples/Vector.cs:145— Samples/DomainTypesExamples/Vector.cs:145-152 | Samples/DomainTypesExamples/Vector.cs:167-174 — 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 `Samples/DomainTypesExamples/Vector.cs:145` 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 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, `Samples/DomainTypesExamples/Vector.cs:144` calls `AsSpan` and `Samples/DomainTypesExamples/Vector.cs:166` 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 (5 lines × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2625— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2625-2629 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:1112-1116 — `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs` and `LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.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 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. 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) LanguageExt.Core/Utility/Reflect.cs:127— LanguageExt.Core/Utility/Reflect.cs:127-131 | LanguageExt.Core/Utility/Reflect.cs:188-192 — 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. 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 (5 lines × 2) LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:209— LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:209-213 | LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:216-220 — 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 `LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:209` 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 `f` to `Func<A, Option<long>, Option<long>, Option<long>>` in one and `Func<A, Option<B>, Option<B>, Option<B>>` 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 (5 lines × 2) LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:263— LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:263-267 | LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:283-287 — 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 `LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:263` 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 × 2) LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:276— LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:276-280 | LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:277-281 — 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 `LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:276` 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 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 × 2) LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:264— LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:264-268 | LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:284-288 — 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 `LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:264` 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 × 2) LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:25— LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:25-29 | LanguageExt.Streaming/SourceT/DSL/Reader4SourceT.cs:27-31 — 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 (5 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:792— LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:792-796 | LanguageExt.Core/Immutable Collections/IterableNE/IterableNE.cs:464-468 — 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 (5 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:809— LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:809-813 | LanguageExt.Core/Immutable Collections/IterableNE/IterableNE.cs:481-485 — 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 (5 lines × 2) LanguageExt.Core/Monads/Free/Trait/Free.TraitImpl.cs:41— LanguageExt.Core/Monads/Free/Trait/Free.TraitImpl.cs:41-45 | LanguageExt.Core/Monads/Free/Trait/Free.TraitImpl.cs:50-54 — 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.
Sync-over-async (deadlock risk) LanguageExt.Core/Effects/IO/IO.cs:411— 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) LanguageExt.Core/Effects/IO/IO.cs:716— 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) LanguageExt.Core/Effects/IO/IO.cs:744— 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) LanguageExt.Streaming/ConduitT/Internal/ConduitT.ABC.cs:77— 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) LanguageExt.Streaming/ConduitT/Internal/ConduitT.ABC.cs:79— 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) LanguageExt.Streaming/SourceT/DSL/ObservablePureSourceT.cs:21— 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) LanguageExt.Streaming/SourceT/DSL/ObservableSourceT.cs:21— 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) LanguageExt.Streaming/SourceT/DSL/Reader2SourceT.cs:29— 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) LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:34— 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) LanguageExt.Streaming/SourceT/DSL/Reader4SourceT.cs:37— 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.
Condition was already decided — an earlier guard makes this test constant LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:449— Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 443 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:457— Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 443 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:473— Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 467 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:481— Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 467 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:512— Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 506 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:520— Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 506 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:537— Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 531 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:545— Control only reaches here when `env.Token.IsCancellationRequested` is false, because the guard on line 531 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Duplicated block (25 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:561— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:561-585 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:535-559 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (25 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:596— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:596-620 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:570-594 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (25 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1166— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1166-1190 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1140-1164 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (25 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1199— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1199-1223 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1173-1197 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (25 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1237— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1237-1261 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1211-1235 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (25 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1269— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1269-1293 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1243-1267 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (25 lines × 2) LanguageExt.Core/DataTypes/ValueTuple/Tuple1/ValueTuple1.Extensions.cs:13— LanguageExt.Core/DataTypes/ValueTuple/Tuple1/ValueTuple1.Extensions.cs:13-51 | LanguageExt.Core/DataTypes/ValueTuple/Tuple1/ValueTuple1.Prelude.cs:14-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. 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 (23 lines × 2) LanguageExt.Parsec/Parsec.Internal.cs:118— LanguageExt.Parsec/Parsec.Internal.cs:118-140 | LanguageExt.Parsec/ParsecIO.Internal.cs:112-134 — before extracting anything, compare `LanguageExt.Parsec/Parsec.Internal.cs` and `LanguageExt.Parsec/ParsecIO.Internal.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 `LanguageExt.Parsec/Parsec.Internal.cs:118` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:692— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:692-714 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:666-688 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (23 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:978— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:978-1000 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:952-974 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (23 lines × 2) LanguageExt.Core/Memo/Memo.F.cs:123— LanguageExt.Core/Memo/Memo.F.cs:123-145 | LanguageExt.Core/Memo/Memo.cs:123-145 — 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 `LanguageExt.Core/Memo/Memo.F.cs:123` 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 (23 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:690— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:690-712 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:783-805 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:690` 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 (23 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:724— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:724-746 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:816-838 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:724` 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 (23 lines × 2) LanguageExt.Core/Monads/Alternative Monads/Validation/Prelude/Validation.Prelude.cs:17— LanguageExt.Core/Monads/Alternative Monads/Validation/Prelude/Validation.Prelude.cs:17-39 | LanguageExt.Core/Monads/Alternative Monads/Validation/Validation.Module.cs:17-74 — before extracting anything, compare `LanguageExt.Core/Monads/Alternative Monads/Validation/Prelude/Validation.Prelude.cs` and `LanguageExt.Core/Monads/Alternative Monads/Validation/Validation.Module.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. 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. 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 (17 lines × 2) LanguageExt.Parsec/ParserIOs/Prim.cs:295— LanguageExt.Parsec/ParserIOs/Prim.cs:295-311 | LanguageExt.Parsec/Parsers/Prim.cs:334-350 — 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 `LanguageExt.Parsec/ParserIOs/Prim.cs:295` 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) LanguageExt.Streaming/SourceT/DSL/Zip3SourceT.cs:32— LanguageExt.Streaming/SourceT/DSL/Zip3SourceT.cs:32-48 | LanguageExt.Streaming/SourceT/DSL/Zip4SourceT.cs:33-49 — before extracting anything, compare `LanguageExt.Streaming/SourceT/DSL/Zip3SourceT.cs` and `LanguageExt.Streaming/SourceT/DSL/Zip4SourceT.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (17 lines × 2) LanguageExt.Core/Class Instances/Ord/OrdEnumerable.cs:40— LanguageExt.Core/Class Instances/Ord/OrdEnumerable.cs:40-56 | LanguageExt.Core/Class Instances/Ord/OrdIterable.cs:38-54 — before extracting anything, compare `LanguageExt.Core/Class Instances/Ord/OrdEnumerable.cs` and `LanguageExt.Core/Class Instances/Ord/OrdIterable.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Class Instances/Ord/OrdEnumerable.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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `x` to `IEnumerable<A>` in one and `Iterable<A>` 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 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1104— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1104-1120 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1128-1144 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1104` 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 × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:231— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:231-247 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:269-285 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:231` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:342— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:342-358 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:415-431 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:342` 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) LanguageExt.Core/Utility/EnumerableOptimal.cs:168— LanguageExt.Core/Utility/EnumerableOptimal.cs:168-184 | LanguageExt.Core/Utility/EnumerableOptimal.cs:196-212 — 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 `LanguageExt.Core/Utility/EnumerableOptimal.cs:196` 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 (9 lines × 3) LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:424— LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:424-432 | LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:507-515 | LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:590-598 — 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 `LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:424` 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 (9 lines × 3) LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:58— LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:58-66 | LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:88-96 | LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:119-127 — 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 `LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:58` 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 × 3) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:575— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:575-583 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:600-608 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:632-640 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:575` 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 (9 lines × 3) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:664— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:664-672 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:689-697 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:723-731 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:664` 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 (9 lines × 3) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:756— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:756-764 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:782-790 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:815-823 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:756` 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 (9 lines × 3) LanguageExt.Core/Utility/IL.cs:87— LanguageExt.Core/Utility/IL.cs:87-95 | LanguageExt.Core/Utility/IL.cs:124-132 | LanguageExt.Core/Utility/IL.cs:165-173 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `LanguageExt.Core/Utility/IL.cs:133` calls `Emit` and `LanguageExt.Core/Utility/IL.cs:96` 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 × 3) LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:23— LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:23-31 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs:23-31 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.cs:23-31 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs` and `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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) LanguageExt.Core/Traits/Resolve/EqResolver.cs:9— LanguageExt.Core/Traits/Resolve/EqResolver.cs:9-17 | LanguageExt.Core/Traits/Resolve/OrdResolver.cs:10-18 — 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 (9 lines × 2) LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:84— LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:84-92 | LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:123-131 — 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 `LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.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 (9 lines × 2) LanguageExt.Core/Utility/IL.cs:1185— LanguageExt.Core/Utility/IL.cs:1185-1193 | LanguageExt.Core/Utility/IL.cs:1228-1236 — 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 `LanguageExt.Core/Utility/IL.cs:1185` 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 (9 lines × 2) LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:141— LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:141-149 | LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Prelude.cs:135-143 — 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 (9 lines × 2) LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs:564— LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs:564-572 | LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs:607-616 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/HashSet/HashSet.Eq.cs` and `LanguageExt.Core/Immutable Collections/HashSet/HashSet.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 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. 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) Samples/DomainTypesExamples/Vector.cs:159— Samples/DomainTypesExamples/Vector.cs:159-167 | Samples/DomainTypesExamples/Vector.cs:181-189 — 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 `Samples/DomainTypesExamples/Vector.cs:159` 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) LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:32— LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:32-40 | LanguageExt.Benchmarks/HashMapRandomRemovalBenchmarks.cs:32-40 — 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.
Swallowed exception (empty catch) LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:149— 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) LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:146— 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) LanguageExt.Core/Effects/IO/IO.cs:1030— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) LanguageExt.Core/Effects/IO/IO.cs:1031— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) Samples/TestBed/ResourcesDiscussion1366.cs:37— 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) Samples/TestBed/ResourcesDiscussion1366.cs:56— 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) Samples/TestBed/ResourcesDiscussion1366.cs:75— 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.
Duplicated block (21 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1819— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1819-1839 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1800-1820 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (21 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1850— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1850-1870 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1831-1851 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (21 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1885— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1885-1905 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1866-1886 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (21 lines × 2) LanguageExt.Parsec/Parser.cs:79— LanguageExt.Parsec/Parser.cs:79-99 | LanguageExt.Parsec/ParserIO.cs:84-104 — 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 `LanguageExt.Parsec/Parser.cs:79` 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) LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Lift.cs:15— LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Lift.cs:15-35 | LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Lift.cs:11-31 — 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.
Duplicated block (21 lines × 2) LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Memo.Lift.cs:15— LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Memo.Lift.cs:15-35 | LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Memo.Lift.cs:11-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.
Duplicated block (7 lines × 3) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1007— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1007-1013 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1055-1061 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1079-1085 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1007` 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 (7 lines × 3) LanguageExt.Parsec/Parsec.Internal.cs:109— LanguageExt.Parsec/Parsec.Internal.cs:109-115 | LanguageExt.Parsec/Parsec.Internal.cs:139-145 | LanguageExt.Parsec/Parsec.Internal.cs:184-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 `LanguageExt.Parsec/Parsec.Internal.cs:109` 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 × 3) LanguageExt.Parsec/ParsecIO.Internal.cs:103— LanguageExt.Parsec/ParsecIO.Internal.cs:103-109 | LanguageExt.Parsec/ParsecIO.Internal.cs:133-139 | LanguageExt.Parsec/ParsecIO.Internal.cs:178-184 — 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 `LanguageExt.Parsec/ParsecIO.Internal.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.
Duplicated block (7 lines × 3) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1994— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1994-2000 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2060-2066 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2082-2088 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1994` 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 × 3) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:974— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:974-980 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:996-1002 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1018-1024 — 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:974` 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 × 3) LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:35— LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:35-41 | LanguageExt.Benchmarks/HashMapIterateBenchmarks.cs:31-37 | LanguageExt.Benchmarks/HashMapRandomRemovalBenchmarks.cs:35-41 — 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 `LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:35` 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, `LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:33` calls `ToArray` and `LanguageExt.Benchmarks/HashMapIterateBenchmarks.cs:29` 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 (14 lines × 2) LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:18— LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:18-31 | LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:48-61 — 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 (14 lines × 2) LanguageExt.Streaming/Conduit/Internal/Conduit.ABC.cs:98— LanguageExt.Streaming/Conduit/Internal/Conduit.ABC.cs:98-111 | LanguageExt.Streaming/Conduit/Internal/Conduit.ABC.cs:125-138 — 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. 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 × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:52— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:52-66 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:85-98 — 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 `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:52` 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 × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:1639— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:1639-1652 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:527-540 — `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs` and `LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.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 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. 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) LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs:21— LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs:21-34 | LanguageExt.Streaming/SourceT/DSL/MultiListenerSourceT.cs:21-34 — before extracting anything, compare `LanguageExt.Streaming/SourceT/DSL/MultiListenerPureSourceT.cs` and `LanguageExt.Streaming/SourceT/DSL/MultiListenerSourceT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 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 (6 lines × 3) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1990— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1990-1995 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1971-1976 | LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:584-589 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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, `LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:597` calls `MethodImpl` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1984` 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 (6 lines × 3) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2022— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2022-2027 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:2003-2008 | LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:630-635 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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, `LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:643` calls `MethodImpl` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2035` 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 (6 lines × 3) LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1088— LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1088-1093 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.cs:1022-1027 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.cs:1023-1028 — `LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs` and `LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.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 30 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 (6 lines × 3) LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1123— LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1123-1128 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.cs:1063-1068 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.cs:1064-1069 — `LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs` and `LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.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 30 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 (6 lines × 3) LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:44— LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:44-49 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs:44-49 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.cs:44-49 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs` and `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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.
Async call defeats the CancellationToken: ForAll LanguageExt.Core/Concurrency/Task/Tasks.cs:15— Holds a CancellationToken but hands `default` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
Async call defeats the CancellationToken: ForAll LanguageExt.Core/Concurrency/Task/Tasks.cs:22— Holds a CancellationToken but hands `default` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
Async call defeats the CancellationToken: Exists LanguageExt.Core/Concurrency/Task/Tasks.cs:29— Holds a CancellationToken but hands `default` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
Async call defeats the CancellationToken: Exists LanguageExt.Core/Concurrency/Task/Tasks.cs:36— Holds a CancellationToken but hands `default` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
Async call defeats the CancellationToken: ForAll LanguageExt.Core/Concurrency/ValueTask/ValueTasks.cs:15— Holds a CancellationToken but hands `default` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (6 members, 50+ identical tokens) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:402— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:402-425 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:940-963 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:977-1000 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:376-399 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:914-937 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:951-974 — 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:227— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:227-247 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:265-285 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:338-358 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:411-431 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:477-490 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:552-565 — 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:663— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:663-680 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:688-712 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:722-746 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:755-772 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:781-805 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:814-838 — 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:847— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:847-866 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:876-895 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:905-924 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:934-953 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1152-1174 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1183-1205 — 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (5 members, 50+ identical tokens) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:373— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:373-392 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:132-148 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Cast.cs:65-81 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:182-198 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Enumerable.cs:114-148 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:395— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:395-414 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:157-173 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Cast.cs:84-100 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:201-217 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Enumerable.cs:151-167 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1158— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1158-1185 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:83-110 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs:83-110 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.cs:83-110 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1479-1506 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) Samples/DomainTypesExamples/Vector.cs:83— Samples/DomainTypesExamples/Vector.cs:83-104 | Samples/DomainTypesExamples/Vector.cs:107-128 | Samples/DomainTypesExamples/Vector.cs:134-155 | Samples/DomainTypesExamples/Vector.cs:158-177 | Samples/DomainTypesExamples/Vector.cs:180-199 — These 5 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 5 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 5 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (8 members, 50+ identical tokens) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:71— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:71-95 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:106-130 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:145-170 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:185-210 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:297-321 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:370-394 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:442-459 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:509-526 — 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.
Members sharing a duplicated core (8 members, 50+ identical tokens) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1382— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1382-1419 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1426-1463 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1470-1507 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1514-1551 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1558-1581 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1588-1611 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1618-1641 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1648-1671 — 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.
Members sharing a duplicated core (8 members, 50+ identical tokens) LanguageExt.Core/Utility/Reflect.cs:77— LanguageExt.Core/Utility/Reflect.cs:77-88 | LanguageExt.Core/Utility/Reflect.cs:91-103 | LanguageExt.Core/Utility/Reflect.cs:106-118 | LanguageExt.Core/Utility/Reflect.cs:121-134 | LanguageExt.Core/Utility/Reflect.cs:137-150 | LanguageExt.Core/Utility/Reflect.cs:166-178 | LanguageExt.Core/Utility/Reflect.cs:182-195 | LanguageExt.Core/Utility/Reflect.cs:210-223 — 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.
Duplicated block (21 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:530— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:530-550 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:632-652 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:504-524 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:606-626 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (21 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:663— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:663-683 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1079-1099 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:637-657 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1053-1073 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (21 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1108— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1108-1128 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1137-1157 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1082-1102 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1111-1131 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `items` to `IEnumerable<KeyValuePair<K, V>>` in one and `IEnumerable<(K Key, V Value)>` 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 × 4) LanguageExt.Core/Utility/IL.cs:267— LanguageExt.Core/Utility/IL.cs:267-284 | LanguageExt.Core/Utility/IL.cs:316-333 | LanguageExt.Core/Utility/IL.cs:368-385 | LanguageExt.Core/Utility/IL.cs:423-440 — 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 `LanguageExt.Core/Utility/IL.cs:267` 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, `LanguageExt.Core/Utility/IL.cs:334` calls `Emit` and `LanguageExt.Core/Utility/IL.cs:285` 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 × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1593— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1593-1610 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1619-1636 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1575-1592 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1601-1618 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1593` 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 (18 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1765— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1765-1782 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1792-1809 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1746-1763 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1773-1790 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1765` 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 `rhs` to `HashMap<EqK, K, V>` in one and `HashMap<K, V>` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1791` calls `toSeq` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1764` 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 (19 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:336— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:336-354 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:310-328 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (19 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1052— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1052-1070 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1026-1044 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (19 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1670— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1670-1688 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1651-1669 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `rhs` to `HashMap<EqK, K, V>` in one and `HashMap<K, V>` 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 (16 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:111— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:111-126 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:111-126 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:111` 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 (16 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:665— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:665-680 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:757-772 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:665` 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 (16 lines × 2) LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:22— LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:22-37 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:71-86 — 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 `LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.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.
Duplicated block (11 lines × 3) LanguageExt.Streaming/SourceT/DSL/Zip2SourceT.cs:25— LanguageExt.Streaming/SourceT/DSL/Zip2SourceT.cs:25-35 | LanguageExt.Streaming/SourceT/DSL/Zip3SourceT.cs:32-42 | LanguageExt.Streaming/SourceT/DSL/Zip4SourceT.cs:33-43 — before extracting anything, compare `LanguageExt.Streaming/SourceT/DSL/Zip3SourceT.cs` and `LanguageExt.Streaming/SourceT/DSL/Zip4SourceT.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (11 lines × 3) LanguageExt.Core/Class Instances/Eq/EqLst.cs:20— LanguageExt.Core/Class Instances/Eq/EqLst.cs:20-30 | LanguageExt.Core/Class Instances/Eq/EqQue.cs:21-31 | LanguageExt.Core/Class Instances/Eq/EqStck.cs:20-30 — 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 `LanguageExt.Core/Class Instances/Eq/EqLst.cs:20` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `x` to `Lst<A>` in one and `Que<A>` 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 (11 lines × 3) Samples/DomainTypesExamples/Vector.cs:84— Samples/DomainTypesExamples/Vector.cs:84-94 | Samples/DomainTypesExamples/Vector.cs:108-118 | Samples/DomainTypesExamples/Vector.cs:135-145 — 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 `Samples/DomainTypesExamples/Vector.cs:84` 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 × 4) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2257— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2257-2263 | LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2291-2297 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:747-753 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:781-787 — `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs` and `LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2257` 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 × 4) LanguageExt.Core/Utility/IL.cs:127— LanguageExt.Core/Utility/IL.cs:127-133 | LanguageExt.Core/Utility/IL.cs:168-174 | LanguageExt.Core/Utility/IL.cs:381-387 | LanguageExt.Core/Utility/IL.cs:436-442 — 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 `LanguageExt.Core/Utility/IL.cs:127` 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, `LanguageExt.Core/Utility/IL.cs:175` calls `Emit` and `LanguageExt.Core/Utility/IL.cs:134` 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 (7 lines × 4) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1857— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1857-1863 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1994-2000 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2060-2066 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2082-2088 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1857` 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 × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:72— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:72-80 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:146-154 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:298-306 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:443-451 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:72` 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 (9 lines × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107-115 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:186-194 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:371-379 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:510-518 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107` 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 (9 lines × 4) LanguageExt.Core/Utility/Reflect.cs:238— LanguageExt.Core/Utility/Reflect.cs:238-246 | LanguageExt.Core/Utility/Reflect.cs:252-260 | LanguageExt.Core/Utility/Reflect.cs:267-275 | LanguageExt.Core/Utility/Reflect.cs:283-291 — 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 `LanguageExt.Core/Utility/Reflect.cs:238` 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) LanguageExt.Core/Utility/Reflect.cs:91— LanguageExt.Core/Utility/Reflect.cs:91-98 | LanguageExt.Core/Utility/Reflect.cs:106-113 | LanguageExt.Core/Utility/Reflect.cs:121-128 | LanguageExt.Core/Utility/Reflect.cs:137-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 `LanguageExt.Core/Utility/Reflect.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.
Duplicated block (8 lines × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:229— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:229-236 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:267-274 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:340-347 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:413-420 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:229` 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 × 4) LanguageExt.Core/Utility/IL.cs:52— LanguageExt.Core/Utility/IL.cs:52-59 | LanguageExt.Core/Utility/IL.cs:87-94 | LanguageExt.Core/Utility/IL.cs:124-131 | LanguageExt.Core/Utility/IL.cs:165-172 — 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, `LanguageExt.Core/Utility/IL.cs:95` calls `Emit` and `LanguageExt.Core/Utility/IL.cs:60` 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 × 4) LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:42— LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:42-46 | LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Prelude.cs:43-47 | LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:42-46 | LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Prelude.cs:43-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:47` calls `Equals` and `LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:47` 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 × 4) LanguageExt.Core/Utility/IL.cs:363— LanguageExt.Core/Utility/IL.cs:363-367 | LanguageExt.Core/Utility/IL.cs:417-421 | LanguageExt.Core/Utility/Reflect.cs:273-277 | LanguageExt.Core/Utility/Reflect.cs:289-293 — 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. 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 (5 lines × 4) LanguageExt.Streaming/Transducers/Transducer/DSL/ComposeTransducer.cs:64— LanguageExt.Streaming/Transducers/Transducer/DSL/ComposeTransducer.cs:64-68 | LanguageExt.Streaming/Transducers/Transducer/DSL/ComposeTransducer.cs:91-95 | LanguageExt.Streaming/Transducers/TransducerM/DSL/ComposeTransducer.cs:52-56 | LanguageExt.Streaming/Transducers/TransducerM/DSL/ComposeTransducer.cs:76-80 — 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 `LanguageExt.Streaming/Transducers/Transducer/DSL/ComposeTransducer.cs:64` 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.
Outbound HTTP without resilience Samples/Newsletter/Newsletter/Effects/Runtime.cs:31— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Outbound HTTP without resilience Samples/Newsletter/Newsletter/Effects/Runtime.cs:40— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Outbound HTTP without resilience Samples/TestBed.Web.Runner/Program.cs:5— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
VectorClock.relation (cyclomatic 19) LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:259— VectorClock.relation has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function items inside it that branch (go, checkCauses). 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.
VectorClock.relation (cyclomatic 19) LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:260— VectorClock.relation has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function items inside it that branch (go, checkCauses). 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.
Iterable.Bind (cyclomatic 16) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:432— Iterable.Bind 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. This shape REPEATS in the file: one other method here (Iterable.Bind) 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.
Iterable.Bind (cyclomatic 16) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:495— Iterable.Bind 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. This shape REPEATS in the file: one other method here (Iterable.Bind) 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.
Iterable.Bind (cognitive 41) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:432— Iterable.Bind has cognitive complexity 41 (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. This shape REPEATS in the file: one other method here (Iterable.Bind) 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.
Iterable.Bind (cognitive 41) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:495— Iterable.Bind has cognitive complexity 41 (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. This shape REPEATS in the file: one other method here (Iterable.Bind) 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.
IterableAdd.FoldWhileIO (cognitive 31) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:80— IterableAdd.FoldWhileIO has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 85, 121). 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. This shape REPEATS in the file: 3 other methods here (IterableAdd.FoldWhileIO, IterableAdd.FoldUntilIO, IterableAdd.FoldUntilIO) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
IterableAdd.FoldWhileIO (cognitive 31) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:158— IterableAdd.FoldWhileIO has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 160, 196). 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. This shape REPEATS in the file: 3 other methods here (IterableAdd.FoldWhileIO, IterableAdd.FoldUntilIO, IterableAdd.FoldUntilIO) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
IterableAdd.FoldUntilIO (cognitive 31) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:233— IterableAdd.FoldUntilIO has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 238, 270). 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. This shape REPEATS in the file: 3 other methods here (IterableAdd.FoldWhileIO, IterableAdd.FoldWhileIO, IterableAdd.FoldUntilIO) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
IterableAdd.FoldUntilIO (cognitive 31) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:304— IterableAdd.FoldUntilIO has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 306, 338). 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. This shape REPEATS in the file: 3 other methods here (IterableAdd.FoldWhileIO, IterableAdd.FoldWhileIO, IterableAdd.FoldUntilIO) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
VectorClock.relation::go (cognitive 26) LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:263— VectorClock.relation::go has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (26 pts) (nesting depth added 17). 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.
VectorClock.relation::go (cognitive 26) LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:264— VectorClock.relation::go has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (26 pts) (nesting depth added 17). 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.
Entries.Update (cognitive 24) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2289— Entries.Update 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.
Entries.Update (cognitive 24) LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:779— Entries.Update 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.
Entries.Remove (cognitive 21) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2168— Entries.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.
Entries.Remove (cognitive 21) LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:664— Entries.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.
IterableConcat.FoldWhileIO (cognitive 18) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:51— IterableConcat.FoldWhileIO has cognitive complexity 18 (threshold 15). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 52). 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: 3 other methods here (IterableConcat.FoldWhileIO, IterableConcat.FoldUntilIO, IterableConcat.FoldUntilIO) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
IterableConcat.FoldWhileIO (cognitive 18) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:84— IterableConcat.FoldWhileIO has cognitive complexity 18 (threshold 15). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 85). 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: 3 other methods here (IterableConcat.FoldWhileIO, IterableConcat.FoldUntilIO, IterableConcat.FoldUntilIO) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
IterableConcat.FoldUntilIO (cognitive 18) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:117— IterableConcat.FoldUntilIO has cognitive complexity 18 (threshold 15). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 118). 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: 3 other methods here (IterableConcat.FoldWhileIO, IterableConcat.FoldWhileIO, IterableConcat.FoldUntilIO) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
IterableConcat.FoldUntilIO (cognitive 18) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:149— IterableConcat.FoldUntilIO has cognitive complexity 18 (threshold 15). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 150). 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: 3 other methods here (IterableConcat.FoldWhileIO, IterableConcat.FoldWhileIO, IterableConcat.FoldUntilIO) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
MethodTooLong: Token.makeTokenParser LanguageExt.Parsec/Parsers/Token.cs:44— MethodTooLong — makeTokenParser runs 253 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× 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: Token2.makeTokenParser LanguageExt.Parsec/Parsers/Token2.cs:44— MethodTooLong — makeTokenParser runs 244 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 144 over it, 2.44× 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.
Change coupling: Effect.cs ↔ Pipe.cs LanguageExt.Streaming/Pipes/Effect/Effect.cs:1— `LanguageExt.Streaming/Pipes/Effect/Effect.cs` and `LanguageExt.Streaming/Pipes/Pipe/Pipe.cs` change together 55% of the time (11 of the 20 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `3a50433e` Add Producer and Consumer monad-transformer abstractions (at that commit the files were still `LanguageExt.Pipes/Effect/Effect.cs` and `LanguageExt.Pipes/Pipe/Pipe.cs`); `782ffb26` Pipes transformer refactor WIP (at that commit the files were still `LanguageExt.Core/Effects/Pipes/Effect/Effect.cs` and `LanguageExt.Core/Effects/Pipes/Pipe/Pipe.cs`); `cdaf6a5f` Merge error handling (at that commit the files were still `LanguageExt.Core/Effects/Pipes/Effect/Effect.cs` and `LanguageExt.Core/Effects/Pipes/Pipe/Pipe.cs`) — run `git show` on any of them.
Change coupling: Consumer.cs ↔ Effect.cs LanguageExt.Streaming/Pipes/Consumer/Consumer.cs:1— `LanguageExt.Streaming/Pipes/Consumer/Consumer.cs` and `LanguageExt.Streaming/Pipes/Effect/Effect.cs` change together 50% of the time (8 of the 16 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `9158b53d` Refactor pipes to support `Eff` and enhance type-safety. (at that commit the files were still `LanguageExt.Pipes/Consumer/Consumer.cs` and `LanguageExt.Pipes/Effect/Effect.cs`); `3a50433e` Add Producer and Consumer monad-transformer abstractions (at that commit the files were still `LanguageExt.Pipes/Consumer/Consumer.cs` and `LanguageExt.Pipes/Effect/Effect.cs`); `782ffb26` Pipes transformer refactor WIP (at that commit the files were still `LanguageExt.Core/Effects/Pipes/Consumer/Consumer.cs` and `LanguageExt.Core/Effects/Pipes/Effect/Effect.cs`) — run `git show` on any of them.
Duplicated block (29 lines × 2) LanguageExt.Parsec/Parsec.Internal.cs:156— LanguageExt.Parsec/Parsec.Internal.cs:156-184 | LanguageExt.Parsec/ParsecIO.Internal.cs:150-178 — before extracting anything, compare `LanguageExt.Parsec/Parsec.Internal.cs` and `LanguageExt.Parsec/ParsecIO.Internal.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 `LanguageExt.Parsec/Parsec.Internal.cs:156` 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) LanguageExt.Core/Traits/Eq/Eq.Extensions.cs:18— LanguageExt.Core/Traits/Eq/Eq.Extensions.cs:18-46 | LanguageExt.Core/Traits/Eq/Eq.Prelude.cs:18-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.
Duplicated block (25–26 lines × 2) LanguageExt.Parsec/Parsec.Internal.cs:146— LanguageExt.Parsec/Parsec.Internal.cs:146-171 | LanguageExt.Parsec/Parsec.Internal.cs:191-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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Parsec/Parsec.Internal.cs:146` 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. 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 (25–26 lines × 2) LanguageExt.Parsec/ParsecIO.Internal.cs:140— LanguageExt.Parsec/ParsecIO.Internal.cs:140-165 | LanguageExt.Parsec/ParsecIO.Internal.cs:185-209 — 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 `LanguageExt.Parsec/ParsecIO.Internal.cs:140` 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. 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 (22 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:561— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:561-582 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:596-617 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:535-556 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:570-591 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:561` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `range` to `IEnumerable<(K Key, V Value)>` in one and `IEnumerable<KeyValuePair<K, V>>` 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 (22 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1166— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1166-1187 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1199-1220 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1140-1161 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1173-1194 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1166` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `items` to `IEnumerable<KeyValuePair<K, V>>` in one and `IEnumerable<(K Key, V Value)>` 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 × 4) LanguageExt.Parsec/Parsec.Internal.cs:149— LanguageExt.Parsec/Parsec.Internal.cs:149-167 | LanguageExt.Parsec/Parsec.Internal.cs:194-212 | LanguageExt.Parsec/ParsecIO.Internal.cs:143-161 | LanguageExt.Parsec/ParsecIO.Internal.cs:188-206 — before extracting anything, compare `LanguageExt.Parsec/Parsec.Internal.cs` and `LanguageExt.Parsec/ParsecIO.Internal.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 `LanguageExt.Parsec/Parsec.Internal.cs:149` 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 × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:270— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:270-288 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:307-325 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:244-262 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:281-299 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `pred` to `Func<V, bool>` in one and `Func<K, V, bool>` 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 (20 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1710— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1710-1729 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1737-1756 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1691-1710 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1718-1737 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `rhs` to `IEnumerable<K>` in one and `IEnumerable<(K Key, V Value)>` 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 (20 lines × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:847— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:847-866 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:876-895 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:905-924 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:934-953 — 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.
Duplicated block (19–20 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:251— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:251-269 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:283-302 — 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 `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:251` 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. 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–20 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:319— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:319-337 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:351-370 — 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 `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.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. 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. 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 (15 lines × 2) LanguageExt.Core/Utility/IL.cs:168— LanguageExt.Core/Utility/IL.cs:168-182 | LanguageExt.Core/Utility/IL.cs:436-450 — 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 `LanguageExt.Core/Utility/IL.cs:168` 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 (15 lines × 2) LanguageExt.Core/Immutable Collections/Seq/Seq.cs:314— LanguageExt.Core/Immutable Collections/Seq/Seq.cs:314-328 | LanguageExt.Core/Immutable Collections/Seq/Seq.cs:340-354 — 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 `LanguageExt.Core/Immutable Collections/Seq/Seq.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. 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 (18 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1646— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1646-1663 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1627-1644 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1646` 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 (18 lines × 2) LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:121— LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:121-138 | LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:160-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 `LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:121` 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 × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:411— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:411-425 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:949-963 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:385-399 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:923-937 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:411` 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 × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:941— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:941-955 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:978-992 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:915-929 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:952-966 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:941` 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 (12 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:756— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:756-767 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:786-797 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:730-741 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:760-771 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:756` 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 (12 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:819— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:819-830 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:849-860 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:793-804 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:823-834 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:819` 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 `None` to `Func<Option<V>>` in one and `Option<V>` 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 (8 lines × 3) LanguageExt.Core/Utility/Reflect.cs:166— LanguageExt.Core/Utility/Reflect.cs:166-173 | LanguageExt.Core/Utility/Reflect.cs:182-189 | LanguageExt.Core/Utility/Reflect.cs:210-217 — 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 `LanguageExt.Core/Utility/Reflect.cs:166` 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) LanguageExt.Core/Class Instances/Ord/OrdEnumerable.cs:51— LanguageExt.Core/Class Instances/Ord/OrdEnumerable.cs:51-58 | LanguageExt.Core/Class Instances/Ord/OrdIterable.cs:49-56 | LanguageExt.Core/Class Instances/Ord/OrdSeq.cs:43-50 — before extracting anything, compare `LanguageExt.Core/Class Instances/Ord/OrdEnumerable.cs` and `LanguageExt.Core/Class Instances/Ord/OrdIterable.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Class Instances/Ord/OrdEnumerable.cs:51` 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 × 3) LanguageExt.Core/Utility/Reflect.cs:252— LanguageExt.Core/Utility/Reflect.cs:252-261 | LanguageExt.Core/Utility/Reflect.cs:267-276 | LanguageExt.Core/Utility/Reflect.cs:283-292 — 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 `LanguageExt.Core/Utility/Reflect.cs:252` 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 (10 lines × 3) LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:24— LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:24-33 | LanguageExt.Core/Immutable Collections/HashSet/Trait/HashSet.TraitImpl.cs:22-31 | LanguageExt.Core/Immutable Collections/Set/Trait/Set.TraitImpl.cs:20-29 — 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 × 5) LanguageExt.Core/Utility/Reflect.cs:78— LanguageExt.Core/Utility/Reflect.cs:78-83 | LanguageExt.Core/Utility/Reflect.cs:93-98 | LanguageExt.Core/Utility/Reflect.cs:108-113 | LanguageExt.Core/Utility/Reflect.cs:123-128 | LanguageExt.Core/Utility/Reflect.cs:139-144 — all 5 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 `LanguageExt.Core/Utility/Reflect.cs:78` 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 (6 lines × 5) LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1191— LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1191-1196 | LanguageExt.Core/Immutable Collections/Map/Map.Ord.cs:961-966 | LanguageExt.Core/Immutable Collections/Map/Map.cs:1256-1261 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.cs:1135-1140 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.cs:1136-1141 — `LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs` and `LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.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 30 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1188` calls `MethodImpl` and `LanguageExt.Core/Immutable Collections/Map/Map.Ord.cs:951` 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 × 3) LanguageExt.Streaming/SourceT/DSL/Reader2SourceT.cs:14— LanguageExt.Streaming/SourceT/DSL/Reader2SourceT.cs:14-18 | LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:17-21 | LanguageExt.Streaming/SourceT/DSL/Reader4SourceT.cs:18-22 — 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 `LanguageExt.Streaming/SourceT/DSL/Reader2SourceT.cs:14` 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 (5 lines × 3) LanguageExt.Streaming/SourceT/DSL/Zip2SourceT.cs:66— LanguageExt.Streaming/SourceT/DSL/Zip2SourceT.cs:66-70 | LanguageExt.Streaming/SourceT/DSL/Zip3SourceT.cs:81-85 | LanguageExt.Streaming/SourceT/DSL/Zip4SourceT.cs:91-95 — before extracting anything, compare `LanguageExt.Streaming/SourceT/DSL/Zip3SourceT.cs` and `LanguageExt.Streaming/SourceT/DSL/Zip4SourceT.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (99 lines × 2) LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Arithmetic.cs:24— LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Arithmetic.cs:24-122 | LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Arithmetic.cs:20-118 — `LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Arithmetic.cs` and `LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Arithmetic.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 99 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 (99 lines × 2) LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Memo.Arithmetic.cs:24— LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Memo.Arithmetic.cs:24-122 | LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Memo.Arithmetic.cs:20-118 — `LanguageExt.Core/Traits/Applicative/Extensions/Applicative.Extensions.Memo.Arithmetic.cs` and `LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Memo.Arithmetic.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 99 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 (69 lines × 2) LanguageExt.Core/Traits/Fallible/Fallible.Extensions.Fails.E.cs:22— LanguageExt.Core/Traits/Fallible/Fallible.Extensions.Fails.E.cs:22-90 | LanguageExt.Core/Traits/Fallible/Fallible.Prelude.Fails.E.cs:21-102 — 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 (69 lines × 2) LanguageExt.Core/Traits/Fallible/Fallible.Extensions.Succs.E.cs:22— LanguageExt.Core/Traits/Fallible/Fallible.Extensions.Succs.E.cs:22-90 | LanguageExt.Core/Traits/Fallible/Fallible.Prelude.Succs.E.cs:21-102 — 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.
Hollow method — returns a constant without doing the work LanguageExt.Core/Class Instances/Ord/OrdTrue.cs:10— `Compare` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work LanguageExt.Core/DataTypes/Fail/Fail.cs:41— `SelectMany` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
IC1 · Incompleteness & stubs· Both branches open with the same statements · ×2
Both branches open with the same statements — the condition does not decide them LanguageExt.Parsec/Parsec.Internal.cs:119— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them LanguageExt.Parsec/ParsecIO.Internal.cs:113— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
X2 · Cancellation propagation· Async local function without CancellationToken · ×2
Async local function without CancellationToken: chunks LanguageExt.Sys/Sys/IO/Stream.cs:22— 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.
Async local function without CancellationToken: go LanguageExt.Sys/Sys/IO/TextRead.cs:36— 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.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
Internal.chaini (cyclomatic 29) LanguageExt.Parsec/Parsec.Internal.cs:85— Internal.chaini has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 88). 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.
InternalIO.chaini (cyclomatic 29) LanguageExt.Parsec/ParsecIO.Internal.cs:79— InternalIO.chaini has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 82). 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.
Patch.Combine (cyclomatic 21) LanguageExt.Core/DataTypes/Patch/Patch.cs:105— Patch.Combine has cyclomatic complexity 21 (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.
TaskExtensions.WindowMap (cyclomatic 19) LanguageExt.Core/Concurrency/Task/Task.Extensions.cs:303— TaskExtensions.WindowMap has cyclomatic complexity 19 (threshold 15). Of this number, 18 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.
Patch.transformWith (cyclomatic 19) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:374— Patch.transformWith has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function items inside it that branch (go, offset). 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.
ParserExtensions.SelectMany (cyclomatic 19) LanguageExt.Parsec/Parser.cs:107— ParserExtensions.SelectMany has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 111). 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.
ParserIOExtensions.SelectMany (cyclomatic 19) LanguageExt.Parsec/ParserIO.cs:112— ParserIOExtensions.SelectMany has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 116). 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.
Patch.composable::go (cyclomatic 17) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:141— Patch.composable::go has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
IO.RunAsyncInternal (cyclomatic 17) LanguageExt.Core/Effects/IO/IO.cs:917— IO.RunAsyncInternal has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ListModule.Remove (cyclomatic 17) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:848— ListModule.Remove 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.
ListModule.Remove (cyclomatic 16) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:799— ListModule.Remove 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.
Internal.chaini (cognitive 74) LanguageExt.Parsec/Parsec.Internal.cs:85— Internal.chaini has cognitive complexity 74 (threshold 15). Most of this is not in the body itself: 1 of the 74 points is its own statement and the rest belongs to one function literal inside it that branches (line 88). 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.
InternalIO.chaini (cognitive 74) LanguageExt.Parsec/ParsecIO.Internal.cs:79— InternalIO.chaini has cognitive complexity 74 (threshold 15). Most of this is not in the body itself: 1 of the 74 points is its own statement and the rest belongs to one function literal inside it that branches (line 82). 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.
IO.RunAsyncInternal (cognitive 31) LanguageExt.Core/Effects/IO/IO.cs:917— IO.RunAsyncInternal 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.
Patch.Combine (cognitive 29) LanguageExt.Core/DataTypes/Patch/Patch.cs:105— Patch.Combine 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.
TaskExtensions.WindowMap (cognitive 28) LanguageExt.Core/Concurrency/Task/Task.Extensions.cs:303— TaskExtensions.WindowMap has cognitive complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 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.
Iterable.CompareToIO (cognitive 27) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:1029— Iterable.CompareToIO has cognitive complexity 27 (threshold 15). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1036, 1060). 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.
ParserExtensions.SelectMany (cognitive 24) LanguageExt.Parsec/Parser.cs:107— ParserExtensions.SelectMany has cognitive complexity 24 (threshold 15). None of this is in the body itself: all 24 points belong to one function literal inside it that branches (line 111). 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.
ParserIOExtensions.SelectMany (cognitive 24) LanguageExt.Parsec/ParserIO.cs:112— ParserIOExtensions.SelectMany has cognitive complexity 24 (threshold 15). None of this is in the body itself: all 24 points belong to one function literal inside it that branches (line 116). 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.
Reach.offset (cognitive 24) LanguageExt.Megaparsec/Reach.cs:18— Reach.offset 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.
ListModule.Remove (cognitive 22) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:848— ListModule.Remove has cognitive complexity 22 (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.
IL.ToString (cognitive 22) LanguageExt.Core/Utility/IL.cs:837— IL.ToString has cognitive complexity 22 (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.
Common.mergeError (cognitive 22) LanguageExt.Parsec/Common.cs:16— Common.mergeError has cognitive complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to one function literal 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.
Patch.transformWith::go (cognitive 21) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:379— Patch.transformWith::go has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (9 pts), boolean chains 1 (nesting depth added 10). 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.
ListModule.Remove (cognitive 21) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:799— ListModule.Remove has cognitive complexity 21 (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.
BindIter.MoveNext (cognitive 20) LanguageExt.Core/Utility/EnumerableOptimal.cs:163— BindIter.MoveNext has cognitive complexity 20 (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.
Prim.manyn0 (cognitive 19) LanguageExt.Parsec/Parsers/Prim.cs:432— Prim.manyn0 has cognitive complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 435). 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.
IO.RunAsync (cognitive 18) LanguageExt.Core/Effects/IO/IO.cs:835— IO.RunAsync 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.
ListModule.Remove (cognitive 17) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:897— ListModule.Remove 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.
SeqLazy.Take (cognitive 17) LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:393— SeqLazy.Take 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.
Patch.composable::go (cognitive 16) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:141— Patch.composable::go has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 5, if/else 4, ternaries 1 (4 pts), match/switch 1 (3 pts) (nesting depth added 5). 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.
Patch.apply (cognitive 16) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:273— Patch.apply 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 (go). 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.
ConsValueEnum.TailAsync (cognitive 16) LanguageExt.Core/Immutable Collections/IteratorAsync/DSL/IteratorAsync.ConsValueEnum.cs:76— ConsValueEnum.TailAsync 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.
ClassTooLong: IL LanguageExt.Core/Utility/IL.cs— ClassTooLong — 776 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 376 over it, 1.94× 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.
Near-duplicate member pair (240 shared lines) LanguageExt.Parsec/Parsers/Token.cs:45— LanguageExt.Parsec/Parsers/Token.cs:45-359 | LanguageExt.Parsec/Parsers/Token2.cs:45-348 — These two members are variants of one another: 240 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 (104 shared lines) LanguageExt.Parsec/Parsec.Internal.cs:86— LanguageExt.Parsec/Parsec.Internal.cs:86-228 | LanguageExt.Parsec/ParsecIO.Internal.cs:80-222 — These two members are variants of one another: 104 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 (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) LanguageExt.Core/Monads/Free/Trait/Free.TraitImpl.cs:39— LanguageExt.Core/Monads/Free/Trait/Free.TraitImpl.cs:39-45 | LanguageExt.Core/Monads/Free/Trait/Free.TraitImpl.cs:48-54 — These two members are one piece of code written twice and then edited apart: 7 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· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:16— LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:16-32 | LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:46-62 — These two members are one piece of code written twice and then edited apart: 17 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· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) LanguageExt.Parsec/Parser.cs:79— LanguageExt.Parsec/Parser.cs:79-105 | LanguageExt.Parsec/ParserIO.cs:84-110 — These two members are one piece of code written twice and then edited apart: 22 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 (13 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (13 members, 50+ identical tokens) LanguageExt.Core/Utility/IL.cs:44— LanguageExt.Core/Utility/IL.cs:44-72 | LanguageExt.Core/Utility/IL.cs:79-109 | LanguageExt.Core/Utility/IL.cs:116-148 | LanguageExt.Core/Utility/IL.cs:155-191 | LanguageExt.Core/Utility/IL.cs:197-249 | LanguageExt.Core/Utility/IL.cs:255-297 | LanguageExt.Core/Utility/IL.cs:303-348 | LanguageExt.Core/Utility/IL.cs:354-402 | LanguageExt.Core/Utility/IL.cs:408-459 | LanguageExt.Core/Utility/Reflect.cs:238-249 | LanguageExt.Core/Utility/Reflect.cs:252-264 | LanguageExt.Core/Utility/Reflect.cs:267-280 | LanguageExt.Core/Utility/Reflect.cs:283-297 — 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 (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:372— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:372-391 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:436-455 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:468-487 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:500-519 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:878-897 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:910-929 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:346-365 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:410-429 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:442-461 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:474-493 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:852-871 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:884-903 — These 12 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 12 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 12 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:335— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:335-354 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:529-550 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:631-652 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:662-683 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1078-1099 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:309-328 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:503-524 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:605-626 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:636-657 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1052-1073 — 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.
Duplicated block (59 lines × 2) LanguageExt.Parsec/Parsers/Token.cs:278— LanguageExt.Parsec/Parsers/Token.cs:278-336 | LanguageExt.Parsec/Parsers/Token2.cs:267-325 — before extracting anything, compare `LanguageExt.Parsec/Parsers/Token.cs` and `LanguageExt.Parsec/Parsers/Token2.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 240 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 (60 lines × 2) LanguageExt.Parsec/Parsers/Token.cs:46— LanguageExt.Parsec/Parsers/Token.cs:46-105 | LanguageExt.Parsec/Parsers/Token2.cs:46-105 — before extracting anything, compare `LanguageExt.Parsec/Parsers/Token.cs` and `LanguageExt.Parsec/Parsers/Token2.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 240 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 (57 lines × 2) LanguageExt.Parsec/Parser.cs:111— LanguageExt.Parsec/Parser.cs:111-167 | LanguageExt.Parsec/ParserIO.cs:116-172 — 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 `LanguageExt.Parsec/Parser.cs:111` 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 (54 lines × 2) LanguageExt.Parsec/Parsers/Token.cs:186— LanguageExt.Parsec/Parsers/Token.cs:186-239 | LanguageExt.Parsec/Parsers/Token2.cs:174-227 — before extracting anything, compare `LanguageExt.Parsec/Parsers/Token.cs` and `LanguageExt.Parsec/Parsers/Token2.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 240 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 `LanguageExt.Parsec/Parsers/Token.cs:186` 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 (42 lines × 2) LanguageExt.Parsec/Parsers/Token.cs:107— LanguageExt.Parsec/Parsers/Token.cs:107-148 | LanguageExt.Parsec/Parsers/Token2.cs:107-148 — before extracting anything, compare `LanguageExt.Parsec/Parsers/Token.cs` and `LanguageExt.Parsec/Parsers/Token2.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 240 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 (40 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:210— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:210-249 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:184-223 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 (31–32 lines × 2) LanguageExt.Parsec/Parsers/Prim.cs:377— LanguageExt.Parsec/Parsers/Prim.cs:377-407 | LanguageExt.Parsec/Parsers/Prim.cs:435-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 `LanguageExt.Parsec/Parsers/Prim.cs:377` 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 (28 lines × 2) LanguageExt.Parsec/Parsec.Internal.cs:201— LanguageExt.Parsec/Parsec.Internal.cs:201-228 | LanguageExt.Parsec/ParsecIO.Internal.cs:195-222 — before extracting anything, compare `LanguageExt.Parsec/Parsec.Internal.cs` and `LanguageExt.Parsec/ParsecIO.Internal.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 `LanguageExt.Parsec/Parsec.Internal.cs:201` 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. 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 (27 lines × 4) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1159— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1159-1185 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:84-110 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs:84-110 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.cs:84-110 — before extracting anything, compare `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs` and `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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 before the matched lines, `LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1156` calls `MethodImpl` and `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:80` 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 (25 lines × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1383— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1383-1407 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1427-1451 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1471-1495 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1515-1539 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1383` 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 (26–27 lines × 2) LanguageExt.Core/Effects/IO/IO.cs:869— LanguageExt.Core/Effects/IO/IO.cs:869-895 | LanguageExt.Core/Effects/IO/IO.cs:963-988 — 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 `LanguageExt.Core/Effects/IO/IO.cs:869` 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. 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. 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 (26 lines × 2) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:821— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:821-846 | LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:870-895 — 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 `LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:821` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (24–26 lines × 2) LanguageExt.Core/Utility/IL.cs:565— LanguageExt.Core/Utility/IL.cs:565-590 | LanguageExt.Core/Utility/IL.cs:631-654 — 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 `LanguageExt.Core/Utility/IL.cs:565` 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–23 lines × 2) LanguageExt.Core/Utility/IL.cs:1025— LanguageExt.Core/Utility/IL.cs:1025-1047 | LanguageExt.Core/Utility/IL.cs:1104-1125 — 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 `LanguageExt.Core/Utility/IL.cs:1025` 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 (19 lines × 12) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:373— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:373-391 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:437-455 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:469-487 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:501-519 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:879-897 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:911-929 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:347-365 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:411-429 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:443-461 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:475-493 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:853-871 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:885-903 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `None` to `Func<V>` in one and `V` 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 × 8) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:530— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:530-548 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:632-650 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:663-681 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1079-1097 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:504-522 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:606-624 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:637-655 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1053-1071 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:530` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `range` to `IEnumerable<(K Key, V Value)>` in one and `IEnumerable<KeyValuePair<K, V>>` 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 × 10) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:337— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:337-354 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:533-550 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:635-652 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:666-683 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1082-1099 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:311-328 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:507-524 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:609-626 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:640-657 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1056-1073 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:337` 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, `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:531` calls `toSeq` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:336` 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–18 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:575— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:575-591 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1214-1231 — 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 (15 lines × 5) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:376— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:376-390 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:133-147 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Cast.cs:66-80 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:183-197 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Enumerable.cs:116-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 all 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:376` 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 × 5) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:398— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:398-413 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:158-173 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Cast.cs:85-100 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:202-217 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Enumerable.cs:152-167 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:398` 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 (14 lines × 3) LanguageExt.Core/Utility/IL.cs:46— LanguageExt.Core/Utility/IL.cs:46-59 | LanguageExt.Core/Utility/IL.cs:81-94 | LanguageExt.Core/Utility/IL.cs:118-131 — 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 `LanguageExt.Core/Utility/IL.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `LanguageExt.Core/Utility/IL.cs:95` calls `Emit` and `LanguageExt.Core/Utility/IL.cs:60` 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 × 2) LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:81— LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:81-96 | LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:110-124 — 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 `LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:81` 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–15 lines × 2) LanguageExt.Core/Concurrency/AtomQue/AtomQue.cs:172— LanguageExt.Core/Concurrency/AtomQue/AtomQue.cs:172-185 | LanguageExt.Core/Concurrency/AtomQue/AtomQue.cs:197-211 — 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 `LanguageExt.Core/Concurrency/AtomQue/AtomQue.cs:172` 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 (13 lines × 4) LanguageExt.Core/Concurrency/Atom/Atom.Metadata.cs:95— LanguageExt.Core/Concurrency/Atom/Atom.Metadata.cs:95-107 | LanguageExt.Core/Concurrency/Atom/Atom.Metadata.cs:136-148 | LanguageExt.Core/Concurrency/Atom/Atom.cs:93-105 | LanguageExt.Core/Concurrency/Atom/Atom.cs:134-146 — before extracting anything, compare `LanguageExt.Core/Concurrency/Atom/Atom.Metadata.cs` and `LanguageExt.Core/Concurrency/Atom/Atom.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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Concurrency/Atom/Atom.Metadata.cs:95` 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 (13 lines × 3) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:617— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:617-629 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1892-1904 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:874-886 — 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. 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–14 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1272— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1272-1284 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1294-1307 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1272` 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 × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1559— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1559-1569 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1589-1599 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1619-1629 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1649-1659 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1559` 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 × 5) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1159— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1159-1168 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:84-93 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs:84-93 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.cs:84-93 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1480-1489 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1159` 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, `LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1156` calls `MethodImpl` and `LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:80` 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 × 5) LanguageExt.Core/Utility/IL.cs:198— LanguageExt.Core/Utility/IL.cs:198-206 | LanguageExt.Core/Utility/IL.cs:256-264 | LanguageExt.Core/Utility/IL.cs:304-312 | LanguageExt.Core/Utility/IL.cs:355-363 | LanguageExt.Core/Utility/IL.cs:409-417 — all 5 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 `LanguageExt.Core/Utility/IL.cs:198` 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 × 5) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:847— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:847-857 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:876-886 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:905-915 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:934-944 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1152-1162 — all 5 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:847` 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 × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:690— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:690-699 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:724-733 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:783-792 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:816-825 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:690` 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 × 6) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:227— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:227-234 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:265-272 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:338-345 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:411-418 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:477-484 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:552-559 — all 6 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:227` 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 (5 lines × 6) LanguageExt.Core/Utility/IL.cs:311— LanguageExt.Core/Utility/IL.cs:311-315 | LanguageExt.Core/Utility/IL.cs:362-366 | LanguageExt.Core/Utility/IL.cs:416-420 | LanguageExt.Core/Utility/Reflect.cs:257-261 | LanguageExt.Core/Utility/Reflect.cs:272-276 | LanguageExt.Core/Utility/Reflect.cs:288-292 — 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. 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 (124 lines × 2) LanguageExt.Core/DataTypes/ValueTuple/Tuple4/ValueTuple4.Extensions.cs:13— LanguageExt.Core/DataTypes/ValueTuple/Tuple4/ValueTuple4.Extensions.cs:13-143 | LanguageExt.Core/DataTypes/ValueTuple/Tuple4/ValueTuple4.Prelude.cs:14-137 — 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 (133 lines × 2) LanguageExt.Core/DataTypes/ValueTuple/Tuple5/ValueTuple5.Extensions.cs:13— LanguageExt.Core/DataTypes/ValueTuple/Tuple5/ValueTuple5.Extensions.cs:13-152 | LanguageExt.Core/DataTypes/ValueTuple/Tuple5/ValueTuple5.Prelude.cs:14-146 — 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 (46 lines × 2) LanguageExt.Core/Monads/Alternative Monads/These/Prelude/These.Prelude.cs:14— LanguageExt.Core/Monads/Alternative Monads/These/Prelude/These.Prelude.cs:14-59 | LanguageExt.Core/Monads/Alternative Monads/These/These.Module.cs:14-61 — before extracting anything, compare `LanguageExt.Core/Monads/Alternative Monads/These/Prelude/These.Prelude.cs` and `LanguageExt.Core/Monads/Alternative Monads/These/These.Module.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. 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 (48 lines × 2) LanguageExt.Core/Monads/State and Environment Monads/Writer/Writer/Prelude/Writer.Prelude.cs:16— LanguageExt.Core/Monads/State and Environment Monads/Writer/Writer/Prelude/Writer.Prelude.cs:16-63 | LanguageExt.Core/Monads/State and Environment Monads/Writer/Writer/Writer.Module.cs:9-73 — before extracting anything, compare `LanguageExt.Core/Monads/State and Environment Monads/Writer/Writer/Prelude/Writer.Prelude.cs` and `LanguageExt.Core/Monads/State and Environment Monads/Writer/Writer/Writer.Module.cs` as WHOLE FILES: 98% 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 `LanguageExt.Core/Monads/State and Environment Monads/Writer/Writer/Writer.Module.cs:9` 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 (117 lines × 2) LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Zip.cs:16— LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Zip.cs:16-132 | LanguageExt.Core/Traits/Applicative/Prelude/Applicative.Prelude.cs:19-231 — 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.
Duplicated block (36 lines × 2) LanguageExt.Core/Traits/Fallible/Fallible.Module.cs:22— LanguageExt.Core/Traits/Fallible/Fallible.Module.cs:22-57 | LanguageExt.Core/Traits/Fallible/Fallible.Prelude.cs:23-58 — before extracting anything, compare `LanguageExt.Core/Traits/Fallible/Fallible.Module.cs` and `LanguageExt.Core/Traits/Fallible/Fallible.Prelude.cs` as WHOLE FILES: 94% 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 (468 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Module.cs:24— LanguageExt.Core/Traits/Foldable/Foldable.Module.cs:24-724 | LanguageExt.Core/Traits/Foldable/Foldable.Prelude.cs:21-488 — before extracting anything, compare `LanguageExt.Core/Traits/Foldable/Foldable.Module.cs` and `LanguageExt.Core/Traits/Foldable/Foldable.Prelude.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. 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 (6 lines × 8) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2100— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2100-2105 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:2090-2095 | LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.cs:714-719 | LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1223-1228 | LanguageExt.Core/Immutable Collections/Map/Map.Ord.cs:991-996 | LanguageExt.Core/Immutable Collections/Map/Map.cs:1288-1293 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.cs:1165-1170 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.cs:1166-1171 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 before the matched lines, `LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1220` calls `MethodImpl` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2090` 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 (6 lines × 9) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2168— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2168-2173 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:2157-2162 | LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:1270-1275 | LanguageExt.Core/Immutable Collections/HashMap/HashMap.cs:1186-1191 | LanguageExt.Core/Immutable Collections/Map/Map.Ord.cs:1244-1249 | LanguageExt.Core/Immutable Collections/Map/Map.cs:1479-1484 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.cs:1203-1208 | LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.cs:1215-1220 | LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2760-2765 — before extracting anything, compare `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs` and `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 968 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:2168` 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.
Off the main sequence: LanguageExt.Core LanguageExt.Core/LanguageExt.Core.csproj:1— LanguageExt.Core: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Low cohesion: SeqLazy (LCOM4 4) LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:11— SeqLazy's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
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.
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 endpoint handler without CancellationToken: /async Samples/TestBed.Web/Program.cs:14— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Duplicated predicate LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1165— `!NodeCurrent.IsEmpty && skip != Prev(NodeCurrent).Count` appears character-identically in 5 files — LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs, LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs, LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs, LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.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 LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2390— `!current.IsEmpty && !current.Left.IsEmpty` appears character-identically in 2 files — LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs, LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.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 LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2464— `!current.IsEmpty && !current.Right.IsEmpty` appears character-identically in 2 files — LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs, LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.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 LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:701— `!node.IsEmpty && (pred(node.Key) || Exists(node.Left, pred) || Exists(node.Right, pred))` appears character-identically in 2 files — LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs, LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.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 LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:995— `!node.Left.IsEmpty && node.Left.Count == amount` appears character-identically in 3 files — LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs, LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs, LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.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 LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:999— `!node.Left.IsEmpty && node.Left.Count == amount - 1` appears character-identically in 3 files — LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs, LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs, LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.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 LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:916— `!node.Right.IsEmpty && node.Left.IsEmpty` appears character-identically in 2 files — LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs, LanguageExt.Core/Immutable Collections/Map/Map.Internal.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 LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:229— `1 == Interlocked.Exchange(ref consDisallowed, 1) || start == 0` appears character-identically in 2 files — LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs, LanguageExt.Core/Immutable Collections/Seq/DSL/SeqStrict.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 LanguageExt.Core/DataTypes/ValueTuple/Tuple3/ValueTuple3.Extensions.cs:58— `EQ.Equals(self.Item1, value) || EQ.Equals(self.Item2, value) || EQ.Equals(self.Item3, value)` appears character-identically in 2 files — LanguageExt.Core/DataTypes/ValueTuple/Tuple3/ValueTuple3.Extensions.cs, LanguageExt.Core/DataTypes/ValueTuple/Tuple3/ValueTuple3.Prelude.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 LanguageExt.Core/DataTypes/ValueTuple/Tuple4/ValueTuple4.Extensions.cs:42— `EQ.Equals(self.Item1, value) || EQ.Equals(self.Item2, value) || EQ.Equals(self.Item3, value) || EQ.Equals(self.Item4, value)` appears character-identically in 2 files — LanguageExt.Core/DataTypes/ValueTuple/Tuple4/ValueTuple4.Extensions.cs, LanguageExt.Core/DataTypes/ValueTuple/Tuple4/ValueTuple4.Prelude.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 LanguageExt.Core/DataTypes/ValueTuple/Tuple5/ValueTuple5.Extensions.cs:42— `EQ.Equals(self.Item1, value) || EQ.Equals(self.Item2, value) || EQ.Equals(self.Item3, value) || EQ.Equals(self.Item4, value) || EQ.Equals(se…` appears character-identically in 2 files — LanguageExt.Core/DataTypes/ValueTuple/Tuple5/ValueTuple5.Extensions.cs, LanguageExt.Core/DataTypes/ValueTuple/Tuple5/ValueTuple5.Prelude.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 LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:42— `EQ.Equals(self.Item1, value) || EQ.Equals(self.Item2, value) || EQ.Equals(self.Item3, value) || EQ.Equals(self.Item4, value) || EQ.Equals(se…` appears character-identically in 2 files — LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs, LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Prelude.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 LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:42— `EQ.Equals(self.Item1, value) || EQ.Equals(self.Item2, value) || EQ.Equals(self.Item3, value) || EQ.Equals(self.Item4, value) || EQ.Equals(se…` appears character-identically in 2 files — LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs, LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Prelude.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 LanguageExt.Core/Immutable Collections/Queue/Que.cs:284— `GetHashCode() == other.GetHashCode() && EqEnumerable<A>.Equals(Value, other.Value)` appears character-identically in 2 files — LanguageExt.Core/Immutable Collections/Queue/Que.cs, LanguageExt.Core/Immutable Collections/Stack/Stck.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 LanguageExt.Parsec/ParserResult.cs:78— `Tag == ResultTag.Consumed && Reply.Tag == ReplyTag.Error` appears character-identically in 2 files — LanguageExt.Parsec/ParserResult.cs, LanguageExt.Parsec/ParserResultIO.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 LanguageExt.Parsec/ParserResult.cs:136— `Tag == ResultTag.Consumed && Reply.Tag == ReplyTag.OK` appears character-identically in 2 files — LanguageExt.Parsec/ParserResult.cs, LanguageExt.Parsec/ParserResultIO.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 LanguageExt.Parsec/ParserResult.cs:74— `Tag == ResultTag.Empty && Reply.Tag == ReplyTag.Error` appears character-identically in 2 files — LanguageExt.Parsec/ParserResult.cs, LanguageExt.Parsec/ParserResultIO.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 LanguageExt.Parsec/ParserResult.cs:128— `Tag == ResultTag.Empty && Reply.Tag == ReplyTag.OK` appears character-identically in 2 files — LanguageExt.Parsec/ParserResult.cs, LanguageExt.Parsec/ParserResultIO.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 LanguageExt.Parsec/Parsers/Token.cs:98— `def.CommentLine == null && def.CommentStart == null` appears character-identically in 2 files — LanguageExt.Parsec/Parsers/Token.cs, LanguageExt.Parsec/Parsers/Token2.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 LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs:152— `index.Value >= 0 && index.Value < list.Count` appears character-identically in 2 files — LanguageExt.Core/Immutable Collections/List/Trait/Lst.TraitImpl.cs, LanguageExt.Core/Immutable Collections/Seq/Trait/Seq.TraitImpl.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 LanguageExt.Parsec/ParserIOs/Prim.cs:148— `n.Tag == ResultTag.Empty && n.Reply.Tag == ReplyTag.Error` appears character-identically in 2 files — LanguageExt.Parsec/ParserIOs/Prim.cs, LanguageExt.Parsec/Parsers/Prim.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 LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:912— `node.Right.IsEmpty && !node.Left.IsEmpty` appears character-identically in 2 files — LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs, LanguageExt.Core/Immutable Collections/Map/Map.Internal.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 LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1893— `obj is AtomHashMap<K, V> hm && Equals(hm)` appears character-identically in 2 files — LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs, LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.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 LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1900— `other is not null && Items.Equals(other.Items)` appears character-identically in 5 files — LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs, LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs, LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.K.V.cs, LanguageExt.Core/Concurrency/VersionHashMap/VersionHashMap.ConflictV.OrdActor.EqK.Actor.K.V.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 LanguageExt.Parsec/Parser.cs:40— `res.Reply.Error is null || res.Reply.Error.Tag == ParserErrorTag.Unknown` appears character-identically in 2 files — LanguageExt.Parsec/Parser.cs, LanguageExt.Parsec/ParserIO.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.
Commented-out code LanguageExt.Core/Class Instances/Monoid/Addition.cs:2— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Class Instances/Monoid/MError.cs:2— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Class Instances/Monoid/Product.cs:2— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Concurrency/Async/AsyncEnumerable/AsyncEnumberable.Extensions.cs:9— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/DataTypes/Range/Range.cs:35— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Deriving/Maybe/MonadIO.cs:2— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Deriving/Maybe/MonadUnliftIO.cs:2— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Deriving/Maybe/MonadUnliftIO.cs:37— 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Immutable Collections/Arr/Arr.cs:703— 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 LanguageExt.Core/Immutable Collections/List/Lst.cs:238— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1312— 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 LanguageExt.Core/Immutable Collections/Seq/Seq.cs:486— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Immutable Collections/Set/Set.cs:147— 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2257— 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 LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2264— 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 LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2279— 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 LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2291— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Fat interface: Alternative<F> (22 members) LanguageExt.Core/Traits/Alternative/Alternative.Trait.cs:7— `Alternative<F>` declares 22 members: `Empty`, `Choice`, `Choice`, `Some`, `Many`, `EndBy`, `EndBy1`, `Either`, `ManyUntil`, `ManyUntil2`, `SomeUntil`, `SomeUntil2`, `Option`, `SepBy`, `SepBy1`, `SepByEnd`, `SepByEnd1`, `SkipMany`, `SkipSome`, `Skip`, `SkipManyUntil`, `SkipSomeUntil`. 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. Those 22 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: Applicative<F> (16 members) LanguageExt.Core/Traits/Applicative/Applicative.Trait.cs:16— `Applicative<F>` declares 16 members under just 7 distinct name(s): `Pure`, `Apply`, `Apply`, `Apply`, `Apply`, `Action`, `BackAction`, `Action`, `BackAction`, `Action`, `BackAction`, `Action`, `BackAction`, `Actions`, `Between`, `Replicate`. 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. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 7 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: Floating<A> (18 members) LanguageExt.Core/Traits/Floating/Floating.cs:10— `Floating<A>` declares 18 members: `Pi`, `Exp`, `Sqrt`, `Log`, `Pow`, `LogBase`, `Sin`, `Cos`, `Tan`, `Asin`, `Acos`, `Atan`, `Sinh`, `Cosh`, `Tanh`, `Asinh`, `Acosh`, `Atanh`. 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: Foldable<T> (58 members) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:10— `Foldable<T>` declares 58 members: `FoldStep`, `FoldStepBack`, `FoldWhile`, `FoldBackWhile`, `FoldMaybe`, `FoldBackMaybe`, `FoldWhileM`, `FoldBackWhileM`, `FoldUntil`, `FoldUntilM`, `FoldBackUntil`, `FoldBackUntilM`, `Fold`, `FoldM`, `FoldBack`, `FoldBackM`, `Fold`, `FoldWhile`, `FoldUntil`, `FoldMap`, `FoldMapWhile`, `FoldMapUntil`, `FoldMapBack`, `FoldMapWhileBack`, `FoldMapUntilBack`, `ToSeq`, `ToLst`, `ToArr`, `ToIterable`, `IsEmpty`, `Count`, `Exists`, `ForAll`, `Contains`, `Contains`, `Find`, `FindBack`, `FindAll`, `FindAllBack`, `Sum`, and 18 more. 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. Those 58 declarations carry 45 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 45 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: MonadUnliftIO<M> (73 members) LanguageExt.Core/Traits/Monads/MonadUnliftIO/MonadUnliftIO.Trait.cs:19— `MonadUnliftIO<M>` declares 73 members: `ToIO`, `MapIO`, `ForkIO`, `Await`, `LocalIO`, `UninterruptibleIO`, `PostIO`, `TimeoutIO`, `BracketIO`, `BracketIO`, `BracketIO`, `RepeatIO`, `RepeatIO`, `RepeatWhileIO`, `RepeatWhileIO`, `RepeatUntilIO`, `RepeatUntilIO`, `RetryIO`, `RetryIO`, `RetryWhileIO`, `RetryWhileIO`, `RetryUntilIO`, `RetryUntilIO`, `FoldIO`, `FoldIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldWhileIO`, `FoldUntilIO`, `FoldUntilIO`, `FoldUntilIO`, `FoldUntilIO`, `FoldUntilIO`, `FoldUntilIO`, `LanguageExt.Traits.Maybe.MonadUnliftIO<M>.MapIOMaybe`, `LanguageExt.Traits.Maybe.MonadUnliftIO<M>.ToIOMaybe`, `LanguageExt.Traits.Maybe.MonadUnliftIO<M>.ForkIOMaybe`, and 33 more. 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. Those 73 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: DirectoryIO (30 members) LanguageExt.Sys/Traits/DirectoryIO.cs:6— `DirectoryIO` declares 30 members: `Create`, `Delete`, `GetParent`, `Exists`, `SetCreationTime`, `SetCreationTimeUtc`, `GetCreationTime`, `GetCreationTimeUtc`, `SetLastWriteTime`, `SetLastWriteTimeUtc`, `GetLastWriteTime`, `GetLastWriteTimeUtc`, `SetLastAccessTime`, `SetLastAccessTimeUtc`, `GetLastAccessTime`, `GetLastAccessTimeUtc`, `EnumerateDirectories`, `EnumerateDirectories`, `EnumerateDirectories`, `EnumerateFiles`, `EnumerateFiles`, `EnumerateFiles`, `EnumerateFileSystemEntries`, `EnumerateFileSystemEntries`, `EnumerateFileSystemEntries`, `GetDirectoryRoot`, `GetCurrentDirectory`, `SetCurrentDirectory`, `Move`, `GetLogicalDrives`. 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. Those 30 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: EnvironmentIO (34 members) LanguageExt.Sys/Traits/EnvironmentIO.cs:5— `EnvironmentIO` declares 34 members: `CommandLine`, `CurrentManagedThreadId`, `Exit`, `ExitCode`, `SetExitCode`, `ExpandEnvironmentVariables`, `FailFast`, `FailFast`, `GetCommandLineArgs`, `GetEnvironmentVariable`, `GetEnvironmentVariable`, `GetEnvironmentVariables`, `GetEnvironmentVariables`, `GetFolderPath`, `GetFolderPath`, `GetLogicalDrives`, `HasShutdownStarted`, `Is64BitOperatingSystem`, `Is64BitProcess`, `MachineName`, `NewLine`, `OSVersion`, `ProcessorCount`, `SetEnvironmentVariable`, `SetEnvironmentVariable`, `StackTrace`, `SystemDirectory`, `SystemPageSize`, `TickCount`, `UserDomainName`, `UserInteractive`, `UserName`, `Version`, `WorkingSet`. 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. Those 34 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: FileIO (19 members) LanguageExt.Sys/Traits/FileIO.cs:7— `FileIO` declares 19 members: `Copy`, `Move`, `Move`, `AppendAllLines`, `ReadAllLines`, `ReadAllText`, `ReadAllBytes`, `WriteAllText`, `WriteAllLines`, `WriteAllBytes`, `Delete`, `Exists`, `OpenText`, `CreateText`, `AppendText`, `OpenRead`, `Open`, `Open`, `OpenWrite`. 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. Those 19 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: MonadParsecT<MP, E, S, T, M> (17 members) LanguageExt.Megaparsec/MonadParsecT/MonadParsecT.cs:21— `MonadParsecT<MP, E, S, T, M>` declares 17 members: `Error`, `Label`, `Hidden`, `Try`, `LookAhead`, `NotFollowedBy`, `WithRecovery`, `EOF`, `Observing`, `Token`, `Tokens`, `OneOf`, `NoneOf`, `TakeWhile`, `TakeWhile1`, `Take`, `Lift`. 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.
Silent fallback default in catch LanguageExt.Core/Monads/Alternative Monads/Fin/Fin.cs:403— `convert` swallows every exception into `return None;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch LanguageExt.Core/Prelude/Value parsing/Prelude.Parse.cs:24— `convert` swallows every exception into `return None;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch LanguageExt.Core/Prelude/Value parsing/Prelude.Parse.cs:44— `convert` swallows every exception into `return M.Empty<A>();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch LanguageExt.Core/Prelude/Value parsing/Prelude.Parse.cs:75— `parseInt` swallows every exception into `return None;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch LanguageExt.Core/Prelude/Value parsing/Prelude.Parse.cs:89— `parseInt` swallows every exception into `return M.Empty<int>();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch LanguageExt.Core/Traits/Resolve/Resolver.cs:57— `LoadAssembly` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch LanguageExt.Core/Utility/IL.cs:1264— `GetAvailability` swallows `PlatformNotSupportedException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
README/code drift README.md:77— README.md names the project `LanguageExt.Prelude`, 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 Major Version Release Notes/Version 5/README.md:89— Major Version Release Notes/Version 5/README.md names the project `LanguageExt.SysX`, 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 Major Version Release Notes/Version 5/README.md:90— Major Version Release Notes/Version 5/README.md names the project `LanguageExt.CodeGen`, 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 Major Version Release Notes/Version 5/README.md:91— Major Version Release Notes/Version 5/README.md names the project `LanguageExt.Transformers`, 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 Major Version Release Notes/Version 5/README.md:735— Major Version Release Notes/Version 5/README.md names the project `LanguageExt.Prelude`, 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 Major Version Release Notes/Version 5/README.md:735— Major Version Release Notes/Version 5/README.md names the project `LanguageExt.UnitsOfMeasure`, 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.
Orphaned file LanguageExt.Core/Effects/Schedule/Duration.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 LanguageExt.Core/Prism/Prelude_Prism.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 LanguageExt.Streaming/Transducers/ReducedM.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.
redundant comment Samples/TestBed/Program.cs:24— "This is just my scratch pad for quickly testing stuff, not for human consumption" — keep - it names the purpose of a temporary test call and the audience; no code restatement
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 23 project(s) overshoot their size bounds, lowering Project Cohesion to 8.3/10. The most over is `LanguageExt.Core` (137701 LoC, 1647 public types across 19 namespaces). Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
Scattered collaborators — 56 % of calls cross a namespace and only 46 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 3 of 602 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 602 of the 1389 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: LanguageExt.Core/Effects/Schedule/Duration.cs, LanguageExt.Core/Prism/Prelude_Prism.cs, LanguageExt.Streaming/Transducers/ReducedM.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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'.
Inconsistent root namespaces — Only 10/23 projects share a common root namespace — the code's module identity is inconsistent.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 1902/2239 types (85%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P10 · Library API & versioning· No explicit versioning · ×1
No explicit versioning — No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
Logging is not universal — Only 1/5 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 5, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
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.)
Benchmarks don't track allocations — A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way hot code pressures the GC) aren't being measured.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 26/59 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.
X2 · Cancellation propagation· Some async methods drop the CancellationToken they accept · ×1
Some async methods drop the CancellationToken they accept — 8 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
Nullable reference types not enabled everywhere — 21/22 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 — ~0.5 `!` suppressions per 1k syntax nodes — 394 suppression(s) across the 805290 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 on parse failure LanguageExt.Sys/MemoryConsole.cs:107— `CharToConsoleKey` falls back to `default` when `Enum.TryParse<ConsoleKey>(ch.ToString(), out var ck)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
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.
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a168a8-698f-7bd9-a4a3-26f6499b6f27 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 5 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 29 · Warnings: 837 · Recommendations: 86 · Info: 6 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 12:07 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.