Public report of MarsonShine/Books, published 22 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, 22 October 2026, 05:21 UTC · Survey ID cd_eed65ea6452d444db5368a7e151b4b53
MarsonShine/Books
Measured 22 October 2026, 05:10 UTC, at code version 1ccbbee
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 32,128 lines of product code in 150 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 33
Findings by how serious they are
79 critical850 serious272 minor
8 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
22 October 2026, 05:10 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 ▸
86of 92 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
1169of 1201 findings point to an exact file and line, so you can open each one in the code. The other 32 concern the repository as a whole, such as missing documentation.
92dimensions across 7 lenses, read from 32,128 lines of product code in 150 projects.
MarsonShine/Books scores 40 out of 100 and is rated Weak, while five of its seven lenses score higher still: Architecture at 100, rated Exemplary, Accessibility at 80 and Performance at 72, both rated Strong, Code Health at 56, rated Adequate, and Maturity at 41, rated Weak.
The score is lower than those five because the weakest lens counts most, and here that is Production Readiness, which scores 33 and is rated Weak. Its DR & Backup 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 8 End-of-life runtime finding(s) in Platform End-of-Life and to protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler, and if Production Readiness rose to 70, the score would rise from 40 to about 45.
79 findings are critical: 48 in Explicit Debt, 19 in Static Analysis (SAST), six in Incompleteness & stubs, four in IaC & Container Security and two in Test Quality.
Watchdog couldn't measure 6 dimensions in this code, among them Code Coverage, Dependency Hygiene and Navigability, so they are left out of the score. The product code is 32,128 lines, which would take an estimated 0.2 person-years, around €33,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: 13 findings
These 13 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.
Coupling · Off the main sequence: DynamicLoadExtension (WHPerformanceDotNet/src/DynamicLoadExtension)
Coupling · Off the main sequence: DynamicLoadExtension (docs/WHPerformanceDotNet/src/DynamicLoadExtension)
Outbound HTTP resilience · Outbound HTTP without resilience
Async & latency hygiene · Awaits without ConfigureAwait(false)
Rebuild cost: about €33,000 · Estimate
Cost to rebuild
€11,000 to €55,000, for 183 to 578 hours of work, about 0.2 person-years for one engineer
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 40. 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
Medium: 32,128 lines of product code
Comment lines
The estimate prices 30,528 lines. Comment lines count towards the size of 32,128 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 8 End-of-life runtime finding(s) in Platform End-of-Life — start with Chapter14_ConciseCode.csproj, Net6WebDemo.csproj, SyntaxWalker.csproj.
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Raises the score by about 4 points · Medium effort · Access Controls
3
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs (2).
Raises the score by about 2 points · Low effort · Test Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €33,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 33 (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 8 End-of-life runtime finding(s) in Platform End-of-Life. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 8 Platform End-of-Life 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.
170 modules, with 13 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 130 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
CSharpGuide.LanguageVersions._8._0 uses CSharpGuide.LanguageVersions._8._0.demo, so a change to CSharpGuide.LanguageVersions._8._0.demo can break CSharpGuide.LanguageVersions._8._0, while a change to CSharpGuide.LanguageVersions._8._0 can't break CSharpGuide.LanguageVersions._8._0.demo.
Position
Below the diagonal: CSharpGuide.LanguageVersions._8._0 uses a module listed above it, which is the healthy direction.
DesignPatternCore.Factory.AbstractFactory uses DesignPatternCore.Factory, so a change to DesignPatternCore.Factory can break DesignPatternCore.Factory.AbstractFactory, while a change to DesignPatternCore.Factory.AbstractFactory can't break DesignPatternCore.Factory.
Position
Below the diagonal: DesignPatternCore.Factory.AbstractFactory uses a module listed above it, which is the healthy direction.
DesignPatternCore.Strategy uses DesignPatternCore.Factory, so a change to DesignPatternCore.Factory can break DesignPatternCore.Strategy, while a change to DesignPatternCore.Strategy can't break DesignPatternCore.Factory.
Position
Below the diagonal: DesignPatternCore.Strategy uses a module listed above it, which is the healthy direction.
GenericOptimization.Benchmarks uses GenericOptimization, so a change to GenericOptimization can break GenericOptimization.Benchmarks, while a change to GenericOptimization.Benchmarks can't break GenericOptimization.
Position
Below the diagonal: GenericOptimization.Benchmarks uses a module listed above it, which is the healthy direction.
MarsonShine.Functional uses MarsonShine.Functional.Option, so a change to MarsonShine.Functional.Option can break MarsonShine.Functional, while a change to MarsonShine.Functional can't break MarsonShine.Functional.Option.
Position
Below the diagonal: MarsonShine.Functional uses a module listed above it, which is the healthy direction.
MomeryAllocation uses MomeryAllocation.AvoidBoxed, so a change to MomeryAllocation.AvoidBoxed can break MomeryAllocation, while a change to MomeryAllocation can't break MomeryAllocation.AvoidBoxed.
Position
Below the diagonal: MomeryAllocation uses a module listed above it, which is the healthy direction.
MySourceGenerator.Enums uses MySourceGenerator, so a change to MySourceGenerator can break MySourceGenerator.Enums, while a change to MySourceGenerator.Enums can't break MySourceGenerator.
Position
Below the diagonal: MySourceGenerator.Enums uses a module listed above it, which is the healthy direction.
MySourceGenerator.Enums2 uses MySourceGenerator, so a change to MySourceGenerator can break MySourceGenerator.Enums2, while a change to MySourceGenerator.Enums2 can't break MySourceGenerator.
Position
Below the diagonal: MySourceGenerator.Enums2 uses a module listed above it, which is the healthy direction.
enumerated.cartoons uses net.mindview.util, so a change to net.mindview.util can break enumerated.cartoons, while a change to enumerated.cartoons can't break net.mindview.util.
Position
Below the diagonal: enumerated.cartoons uses a module listed above it, which is the healthy direction.
excs.concurrency uses net.mindview.util, so a change to net.mindview.util can break excs.concurrency, while a change to excs.concurrency can't break net.mindview.util.
Position
Below the diagonal: excs.concurrency uses a module listed above it, which is the healthy direction.
CSharpGuide uses CSharpGuide.LanguageVersions._8._0, so a change to CSharpGuide.LanguageVersions._8._0 can break CSharpGuide, while a change to CSharpGuide can't break CSharpGuide.LanguageVersions._8._0.
Position
Below the diagonal: CSharpGuide uses a module listed above it, which is the healthy direction.
MarsonShine.Functional.Traversable uses MarsonShine.Functional, so a change to MarsonShine.Functional can break MarsonShine.Functional.Traversable, while a change to MarsonShine.Functional.Traversable can't break MarsonShine.Functional.
Position
Below the diagonal: MarsonShine.Functional.Traversable uses a module listed above it, which is the healthy direction.
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
A02:2025 — Security Misconfiguration
129
High / Critical
A05:2025 — Injection
39
High / Critical
A03:2025 — Software Supply Chain Failures
6
Medium
A01:2025 — Broken Access Control
2
Medium
Roadmap
First, enforce strict access controls by applying default-deny authorization to all endpoints and handlers. Second, establish a robust disaster recovery strategy by codifying backups and geo-recovery procedures in infrastructure as code, ensuring clear recovery time and point objectives. Third, align documentation with the actual codebase to eliminate discrepancies and ensure accuracy. Finally, integrate static application security testing into the continuous integration pipeline to prevent security regressions, and implement encryption for sensitive data at rest with proper key management.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 8 End-of-life runtime finding(s) in Platform End-of-Life — start with Chapter14_ConciseCode.csproj, Net6WebDemo.csproj, SyntaxWalker.csproj.
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Reconcile the README with reality: APUE/README.md documents the environment variable `PROT_EXEC`, but no code, script or configuration file names it; APUE/README.md documents the environment variable `PROT_NONE`, but no code, script or configuration file names it; APUE/README.md documents the environment variable `MAP_PRIVATE`, but no code, script or configuration file names it; APUE/README.md documents the environment variable `MAP_FIXED`, but no code, script or configuration file names it; APUE/README.md documents the environment variable `MAP_ANONYMOUS`, but no code, script or configuration file names it.
Add a SAST step to CI running 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 — so a security regression fails the build instead of landing.
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 — 79
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 — 850
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 — 272
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
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. 86 of 92 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 92 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, 1169 of 1201 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.
D4 Code Duplication — 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 376 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .c (8,016 lines, 25% of production source), .cpp (4,508 lines, 14% of production source), .cc (13 lines, 0% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
D8 Code Coverage — 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. Coverage NOT MEASURED: this repository's production source spans .cs, .c, .cc, .cpp, .go, .java, .py, .ts, and our analyzer cannot run the .c, .cc, .cpp, .go, .java, .py, .ts test suite(s) — so no coverage was collected for the repository as a whole. The .NET half may well have built and run; what is missing is a coverage figure that covers the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. In the meantime, produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference (.NET: C#, VB.NET and F# alike), lcov — `swift test --enable-code-coverage` or `xcodebuild -enableCodeCoverage YES` then `xcrun llvm-cov export -format=lcov` (Swift/Xcode), `cargo llvm-cov --lcov`, `go test -coverprofile`, `rebar3 do eunit --cover, cover` or covertool (Erlang/BEAM), `flutter test --coverage` or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov` (Dart/Flutter), `sbt clean coverage test coverageReport` via the sbt-scoverage plugin in `project/plugins.sbt` (Scala/sbt), jest/nyc, JaCoCo/Cobertura XML, coverage.py … most ecosystems' coverage tools can emit one) 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 and real coverage will be read. You can widen what we reach: optional: add a coverage collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and the real number is read on the next scan.
D10 Test Quality — 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 22 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 1 test source file(s) (.java) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
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. The NuGet registry this repository's packages resolve from could not be reached on this run, so no outdated, vulnerable or deprecated package could be read. The tool said: NU1301: Unable to load the service index for source https://dotnet.myget.org/F/roslyn/api/v3/index.json. [WHPerformanceDotNet/src/writehighperformancedotnetcode.sln] The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'." [WHPerformanceDotNet/src/writehighperfor…. This is OUR side and an ENVIRONMENT fault — the collector exists and ran — so the remedy is the scan's network path to dotnet.myget.org, and a re-run with it reachable measures this repository.
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 (5 contributor(s) across 1010 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 4 hold 2.8% 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 'WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzer.CodeFixes.csproj' with message: Error reading assets file: Error loading lock file 'WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFix….
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 159 deducted marker(s) and the 2.3/KLoC density on this row were taken over this repository's .NET projects ALONE: .c (8,016 lines, 25% of production source), .cpp (4,508 lines, 14% of production source), .cc (13 lines, 0% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
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 (29,951 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"]`.
D27 Navigability — 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D30 Dependency Vulnerabilities — 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. Dotnet.myget.org could not be reached (NU1301: Unable to load the service index for source https://dotnet.myget.org/F/roslyn/api/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.). 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
D32 Data Compliance (PII/GDPR) — 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. `CSharpGuide/LanguageVersions/14.0/Extensions.cs`, `CSharpGuide/LanguageVersions/14.0/Program.cs`, `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs`, `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs`, `CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs`, … (+8 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AXR1 Runtime accessibility — 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. Render strategy: boot via ToolchainServer (CSharpGuide/Net6WebDemo). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'Net6WebDemo.csproj'`: ; runtime evidence skipped (launch chosen because CSharpGuide/Net6WebDemo/Net6WebDemo.csproj is a Microsoft.NET.Sdk.Web project).
ED5 Idempotency — 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. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
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. 436 further occurrence(s) are not listed individually; the score already reflects all 476.
M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
M4 Documentation accuracy — 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. 91 further occurrence(s) are not listed individually; the score already reflects all 131.
P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
X18 Disposal-pattern correctness — 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. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
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. 69 further occurrence(s) are not listed individually; the score already reflects all 109.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.Test/SampleCodeAnalyzer.Test.csproj, docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzer.CodeFixes.csproj, docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.Package/SampleCodeAnalyzer.Package.csproj, docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.Test/SampleCodeAnalyzer.Test.csproj, docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.Vsix/SampleCodeAnalyzer.Vsix.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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, 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.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
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.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (6): D19, D20, D21, D24, D26, 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.
Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with prepare_docs._complete_nav (cyclomatic 19), Lexer.scan (cyclomatic 18). — 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 Cyclomatic Complexity from 9.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — 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.
Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with VectorOperator.Contains (cognitive 32), VectorOperator.Contains (cognitive 32), prepare_docs._complete_nav (cognitive 30). — 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 6 together lifts Cognitive Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — 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 Classes10.0 / 10Exemplary✓ 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.
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.
376 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 6 of the 382 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. Measured on part of this repository only: .c, .cpp, .cc (39% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
+ 63 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 27 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with REDACTED (5), Success.cs (2), EnumToGenerator.cs (2). — One of this dimension's main actionable groups (27 warning-level).
Resolve the 25 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with REDACTED (9), PatnerMatching.cs (3), REDACTED. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 24 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with REDACTED (4), SpanAndMemoryAccess.cs (3), REDACTED (2). — One of this dimension's main actionable groups (24 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — 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.9 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
Off the main sequence: SampleCodeAnalyzer (WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer) · ×2WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzer.csproj:1
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling — start with SampleCodeAnalyzer.csproj (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — 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.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 5 mechanizable ADR(s) are enforced: 5 by analyzers, 0 by tests. Cycles found: 0.
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
22 test methods: 22 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 Quality7.3 / 10Adequategated by 2 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, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 22 tests. Measured on the C# suite only — at least 1 test source file(s) (.java) went unread, so its test quality is unmeasured and is not in these counts.
No assertions (empty test): TestMethod1 · ×2ConcurrencyInCSharpCookbook/06UnitTest/UnitTest1.cs:8
Test project verifies nothing: 06UnitTestConcurrencyInCSharpCookbook/06UnitTest/UnitTest1.cs:8
What to do
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with UnitTest1.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
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 349 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 45 direct `PackageReference`(s), and 205 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.
159 deducted debt markers + unmeasured dead symbols across 29951 LoC in the .NET projects (2.3/KLoC) → score 5.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .c, .cpp, .cc (39% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 44 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Found.cs (8), REDACTED (4), FileReadingPooledValueTaskSource.cs (4). — One of this dimension's main actionable groups (44 issue-level).
Resolve the 2 DiscardedPureResult finding(s) in Explicit Debt — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with AsyncDataBind.cs (2). — One of this dimension's main actionable groups (2 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — 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 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.
This is a comprehensive documentation set: the README files (including the root repository README) are all present and describe their respective directories, with no missing overview or installation; architecture/design markdown files are also fully covered; XML-doc coverage for C# topics is low (<2%), but the visible content is clear and complete. The quality is high. The repository is well documented: the READMEs of each directory (e.g. CleanCode/, DDIA/, FunctionalCSharp/) document what that directory contains and give an overview; architecture/design docs are present (496 markdown files); XML-doc coverage for C# types is low (<2%), but no single file's absence is flagged as a defect. The content is high quality, well-organized, and complete within its scope. The documentation is strong for its niche audience: a cohesive set of READMEs and architecture/design markdown files covering the PostgresSQL page-pruning/HOT-update internals, SystemPerformance-Enterprise-Cloud USE-performance analysis with 5 Why, microbenchmarks, and statistics (average values, standard deviation, percentiles), TCP/IP protocol reference glossary, and an SMP/NUMA optimization guide. The XML-doc coverage is thin (<2% for most namespaces) but the visible content is clear and complete within its scope.
Resolve the 6 Documentation finding(s) in Documentation Quality — start with README.md (6). — One of this dimension's main actionable groups (6 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR QualityCritical◐ Sampled · advisory
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
Evaluated 5 ADR(s) individually; mean quality 1.5/10 (frequently incomplete). 5 flagged with a specific gap.
Title '0001' contains only random junk and no meaningful context or decisionWHPerformanceDotNet/src/TPLDataflow/0001.txt
The body is a repeated, garbled string containing only adajdal/...djasdfposdfjkosijufsdijfnkljnckljxhcnqiwurq[werioeritrewtuphvxkjnvxm,npejup] fragments with no context/problem and no explicit decisionWHPerformanceDotNet/src/TPLDataflow/0001_1.txt
Title '0002' contains no meaningful content and is a noise filler. Context/problem, explicit decision, consequences/trade-offs, and clarity are all absent.WHPerformanceDotNet/src/TPLDataflow/0002.txt
Title '0003' contains only random junk and no meaningful context or decisionWHPerformanceDotNet/src/TPLDataflow/0003.txt
Title '0004' contains only random junk and no meaningful content (decision and context are both absent), plus the body is a repeated jumbled string with no real decisionWHPerformanceDotNet/src/TPLDataflow/0004.txt
What to do
Resolve the 1 Title '0001' contains only random junk and no meaningful context or… finding(s) in ADR Quality — start with 0001.txt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 The body is a repeated, garbled string containing only… finding(s) in ADR Quality — start with 0001_1.txt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Title '0002' contains no meaningful content and is a noise filler.… finding(s) in ADR Quality — start with 0002.txt. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d20_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.
4 naming inconsistencies across 200 sampled symbols.
Inconsistent spelling of 'Memory' across the codebase. Some symbols use 'Momery' (e.g., MomeryAllocation), while others use 'PerFormance' or 'Performances' (capitalization inconsistency) or 'Performance' (standard spelling). Specifically, 'Momery' appears to be a typo for 'Memory', and 'PerFormance' mixes casing styles.
Inconsistent spelling of 'Partner'. The namespace and type name use 'Patner' (missing 'r'), which is likely a typo for 'Partner'.
Inconsistent spelling of 'Prompt'. The parameter 'promt' is missing the second 'p', while 'Messages' is spelled correctly. While 'promt' is a parameter, it suggests a broader typo issue in the codebase's vocabulary.
Typo in type name 'CirCle' (capital C in the middle).
What to do
Resolve the 1 Inconsistent spelling of 'Memory' across the codebase. Some symbols use… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Inconsistent spelling of 'Partner'. The namespace and type name use… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Inconsistent spelling of 'Prompt'. The parameter 'promt' is missing the… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: Whether 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).
39 finding(s): 0 critical, 19 high, 20 medium, 0 low. 5 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 22 file(s) — `APUE/src/3-11/demo1.c`, `REDACTED` (line 124), `CPPPrimer/src/13-operator-override/strVec.h` (line 25), `CPPPrimer/src/16-generic-template/strVec.h` (line 27), `CSAPP/cpps/csapp/05opcode/optvec.c` (line 58, line 70, line 86, …), … (+17 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 3 of those file(s) — `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs`, `CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs`, `CSharpGuide/performance/strings/Strings.cs` — 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 7 of those file(s) — `CSharpGuide/LanguageVersions/14.0/Extensions.cs`, `CSharpGuide/simd-vector-demo/VectorOperator.cs`, `Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 2/Extensions.cs`, `Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/Extensions.cs`, `Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 6/Combinations.cs`, … (+2 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.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. nuget was not scanned (nuget: dotnet.myget.org could not be reached (NU1301: Unable to load the service index for source https://dotnet.myget.org/F/roslyn/api/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.)), so this is not the whole dependency surface and the result is reported at reduced confidence.
REDACTED
What to do
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 101 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (27), REDACTED (25), REDACTED (23). — One of this dimension's main actionable groups (101 warning-level).
Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 24 Low IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (6), REDACTED (6). — One of this dimension's main actionable groups (24 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ 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, 0 high, 2 medium, 0 low. semgrep could not parse 13 file(s) — `CSharpGuide/LanguageVersions/14.0/Extensions.cs`, `CSharpGuide/LanguageVersions/14.0/Program.cs`, `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs`, `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs`, `CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs`, … (+8 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 warning-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.
5 of 67 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is DesignPattern/DesignPatternCore/Program.cs. Counted over 67 of the 427 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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
0/5 workload(s) run every container under a seccomp profile; 0/5 declare an AppArmor/SELinux profile.
No seccomp profile · ×5REDACTED:2
What to do
Resolve the 5 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
8 end-of-life runtime(s) and 0 end-of-life framework(s), read from 155 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 8 End-of-life runtime finding(s) in Platform End-of-Life — start with Chapter14_ConciseCode.csproj, Net6WebDemo.csproj, SyntaxWalker.csproj. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 10 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
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.
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.
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 · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
`MapGet("/weatherforecast")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×4) — CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:23, CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:23, docs/CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:23, …
`MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×4) — CSharpGuide/performance/strings/Program.cs:14, CSharpGuide/performance/strings/Program.cs:14, docs/CSharpGuide/performance/strings/Program.cs:14, …
What to do
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Do you agree with this assessment?
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
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. (×20) — CSharpGuide/LanguageVersions/7.0/IValueMark.cs:17, CSharpGuide/LanguageVersions/7.0/IValueMark.cs:19, CSharpGuide/LanguageVersions/8.0/Introducer.cs:66, …
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.
`Show` is a shipped member whose body only throws — and it is REACHED: AsyncInCSharp/TAPs/Program.cs:18 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — AsyncInCSharp/TAPs/PermissionDialog.cs:8
`Do` is a shipped member whose body only throws — and it is REACHED: CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:48 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:34
`LoadConfigurationData` is a shipped member whose body only throws — and it is REACHED: CSharpGuide/net8-guide/Performances/FrozenTypes.cs:15 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — CSharpGuide/net8-guide/Performances/FrozenTypes.cs:16
`Show` is a shipped member whose body only throws — and it is REACHED: docs/AsyncInCSharp/TAPs/Program.cs:18 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — docs/AsyncInCSharp/TAPs/PermissionDialog.cs:8
`Do` is a shipped member whose body only throws — and it is REACHED: docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:48 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:34
`LoadConfigurationData` is a shipped member whose body only throws — and it is REACHED: docs/CSharpGuide/net8-guide/Performances/FrozenTypes.cs:15 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — docs/CSharpGuide/net8-guide/Performances/FrozenTypes.cs:16
`SomeMethod` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — CSharpGuide/LanguageVersions/4.0/Example.cs:39, docs/CSharpGuide/LanguageVersions/4.0/Example.cs:39
`Length` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — CSharpGuide/LanguageVersions/7.0/IValueMark.cs:19, docs/CSharpGuide/LanguageVersions/7.0/IValueMark.cs:19
`GetResultsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — CSharpGuide/LanguageVersions/8.0/Introducer.cs:66, docs/CSharpGuide/LanguageVersions/8.0/Introducer.cs:66
`DoStuff` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:40, docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:40
`DisposeAndClear` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:71, docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:71
`DisposeAndClear_DisallowNull` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:75, docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:75
`MyAssert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:133, docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:133
`Main` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×4) — CSharpGuide/Net6WebDemo/Program.cs:7, WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:11, docs/CSharpGuide/Net6WebDemo/Program.cs:7, …
`OnVisitSyntaxNode` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:96, docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:96
`SupportedDiagnostics` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:21, docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:21
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×9) — AsyncInCSharp/AsyncAwaitable/ExampleAwaitable.cs:30, REDACTED:33, REDACTED:16, …
`SyncThrowException` has an empty body — confirm it's an intentional no-op and not an unfinished method. — AsyncInCSharp/ExceptionInAsync/Program.cs:10
`EmptyAsync` has an empty body — confirm it's an intentional no-op and not an unfinished method. — AsyncInCSharp/PerFormanceComparison/AsyncAndSyncComparison.cs:23
`Empty` has an empty body — confirm it's an intentional no-op and not an unfinished method. — AsyncInCSharp/PerFormanceComparison/AsyncAndSyncComparison.cs:27
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.
The root README is 118 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 136 of 148 project(s) that lack one — worth up to 1.8 pts.
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/148 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.
APUE/README.md documents the environment variable `PROT_EXEC`, but no code, script or configuration file names it. 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. — APUE/README.md:857
APUE/README.md documents the environment variable `PROT_NONE`, but no code, script or configuration file names it. 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. — APUE/README.md:858
APUE/README.md documents the environment variable `MAP_PRIVATE`, but no code, script or configuration file names it. 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. — APUE/README.md:862
APUE/README.md documents the environment variable `MAP_FIXED`, but no code, script or configuration file names it. 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. — APUE/README.md:863
APUE/README.md documents the environment variable `MAP_ANONYMOUS`, but no code, script or configuration file names it. 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. — APUE/README.md:864
APUE/README.md documents the environment variable `PIPE_BUF`, but no code, script or configuration file names it. 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. — APUE/README.md:965
APUE/README.md documents the environment variable `PTHREAD_PROCESS_SHARED`, but no code, script or configuration file names it. 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. — APUE/README.md:1096
APUE/README.md documents the environment variable `SO_REUSEADDR`, but no code, script or configuration file names it. 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. — APUE/README.md:1295
APUE/README.md documents the environment variable `SO_KEEPALIVE`, but no code, script or configuration file names it. 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. — APUE/README.md:1296
APUE/README.md documents the environment variable `SO_SNDBUF`, but no code, script or configuration file names it. 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. — APUE/README.md:1297
APUE/README.md documents the environment variable `SO_RCVBUF`, but no code, script or configuration file names it. 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. — APUE/README.md:1297
APUE/README.md documents the environment variable `TCP_NODELAY`, but no code, script or configuration file names it. 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. — APUE/README.md:1298
CurrentProgramming-for-Scalable-WebArchitectures/README.md links to `scalability`, but `CurrentProgramming-for-Scalable-WebArchitectures/scalability` does not exist. 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. — CurrentProgramming-for-Scalable-WebArchitectures/README.md:7
Postgresql-In-Internal/README.MD documents the environment variable `PD_PAGE_FULL`, but no code, script or configuration file names it. 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. — Postgresql-In-Internal/README.MD:11
Postgresql-In-Internal/README.MD links to `github.com/reorg/pg_repack`, but `Postgresql-In-Internal/github.com/reorg/pg_repack` does not exist. 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. — Postgresql-In-Internal/README.MD:173
TheArtOfUnixProgramming/README.md links to `[Books/CSAPP/docs/cache-in-deep.md`, but `TheArtOfUnixProgramming/[Books/CSAPP/docs/cache-in-deep.md` does not exist. 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. — TheArtOfUnixProgramming/README.md:40
docs/index.md links to `AsyncInCSharp/docs/`, but `docs/AsyncInCSharp/docs` does not exist. 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. — docs/index.md:4
docs/index.md links to `CleanArchitecture/`, but `docs/CleanArchitecture` does not exist. 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. — docs/index.md:5
docs/index.md links to `CleanCode/`, but `docs/CleanCode` does not exist. 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. — docs/index.md:6
docs/index.md links to `WHPerformanceDotNet/`, but `docs/WHPerformanceDotNet` does not exist. 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. — docs/index.md:7
docs/index.md links to `ConcurrencyInCSharpCookbook/03ParallerBasic/`, but `docs/ConcurrencyInCSharpCookbook/03ParallerBasic` does not exist. 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. — docs/index.md:8
docs/index.md links to `CSharpGuide/docs/`, but `docs/CSharpGuide/docs` does not exist. 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. — docs/index.md:9
docs/index.md links to `CSAPP/`, but `docs/CSAPP` does not exist. 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. — docs/index.md:10
docs/index.md links to `CSharpInDepth/`, but `docs/CSharpInDepth` does not exist. 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. — docs/index.md:11
docs/index.md links to `DesignPattern/DesignPatternCore/`, but `docs/DesignPattern/DesignPatternCore` does not exist. 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. — docs/index.md:12
docs/index.md links to `EffectiveJava/`, but `docs/EffectiveJava` does not exist. 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. — docs/index.md:13
docs/index.md links to `linux/doc/`, but `docs/linux/doc` does not exist. 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. — docs/index.md:14
docs/index.md links to `TCPIP/`, but `docs/TCPIP` does not exist. 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. — docs/index.md:15
docs/index.md links to `ThinkingInJava/docs/`, but `docs/ThinkingInJava/docs` does not exist. 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. — docs/index.md:16
docs/index.md links to `ts/`, but `docs/ts` does not exist. 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. — docs/index.md:17
docs/index.md links to `DDIA/`, but `docs/DDIA` does not exist. 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. — docs/index.md:18
docs/index.md links to `GarbageCollection/`, but `docs/GarbageCollection` does not exist. 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. — docs/index.md:19
docs/index.md links to `blogs/`, but `docs/blogs` does not exist. 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. — docs/index.md:20
CSAPP/docs/linker.md names `.rel.plt`, but no file or folder `.rel.plt` 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. — CSAPP/docs/linker.md:126
CSAPP/docs/memory-hierarchy.md links to `./asserts/flexible-logical-to-physical`, but `CSAPP/docs/asserts/flexible-logical-to-physical` does not exist. 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. — CSAPP/docs/memory-hierarchy.md:171
CSharpGuide/docs/vectorization-guidelines.md documents the environment variable `MEM_NOACCESS`, but no code, script or configuration file names it. 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. — CSharpGuide/docs/vectorization-guidelines.md:405
CSharpGuide/net11-runtime-async/README.md names `async/await`, but no file or folder `async/await` 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. — CSharpGuide/net11-runtime-async/README.md:3
CSharpGuide/net11-runtime-async/README.md names .NET 11, but the projects target .NET 2, 3, 5, 6, 7, 8, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CSharpGuide/net11-runtime-async/README.md:3
RxNet/docs/operation-filtering.md links to `First/Last/Single[OrDefault]的阻塞版本`, but `RxNet/docs/First/Last/Single[OrDefault]的阻塞版本` does not exist. 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. — RxNet/docs/operation-filtering.md:139
RxNet/docs/operation-filtering.md names `async/await`, but no file or folder `async/await` 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. — RxNet/docs/operation-filtering.md:250
What to do
Reconcile the README with reality: APUE/README.md documents the environment variable `PROT_EXEC`, but no code, script or configuration file names it; APUE/README.md documents the environment variable `PROT_NONE`, but no code, script or configuration file names it; APUE/README.md documents the environment variable `MAP_PRIVATE`, but no code, script or configuration file names it; APUE/README.md documents the environment variable `MAP_FIXED`, but no code, script or configuration file names it; APUE/README.md documents the environment variable `MAP_ANONYMOUS`, but no code, script or configuration file names it.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ 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.
What to do
Run the test suite in CI via an explicit runner step (`pytest` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
P2 · Observability7.6 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 1078 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
Add a SAST step to CI running 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 — 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 automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×16) — CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22, REDACTED:11, REDACTED:12, …
What to do
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
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 117 use(s) across 33,571 production line(s) (~3.5/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.
12 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).
`.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×6) — ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:66, ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:79, ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:88, …
`parent.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:73, docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:73
`Completion.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:34, docs/ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:34
`_initialized.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs:21, docs/ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs:21
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Do you agree with this assessment?
R1 · Type Safety5.7 / 10Adequate✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
16 typed · 12 plain JS — the untyped files are ts/lib/TypeAssertion.js, ts/lib/anyType.js, ts/lib/declarefile.js, ts/lib/declaresynax.js, ts/lib/extensionGlobalVarious.js, ts/lib/fiveType.js (+6 more).
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
ts/lib/declarefile.js:6 · ts/src/declarefile.ts:7 — the two spans are one implementation copied and then locally edited — 94 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ts/lib/declarefile.js:6
ts/lib/function.js:13 · ts/lib/function.js:23 — 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. — ts/lib/function.js:13
ts/lib/function.js:31 · ts/src/function.ts:40 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — ts/lib/function.js:31
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R7 · Dead Code9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
46 file(s) (~735 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×4) — ts/lib/index.js:8, ts/lib/index.js:9, ts/src/index.ts:8, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×6) — CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:2, CSharpGuide/diagnostics/DistributedTraceWebDemo/Program.cs:3, CSharpGuide/performance/strings/Program.cs:11, …
What to do
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Do you agree with this assessment?
X1 · Async correctness4.8 / 10Weak✓ Tool-verified
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. (×10) — CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:115, docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:115, WHPerformanceDotNet/src/AsyncProgram/Program.cs:58, …
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×10) — CSharpGuide/threads/ThreadChannelDemo.cs:11, docs/CSharpGuide/threads/ThreadChannelDemo.cs:11, ConcurrencyInCSharpCookbook/ThreadBasic/MyAsyncCommand.cs:9, …
`Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead. (×6) — WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:64, WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:84, docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:64, …
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) — ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:66, ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:73, ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:79, …
`Task.WaitAny` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAny(…)` instead. (×2) — ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:35, docs/ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:35
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.
`workingSetCounter` is a `PollingCounter`, which implements `IDisposable`, and it is created here (line 19). Every use of it in `MinimalEventCounterSource` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var workingSetCounter = …;`), which releases it at the end of the scope on every path including a throw. (×2) — CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:19, docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:19
`monitorContentCounter` is a `IncrementingPollingCounter`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `MinimalEventCounterSource` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var monitorContentCounter = …;`), which releases it at the end of the scope on every path including a throw. (×2) — CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:26, docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:26
`client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `MakeRequest` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22, docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22
`tokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tokenSource = …;`), which releases it at the end of the scope on every path including a throw. (×2) — WHPerformanceDotNet/src/AsyncProgram/Program.cs:38, docs/WHPerformanceDotNet/src/AsyncProgram/Program.cs:38
`client` is a `WebClient`, which implements `IDisposable`, and it is created here (line 23). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — REDACTED:23, docs/REDACTED:23
`watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 34). Every use of it in `FileSystemWatcher` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw. (×2) — ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:34, docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:34
`timer` is a `Timer`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `EncapsulateFromNotStandardEventHandler` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var timer = …;`), which releases it at the end of the scope on every path including a throw. (×2) — REDACTED:57, docs/REDACTED:57
`watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `ObserveOn` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw. (×2) — ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:21, docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:21
`watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `UseThrottle` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw. (×2) — ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:13, docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:13
`watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `UseSample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw. (×2) — ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:26, docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:26
`client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 11). Every use of it in `UseTimeout` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — REDACTED:11, docs/REDACTED:11
`client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `UseToObservable` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — REDACTED:12, docs/REDACTED:12
`client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 18). Every use of it in `UseStartAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — REDACTED:18, docs/REDACTED:18
`client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `UseFromAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — REDACTED:26, docs/REDACTED:26
`client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 37). Every use of it in `UseSelectMany` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — REDACTED:37, docs/REDACTED:37
`client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `GetWithTimeoutAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs:42, docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs:42
`httpClient` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `DownloadUrlsAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var httpClient = …;`), which releases it at the end of the scope on every path including a throw. (×2) — ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:36, docs/ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:36
`semaphore` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 37). Every use of it in `DownloadUrlsAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var semaphore = …;`), which releases it at the end of the scope on every path including a throw. (×2) — ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:37, docs/ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:37
`webClient` is a `WebClient`, which implements `IDisposable`, and it is created here (line 10). Every use of it in `GetPageSizeAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var webClient = …;`), which releases it at the end of the scope on every path including a throw. — AsyncInCSharp/AsyncPatternInNet/AsyncMethodContagious.cs:10
`webClient` is a `WebClient`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `DumpWebPage` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var webClient = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:12
`webclient` is a `WebClient`, which implements `IDisposable`, and it is created here (line 63). Every use of it in `AddFavicon` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var webclient = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:63
`client` is a `WebClient`, which implements `IDisposable`, and it is created here (line 9). Every use of it in `DumpWebPageAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:9
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 13/121 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. (×33) — CSharpGuide/async/AsyncLocalViaThreadLocal.cs:14, CSharpGuide/async/AsyncLocalViaThreadLocal.cs:28, CSharpGuide/async/StockPrices.cs:17, …
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. (×4) — CSharpGuide/diagnostics/EventSourceDemo/Program.cs:14, CSharpGuide/diagnostics/EventSourceDemo/Program.cs:23, docs/CSharpGuide/diagnostics/EventSourceDemo/Program.cs:14, …
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. (×2) — CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs:16, docs/CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs:16
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. (×2) — ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:22, docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:22
`catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:31, docs/AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:31
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — AsyncInCSharp/ExceptionInAsync/MultipleException.cs:11, docs/AsyncInCSharp/ExceptionInAsync/MultipleException.cs:11
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.
This method contradicts itself about `myclass`: line 50 assigns it with `as MyClass`, which hands back null rather than throwing when the value is not a `MyClass`, but line 51 then dereferences it directly as `myclass.Initialization` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `myclass` once before the first use and handle the null case, or cast with `(MyClass)` so the failure is reported where it happens — rather than leaving the two readings side by side. — ConcurrencyInCSharpCookbook/10OOP/AsyncInitializeClassPattern.cs:51
48/85 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~1.6 `!` suppressions per 1k syntax nodes — 119 suppression(s) across the 75489 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
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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 — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
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.
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.
Not included — 35 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 image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'Net6WebDemo.csproj'`: ; runtime evidence skipped (launch chosen because CSharpGuide/Net6WebDemo/Net6WebDemo.csproj is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D12 Dependency Hygiene — Dependency hygiene not measured — dotnet.myget.org could not be reached
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .c, .cc, .cpp, .go, .java, .py, .ts, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
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 — none of 5 ADRs are conformance-checkable — unverifiable.
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .c, .cc, .cpp, .go, .java, .py, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 16 value object(s)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 CQRS handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — the JS/TS workspace (27 production file(s)) has no JavaScript/TypeScript test, but it is 4.92% of this repository's production source and the other 95.08% carries 2,287 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
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.
WriteOnlyPrivateField CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/CocurrentRequestEventCounterSource.cs:10— private IncrementingPollingCounter _requestRateCounter — 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 docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/CocurrentRequestEventCounterSource.cs:10— private IncrementingPollingCounter _requestRateCounter — 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 CSharpGuide/diagnostics/CollectionMetricDemo/Program.cs:12— private Counter<int> s_hatsSold — 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 CSharpGuide/diagnostics/MetricDemo/Program.cs:9— private Counter<int> s_hatsSold — 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 docs/CSharpGuide/diagnostics/CollectionMetricDemo/Program.cs:12— private Counter<int> s_hatsSold — 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 docs/CSharpGuide/diagnostics/MetricDemo/Program.cs:9— private Counter<int> s_hatsSold — 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 REDACTED:15— private ILogger<ErrorModel> _logger — 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 docs/REDACTED:15— private ILogger<ErrorModel> _logger — 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 CSharpGuide/diagnostics/DistributedTraceWebDemo/Pages/Index.cshtml.cs:8— private ILogger<IndexModel> _logger — 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 docs/CSharpGuide/diagnostics/DistributedTraceWebDemo/Pages/Index.cshtml.cs:8— private ILogger<IndexModel> _logger — 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 CSharpGuide/diagnostics/DistributedTraceWebDemo/Pages/Privacy.cshtml.cs:8— private ILogger<PrivacyModel> _logger — 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 docs/CSharpGuide/diagnostics/DistributedTraceWebDemo/Pages/Privacy.cshtml.cs:8— private ILogger<PrivacyModel> _logger — 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 CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:45— private IDisposable listenerSubscribtion — 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 docs/CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:45— private IDisposable listenerSubscribtion — 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 CSharpGuide/net8-guide/Performances/FrozenTypes.cs:15— private FrozenDictionary<string, bool> s_configurationData — 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 docs/CSharpGuide/net8-guide/Performances/FrozenTypes.cs:15— private FrozenDictionary<string, bool> s_configurationData — 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 CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:40— private object? state — assigned 3 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 docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:40— private object? state — assigned 3 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 CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:41— private ExecutionContext? executionContext — assigned 2 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 docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:41— private ExecutionContext? executionContext — assigned 2 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 ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:16— private BlockingCollection<int> m_blockingStack — 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 docs/ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:16— private BlockingCollection<int> m_blockingStack — 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 ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:17— private BlockingCollection<int> m_blockingBag — 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 docs/ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:17— private BlockingCollection<int> m_blockingBag — 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 ConcurrencyInCSharpCookbook/11Sync/AsyncSemaphore.cs:8— private AsyncManualResetEvent _asyncManualResetEvent — 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.
Unfinished stub — throws NotImplementedException AsyncInCSharp/TAPs/PermissionDialog.cs:8— `Show` is a shipped member whose body only throws — and it is REACHED: AsyncInCSharp/TAPs/Program.cs:18 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:34— `Do` is a shipped member whose body only throws — and it is REACHED: CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:48 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException CSharpGuide/net8-guide/Performances/FrozenTypes.cs:16— `LoadConfigurationData` is a shipped member whose body only throws — and it is REACHED: CSharpGuide/net8-guide/Performances/FrozenTypes.cs:15 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException docs/AsyncInCSharp/TAPs/PermissionDialog.cs:8— `Show` is a shipped member whose body only throws — and it is REACHED: docs/AsyncInCSharp/TAPs/Program.cs:18 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:34— `Do` is a shipped member whose body only throws — and it is REACHED: docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:48 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/net8-guide/Performances/FrozenTypes.cs:16— `LoadConfigurationData` is a shipped member whose body only throws — and it is REACHED: docs/CSharpGuide/net8-guide/Performances/FrozenTypes.cs:15 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
D10 · Test Quality· No assertions (empty test) · ×2
No assertions (empty test): TestMethod1 ConcurrencyInCSharpCookbook/06UnitTest/UnitTest1.cs:8— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): TestMethod1 docs/ConcurrencyInCSharpCookbook/06UnitTest/UnitTest1.cs:8— Test method has an empty body — it asserts nothing and exercises no code.
DiscardedPureResult CSharpGuide/Program.cs:176— s.ToString(); — strings are immutable, so this call cannot change the text it was called on: it computes a new string and the statement throws it away, leaving the original exactly as it was. The line reads as the transformation it names, and the value that comes out of this method later is the untransformed one. Assign the result — to the same variable, or to the field or property the transformed text was meant to reach — or, if the call really was pointless, delete the line rather than leaving something that looks like it works.
DiscardedPureResult docs/CSharpGuide/Program.cs:176— s.ToString(); — strings are immutable, so this call cannot change the text it was called on: it computes a new string and the statement throws it away, leaving the original exactly as it was. The line reads as the transformation it names, and the value that comes out of this method later is the untransformed one. Assign the result — to the same variable, or to the field or property the transformed text was meant to reach — or, if the call really was pointless, delete the line rather than leaving something that looks like it works.
EmptyCatchBlock ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:22— 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 docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:22— 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.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×40
Disposable created and abandoned in the method that made it CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:19— `workingSetCounter` is a `PollingCounter`, which implements `IDisposable`, and it is created here (line 19). Every use of it in `MinimalEventCounterSource` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var workingSetCounter = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:26— `monitorContentCounter` is a `IncrementingPollingCounter`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `MinimalEventCounterSource` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var monitorContentCounter = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `MakeRequest` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:19— `workingSetCounter` is a `PollingCounter`, which implements `IDisposable`, and it is created here (line 19). Every use of it in `MinimalEventCounterSource` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var workingSetCounter = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:26— `monitorContentCounter` is a `IncrementingPollingCounter`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `MinimalEventCounterSource` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var monitorContentCounter = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `MakeRequest` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it WHPerformanceDotNet/src/AsyncProgram/Program.cs:38— `tokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tokenSource = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:23— `client` is a `WebClient`, which implements `IDisposable`, and it is created here (line 23). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it docs/WHPerformanceDotNet/src/AsyncProgram/Program.cs:38— `tokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tokenSource = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it docs/REDACTED:23— `client` is a `WebClient`, which implements `IDisposable`, and it is created here (line 23). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:34— `watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 34). Every use of it in `FileSystemWatcher` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:57— `timer` is a `Timer`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `EncapsulateFromNotStandardEventHandler` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var timer = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:21— `watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `ObserveOn` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:13— `watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `UseThrottle` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:26— `watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `UseSample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:11— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 11). Every use of it in `UseTimeout` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:12— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `UseToObservable` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:18— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 18). Every use of it in `UseStartAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:26— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `UseFromAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:37— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 37). Every use of it in `UseSelectMany` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs:42— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `GetWithTimeoutAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:36— `httpClient` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `DownloadUrlsAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var httpClient = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:37— `semaphore` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 37). Every use of it in `DownloadUrlsAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var semaphore = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:34— `watcher` is a `FileSystemWatcher`, which implements `IDisposable`, and it is created here (line 34). Every use of it in `FileSystemWatcher` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var watcher = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it docs/REDACTED:57— `timer` is a `Timer`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `EncapsulateFromNotStandardEventHandler` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var timer = …;`), which releases it at the end of the scope on every path including a throw.
+ 15 more in this group — see findings.md.
X2 · Cancellation propagation· Async method without CancellationToken · ×33
Async method without CancellationToken: AsyncMethodA CSharpGuide/async/AsyncLocalViaThreadLocal.cs:14— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AsyncMethodB CSharpGuide/async/AsyncLocalViaThreadLocal.cs:28— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetStockPriceForAsync CSharpGuide/async/StockPrices.cs:17— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeMapIfNeededAsync CSharpGuide/async/StockPrices.cs:24— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DoSomeWork CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs:23— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StepTwo CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs:42— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StepOne CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs:49— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: MakeRequest CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:20— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Starup CSharpGuide/LanguageVersions/7.0/ValueTasks.cs:10— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GenerateSequence CSharpGuide/LanguageVersions/8.0/AsyncStream.cs:11— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConsumeStream CSharpGuide/LanguageVersions/8.0/DecompilerAsyncStream.cs:10— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GenerateSequence CSharpGuide/LanguageVersions/8.0/DecompilerAsyncStream.cs:29— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetBigResultAsync CSharpGuide/LanguageVersions/8.0/Introducer.cs:45— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetResultAsync CSharpGuide/LanguageVersions/8.0/Introducer.cs:52— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Start CSharpGuide/threads/ThreadChannelDemo.cs:11— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReadAsync CSharpGuide/threads/ThreadChannelDemo.cs:21— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SingleProducerSingleConsumer CSharpGuide/threads/ThreadChannelDemo.cs:32— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: MultipleProducerSingleConsumer CSharpGuide/threads/ThreadChannelDemo.cs:46— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConsumeData CSharpGuide/threads/ThreadChannelDemo.cs:78— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: BeginProducing CSharpGuide/threads/ThreadChannelDemo.cs:108— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AsyncMethodA docs/CSharpGuide/async/AsyncLocalViaThreadLocal.cs:14— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AsyncMethodB docs/CSharpGuide/async/AsyncLocalViaThreadLocal.cs:28— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetStockPriceForAsync docs/CSharpGuide/async/StockPrices.cs:17— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeMapIfNeededAsync docs/CSharpGuide/async/StockPrices.cs:24— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DoSomeWork docs/CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs:23— No CancellationToken parameter — this work can't be stopped early once started.
Duplicated block (8 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:26— WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:26-33 | docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:26-33 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/IDeque.cs:3— Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/IDeque.cs:3-10 | Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 6/Deque.cs:9-16 — 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 `Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/IDeque.cs:3` 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) CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:46— CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:46-53 | docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:46-53 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs` and `docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) REDACTED:47— REDACTED:47-54 | docs/REDACTED:47-54 — before extracting anything, compare `REDACTED` and `docs/REDACTED` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) ConcurrencyInCSharpCookbook/09Cancellation/TimeoutAndCancellation.cs:36— ConcurrencyInCSharpCookbook/09Cancellation/TimeoutAndCancellation.cs:36-43 | docs/ConcurrencyInCSharpCookbook/09Cancellation/TimeoutAndCancellation.cs:36-43 — before extracting anything, compare `ConcurrencyInCSharpCookbook/09Cancellation/TimeoutAndCancellation.cs` and `docs/ConcurrencyInCSharpCookbook/09Cancellation/TimeoutAndCancellation.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) ConcurrencyInCSharpCookbook/11Sync/Program.cs:48— ConcurrencyInCSharpCookbook/11Sync/Program.cs:48-55 | docs/ConcurrencyInCSharpCookbook/11Sync/Program.cs:48-55 — before extracting anything, compare `ConcurrencyInCSharpCookbook/11Sync/Program.cs` and `docs/ConcurrencyInCSharpCookbook/11Sync/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) AsyncInCSharp/ParallelSlimInAsync/RndGenerator.cs:8— AsyncInCSharp/ParallelSlimInAsync/RndGenerator.cs:8-15 | docs/AsyncInCSharp/ParallelSlimInAsync/RndGenerator.cs:8-15 — before extracting anything, compare `AsyncInCSharp/ParallelSlimInAsync/RndGenerator.cs` and `docs/AsyncInCSharp/ParallelSlimInAsync/RndGenerator.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) CSharpGuide/LanguageVersions/7.0/ValueTuples.cs:15— CSharpGuide/LanguageVersions/7.0/ValueTuples.cs:15-22 | docs/CSharpGuide/LanguageVersions/7.0/ValueTuples.cs:15-22 — before extracting anything, compare `CSharpGuide/LanguageVersions/7.0/ValueTuples.cs` and `docs/CSharpGuide/LanguageVersions/7.0/ValueTuples.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) CSharpGuide/LanguageVersions/8.0/AsyncStream.cs:22— CSharpGuide/LanguageVersions/8.0/AsyncStream.cs:22-29 | docs/CSharpGuide/LanguageVersions/8.0/AsyncStream.cs:22-29 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/AsyncStream.cs` and `docs/CSharpGuide/LanguageVersions/8.0/AsyncStream.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/Program.cs:23— CSharpGuide/diagnostics/EventSourceDemo/Program.cs:23-30 | docs/CSharpGuide/diagnostics/EventSourceDemo/Program.cs:23-30 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/Program.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) DesignPattern/DesignPattern/Visitor/Success.cs:12— DesignPattern/DesignPattern/Visitor/Success.cs:12-19 | docs/DesignPattern/DesignPattern/Visitor/Success.cs:12-19 — before extracting anything, compare `DesignPattern/DesignPattern/Visitor/Success.cs` and `docs/DesignPattern/DesignPattern/Visitor/Success.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) DesignPattern/DesignPatternCore/Factory/WpsToPdfConvertor.cs:5— DesignPattern/DesignPatternCore/Factory/WpsToPdfConvertor.cs:5-12 | docs/DesignPattern/DesignPatternCore/Factory/WpsToPdfConvertor.cs:5-12 — before extracting anything, compare `DesignPattern/DesignPatternCore/Factory/WpsToPdfConvertor.cs` and `docs/DesignPattern/DesignPatternCore/Factory/WpsToPdfConvertor.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) DesignPattern/DesignPatternCore/Visitor/Success.cs:12— DesignPattern/DesignPatternCore/Visitor/Success.cs:12-19 | docs/DesignPattern/DesignPatternCore/Visitor/Success.cs:12-19 — before extracting anything, compare `DesignPattern/DesignPatternCore/Visitor/Success.cs` and `docs/DesignPattern/DesignPatternCore/Visitor/Success.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:77— CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:77-84 | docs/CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:77-84 — before extracting anything, compare `CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs` and `docs/CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) CSharpGuide/diagnostics/MetricDemo/Program3.cs:14— CSharpGuide/diagnostics/MetricDemo/Program3.cs:14-21 | docs/CSharpGuide/diagnostics/MetricDemo/Program3.cs:14-21 — before extracting anything, compare `CSharpGuide/diagnostics/MetricDemo/Program3.cs` and `docs/CSharpGuide/diagnostics/MetricDemo/Program3.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) CSharpGuide/Program.cs:186— CSharpGuide/Program.cs:186-193 | docs/CSharpGuide/Program.cs:186-193 — before extracting anything, compare `CSharpGuide/Program.cs` and `docs/CSharpGuide/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:92— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:92-99 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:92-99 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) CSharpGuide/threads/ThreadChannelDemo.cs:23— CSharpGuide/threads/ThreadChannelDemo.cs:23-30 | docs/CSharpGuide/threads/ThreadChannelDemo.cs:23-30 — before extracting anything, compare `CSharpGuide/threads/ThreadChannelDemo.cs` and `docs/CSharpGuide/threads/ThreadChannelDemo.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) DesignPattern/DesignPatternCore/Builder/Client.cs:6— DesignPattern/DesignPatternCore/Builder/Client.cs:6-13 | docs/DesignPattern/DesignPatternCore/Builder/Client.cs:6-13 — before extracting anything, compare `DesignPattern/DesignPatternCore/Builder/Client.cs` and `docs/DesignPattern/DesignPatternCore/Builder/Client.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:71— FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:71-78 | docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:71-78 — before extracting anything, compare `FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs` and `docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:10— ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:10-17 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:10-17 — before extracting anything, compare `ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs` and `docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) REDACTED:25— REDACTED:25-32 | docs/REDACTED:25-32 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:92— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:92-99 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:92-99 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:17— AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:17-24 | docs/AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:17-24 — before extracting anything, compare `AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs` and `docs/AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.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 (8 lines × 2) AsyncInCSharp/WitchThreadRunCode/Program.cs:5— AsyncInCSharp/WitchThreadRunCode/Program.cs:5-12 | docs/AsyncInCSharp/WitchThreadRunCode/Program.cs:5-12 — before extracting anything, compare `AsyncInCSharp/WitchThreadRunCode/Program.cs` and `docs/AsyncInCSharp/WitchThreadRunCode/Program.cs` as WHOLE FILES: 100% 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 (9 lines × 2) CSharpGuide/Program.cs:144— CSharpGuide/Program.cs:144-152 | docs/CSharpGuide/Program.cs:144-152 — before extracting anything, compare `CSharpGuide/Program.cs` and `docs/CSharpGuide/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) DesignPattern/DesignPatternCore/Program.cs:24— DesignPattern/DesignPatternCore/Program.cs:24-32 | docs/DesignPattern/DesignPatternCore/Program.cs:24-32 — before extracting anything, compare `DesignPattern/DesignPatternCore/Program.cs` and `docs/DesignPattern/DesignPatternCore/Program.cs` as WHOLE FILES: 100% 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. 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 `DesignPattern/DesignPatternCore/Program.cs:24` 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) ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:82— ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:82-90 | docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:82-90 — before extracting anything, compare `ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` and `docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 (9 lines × 2) REDACTED:56— REDACTED:56-64 | docs/REDACTED:56-64 — before extracting anything, compare `REDACTED` and `docs/REDACTED` 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. 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 (9 lines × 2) REDACTED:10— REDACTED:10-18 | docs/REDACTED:10-18 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% 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 (9 lines × 2) ConcurrencyInCSharpCookbook/11Sync/Program.cs:25— ConcurrencyInCSharpCookbook/11Sync/Program.cs:25-33 | docs/ConcurrencyInCSharpCookbook/11Sync/Program.cs:25-33 — before extracting anything, compare `ConcurrencyInCSharpCookbook/11Sync/Program.cs` and `docs/ConcurrencyInCSharpCookbook/11Sync/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (9 lines × 2) ConcurrencyInCSharpCookbook/12Schedule/ScheduleParallelCode.cs:12— ConcurrencyInCSharpCookbook/12Schedule/ScheduleParallelCode.cs:12-20 | docs/ConcurrencyInCSharpCookbook/12Schedule/ScheduleParallelCode.cs:12-20 — before extracting anything, compare `ConcurrencyInCSharpCookbook/12Schedule/ScheduleParallelCode.cs` and `docs/ConcurrencyInCSharpCookbook/12Schedule/ScheduleParallelCode.cs` as WHOLE FILES: 100% 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 (9 lines × 2) ConcurrencyInCSharpCookbook/13PracticalSkills/InitializeShareResources.cs:9— ConcurrencyInCSharpCookbook/13PracticalSkills/InitializeShareResources.cs:9-17 | docs/ConcurrencyInCSharpCookbook/13PracticalSkills/InitializeShareResources.cs:9-17 — before extracting anything, compare `ConcurrencyInCSharpCookbook/13PracticalSkills/InitializeShareResources.cs` and `docs/ConcurrencyInCSharpCookbook/13PracticalSkills/InitializeShareResources.cs` as WHOLE FILES: 100% 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 `ConcurrencyInCSharpCookbook/13PracticalSkills/InitializeShareResources.cs:9` 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) REDACTED:22— REDACTED:22-30 | docs/REDACTED:22-30 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 (9 lines × 2) REDACTED:32— REDACTED:32-40 | docs/REDACTED:32-40 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 (9 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:62— CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:62-70 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:62-70 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (9 lines × 2) CSharpGuide/LanguageVersions/14.0/User.cs:6— CSharpGuide/LanguageVersions/14.0/User.cs:6-14 | docs/CSharpGuide/LanguageVersions/14.0/User.cs:6-14 — before extracting anything, compare `CSharpGuide/LanguageVersions/14.0/User.cs` and `docs/CSharpGuide/LanguageVersions/14.0/User.cs` as WHOLE FILES: 100% 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 `CSharpGuide/LanguageVersions/14.0/User.cs:6` 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) CSharpGuide/diagnostics/MetricDemo/Program5.cs:16— CSharpGuide/diagnostics/MetricDemo/Program5.cs:16-24 | docs/CSharpGuide/diagnostics/MetricDemo/Program5.cs:16-24 — before extracting anything, compare `CSharpGuide/diagnostics/MetricDemo/Program5.cs` and `docs/CSharpGuide/diagnostics/MetricDemo/Program5.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) DesignPattern/DesignPatternCore/Specification/AndSpecification.cs:6— DesignPattern/DesignPatternCore/Specification/AndSpecification.cs:6-14 | docs/DesignPattern/DesignPatternCore/Specification/AndSpecification.cs:6-14 — before extracting anything, compare `DesignPattern/DesignPatternCore/Specification/AndSpecification.cs` and `docs/DesignPattern/DesignPatternCore/Specification/AndSpecification.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/Int.cs:7— FunctionalCSharp/src/MarsonShine.Functional/Int.cs:7-15 | docs/FunctionalCSharp/src/MarsonShine.Functional/Int.cs:7-15 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/Int.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/Int.cs` as WHOLE FILES: 100% 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 (9 lines × 2) CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:18— CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:18-26 | docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:18-26 — before extracting anything, compare `CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs` and `docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:25— CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:25-33 | docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:25-33 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` and `docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:60— CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:60-68 | docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:60-68 — before extracting anything, compare `CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` and `docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:49— WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:49-57 | docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:49-57 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) ConcurrencyInCSharpCookbook/11Sync/Program.cs:38— ConcurrencyInCSharpCookbook/11Sync/Program.cs:38-46 | docs/ConcurrencyInCSharpCookbook/11Sync/Program.cs:38-46 — before extracting anything, compare `ConcurrencyInCSharpCookbook/11Sync/Program.cs` and `docs/ConcurrencyInCSharpCookbook/11Sync/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:22— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:22-30 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:22-30 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:54— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:54-62 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:54-62 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:89— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:89-97 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:89-97 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:68— CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:68-76 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:68-76 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) CSharpGuide/simd-vector-demo/VectorOperator.cs:15— CSharpGuide/simd-vector-demo/VectorOperator.cs:15-23 | docs/CSharpGuide/simd-vector-demo/VectorOperator.cs:15-23 — before extracting anything, compare `CSharpGuide/simd-vector-demo/VectorOperator.cs` and `docs/CSharpGuide/simd-vector-demo/VectorOperator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) CSharpGuide/roslySdkDemo/SyntaxWalker/UsingCollector.cs:16— CSharpGuide/roslySdkDemo/SyntaxWalker/UsingCollector.cs:16-22 | docs/CSharpGuide/roslySdkDemo/SyntaxWalker/UsingCollector.cs:16-22 — before extracting anything, compare `CSharpGuide/roslySdkDemo/SyntaxWalker/UsingCollector.cs` and `docs/CSharpGuide/roslySdkDemo/SyntaxWalker/UsingCollector.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) DesignPattern/DesignPatternCore/Builder/DefaultFullComputerBuilder.cs:25— DesignPattern/DesignPatternCore/Builder/DefaultFullComputerBuilder.cs:25-31 | docs/DesignPattern/DesignPatternCore/Builder/DefaultFullComputerBuilder.cs:25-31 — before extracting anything, compare `DesignPattern/DesignPatternCore/Builder/DefaultFullComputerBuilder.cs` and `docs/DesignPattern/DesignPatternCore/Builder/DefaultFullComputerBuilder.cs` as WHOLE FILES: 100% 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 `DesignPattern/DesignPatternCore/Builder/DefaultFullComputerBuilder.cs:25` 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) FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:4— FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:4-10 | docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:4-10 — before extracting anything, compare `FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs` and `docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:4` 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) WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:31— WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:31-37 | docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:31-37 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 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 (7 lines × 2) REDACTED:35— REDACTED:35-41 | docs/REDACTED:35-41 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (7 lines × 2) ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:11— ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:11-17 | docs/ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:11-17 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs` as WHOLE FILES: 100% 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. 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 `ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) CSharpInDepth/Chapter_3_Generic/Pair.cs:7— CSharpInDepth/Chapter_3_Generic/Pair.cs:7-13 | docs/CSharpInDepth/Chapter_3_Generic/Pair.cs:7-13 — before extracting anything, compare `CSharpInDepth/Chapter_3_Generic/Pair.cs` and `docs/CSharpInDepth/Chapter_3_Generic/Pair.cs` as WHOLE FILES: 100% 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. 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 `CSharpInDepth/Chapter_3_Generic/Pair.cs:7` 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) FunctionalCSharp/src/MarsonShine.Functional/FuncExt.cs:14— FunctionalCSharp/src/MarsonShine.Functional/FuncExt.cs:14-20 | docs/FunctionalCSharp/src/MarsonShine.Functional/FuncExt.cs:14-20 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/FuncExt.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/FuncExt.cs` as WHOLE FILES: 100% 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 (7 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:12— CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:12-18 | docs/CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:12-18 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:67— CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:67-73 | docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:67-73 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` and `docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 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 (7 lines × 2) CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:76— CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:76-82 | docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:76-82 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` and `docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 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 (7 lines × 2) CSharpGuide/Program.cs:126— CSharpGuide/Program.cs:126-132 | docs/CSharpGuide/Program.cs:126-132 — before extracting anything, compare `CSharpGuide/Program.cs` and `docs/CSharpGuide/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:246— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:246-252 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:246-252 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) CSharpGuide/threads/ThreadChannelDemo.cs:13— CSharpGuide/threads/ThreadChannelDemo.cs:13-19 | docs/CSharpGuide/threads/ThreadChannelDemo.cs:13-19 — before extracting anything, compare `CSharpGuide/threads/ThreadChannelDemo.cs` and `docs/CSharpGuide/threads/ThreadChannelDemo.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) DesignPattern/DesignPatternCore/ServiceLocator/Program.cs:7— DesignPattern/DesignPatternCore/ServiceLocator/Program.cs:7-13 | docs/DesignPattern/DesignPatternCore/ServiceLocator/Program.cs:7-13 — before extracting anything, compare `DesignPattern/DesignPatternCore/ServiceLocator/Program.cs` and `docs/DesignPattern/DesignPatternCore/ServiceLocator/Program.cs` as WHOLE FILES: 100% 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 (7 lines × 2) WHPerformanceDotNet/src/AsyncProgram/Program.cs:57— WHPerformanceDotNet/src/AsyncProgram/Program.cs:57-63 | docs/WHPerformanceDotNet/src/AsyncProgram/Program.cs:57-63 — before extracting anything, compare `WHPerformanceDotNet/src/AsyncProgram/Program.cs` and `docs/WHPerformanceDotNet/src/AsyncProgram/Program.cs` as WHOLE FILES: 100% 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. 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 (7 lines × 2) WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:15— WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:15-21 | docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:15-21 — before extracting anything, compare `WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` and `docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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 (7 lines × 2) REDACTED:17— REDACTED:17-23 | docs/REDACTED:17-23 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (7 lines × 2) ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs:14— ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs:14-20 | docs/ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs:14-20 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs` as WHOLE FILES: 100% 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. 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 (7 lines × 2) REDACTED:39— REDACTED:39-45 | docs/REDACTED:39-45 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (7 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:30— CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:30-36 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:30-36 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:41— CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:41-47 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:41-47 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:51— CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:51-57 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:51-57 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) ThinkingInJava/src/concurrency/SleepingTask.java:24— ThinkingInJava/src/concurrency/SleepingTask.java:24-30 | ThinkingInJava/src/concurrency/SleepingTask2.java:23-29 — 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 (11 lines × 2) CSharpGuide/performance/strings/Strings.cs:73— CSharpGuide/performance/strings/Strings.cs:73-83 | docs/CSharpGuide/performance/strings/Strings.cs:73-83 — before extracting anything, compare `CSharpGuide/performance/strings/Strings.cs` and `docs/CSharpGuide/performance/strings/Strings.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) CSharpGuide/threads/ThreadChannelDemo.cs:34— CSharpGuide/threads/ThreadChannelDemo.cs:34-44 | docs/CSharpGuide/threads/ThreadChannelDemo.cs:34-44 — before extracting anything, compare `CSharpGuide/threads/ThreadChannelDemo.cs` and `docs/CSharpGuide/threads/ThreadChannelDemo.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:77— CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:77-87 | docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:77-87 — before extracting anything, compare `CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` and `docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:72— WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:72-82 | docs/WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:72-82 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) WHPerformanceDotNet/src/EtlDemo/ConsoleListener.cs:16— WHPerformanceDotNet/src/EtlDemo/ConsoleListener.cs:16-26 | docs/WHPerformanceDotNet/src/EtlDemo/ConsoleListener.cs:16-26 — before extracting anything, compare `WHPerformanceDotNet/src/EtlDemo/ConsoleListener.cs` and `docs/WHPerformanceDotNet/src/EtlDemo/ConsoleListener.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) CSharpInDepth/Chapter06/IteratorWorkflow.cs:16— CSharpInDepth/Chapter06/IteratorWorkflow.cs:16-26 | docs/CSharpInDepth/Chapter06/IteratorWorkflow.cs:16-26 — before extracting anything, compare `CSharpInDepth/Chapter06/IteratorWorkflow.cs` and `docs/CSharpInDepth/Chapter06/IteratorWorkflow.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) CSharpGuide/diagnostics/MetricDemo/Program2.cs:5— CSharpGuide/diagnostics/MetricDemo/Program2.cs:5-15 | docs/CSharpGuide/diagnostics/MetricDemo/Program2.cs:5-15 — before extracting anything, compare `CSharpGuide/diagnostics/MetricDemo/Program2.cs` and `docs/CSharpGuide/diagnostics/MetricDemo/Program2.cs` as WHOLE FILES: 100% 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. 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 `CSharpGuide/diagnostics/MetricDemo/Program2.cs:5` 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) CSharpGuide/random/Distribution.cs:16— CSharpGuide/random/Distribution.cs:16-26 | docs/CSharpGuide/random/Distribution.cs:16-26 — before extracting anything, compare `CSharpGuide/random/Distribution.cs` and `docs/CSharpGuide/random/Distribution.cs` as WHOLE FILES: 100% 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 (11 lines × 2) WHPerformanceDotNet/src/GCPool/PoolManager.cs:42— WHPerformanceDotNet/src/GCPool/PoolManager.cs:42-52 | docs/WHPerformanceDotNet/src/GCPool/PoolManager.cs:42-52 — before extracting anything, compare `WHPerformanceDotNet/src/GCPool/PoolManager.cs` and `docs/WHPerformanceDotNet/src/GCPool/PoolManager.cs` as WHOLE FILES: 100% 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. 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 (11 lines × 2) WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:23— WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:23-33 | docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:23-33 — before extracting anything, compare `WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` and `docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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 (11 lines × 2) WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:59— WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:59-69 | docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:59-69 — before extracting anything, compare `WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` and `docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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 (11 lines × 2) WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:10— WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:10-20 | docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:10-20 — before extracting anything, compare `WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs` and `docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs` as WHOLE FILES: 100% 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. 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 `WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:10` 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) ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:109— ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:109-119 | docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:109-119 — before extracting anything, compare `ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` and `docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 (11 lines × 2) ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs:18— ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs:18-28 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs:18-28 — before extracting anything, compare `ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs` and `docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs` as WHOLE FILES: 100% 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. 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 (11 lines × 2) ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:12— ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:12-22 | docs/ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:12-22 — before extracting anything, compare `ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs` and `docs/ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs` as WHOLE FILES: 100% 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. 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 (11 lines × 2) CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:33— CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:33-43 | docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs:33-43 — before extracting anything, compare `CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs` and `docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/MinimalEventCounterSource.cs` as WHOLE FILES: 100% 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 (11 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/DeconstructionExtensions.cs:14— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/DeconstructionExtensions.cs:14-24 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/DeconstructionExtensions.cs:14-24 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/DeconstructionExtensions.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/DeconstructionExtensions.cs` as WHOLE FILES: 100% 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 (11 lines × 2) DesignPattern/DesignPatternCore/Specification/CompositeSpecification.cs:9— DesignPattern/DesignPatternCore/Specification/CompositeSpecification.cs:9-19 | docs/DesignPattern/DesignPatternCore/Specification/CompositeSpecification.cs:9-19 — before extracting anything, compare `DesignPattern/DesignPatternCore/Specification/CompositeSpecification.cs` and `docs/DesignPattern/DesignPatternCore/Specification/CompositeSpecification.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/Traversable/IEnumerable.cs:7— FunctionalCSharp/src/MarsonShine.Functional/Traversable/IEnumerable.cs:7-17 | docs/FunctionalCSharp/src/MarsonShine.Functional/Traversable/IEnumerable.cs:7-17 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/Traversable/IEnumerable.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/Traversable/IEnumerable.cs` as WHOLE FILES: 100% 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 (11 lines × 2) CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:115— CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:115-125 | docs/CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:115-125 — before extracting anything, compare `CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs` and `docs/CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:46— CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:46-56 | docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:46-56 — before extracting anything, compare `CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` and `docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) AsyncInCSharp/ExceptionInAsync/MultipleException.cs:6— AsyncInCSharp/ExceptionInAsync/MultipleException.cs:6-16 | docs/AsyncInCSharp/ExceptionInAsync/MultipleException.cs:6-16 — before extracting anything, compare `AsyncInCSharp/ExceptionInAsync/MultipleException.cs` and `docs/AsyncInCSharp/ExceptionInAsync/MultipleException.cs` as WHOLE FILES: 100% 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 (11 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:90— CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:90-100 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:90-100 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 71 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.
DeadPreprocessorBranch CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs:17— #if ERROR — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs:17— #if ERROR — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch CSharpGuide/diagnostics/EventSourceDemo/Program.cs:33— #if ActivityIDs — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/CSharpGuide/diagnostics/EventSourceDemo/Program.cs:33— #if ActivityIDs — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch CSharpGuide/performance/ArrayChunkOfStruct.cs:18— #if FIRST — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/CSharpGuide/performance/ArrayChunkOfStruct.cs:18— #if FIRST — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch CSharpGuide/performance/ArrayChunkOfStruct.cs:27— #if Second — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/CSharpGuide/performance/ArrayChunkOfStruct.cs:27— #if Second — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch DesignPattern/DesignPattern/Program.cs:18— #if DECORATOR — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/DesignPattern/DesignPattern/Program.cs:18— #if DECORATOR — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch DesignPattern/DesignPattern/Program.cs:27— #if Proxy — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch DesignPattern/DesignPatternCore/Program.cs:34— #if Proxy — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/DesignPattern/DesignPattern/Program.cs:27— #if Proxy — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/DesignPattern/DesignPatternCore/Program.cs:34— #if Proxy — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch DesignPattern/DesignPattern/Program.cs:37— #if ChanOfResposibility — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch DesignPattern/DesignPatternCore/Program.cs:44— #if ChanOfResposibility — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/DesignPattern/DesignPattern/Program.cs:37— #if ChanOfResposibility — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/DesignPattern/DesignPatternCore/Program.cs:44— #if ChanOfResposibility — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch DesignPattern/DesignPattern/Program.cs:54— #if ChainOfResiposibility — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch DesignPattern/DesignPatternCore/Program.cs:61— #if ChainOfResiposibility — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/DesignPattern/DesignPattern/Program.cs:54— #if ChainOfResiposibility — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch docs/DesignPattern/DesignPatternCore/Program.cs:61— #if ChainOfResiposibility — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
Duplicated block (16 lines × 2) CSharpGuide/diagnostics/CollectionMetricDemo/PromethusProgram.cs:16— CSharpGuide/diagnostics/CollectionMetricDemo/PromethusProgram.cs:16-31 | docs/CSharpGuide/diagnostics/CollectionMetricDemo/PromethusProgram.cs:16-31 — before extracting anything, compare `CSharpGuide/diagnostics/CollectionMetricDemo/PromethusProgram.cs` and `docs/CSharpGuide/diagnostics/CollectionMetricDemo/PromethusProgram.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs:25— CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs:25-40 | docs/CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs:25-40 — before extracting anything, compare `CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs` and `docs/CSharpGuide/diagnostics/DistributedTraceDemo/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpGuide/is-operator/IsOperatorInCsharp.cs:15— CSharpGuide/is-operator/IsOperatorInCsharp.cs:15-30 | docs/CSharpGuide/is-operator/IsOperatorInCsharp.cs:15-30 — before extracting anything, compare `CSharpGuide/is-operator/IsOperatorInCsharp.cs` and `docs/CSharpGuide/is-operator/IsOperatorInCsharp.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpGuide/LanguageVersions/8.0/DecompilerAsyncStream.cs:12— CSharpGuide/LanguageVersions/8.0/DecompilerAsyncStream.cs:12-27 | docs/CSharpGuide/LanguageVersions/8.0/DecompilerAsyncStream.cs:12-27 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/DecompilerAsyncStream.cs` and `docs/CSharpGuide/LanguageVersions/8.0/DecompilerAsyncStream.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpGuide/performance/strings/Strings.cs:30— CSharpGuide/performance/strings/Strings.cs:30-45 | docs/CSharpGuide/performance/strings/Strings.cs:30-45 — before extracting anything, compare `CSharpGuide/performance/strings/Strings.cs` and `docs/CSharpGuide/performance/strings/Strings.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpGuide/threads/ThreadChannelDemo.cs:48— CSharpGuide/threads/ThreadChannelDemo.cs:48-63 | docs/CSharpGuide/threads/ThreadChannelDemo.cs:48-63 — before extracting anything, compare `CSharpGuide/threads/ThreadChannelDemo.cs` and `docs/CSharpGuide/threads/ThreadChannelDemo.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:29— WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:29-44 | docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:29-44 — before extracting anything, compare `WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` and `docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs:54— WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs:54-69 | docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs:54-69 — before extracting anything, compare `WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs` and `docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpInDepth/Chapter06/Program.cs:15— CSharpInDepth/Chapter06/Program.cs:15-30 | docs/CSharpInDepth/Chapter06/Program.cs:15-30 — before extracting anything, compare `CSharpInDepth/Chapter06/Program.cs` and `docs/CSharpInDepth/Chapter06/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:15— WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:15-30 | docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:15-30 — before extracting anything, compare `WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs` and `docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 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 (16 lines × 2) ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:92— ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:92-107 | docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:92-107 — before extracting anything, compare `ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` and `docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 (16 lines × 2) REDACTED:30— REDACTED:30-45 | docs/REDACTED:30-45 — before extracting anything, compare `REDACTED` and `docs/REDACTED` 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. 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 (16 lines × 2) ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:24— ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:24-39 | docs/ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:24-39 — before extracting anything, compare `ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs` and `docs/ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs` as WHOLE FILES: 100% 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. 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 (16 lines × 2) CSharpGuide/LanguageVersions/10.0/StringInterpolate/LogInterpolatedStringHandler.cs:21— CSharpGuide/LanguageVersions/10.0/StringInterpolate/LogInterpolatedStringHandler.cs:21-36 | docs/CSharpGuide/LanguageVersions/10.0/StringInterpolate/LogInterpolatedStringHandler.cs:21-36 — before extracting anything, compare `CSharpGuide/LanguageVersions/10.0/StringInterpolate/LogInterpolatedStringHandler.cs` and `docs/CSharpGuide/LanguageVersions/10.0/StringInterpolate/LogInterpolatedStringHandler.cs` as WHOLE FILES: 100% 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 (16 lines × 2) CSharpGuide/random/BetterRandom.cs:10— CSharpGuide/random/BetterRandom.cs:10-25 | docs/CSharpGuide/random/BetterRandom.cs:10-25 — before extracting anything, compare `CSharpGuide/random/BetterRandom.cs` and `docs/CSharpGuide/random/BetterRandom.cs` as WHOLE FILES: 100% 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 (16 lines × 2) CSharpGuide/Program.cs:156— CSharpGuide/Program.cs:156-171 | docs/CSharpGuide/Program.cs:156-171 — before extracting anything, compare `CSharpGuide/Program.cs` and `docs/CSharpGuide/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) WHPerformanceDotNet/src/TPLDataflow/Program.cs:17— WHPerformanceDotNet/src/TPLDataflow/Program.cs:17-32 | docs/WHPerformanceDotNet/src/TPLDataflow/Program.cs:17-32 — before extracting anything, compare `WHPerformanceDotNet/src/TPLDataflow/Program.cs` and `docs/WHPerformanceDotNet/src/TPLDataflow/Program.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:34— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:34-49 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:34-49 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpGuide/simd-vector-demo/Extensions.cs:13— CSharpGuide/simd-vector-demo/Extensions.cs:13-28 | docs/CSharpGuide/simd-vector-demo/Extensions.cs:13-28 — before extracting anything, compare `CSharpGuide/simd-vector-demo/Extensions.cs` and `docs/CSharpGuide/simd-vector-demo/Extensions.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) CSharpGuide/simd-vector-demo/VectorOperator.cs:27— CSharpGuide/simd-vector-demo/VectorOperator.cs:27-42 | docs/CSharpGuide/simd-vector-demo/VectorOperator.cs:27-42 — before extracting anything, compare `CSharpGuide/simd-vector-demo/VectorOperator.cs` and `docs/CSharpGuide/simd-vector-demo/VectorOperator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) CSharpGuide/LanguageVersions/7.0/Discards.cs:14— CSharpGuide/LanguageVersions/7.0/Discards.cs:14-23 | docs/CSharpGuide/LanguageVersions/7.0/Discards.cs:14-23 — before extracting anything, compare `CSharpGuide/LanguageVersions/7.0/Discards.cs` and `docs/CSharpGuide/LanguageVersions/7.0/Discards.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) CSharpGuide/Program.cs:197— CSharpGuide/Program.cs:197-206 | docs/CSharpGuide/Program.cs:197-206 — before extracting anything, compare `CSharpGuide/Program.cs` and `docs/CSharpGuide/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/FileTransformGenerator.cs:15— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/FileTransformGenerator.cs:15-24 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/FileTransformGenerator.cs:15-24 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/FileTransformGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/FileTransformGenerator.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:59— WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:59-68 | docs/WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:59-68 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/Program.cs:89— WHPerformanceDotNet/src/MomeryAllocation/Program.cs:89-98 | docs/WHPerformanceDotNet/src/MomeryAllocation/Program.cs:89-98 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/Program.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:121— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:121-130 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:121-130 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:16— CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:16-25 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs:16-25 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/SpanAndMemoryAccess.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:93— CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:93-102 | docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:93-102 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` and `docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 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) WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:48— WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:48-57 | docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:48-57 — before extracting anything, compare `WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` and `docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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) ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs:16— ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs:16-25 | docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs:16-25 — before extracting anything, compare `ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs` and `docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs` as WHOLE FILES: 100% 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. 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) REDACTED:51— REDACTED:51-60 | docs/REDACTED:51-60 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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) AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:49— AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:49-58 | docs/AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:49-58 — before extracting anything, compare `AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs` and `docs/AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.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) CSharpGuide/async/AsyncLocalViaThreadLocal.cs:28— CSharpGuide/async/AsyncLocalViaThreadLocal.cs:28-37 | docs/CSharpGuide/async/AsyncLocalViaThreadLocal.cs:28-37 — before extracting anything, compare `CSharpGuide/async/AsyncLocalViaThreadLocal.cs` and `docs/CSharpGuide/async/AsyncLocalViaThreadLocal.cs` as WHOLE FILES: 100% 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 (10 lines × 2) WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:31— WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:31-40 | docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:31-40 — before extracting anything, compare `WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs` and `docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs` as WHOLE FILES: 100% 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. 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) CSharpGuide/performance/strings/Strings.cs:87— CSharpGuide/performance/strings/Strings.cs:87-96 | docs/CSharpGuide/performance/strings/Strings.cs:87-96 — before extracting anything, compare `CSharpGuide/performance/strings/Strings.cs` and `docs/CSharpGuide/performance/strings/Strings.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) CSharpGuide/performance/strings/Strings.cs:101— CSharpGuide/performance/strings/Strings.cs:101-110 | docs/CSharpGuide/performance/strings/Strings.cs:101-110 — before extracting anything, compare `CSharpGuide/performance/strings/Strings.cs` and `docs/CSharpGuide/performance/strings/Strings.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:107— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:107-116 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:107-116 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.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.
Duplicated block (10 lines × 2) ConcurrencyInCSharpCookbook/07Interoperate/Program.cs:5— ConcurrencyInCSharpCookbook/07Interoperate/Program.cs:5-14 | docs/ConcurrencyInCSharpCookbook/07Interoperate/Program.cs:5-14 — before extracting anything, compare `ConcurrencyInCSharpCookbook/07Interoperate/Program.cs` and `docs/ConcurrencyInCSharpCookbook/07Interoperate/Program.cs` as WHOLE FILES: 100% 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 (10 lines × 2) ConcurrencyInCSharpCookbook/11Sync/AsyncLock.cs:14— ConcurrencyInCSharpCookbook/11Sync/AsyncLock.cs:14-23 | docs/ConcurrencyInCSharpCookbook/11Sync/AsyncLock.cs:14-23 — before extracting anything, compare `ConcurrencyInCSharpCookbook/11Sync/AsyncLock.cs` and `docs/ConcurrencyInCSharpCookbook/11Sync/AsyncLock.cs` as WHOLE FILES: 100% 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 (10 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:107— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:107-116 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:107-116 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.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.
Unfinished stub — throws NotImplementedException CSharpGuide/LanguageVersions/7.0/IValueMark.cs:17— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CSharpGuide/LanguageVersions/7.0/IValueMark.cs:19— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CSharpGuide/LanguageVersions/8.0/Introducer.cs:66— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:34— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:40— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CSharpGuide/net8-guide/Performances/FrozenTypes.cs:16— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:96— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/LanguageVersions/7.0/IValueMark.cs:17— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/LanguageVersions/7.0/IValueMark.cs:19— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/LanguageVersions/8.0/Introducer.cs:66— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:34— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:40— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/net8-guide/Performances/FrozenTypes.cs:16— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:96— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:21— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:21— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException AsyncInCSharp/TAPs/PermissionDialog.cs:8— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/AsyncInCSharp/TAPs/PermissionDialog.cs:8— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/Deque.cs:156— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/Deque.cs:190— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Duplicated block (12 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs:24— CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs:24-35 | docs/CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs:24-35 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:52— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:52-63 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:52-63 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs:17— DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs:17-28 | docs/DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs:17-28 — before extracting anything, compare `DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs` and `docs/DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.cs:17— DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.cs:17-28 | docs/DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.cs:17-28 — before extracting anything, compare `DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.cs` and `docs/DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:24— CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:24-35 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:24-35 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) DesignPattern/DesignPattern/Program.cs:79— DesignPattern/DesignPattern/Program.cs:79-90 | docs/DesignPattern/DesignPattern/Program.cs:79-90 — before extracting anything, compare `DesignPattern/DesignPattern/Program.cs` and `docs/DesignPattern/DesignPattern/Program.cs` as WHOLE FILES: 100% 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 `DesignPattern/DesignPattern/Program.cs:79` 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) WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:35— WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:35-46 | docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs:35-46 — before extracting anything, compare `WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` and `docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/AsyncLock.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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 (12 lines × 2) ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:16— ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:16-27 | docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:16-27 — before extracting anything, compare `ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs` and `docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 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 (12 lines × 2) ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs:27— ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs:27-38 | docs/ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs:27-38 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs` as WHOLE FILES: 100% 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. 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 (12 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/AdvancedCustomizedEventSource.cs:16— CSharpGuide/diagnostics/EventSourceDemo/AdvancedCustomizedEventSource.cs:16-27 | docs/CSharpGuide/diagnostics/EventSourceDemo/AdvancedCustomizedEventSource.cs:16-27 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/AdvancedCustomizedEventSource.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/AdvancedCustomizedEventSource.cs` as WHOLE FILES: 100% 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 (12 lines × 2) CSharpGuide/random/Normal.cs:11— CSharpGuide/random/Normal.cs:11-22 | docs/CSharpGuide/random/Normal.cs:11-22 — before extracting anything, compare `CSharpGuide/random/Normal.cs` and `docs/CSharpGuide/random/Normal.cs` as WHOLE FILES: 100% 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 `CSharpGuide/random/Normal.cs:11` 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 (12 lines × 2) CSharpGuide/random/Pseudorandom.cs:11— CSharpGuide/random/Pseudorandom.cs:11-22 | docs/CSharpGuide/random/Pseudorandom.cs:11-22 — before extracting anything, compare `CSharpGuide/random/Pseudorandom.cs` and `docs/CSharpGuide/random/Pseudorandom.cs` as WHOLE FILES: 100% 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 (12 lines × 2) DesignPattern/DesignPattern/Visitor/ObjectStructure.cs:18— DesignPattern/DesignPattern/Visitor/ObjectStructure.cs:18-29 | docs/DesignPattern/DesignPattern/Visitor/ObjectStructure.cs:18-29 — before extracting anything, compare `DesignPattern/DesignPattern/Visitor/ObjectStructure.cs` and `docs/DesignPattern/DesignPattern/Visitor/ObjectStructure.cs` as WHOLE FILES: 100% 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 (12 lines × 2) DesignPattern/DesignPatternCore/Visitor/ObjectStructure.cs:18— DesignPattern/DesignPatternCore/Visitor/ObjectStructure.cs:18-29 | docs/DesignPattern/DesignPatternCore/Visitor/ObjectStructure.cs:18-29 — before extracting anything, compare `DesignPattern/DesignPatternCore/Visitor/ObjectStructure.cs` and `docs/DesignPattern/DesignPatternCore/Visitor/ObjectStructure.cs` as WHOLE FILES: 100% 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 (12 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/Traversable/Option.cs:7— FunctionalCSharp/src/MarsonShine.Functional/Traversable/Option.cs:7-18 | docs/FunctionalCSharp/src/MarsonShine.Functional/Traversable/Option.cs:7-18 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/Traversable/Option.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/Traversable/Option.cs` as WHOLE FILES: 100% 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 (12 lines × 2) ConcurrencyInCSharpCookbook/12Schedule/TaskScheduleImplementDataflowSync.cs:11— ConcurrencyInCSharpCookbook/12Schedule/TaskScheduleImplementDataflowSync.cs:11-22 | docs/ConcurrencyInCSharpCookbook/12Schedule/TaskScheduleImplementDataflowSync.cs:11-22 — before extracting anything, compare `ConcurrencyInCSharpCookbook/12Schedule/TaskScheduleImplementDataflowSync.cs` and `docs/ConcurrencyInCSharpCookbook/12Schedule/TaskScheduleImplementDataflowSync.cs` as WHOLE FILES: 100% 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 (12 lines × 2) ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs:27— ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs:27-38 | docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs:27-38 — before extracting anything, compare `ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs` and `docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncLazy.cs` as WHOLE FILES: 100% 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. 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 (12 lines × 2) AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:26— AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:26-37 | docs/AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:26-37 — before extracting anything, compare `AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs` and `docs/AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.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 (14 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs:29— CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs:29-42 | docs/CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs:29-42 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:67— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:67-80 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:67-80 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:20— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:20-33 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:20-33 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) CSharpGuide/threads/ThreadChannelDemo.cs:80— CSharpGuide/threads/ThreadChannelDemo.cs:80-93 | docs/CSharpGuide/threads/ThreadChannelDemo.cs:80-93 — before extracting anything, compare `CSharpGuide/threads/ThreadChannelDemo.cs` and `docs/CSharpGuide/threads/ThreadChannelDemo.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:104— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:104-117 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:104-117 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:53— CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:53-66 | docs/CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:53-66 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (14 lines × 2) CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs:35— CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs:35-48 | docs/CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs:35-48 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs` and `docs/CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs` as WHOLE FILES: 100% 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. 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 (14 lines × 2) DesignPattern/DesignPatternCore/Factory/PdfConvertorFactory.cs:5— DesignPattern/DesignPatternCore/Factory/PdfConvertorFactory.cs:5-18 | docs/DesignPattern/DesignPatternCore/Factory/PdfConvertorFactory.cs:5-18 — before extracting anything, compare `DesignPattern/DesignPatternCore/Factory/PdfConvertorFactory.cs` and `docs/DesignPattern/DesignPatternCore/Factory/PdfConvertorFactory.cs` as WHOLE FILES: 100% 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 (14 lines × 2) ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:62— ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:62-75 | docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:62-75 — before extracting anything, compare `ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs` and `docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 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 (14 lines × 2) ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs:12— ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs:12-25 | docs/ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs:12-25 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/ImmutableStackAndQueue.cs` as WHOLE FILES: 100% 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. 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 (14 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReturn.cs:17— CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReturn.cs:17-30 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReturn.cs:17-30 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReturn.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReturn.cs` as WHOLE FILES: 100% 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. 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 (14 lines × 2) CSharpInDepth/Chapter10_Extension/StreamUtil.cs:8— CSharpInDepth/Chapter10_Extension/StreamUtil.cs:8-21 | docs/CSharpInDepth/Chapter10_Extension/StreamUtil.cs:8-21 — before extracting anything, compare `CSharpInDepth/Chapter10_Extension/StreamUtil.cs` and `docs/CSharpInDepth/Chapter10_Extension/StreamUtil.cs` as WHOLE FILES: 100% 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 (14 lines × 2) DesignPattern/DesignPattern/Proxy/Proxy.cs:17— DesignPattern/DesignPattern/Proxy/Proxy.cs:17-30 | docs/DesignPattern/DesignPattern/Proxy/Proxy.cs:17-30 — before extracting anything, compare `DesignPattern/DesignPattern/Proxy/Proxy.cs` and `docs/DesignPattern/DesignPattern/Proxy/Proxy.cs` as WHOLE FILES: 100% 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 (14 lines × 2) DesignPattern/DesignPattern/Proxy/Pursuit.cs:16— DesignPattern/DesignPattern/Proxy/Pursuit.cs:16-29 | docs/DesignPattern/DesignPattern/Proxy/Pursuit.cs:16-29 — before extracting anything, compare `DesignPattern/DesignPattern/Proxy/Pursuit.cs` and `docs/DesignPattern/DesignPattern/Proxy/Pursuit.cs` as WHOLE FILES: 100% 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 (14 lines × 2) DesignPattern/DesignPatternCore/Proxy/Proxy.cs:17— DesignPattern/DesignPatternCore/Proxy/Proxy.cs:17-30 | docs/DesignPattern/DesignPatternCore/Proxy/Proxy.cs:17-30 — before extracting anything, compare `DesignPattern/DesignPatternCore/Proxy/Proxy.cs` and `docs/DesignPattern/DesignPatternCore/Proxy/Proxy.cs` as WHOLE FILES: 100% 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 (14 lines × 2) DesignPattern/DesignPatternCore/Proxy/Pursuit.cs:16— DesignPattern/DesignPatternCore/Proxy/Pursuit.cs:16-29 | docs/DesignPattern/DesignPatternCore/Proxy/Pursuit.cs:16-29 — before extracting anything, compare `DesignPattern/DesignPatternCore/Proxy/Pursuit.cs` and `docs/DesignPattern/DesignPatternCore/Proxy/Pursuit.cs` as WHOLE FILES: 100% 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 (13 lines × 2) CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:30— CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:30-42 | docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:30-42 — before extracting anything, compare `CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs` and `docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs:54— CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs:54-66 | docs/CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs:54-66 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/UtilBaseEventSource.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:12— WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:12-24 | docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:12-24 — before extracting anything, compare `WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` and `docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:9— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:9-21 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:9-21 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:9` 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) WHPerformanceDotNet/src/GCPool/PoolManager.cs:27— WHPerformanceDotNet/src/GCPool/PoolManager.cs:27-39 | docs/WHPerformanceDotNet/src/GCPool/PoolManager.cs:27-39 — before extracting anything, compare `WHPerformanceDotNet/src/GCPool/PoolManager.cs` and `docs/WHPerformanceDotNet/src/GCPool/PoolManager.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:13— WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:13-25 | docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:13-25 — before extracting anything, compare `WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs` and `docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs` as WHOLE FILES: 100% 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. 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 `WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:19— ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:19-31 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:19-31 — before extracting anything, compare `ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs` and `docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (13 lines × 2) ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs:29— ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs:29-41 | docs/ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs:29-41 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/ConCurrentDictionaries.cs` as WHOLE FILES: 100% 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. 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 (13 lines × 2) ConcurrencyInCSharpCookbook/09Cancellation/CancellationByPoll.cs:21— ConcurrencyInCSharpCookbook/09Cancellation/CancellationByPoll.cs:21-33 | docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationByPoll.cs:21-33 — before extracting anything, compare `ConcurrencyInCSharpCookbook/09Cancellation/CancellationByPoll.cs` and `docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationByPoll.cs` as WHOLE FILES: 100% 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 (13 lines × 2) ConcurrencyInCSharpCookbook/09Cancellation/CancellationHelper.cs:11— ConcurrencyInCSharpCookbook/09Cancellation/CancellationHelper.cs:11-23 | docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationHelper.cs:11-23 — before extracting anything, compare `ConcurrencyInCSharpCookbook/09Cancellation/CancellationHelper.cs` and `docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationHelper.cs` as WHOLE FILES: 100% 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 (13 lines × 2) ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:35— ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:35-47 | docs/ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:35-47 — before extracting anything, compare `ConcurrencyInCSharpCookbook/11Sync/Throttling.cs` and `docs/ConcurrencyInCSharpCookbook/11Sync/Throttling.cs` as WHOLE FILES: 100% 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 (13 lines × 2) REDACTED:8— REDACTED:8-20 | docs/REDACTED:8-20 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 (13 lines × 2) CSharpInDepth/Chapter10_Extension/EnumerableUtil.cs:8— CSharpInDepth/Chapter10_Extension/EnumerableUtil.cs:8-20 | docs/CSharpInDepth/Chapter10_Extension/EnumerableUtil.cs:8-20 — before extracting anything, compare `CSharpInDepth/Chapter10_Extension/EnumerableUtil.cs` and `docs/CSharpInDepth/Chapter10_Extension/EnumerableUtil.cs` as WHOLE FILES: 100% 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 `CSharpInDepth/Chapter10_Extension/EnumerableUtil.cs:8` 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) ConcurrencyInCSharpCookbook/ThreadBasic/Program.cs:8— ConcurrencyInCSharpCookbook/ThreadBasic/Program.cs:8-20 | docs/ConcurrencyInCSharpCookbook/ThreadBasic/Program.cs:8-20 — before extracting anything, compare `ConcurrencyInCSharpCookbook/ThreadBasic/Program.cs` and `docs/ConcurrencyInCSharpCookbook/ThreadBasic/Program.cs` as WHOLE FILES: 100% 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 (13 lines × 2) CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:53— CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:53-65 | docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:53-65 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` and `docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) DesignPattern/DesignPatternGo/states/state.go:19— DesignPattern/DesignPatternGo/states/state.go:19-31 | DesignPattern/DesignPatternGo/states/state.go:43-55 — 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.
Outbound HTTP without resilience CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:11— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:12— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:18— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:26— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:37— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs:42— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:36— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience docs/REDACTED:11— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience docs/REDACTED:12— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience docs/REDACTED:18— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience docs/REDACTED:26— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience docs/REDACTED:37— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs:42— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience docs/ConcurrencyInCSharpCookbook/11Sync/Throttling.cs:36— `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. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Duplicated block (5 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:106— WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:106-110 | docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:106-110 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/Deque.cs:261— Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/Deque.cs:261-265 | Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 6/Deque.cs:217-221 — 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 `Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 3/Deque.cs:261` 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 (5 lines × 2) ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:10— ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:10-14 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:10-14 — before extracting anything, compare `ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs` and `docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs` as WHOLE FILES: 100% 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. 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 (5 lines × 2) CSharpGuide/LanguageVersions/10.0/StringInterpolate/InterpolatedStringHandler.cs:30— CSharpGuide/LanguageVersions/10.0/StringInterpolate/InterpolatedStringHandler.cs:30-34 | docs/CSharpGuide/LanguageVersions/10.0/StringInterpolate/InterpolatedStringHandler.cs:30-34 — before extracting anything, compare `CSharpGuide/LanguageVersions/10.0/StringInterpolate/InterpolatedStringHandler.cs` and `docs/CSharpGuide/LanguageVersions/10.0/StringInterpolate/InterpolatedStringHandler.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:77— CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:77-81 | docs/CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs:77-81 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/DiagnosticSourceQuickStart.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:37— CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:37-41 | docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:37-41 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` and `docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) CSharpGuide/random/FakeRandom.cs:5— CSharpGuide/random/FakeRandom.cs:5-9 | docs/CSharpGuide/random/FakeRandom.cs:5-9 — before extracting anything, compare `CSharpGuide/random/FakeRandom.cs` and `docs/CSharpGuide/random/FakeRandom.cs` as WHOLE FILES: 100% 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 (5 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:24— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:24-28 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:24-28 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:54— FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:54-58 | docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:54-58 — before extracting anything, compare `FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs` and `docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) WHPerformanceDotNet/src/EtlDemo/Program.cs:9— WHPerformanceDotNet/src/EtlDemo/Program.cs:9-13 | docs/WHPerformanceDotNet/src/EtlDemo/Program.cs:9-13 — before extracting anything, compare `WHPerformanceDotNet/src/EtlDemo/Program.cs` and `docs/WHPerformanceDotNet/src/EtlDemo/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) REDACTED:65— REDACTED:65-69 | docs/REDACTED:65-69 — before extracting anything, compare `REDACTED` and `docs/REDACTED` 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. 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 (5 lines × 2) ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs:12— ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs:12-16 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs:12-16 — before extracting anything, compare `ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs` and `docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/UseWindowAndBufferToGroupEvent.cs` as WHOLE FILES: 100% 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. 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 (5 lines × 2) REDACTED:62— REDACTED:62-66 | docs/REDACTED:62-66 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (5 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:39— CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:39-43 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:39-43 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:46— CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:46-50 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs:46-50 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/InParameter.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) CSharpGuide/LanguageVersions/14.0/Program.cs:7— CSharpGuide/LanguageVersions/14.0/Program.cs:7-21 | docs/CSharpGuide/LanguageVersions/14.0/Program.cs:7-21 — before extracting anything, compare `CSharpGuide/LanguageVersions/14.0/Program.cs` and `docs/CSharpGuide/LanguageVersions/14.0/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) CSharpGuide/threads/ThreadChannelDemo.cs:110— CSharpGuide/threads/ThreadChannelDemo.cs:110-124 | docs/CSharpGuide/threads/ThreadChannelDemo.cs:110-124 — before extracting anything, compare `CSharpGuide/threads/ThreadChannelDemo.cs` and `docs/CSharpGuide/threads/ThreadChannelDemo.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) CSharpInDepth/Chapter_3_Generic/ReflectorGeneric.cs:11— CSharpInDepth/Chapter_3_Generic/ReflectorGeneric.cs:11-25 | docs/CSharpInDepth/Chapter_3_Generic/ReflectorGeneric.cs:11-25 — before extracting anything, compare `CSharpInDepth/Chapter_3_Generic/ReflectorGeneric.cs` and `docs/CSharpInDepth/Chapter_3_Generic/ReflectorGeneric.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:32— WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:32-46 | docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:32-46 — before extracting anything, compare `WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs` and `docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 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 (15 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/PoolableObject/PoolManager.cs:29— WHPerformanceDotNet/src/MomeryAllocation/PoolableObject/PoolManager.cs:29-43 | docs/WHPerformanceDotNet/src/MomeryAllocation/PoolableObject/PoolManager.cs:29-43 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/PoolableObject/PoolManager.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/PoolableObject/PoolManager.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:41— ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:41-55 | docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:41-55 — before extracting anything, compare `ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` and `docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 (15 lines × 2) ConcurrencyInCSharpCookbook/08Collections/Program.cs:12— ConcurrencyInCSharpCookbook/08Collections/Program.cs:12-26 | docs/ConcurrencyInCSharpCookbook/08Collections/Program.cs:12-26 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/Program.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/Program.cs` as WHOLE FILES: 100% 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 (15 lines × 2) AsyncInCSharp/UtilitiesForTAP/CustomeCombinators.cs:7— AsyncInCSharp/UtilitiesForTAP/CustomeCombinators.cs:7-21 | docs/AsyncInCSharp/UtilitiesForTAP/CustomeCombinators.cs:7-21 — before extracting anything, compare `AsyncInCSharp/UtilitiesForTAP/CustomeCombinators.cs` and `docs/AsyncInCSharp/UtilitiesForTAP/CustomeCombinators.cs` as WHOLE FILES: 100% 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 (15 lines × 2) CSharpGuide/LanguageVersions/14.0/Extensions.cs:15— CSharpGuide/LanguageVersions/14.0/Extensions.cs:15-29 | docs/CSharpGuide/LanguageVersions/14.0/Extensions.cs:15-29 — before extracting anything, compare `CSharpGuide/LanguageVersions/14.0/Extensions.cs` and `docs/CSharpGuide/LanguageVersions/14.0/Extensions.cs` as WHOLE FILES: 100% 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 `CSharpGuide/LanguageVersions/14.0/Extensions.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 (15 lines × 2) CSharpGuide/unsafeclass-useage/Program.cs:22— CSharpGuide/unsafeclass-useage/Program.cs:22-36 | docs/CSharpGuide/unsafeclass-useage/Program.cs:22-36 — before extracting anything, compare `CSharpGuide/unsafeclass-useage/Program.cs` and `docs/CSharpGuide/unsafeclass-useage/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) ConcurrencyInCSharpCookbook/13PracticalSkills/ParameterStatusInConcurrent.cs:13— ConcurrencyInCSharpCookbook/13PracticalSkills/ParameterStatusInConcurrent.cs:13-27 | docs/ConcurrencyInCSharpCookbook/13PracticalSkills/ParameterStatusInConcurrent.cs:13-27 — before extracting anything, compare `ConcurrencyInCSharpCookbook/13PracticalSkills/ParameterStatusInConcurrent.cs` and `docs/ConcurrencyInCSharpCookbook/13PracticalSkills/ParameterStatusInConcurrent.cs` as WHOLE FILES: 100% 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 `ConcurrencyInCSharpCookbook/13PracticalSkills/ParameterStatusInConcurrent.cs:13` 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) WHPerformanceDotNet/src/MomeryAllocation/DelegateOverhead.cs:7— WHPerformanceDotNet/src/MomeryAllocation/DelegateOverhead.cs:7-21 | docs/WHPerformanceDotNet/src/MomeryAllocation/DelegateOverhead.cs:7-21 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/DelegateOverhead.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/DelegateOverhead.cs` as WHOLE FILES: 100% 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 (15 lines × 2) ConcurrencyInCSharpCookbook/12Schedule/TaskScheduler.cs:9— ConcurrencyInCSharpCookbook/12Schedule/TaskScheduler.cs:9-23 | docs/ConcurrencyInCSharpCookbook/12Schedule/TaskScheduler.cs:9-23 — before extracting anything, compare `ConcurrencyInCSharpCookbook/12Schedule/TaskScheduler.cs` and `docs/ConcurrencyInCSharpCookbook/12Schedule/TaskScheduler.cs` as WHOLE FILES: 100% 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.
Sync-over-async blocking — 12 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 ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:66— `.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:73— `parent.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:79— `.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:88— `.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:34— `Completion.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs:21— `_initialized.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:66— `.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:73— `parent.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:79— `.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:88— `.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking docs/ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.cs:34— `Completion.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking docs/ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs:21— `_initialized.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Duplicated block (19 lines × 2) CSharpGuide/diagnostics/CollectionMetricDemo/MeterListenerProgram.cs:15— CSharpGuide/diagnostics/CollectionMetricDemo/MeterListenerProgram.cs:15-33 | docs/CSharpGuide/diagnostics/CollectionMetricDemo/MeterListenerProgram.cs:15-33 — before extracting anything, compare `CSharpGuide/diagnostics/CollectionMetricDemo/MeterListenerProgram.cs` and `docs/CSharpGuide/diagnostics/CollectionMetricDemo/MeterListenerProgram.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) CSharpGuide/performance/strings/Strings.cs:50— CSharpGuide/performance/strings/Strings.cs:50-68 | docs/CSharpGuide/performance/strings/Strings.cs:50-68 — before extracting anything, compare `CSharpGuide/performance/strings/Strings.cs` and `docs/CSharpGuide/performance/strings/Strings.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:54— WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:54-72 | docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:54-72 — before extracting anything, compare `WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` and `docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:67— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:67-85 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs:67-85 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/PatnerMatching.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) CSharpGuide/random/Extensions.cs:7— CSharpGuide/random/Extensions.cs:7-25 | docs/CSharpGuide/random/Extensions.cs:7-25 — before extracting anything, compare `CSharpGuide/random/Extensions.cs` and `docs/CSharpGuide/random/Extensions.cs` as WHOLE FILES: 100% 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. 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 (19 lines × 2) ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:33— ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:33-51 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs:33-51 — before extracting anything, compare `ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs` and `docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/Basic.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (19 lines × 2) ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:19— ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:19-37 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs:19-37 — before extracting anything, compare `ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs` and `docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/SendNotificationToSpecifyContext.cs` as WHOLE FILES: 100% 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. 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 (19 lines × 2) REDACTED:8— REDACTED:8-26 | docs/REDACTED:8-26 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% 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 (19 lines × 2) CSharpGuide/roslySdkDemo/HelloSyntaxTree/StringSyntaxExample.cs:17— CSharpGuide/roslySdkDemo/HelloSyntaxTree/StringSyntaxExample.cs:17-35 | docs/CSharpGuide/roslySdkDemo/HelloSyntaxTree/StringSyntaxExample.cs:17-35 — before extracting anything, compare `CSharpGuide/roslySdkDemo/HelloSyntaxTree/StringSyntaxExample.cs` and `docs/CSharpGuide/roslySdkDemo/HelloSyntaxTree/StringSyntaxExample.cs` as WHOLE FILES: 100% 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 (19 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/RefInExtensions.cs:14— CSharpInDepth/Chapter13_HighPerformancePassByReference/RefInExtensions.cs:14-32 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/RefInExtensions.cs:14-32 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/RefInExtensions.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/RefInExtensions.cs` as WHOLE FILES: 100% 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 `CSharpInDepth/Chapter13_HighPerformancePassByReference/RefInExtensions.cs:14` 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 × 2) WHPerformanceDotNet/src/MomeryAllocation/Vector.cs:13— WHPerformanceDotNet/src/MomeryAllocation/Vector.cs:13-31 | docs/WHPerformanceDotNet/src/MomeryAllocation/Vector.cs:13-31 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/Vector.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/Vector.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs:14— CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs:14-32 | docs/CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs:14-32 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs` and `docs/CSharpGuide/LanguageVersions/8.0/DefaultInterfaceMethod.cs` as WHOLE FILES: 100% 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. 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.
IC1 · Incompleteness & stubs· Empty method body · ×12
Empty method body — does nothing with its inputs CSharpGuide/LanguageVersions/4.0/Example.cs:39— `SomeMethod` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:71— `DisposeAndClear` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:75— `DisposeAndClear_DisallowNull` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:133— `MyAssert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs CSharpGuide/Net6WebDemo/Program.cs:7— `Main` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:11— `Main` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/CSharpGuide/LanguageVersions/4.0/Example.cs:39— `SomeMethod` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:71— `DisposeAndClear` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:75— `DisposeAndClear_DisallowNull` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:133— `MyAssert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/CSharpGuide/Net6WebDemo/Program.cs:7— `Main` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:11— `Main` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Duplicated block (6 lines × 2) FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:62— FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:62-67 | docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:62-67 — before extracting anything, compare `FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs` and `docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:18— WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:18-23 | docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:18-23 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.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.
Duplicated block (6 lines × 2) AsyncInCSharp/UtilitiesForTAP/Program.cs:11— AsyncInCSharp/UtilitiesForTAP/Program.cs:11-16 | docs/AsyncInCSharp/UtilitiesForTAP/Program.cs:11-16 — before extracting anything, compare `AsyncInCSharp/UtilitiesForTAP/Program.cs` and `docs/AsyncInCSharp/UtilitiesForTAP/Program.cs` as WHOLE FILES: 100% 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 (6 lines × 2) CSharpGuide/LanguageVersions/7.2/Spans.cs:9— CSharpGuide/LanguageVersions/7.2/Spans.cs:9-14 | docs/CSharpGuide/LanguageVersions/7.2/Spans.cs:9-14 — before extracting anything, compare `CSharpGuide/LanguageVersions/7.2/Spans.cs` and `docs/CSharpGuide/LanguageVersions/7.2/Spans.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs:44— CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs:44-49 | docs/CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs:44-49 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs` and `docs/CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:44— CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:44-49 | docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:44-49 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` and `docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 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 (6 lines × 2) CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:85— CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:85-90 | docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs:85-90 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` and `docs/CSharpGuide/LanguageVersions/8.0/SwitchExpression.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 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 (6 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:90— WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:90-95 | docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:90-95 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/Program.cs:124— WHPerformanceDotNet/src/MomeryAllocation/Program.cs:124-129 | docs/WHPerformanceDotNet/src/MomeryAllocation/Program.cs:124-129 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/Program.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:40— ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:40-45 | docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:40-45 — before extracting anything, compare `ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs` and `docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 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 (6 lines × 2) Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 6/Combinations.cs:137— Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 6/Combinations.cs:137-142 | Fabulous-Adventures-In-Data-Structures/sourcecode/chapter 6/Permutations.cs:137-144 — 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 (18 lines × 2) CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:46— CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:46-63 | docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:46-63 — before extracting anything, compare `CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs` and `docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) CSharpGuide/performance/strings/Strings.cs:129— CSharpGuide/performance/strings/Strings.cs:129-146 | docs/CSharpGuide/performance/strings/Strings.cs:129-146 — before extracting anything, compare `CSharpGuide/performance/strings/Strings.cs` and `docs/CSharpGuide/performance/strings/Strings.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/performance/strings/Strings.cs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:84— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:84-101 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:84-101 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) WHPerformanceDotNet/src/LockFreeWithInterlocked/Program.cs:19— WHPerformanceDotNet/src/LockFreeWithInterlocked/Program.cs:19-36 | docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/Program.cs:19-36 — before extracting anything, compare `WHPerformanceDotNet/src/LockFreeWithInterlocked/Program.cs` and `docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:48— WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:48-65 | docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:48-65 — before extracting anything, compare `WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs` and `docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 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 (18 lines × 2) ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:59— ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:59-76 | docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:59-76 — before extracting anything, compare `ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` and `docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 (18 lines × 2) AsyncInCSharp/AsyncPatternInNet/AsyncMethodContagious.cs:9— AsyncInCSharp/AsyncPatternInNet/AsyncMethodContagious.cs:9-26 | docs/AsyncInCSharp/AsyncPatternInNet/AsyncMethodContagious.cs:9-26 — before extracting anything, compare `AsyncInCSharp/AsyncPatternInNet/AsyncMethodContagious.cs` and `docs/AsyncInCSharp/AsyncPatternInNet/AsyncMethodContagious.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) ConcurrencyInCSharpCookbook/08Collections/AsyncQueue.cs:14— ConcurrencyInCSharpCookbook/08Collections/AsyncQueue.cs:14-31 | docs/ConcurrencyInCSharpCookbook/08Collections/AsyncQueue.cs:14-31 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/AsyncQueue.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/AsyncQueue.cs` as WHOLE FILES: 100% 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 (18 lines × 2) CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/Program.cs:13— CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/Program.cs:13-30 | docs/CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/Program.cs:13-30 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/Program.cs` and `docs/CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) CSharpGuide/LanguageVersions/8.0/demo/practice_demo.cs:27— CSharpGuide/LanguageVersions/8.0/demo/practice_demo.cs:27-44 | docs/CSharpGuide/LanguageVersions/8.0/demo/practice_demo.cs:27-44 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/demo/practice_demo.cs` and `docs/CSharpGuide/LanguageVersions/8.0/demo/practice_demo.cs` as WHOLE FILES: 100% 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 `CSharpGuide/LanguageVersions/8.0/demo/practice_demo.cs:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Unfinished stub — throws NotImplementedException CSharpGuide/LanguageVersions/7.0/IValueMark.cs:19— `Length` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CSharpGuide/LanguageVersions/8.0/Introducer.cs:66— `GetResultsAsync` 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 CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:40— `DoStuff` 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 CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:96— `OnVisitSyntaxNode` 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 WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:21— `SupportedDiagnostics` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/LanguageVersions/7.0/IValueMark.cs:19— `Length` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException docs/CSharpGuide/LanguageVersions/8.0/Introducer.cs:66— `GetResultsAsync` 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 docs/CSharpGuide/LanguageVersions/8.0/NullableRefferenceExample.cs:40— `DoStuff` 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 docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:96— `OnVisitSyntaxNode` 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 docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/StaticFieldAnalyzer.cs:21— `SupportedDiagnostics` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Sync-over-async (deadlock risk) through `.Result` CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:115— 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` docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:115— 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` WHPerformanceDotNet/src/AsyncProgram/Program.cs:58— 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` docs/WHPerformanceDotNet/src/AsyncProgram/Program.cs:58— 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` ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:48— 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` docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:48— 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` REDACTED:42— 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` REDACTED:54— 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` docs/REDACTED:42— 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` docs/REDACTED:54— 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.
async void method: Start CSharpGuide/threads/ThreadChannelDemo.cs:11— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Start docs/CSharpGuide/threads/ThreadChannelDemo.cs:11— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Execute ConcurrencyInCSharpCookbook/ThreadBasic/MyAsyncCommand.cs:9— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Execute docs/ConcurrencyInCSharpCookbook/ThreadBasic/MyAsyncCommand.cs:9— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: DumpWebPageAsync REDACTED:8— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AddFavicon REDACTED:13— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AlexsMethod AsyncInCSharp/ExceptionInAsync/Program.cs:23— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: DumpWebPageAsync docs/REDACTED:8— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AddFavicon docs/REDACTED:13— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AlexsMethod docs/AsyncInCSharp/ExceptionInAsync/Program.cs:23— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
Sync-over-async (deadlock risk) ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:66— 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) ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:73— 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) ConcurrencyInCSharpCookbook/03ParallerBasic/Program.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) ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:88— 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) ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.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) docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:66— 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) docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:73— 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) docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.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) docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:88— 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) docs/ConcurrencyInCSharpCookbook/07Interoperate/UseRxObservableAndDataFlow.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.
No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
No authorization CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:23— `MapGet("/weatherforecast")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:23— `MapGet("/weatherforecast")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization CSharpGuide/performance/strings/Program.cs:14— `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization CSharpGuide/performance/strings/Program.cs:14— `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization docs/CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:23— `MapGet("/weatherforecast")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization docs/CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:23— `MapGet("/weatherforecast")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization docs/CSharpGuide/performance/strings/Program.cs:14— `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization docs/CSharpGuide/performance/strings/Program.cs:14— `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
Duplicated block (24 lines × 2) CSharpGuide/serializes/JsonDocumentOps.cs:45— CSharpGuide/serializes/JsonDocumentOps.cs:45-68 | docs/CSharpGuide/serializes/JsonDocumentOps.cs:45-68 — before extracting anything, compare `CSharpGuide/serializes/JsonDocumentOps.cs` and `docs/CSharpGuide/serializes/JsonDocumentOps.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:60— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:60-83 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:60-83 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:64— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:64-87 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:64-87 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) CSharpGuide/net8-guide/Randoms/ButtonEnum.cs:3— CSharpGuide/net8-guide/Randoms/ButtonEnum.cs:3-26 | docs/CSharpGuide/net8-guide/Randoms/ButtonEnum.cs:3-26 — before extracting anything, compare `CSharpGuide/net8-guide/Randoms/ButtonEnum.cs` and `docs/CSharpGuide/net8-guide/Randoms/ButtonEnum.cs` as WHOLE FILES: 100% 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 `CSharpGuide/net8-guide/Randoms/ButtonEnum.cs:3` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) CSharpGuide/Net6WebDemo/DemoMiddleware.cs:18— CSharpGuide/Net6WebDemo/DemoMiddleware.cs:18-41 | docs/CSharpGuide/Net6WebDemo/DemoMiddleware.cs:18-41 — before extracting anything, compare `CSharpGuide/Net6WebDemo/DemoMiddleware.cs` and `docs/CSharpGuide/Net6WebDemo/DemoMiddleware.cs` as WHOLE FILES: 100% 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 (24 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/EnumerableExt.cs:8— FunctionalCSharp/src/MarsonShine.Functional/EnumerableExt.cs:8-31 | docs/FunctionalCSharp/src/MarsonShine.Functional/EnumerableExt.cs:8-31 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/EnumerableExt.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/EnumerableExt.cs` as WHOLE FILES: 100% 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 (24 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/TaskExt.cs:6— FunctionalCSharp/src/MarsonShine.Functional/TaskExt.cs:6-29 | docs/FunctionalCSharp/src/MarsonShine.Functional/TaskExt.cs:6-29 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/TaskExt.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/TaskExt.cs` as WHOLE FILES: 100% 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 `FunctionalCSharp/src/MarsonShine.Functional/TaskExt.cs:6` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (24 lines × 2) WHPerformanceDotNet/src/EtlDemo/BaseListener.cs:32— WHPerformanceDotNet/src/EtlDemo/BaseListener.cs:32-55 | docs/WHPerformanceDotNet/src/EtlDemo/BaseListener.cs:32-55 — before extracting anything, compare `WHPerformanceDotNet/src/EtlDemo/BaseListener.cs` and `docs/WHPerformanceDotNet/src/EtlDemo/BaseListener.cs` as WHOLE FILES: 100% 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 (24 lines × 2) CSharpGuide/simd-vector-demo/Extensions.cs:35— CSharpGuide/simd-vector-demo/Extensions.cs:35-58 | docs/CSharpGuide/simd-vector-demo/Extensions.cs:35-58 — before extracting anything, compare `CSharpGuide/simd-vector-demo/Extensions.cs` and `docs/CSharpGuide/simd-vector-demo/Extensions.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
TodoComment CSharpGuide/performance/SerializationPerformance.cs:13— // TODO — 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 docs/CSharpGuide/performance/SerializationPerformance.cs:13— // TODO — 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 WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs:36— // TODO: Replace the following code with your own analysis, generating a CodeAction for each fix to suggest — 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 docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs:36— // TODO: Replace the following code with your own analysis, generating a CodeAction for each fix to suggest — 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 WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:34— // TODO: Consider registering other actions that act on syntax instead of or in addition to symbols
TodoComment docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:34— // TODO: Consider registering other actions that act on syntax instead of or in addition to symbols
TodoComment WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:42— // TODO: Replace the following code with your own analysis, generating Diagnostic objects for any issues you find — 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 docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:42— // TODO: Replace the following code with your own analysis, generating Diagnostic objects for any issues you find — 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 (21 lines × 2) CSharpGuide/LanguageVersions/10.0/Structs/Program.cs:13— CSharpGuide/LanguageVersions/10.0/Structs/Program.cs:13-33 | docs/CSharpGuide/LanguageVersions/10.0/Structs/Program.cs:13-33 — before extracting anything, compare `CSharpGuide/LanguageVersions/10.0/Structs/Program.cs` and `docs/CSharpGuide/LanguageVersions/10.0/Structs/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:96— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:96-116 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:96-116 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:105— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:105-125 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:105-125 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HelloSourceGenerator.cs:12— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HelloSourceGenerator.cs:12-32 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HelloSourceGenerator.cs:12-32 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HelloSourceGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HelloSourceGenerator.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:66— WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:66-86 | docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs:66-86 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/HybirdCache.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) CSharpGuide/random/Extensions.cs:28— CSharpGuide/random/Extensions.cs:28-48 | docs/CSharpGuide/random/Extensions.cs:28-48 — before extracting anything, compare `CSharpGuide/random/Extensions.cs` and `docs/CSharpGuide/random/Extensions.cs` as WHOLE FILES: 100% 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. 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 (21 lines × 2) WHPerformanceDotNet/src/FullGCNotification/Program.cs:7— WHPerformanceDotNet/src/FullGCNotification/Program.cs:7-27 | docs/WHPerformanceDotNet/src/FullGCNotification/Program.cs:7-27 — before extracting anything, compare `WHPerformanceDotNet/src/FullGCNotification/Program.cs` and `docs/WHPerformanceDotNet/src/FullGCNotification/Program.cs` as WHOLE FILES: 100% 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. 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 (21 lines × 2) ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:76— ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:76-96 | docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:76-96 — before extracting anything, compare `ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs` and `docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 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 (17 lines × 2) CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs:9— CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs:9-25 | docs/CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs:9-25 — before extracting anything, compare `CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs` and `docs/CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) CSharpGuide/LanguageVersions/7.0/Discards.cs:26— CSharpGuide/LanguageVersions/7.0/Discards.cs:26-42 | docs/CSharpGuide/LanguageVersions/7.0/Discards.cs:26-42 — before extracting anything, compare `CSharpGuide/LanguageVersions/7.0/Discards.cs` and `docs/CSharpGuide/LanguageVersions/7.0/Discards.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs:34— WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs:34-50 | docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs:34-50 — before extracting anything, compare `WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs` and `docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer.CodeFixes/SampleCodeAnalyzerCodeFixProvider.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) AsyncInCSharp/UtilitiesForTAP/CancellationAsyncMethod.cs:11— AsyncInCSharp/UtilitiesForTAP/CancellationAsyncMethod.cs:11-27 | docs/AsyncInCSharp/UtilitiesForTAP/CancellationAsyncMethod.cs:11-27 — before extracting anything, compare `AsyncInCSharp/UtilitiesForTAP/CancellationAsyncMethod.cs` and `docs/AsyncInCSharp/UtilitiesForTAP/CancellationAsyncMethod.cs` as WHOLE FILES: 100% 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 (17 lines × 2) AsyncInCSharp/WitchThreadRunCode/AnalyzeAwaiting.cs:11— AsyncInCSharp/WitchThreadRunCode/AnalyzeAwaiting.cs:11-27 | docs/AsyncInCSharp/WitchThreadRunCode/AnalyzeAwaiting.cs:11-27 — before extracting anything, compare `AsyncInCSharp/WitchThreadRunCode/AnalyzeAwaiting.cs` and `docs/AsyncInCSharp/WitchThreadRunCode/AnalyzeAwaiting.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) ConcurrencyInCSharpCookbook/13PracticalSkills/RxLazyGetValue.cs:13— ConcurrencyInCSharpCookbook/13PracticalSkills/RxLazyGetValue.cs:13-29 | docs/ConcurrencyInCSharpCookbook/13PracticalSkills/RxLazyGetValue.cs:13-29 — before extracting anything, compare `ConcurrencyInCSharpCookbook/13PracticalSkills/RxLazyGetValue.cs` and `docs/ConcurrencyInCSharpCookbook/13PracticalSkills/RxLazyGetValue.cs` as WHOLE FILES: 100% 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 (17 lines × 2) DesignPattern/DesignPatternCore/Facade/Found.cs:8— DesignPattern/DesignPatternCore/Facade/Found.cs:8-24 | docs/DesignPattern/DesignPatternCore/Facade/Found.cs:8-24 — before extracting anything, compare `DesignPattern/DesignPatternCore/Facade/Found.cs` and `docs/DesignPattern/DesignPatternCore/Facade/Found.cs` as WHOLE FILES: 100% 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 (17 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:32— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:32-48 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:32-48 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
End-of-life runtime: .NET net5.0 CSharpInDepth/Chapter14_ConciseCode/Chapter14_ConciseCode.csproj:5— CSharpInDepth/Chapter14_ConciseCode/Chapter14_ConciseCode.csproj declares .NET net5.0 as this project's target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net6.0 CSharpGuide/Net6WebDemo/Net6WebDemo.csproj:4— CSharpGuide/Net6WebDemo/Net6WebDemo.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 CSharpGuide/roslySdkDemo/SyntaxWalker/SyntaxWalker.csproj:5— CSharpGuide/roslySdkDemo/SyntaxWalker/SyntaxWalker.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET netcoreapp2.0 CSharpInDepth/Chapter_3_Generic/Chapter_3_Generic.csproj:5— CSharpInDepth/Chapter_3_Generic/Chapter_3_Generic.csproj declares .NET netcoreapp2.0 as this project's target framework, and .NET Core 2.0, support ended 2018-10-01. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2018-10-01 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET netcoreapp2.1 ConcurrencyInCSharpCookbook/ThreadBasic/ThreadBasic.csproj:4— ConcurrencyInCSharpCookbook/ThreadBasic/ThreadBasic.csproj declares .NET netcoreapp2.1 as this project's target framework, and .NET Core 2.1, support ended 2021-08-21. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2021-08-21 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET netcoreapp2.2 AsyncInCSharp/PerFormanceComparison/PerFormanceComparison.csproj:5— AsyncInCSharp/PerFormanceComparison/PerFormanceComparison.csproj declares .NET netcoreapp2.2 as this project's target framework, and .NET Core 2.2, support ended 2019-12-23. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2019-12-23 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET netcoreapp3.0 DesignPattern/DesignPatternCore/DesignPatternCore.csproj:5— DesignPattern/DesignPatternCore/DesignPatternCore.csproj declares .NET netcoreapp3.0 as this project's target framework, and .NET Core 3.0, support ended 2020-03-03. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2020-03-03 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET netcoreapp3.1 WHPerformanceDotNet/src/TPLDataflow/TPLDataflow.csproj:5— WHPerformanceDotNet/src/TPLDataflow/TPLDataflow.csproj declares .NET netcoreapp3.1 as this project's target framework, and .NET Core 3.1 LTS, support ended 2022-12-13. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-12-13 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Duplicated block (26 lines × 2) CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:86— CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:86-111 | docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:86-111 — before extracting anything, compare `CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs` and `docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26 lines × 2) CSharpGuide/LanguageVersions/9.0/PatternMatcheDemo.cs:17— CSharpGuide/LanguageVersions/9.0/PatternMatcheDemo.cs:17-42 | docs/CSharpGuide/LanguageVersions/9.0/PatternMatcheDemo.cs:17-42 — before extracting anything, compare `CSharpGuide/LanguageVersions/9.0/PatternMatcheDemo.cs` and `docs/CSharpGuide/LanguageVersions/9.0/PatternMatcheDemo.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:104— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:104-129 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:104-129 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:287— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:287-312 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:287-312 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26 lines × 2) CSharpGuide/random/StandardContinuousUniform.cs:13— CSharpGuide/random/StandardContinuousUniform.cs:13-38 | docs/CSharpGuide/random/StandardContinuousUniform.cs:13-38 — before extracting anything, compare `CSharpGuide/random/StandardContinuousUniform.cs` and `docs/CSharpGuide/random/StandardContinuousUniform.cs` as WHOLE FILES: 100% 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 `CSharpGuide/random/StandardContinuousUniform.cs:13` 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 (26 lines × 2) ConcurrencyInCSharpCookbook/09Cancellation/Program.cs:9— ConcurrencyInCSharpCookbook/09Cancellation/Program.cs:9-34 | docs/ConcurrencyInCSharpCookbook/09Cancellation/Program.cs:9-34 — before extracting anything, compare `ConcurrencyInCSharpCookbook/09Cancellation/Program.cs` and `docs/ConcurrencyInCSharpCookbook/09Cancellation/Program.cs` as WHOLE FILES: 100% 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 (26 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/Try.cs:13— FunctionalCSharp/src/MarsonShine.Functional/Try.cs:13-38 | docs/FunctionalCSharp/src/MarsonShine.Functional/Try.cs:13-38 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/Try.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/Try.cs` as WHOLE FILES: 100% 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 `FunctionalCSharp/src/MarsonShine.Functional/Try.cs:13` 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 (25 lines × 2) CSharpGuide/performance/strings/Strings.cs:154— CSharpGuide/performance/strings/Strings.cs:154-178 | docs/CSharpGuide/performance/strings/Strings.cs:154-178 — before extracting anything, compare `CSharpGuide/performance/strings/Strings.cs` and `docs/CSharpGuide/performance/strings/Strings.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/performance/strings/Strings.cs:154` 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 (25 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:155— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:155-179 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:155-179 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (25 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:41— WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:41-65 | docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs:41-65 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/ObjectCache/SecondaryIndex.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (25 lines × 2) CSharpInDepth/Chapter14_ConciseCode/Program.cs:9— CSharpInDepth/Chapter14_ConciseCode/Program.cs:9-33 | docs/CSharpInDepth/Chapter14_ConciseCode/Program.cs:9-33 — before extracting anything, compare `CSharpInDepth/Chapter14_ConciseCode/Program.cs` and `docs/CSharpInDepth/Chapter14_ConciseCode/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (25 lines × 2) CSharpGuide/generics/GenericInheritance.cs:18— CSharpGuide/generics/GenericInheritance.cs:18-42 | docs/CSharpGuide/generics/GenericInheritance.cs:18-42 — before extracting anything, compare `CSharpGuide/generics/GenericInheritance.cs` and `docs/CSharpGuide/generics/GenericInheritance.cs` as WHOLE FILES: 100% 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 `CSharpGuide/generics/GenericInheritance.cs:18` 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 (25 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/F.cs:8— FunctionalCSharp/src/MarsonShine.Functional/F.cs:8-32 | docs/FunctionalCSharp/src/MarsonShine.Functional/F.cs:8-32 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/F.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/F.cs` as WHOLE FILES: 100% 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 (25 lines × 2) WHPerformanceDotNet/src/EtlDemo/Events.cs:38— WHPerformanceDotNet/src/EtlDemo/Events.cs:38-62 | docs/WHPerformanceDotNet/src/EtlDemo/Events.cs:38-62 — before extracting anything, compare `WHPerformanceDotNet/src/EtlDemo/Events.cs` and `docs/WHPerformanceDotNet/src/EtlDemo/Events.cs` as WHOLE FILES: 100% 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 (20 lines × 2) CSharpGuide/diagnostics/MetricDemo/Program2.cs:19— CSharpGuide/diagnostics/MetricDemo/Program2.cs:19-38 | docs/CSharpGuide/diagnostics/MetricDemo/Program2.cs:19-38 — before extracting anything, compare `CSharpGuide/diagnostics/MetricDemo/Program2.cs` and `docs/CSharpGuide/diagnostics/MetricDemo/Program2.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs:14— CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs:14-33 | docs/CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs:14-33 — before extracting anything, compare `CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs` and `docs/CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22— CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22-41 | docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs:22-41 — before extracting anything, compare `CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs` and `docs/CSharpGuide/LanguageVersions/6.0/TryCatchWhenExpress.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) ConcurrencyInCSharpCookbook/08Collections/ImmutableLists.cs:15— ConcurrencyInCSharpCookbook/08Collections/ImmutableLists.cs:15-34 | docs/ConcurrencyInCSharpCookbook/08Collections/ImmutableLists.cs:15-34 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/ImmutableLists.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/ImmutableLists.cs` as WHOLE FILES: 100% 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 (20 lines × 2) ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:18— ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:18-37 | docs/ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:18-37 — before extracting anything, compare `ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs` and `docs/ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs` as WHOLE FILES: 100% 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. 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 (20 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/AvoidFinalize.cs:22— WHPerformanceDotNet/src/MomeryAllocation/AvoidFinalize.cs:22-41 | docs/WHPerformanceDotNet/src/MomeryAllocation/AvoidFinalize.cs:22-41 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/AvoidFinalize.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/AvoidFinalize.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:66— WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:66-85 | docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:66-85 — before extracting anything, compare `WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs` and `docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 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 (23 lines × 2) CSharpGuide/LanguageVersions/10.0/Main.cs:15— CSharpGuide/LanguageVersions/10.0/Main.cs:15-37 | docs/CSharpGuide/LanguageVersions/10.0/Main.cs:15-37 — before extracting anything, compare `CSharpGuide/LanguageVersions/10.0/Main.cs` and `docs/CSharpGuide/LanguageVersions/10.0/Main.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs:18— CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs:18-40 | docs/CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs:18-40 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs` and `docs/CSharpGuide/LanguageVersions/8.0/AsyncStream.PartII.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) CSharpGuide/LanguageVersions/8.0/Ranges.cs:45— CSharpGuide/LanguageVersions/8.0/Ranges.cs:45-67 | docs/CSharpGuide/LanguageVersions/8.0/Ranges.cs:45-67 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/Ranges.cs` and `docs/CSharpGuide/LanguageVersions/8.0/Ranges.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:129— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:129-151 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:129-151 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) CSharpGuide/LanguageVersions/11.0/csharp11/Program.cs:21— CSharpGuide/LanguageVersions/11.0/csharp11/Program.cs:21-43 | docs/CSharpGuide/LanguageVersions/11.0/csharp11/Program.cs:21-43 — before extracting anything, compare `CSharpGuide/LanguageVersions/11.0/csharp11/Program.cs` and `docs/CSharpGuide/LanguageVersions/11.0/csharp11/Program.cs` as WHOLE FILES: 100% 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 `CSharpGuide/LanguageVersions/11.0/csharp11/Program.cs:21` 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 (23 lines × 2) ConcurrencyInCSharpCookbook/07Interoperate/UseAsyncModifierEncapsulateObservable.cs:12— ConcurrencyInCSharpCookbook/07Interoperate/UseAsyncModifierEncapsulateObservable.cs:12-34 | docs/ConcurrencyInCSharpCookbook/07Interoperate/UseAsyncModifierEncapsulateObservable.cs:12-34 — before extracting anything, compare `ConcurrencyInCSharpCookbook/07Interoperate/UseAsyncModifierEncapsulateObservable.cs` and `docs/ConcurrencyInCSharpCookbook/07Interoperate/UseAsyncModifierEncapsulateObservable.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Sync-over-async (deadlock risk) through `Task.WaitAll` WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:64— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
Sync-over-async (deadlock risk) through `Task.WaitAll` WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:84— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
Sync-over-async (deadlock risk) through `Task.WaitAll` docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:64— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
Sync-over-async (deadlock risk) through `Task.WaitAll` docs/WHPerformanceDotNet/src/HighPerformanceIOProgram/Program.cs:84— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
Sync-over-async (deadlock risk) through `Task.WaitAll` ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:95— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
Sync-over-async (deadlock risk) through `Task.WaitAll` docs/ConcurrencyInCSharpCookbook/03ParallerBasic/Program.cs:95— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) CSharpGuide/performance/strings/Strings.cs:128— CSharpGuide/performance/strings/Strings.cs:128-150 | CSharpGuide/performance/strings/Strings.cs:153-182 | docs/CSharpGuide/performance/strings/Strings.cs:128-150 | docs/CSharpGuide/performance/strings/Strings.cs:153-182 — 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) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:59— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:59-83 | CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:63-87 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:59-83 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:63-87 — 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) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:103— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:103-129 | CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:120-177 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:103-129 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:120-177 — 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) ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:12— ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:12-23 | ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:25-36 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:12-23 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:25-36 — 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 (28 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/SourceGenerationHelper.cs:20— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/SourceGenerationHelper.cs:20-47 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/SourceGenerationHelper.cs:20-47 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/SourceGenerationHelper.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/SourceGenerationHelper.cs` as WHOLE FILES: 100% 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 `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/SourceGenerationHelper.cs:20` 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) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/SourceGenerationHelper.cs:21— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/SourceGenerationHelper.cs:21-48 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/SourceGenerationHelper.cs:21-48 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/SourceGenerationHelper.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/SourceGenerationHelper.cs` as WHOLE FILES: 100% 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 `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/SourceGenerationHelper.cs:21` 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) AsyncInCSharp/ExceptionInAsync/Program.cs:6— AsyncInCSharp/ExceptionInAsync/Program.cs:6-33 | docs/AsyncInCSharp/ExceptionInAsync/Program.cs:6-33 — before extracting anything, compare `AsyncInCSharp/ExceptionInAsync/Program.cs` and `docs/AsyncInCSharp/ExceptionInAsync/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (28 lines × 2) CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/UserClass.cs:26— CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/UserClass.cs:26-53 | docs/CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/UserClass.cs:26-53 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/UserClass.cs` and `docs/CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/UserClass.cs` as WHOLE FILES: 100% 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 `CSharpGuide/SourceGeneratorDemo/SourceGeneratorGuide/UserClass.cs:26` 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 (29 lines × 2) ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:9— ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:9-37 | docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs:9-37 — before extracting anything, compare `ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` and `docs/ConcurrencyInCSharpCookbook/04DataFlow/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 (29 lines × 2) CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/ConditionalEventCounterSource.cs:12— CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/ConditionalEventCounterSource.cs:12-40 | docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/ConditionalEventCounterSource.cs:12-40 — before extracting anything, compare `CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/ConditionalEventCounterSource.cs` and `docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventCounters/ConditionalEventCounterSource.cs` as WHOLE FILES: 100% 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 (29 lines × 2) CSharpGuide/exceptionhandle/Program.cs:20— CSharpGuide/exceptionhandle/Program.cs:20-48 | docs/CSharpGuide/exceptionhandle/Program.cs:20-48 — before extracting anything, compare `CSharpGuide/exceptionhandle/Program.cs` and `docs/CSharpGuide/exceptionhandle/Program.cs` as WHOLE FILES: 100% 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 (29 lines × 2) DesignPattern/DesignPatternCore/Property/Resume.cs:10— DesignPattern/DesignPatternCore/Property/Resume.cs:10-38 | docs/DesignPattern/DesignPatternCore/Property/Resume.cs:10-38 — before extracting anything, compare `DesignPattern/DesignPatternCore/Property/Resume.cs` and `docs/DesignPattern/DesignPatternCore/Property/Resume.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (27 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:183— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:183-209 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:183-209 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (27 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/MyGenerator.cs:18— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/MyGenerator.cs:18-44 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/MyGenerator.cs:18-44 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/MyGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/MyGenerator.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (27 lines × 2) WHPerformanceDotNet/src/GenericOptimization/DynamicModuleLambdaCompiler.cs:13— WHPerformanceDotNet/src/GenericOptimization/DynamicModuleLambdaCompiler.cs:13-39 | docs/WHPerformanceDotNet/src/GenericOptimization/DynamicModuleLambdaCompiler.cs:13-39 — before extracting anything, compare `WHPerformanceDotNet/src/GenericOptimization/DynamicModuleLambdaCompiler.cs` and `docs/WHPerformanceDotNet/src/GenericOptimization/DynamicModuleLambdaCompiler.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (27 lines × 2) WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:27— WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:27-53 | docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs:27-53 — before extracting anything, compare `WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs` and `docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzerAnalyzer.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
X2 · Cancellation propagation· Async local function without CancellationToken · ×4
Async local function without CancellationToken: Query CSharpGuide/diagnostics/EventSourceDemo/Program.cs:14— 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: ProcessWorkItem2 CSharpGuide/diagnostics/EventSourceDemo/Program.cs:23— 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: Query docs/CSharpGuide/diagnostics/EventSourceDemo/Program.cs:14— 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: ProcessWorkItem2 docs/CSharpGuide/diagnostics/EventSourceDemo/Program.cs:23— Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Swallowed exception (caught, then discarded) AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:31— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) AsyncInCSharp/ExceptionInAsync/MultipleException.cs:11— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) docs/AsyncInCSharp/AwaitWhatActuallyToDo/WhereAwaitCanNotBeUsed.cs:31— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) docs/AsyncInCSharp/ExceptionInAsync/MultipleException.cs:11— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Duplicated block (51 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:37— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:37-87 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs:37-87 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/SerializingGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (51 lines × 2) CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/Program.cs:10— CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/Program.cs:10-60 | docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/Program.cs:10-60 — before extracting anything, compare `CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/Program.cs` and `docs/CSharpInDepth/Chapter12_Deconstruction_PatnerMatching/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (51 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:17— CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:17-67 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs:17-67 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 71 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 (46 lines × 2) CSharpGuide/generics/NoneGenericCallGeneric.cs:20— CSharpGuide/generics/NoneGenericCallGeneric.cs:20-65 | docs/CSharpGuide/generics/NoneGenericCallGeneric.cs:20-65 — before extracting anything, compare `CSharpGuide/generics/NoneGenericCallGeneric.cs` and `docs/CSharpGuide/generics/NoneGenericCallGeneric.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (46 lines × 2) WHPerformanceDotNet/src/AsyncProgram/Program.cs:10— WHPerformanceDotNet/src/AsyncProgram/Program.cs:10-55 | docs/WHPerformanceDotNet/src/AsyncProgram/Program.cs:10-55 — before extracting anything, compare `WHPerformanceDotNet/src/AsyncProgram/Program.cs` and `docs/WHPerformanceDotNet/src/AsyncProgram/Program.cs` as WHOLE FILES: 100% 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. 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 (46 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs:16— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs:16-61 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs:16-61 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (30 lines × 2) CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:135— CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:135-164 | docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:135-164 — before extracting anything, compare `CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` and `docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (30 lines × 2) CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:13— CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:13-42 | docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:13-42 — before extracting anything, compare `CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` and `docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) CSharpGuide/net8-guide/Program.cs:50— CSharpGuide/net8-guide/Program.cs:50-79 | docs/CSharpGuide/net8-guide/Program.cs:50-79 — before extracting anything, compare `CSharpGuide/net8-guide/Program.cs` and `docs/CSharpGuide/net8-guide/Program.cs` as WHOLE FILES: 100% 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 (22 lines × 2) CSharpGuide/LanguageVersions/4.0/Example.cs:6— CSharpGuide/LanguageVersions/4.0/Example.cs:6-27 | docs/CSharpGuide/LanguageVersions/4.0/Example.cs:6-27 — before extracting anything, compare `CSharpGuide/LanguageVersions/4.0/Example.cs` and `docs/CSharpGuide/LanguageVersions/4.0/Example.cs` as WHOLE FILES: 100% 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 (22 lines × 2) CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReadOnly.cs:11— CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReadOnly.cs:11-32 | docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReadOnly.cs:11-32 — before extracting anything, compare `CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReadOnly.cs` and `docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReadOnly.cs` as WHOLE FILES: 100% 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 `CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReadOnly.cs:11` 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 (22 lines × 2) WHPerformanceDotNet/src/LockFreeWithInterlocked/LockFreeStack.cs:11— WHPerformanceDotNet/src/LockFreeWithInterlocked/LockFreeStack.cs:11-32 | docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/LockFreeStack.cs:11-32 — before extracting anything, compare `WHPerformanceDotNet/src/LockFreeWithInterlocked/LockFreeStack.cs` and `docs/WHPerformanceDotNet/src/LockFreeWithInterlocked/LockFreeStack.cs` as WHOLE FILES: 100% 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.
HackComment FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:12— // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment docs/FunctionalCSharp/src/Marsonshine.Functional.Data/Bst.cs:12— // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
VectorOperator.Contains (cognitive 32) CSharpGuide/simd-vector-demo/VectorOperator.cs:58— VectorOperator.Contains has cognitive complexity 32 (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. Note what this body is, though: it works in explicit hardware vector and instruction-set types. A kernel divided across a call boundary passes its vectors between the parts and depends on the runtime putting them back together, so the division can cost more than the complexity it removes. The measurement stands — a hot path is not a licence to be unreadable — but the move that pays here is to lift the COLD parts out first (argument validation, fallback and error paths, one-off setup) and leave the kernel whole. Where the kernel itself has to be divided, ask for the extracted parts to be inlined as well, and measure the result rather than assuming the division is free.
VectorOperator.Contains (cognitive 32) docs/CSharpGuide/simd-vector-demo/VectorOperator.cs:58— VectorOperator.Contains has cognitive complexity 32 (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. Note what this body is, though: it works in explicit hardware vector and instruction-set types. A kernel divided across a call boundary passes its vectors between the parts and depends on the runtime putting them back together, so the division can cost more than the complexity it removes. The measurement stands — a hot path is not a licence to be unreadable — but the move that pays here is to lift the COLD parts out first (argument validation, fallback and error paths, one-off setup) and leave the kernel whole. Where the kernel itself has to be divided, ask for the extracted parts to be inlined as well, and measure the result rather than assuming the division is free.
EnumToGenerator.GetTypesToGenerate (cognitive 23) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:119— EnumToGenerator.GetTypesToGenerate has cognitive complexity 23 (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.
EnumToGenerator.GetTypesToGenerate (cognitive 23) docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:119— EnumToGenerator.GetTypesToGenerate has cognitive complexity 23 (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.
Duplicated block (57 lines × 2) CSharpGuide/memory-mapped-files/Program.cs:27— CSharpGuide/memory-mapped-files/Program.cs:27-83 | docs/CSharpGuide/memory-mapped-files/Program.cs:27-83 — before extracting anything, compare `CSharpGuide/memory-mapped-files/Program.cs` and `docs/CSharpGuide/memory-mapped-files/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (57 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:121— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:121-177 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:121-177 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (47 lines × 2) REDACTED:9— REDACTED:9-55 | docs/REDACTED:9-55 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% 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 (47 lines × 2) CSharpInDepth/Chapter_3_Generic/AdvancedGeneric.cs:20— CSharpInDepth/Chapter_3_Generic/AdvancedGeneric.cs:20-66 | docs/CSharpInDepth/Chapter_3_Generic/AdvancedGeneric.cs:20-66 — before extracting anything, compare `CSharpInDepth/Chapter_3_Generic/AdvancedGeneric.cs` and `docs/CSharpInDepth/Chapter_3_Generic/AdvancedGeneric.cs` as WHOLE FILES: 100% 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 `CSharpInDepth/Chapter_3_Generic/AdvancedGeneric.cs:20` 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 (44 lines × 2) CSharpGuide/roslySdkDemo/HelloSyntaxTree/Program.cs:28— CSharpGuide/roslySdkDemo/HelloSyntaxTree/Program.cs:28-71 | docs/CSharpGuide/roslySdkDemo/HelloSyntaxTree/Program.cs:28-71 — before extracting anything, compare `CSharpGuide/roslySdkDemo/HelloSyntaxTree/Program.cs` and `docs/CSharpGuide/roslySdkDemo/HelloSyntaxTree/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (44 lines × 2) CSharpGuide/performance/ArrayChunkOfStruct.cs:18— CSharpGuide/performance/ArrayChunkOfStruct.cs:18-61 | docs/CSharpGuide/performance/ArrayChunkOfStruct.cs:18-61 — before extracting anything, compare `CSharpGuide/performance/ArrayChunkOfStruct.cs` and `docs/CSharpGuide/performance/ArrayChunkOfStruct.cs` as WHOLE FILES: 100% 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 (43 lines × 2) CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:20— CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:20-62 | docs/CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs:20-62 — before extracting anything, compare `CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs` and `docs/CSharpGuide/asynclocal/asynclocal/MemoryLeaskDemo.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (43 lines × 2) CSharpInDepth/Chapter_3_Generic/Program.cs:11— CSharpInDepth/Chapter_3_Generic/Program.cs:11-53 | docs/CSharpInDepth/Chapter_3_Generic/Program.cs:11-53 — before extracting anything, compare `CSharpInDepth/Chapter_3_Generic/Program.cs` and `docs/CSharpInDepth/Chapter_3_Generic/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (38 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:316— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:316-353 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs:316-353 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/HashCode.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (38 lines × 2) CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:94— CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:94-131 | docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs:94-131 — before extracting anything, compare `CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` and `docs/CSharpGuide/valuetask/FileReadingPooledValueTaskSource.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36 lines × 2) CSharpGuide/async/StockPrices.cs:53— CSharpGuide/async/StockPrices.cs:53-88 | docs/CSharpGuide/async/StockPrices.cs:53-88 — before extracting anything, compare `CSharpGuide/async/StockPrices.cs` and `docs/CSharpGuide/async/StockPrices.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36 lines × 2) DesignPattern/DesignPatternCore/ServiceLocator/ServiceLocator.cs:11— DesignPattern/DesignPatternCore/ServiceLocator/ServiceLocator.cs:11-46 | docs/DesignPattern/DesignPatternCore/ServiceLocator/ServiceLocator.cs:11-46 — before extracting anything, compare `DesignPattern/DesignPatternCore/ServiceLocator/ServiceLocator.cs` and `docs/DesignPattern/DesignPatternCore/ServiceLocator/ServiceLocator.cs` as WHOLE FILES: 100% 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 `DesignPattern/DesignPatternCore/ServiceLocator/ServiceLocator.cs:11` 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 (35 lines × 2) CSharpGuide/serializes/JsonDocumentOps.cs:72— CSharpGuide/serializes/JsonDocumentOps.cs:72-106 | docs/CSharpGuide/serializes/JsonDocumentOps.cs:72-106 — before extracting anything, compare `CSharpGuide/serializes/JsonDocumentOps.cs` and `docs/CSharpGuide/serializes/JsonDocumentOps.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (35 lines × 2) ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:14— ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:14-48 | docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:14-48 — before extracting anything, compare `ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs` and `docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs` as WHOLE FILES: 100% 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 `ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.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 (33 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:22— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:22-54 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:22-54 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (33 lines × 2) ConcurrencyInCSharpCookbook/09Cancellation/CancellationAsyncCode.cs:13— ConcurrencyInCSharpCookbook/09Cancellation/CancellationAsyncCode.cs:13-45 | docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationAsyncCode.cs:13-45 — before extracting anything, compare `ConcurrencyInCSharpCookbook/09Cancellation/CancellationAsyncCode.cs` and `docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationAsyncCode.cs` as WHOLE FILES: 100% 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 (31 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/AugmentingGenerator.cs:19— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/AugmentingGenerator.cs:19-49 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/AugmentingGenerator.cs:19-49 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/AugmentingGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/AugmentingGenerator.cs` as WHOLE FILES: 100% 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 (31 lines × 2) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:20— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:20-50 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:20-50 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (34 lines × 2) CSharpGuide/LanguageVersions/8.0/Introducer.cs:36— CSharpGuide/LanguageVersions/8.0/Introducer.cs:36-69 | docs/CSharpGuide/LanguageVersions/8.0/Introducer.cs:36-69 — before extracting anything, compare `CSharpGuide/LanguageVersions/8.0/Introducer.cs` and `docs/CSharpGuide/LanguageVersions/8.0/Introducer.cs` as WHOLE FILES: 100% 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 (34 lines × 2) ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs:20— ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs:20-53 | docs/ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs:20-53 — before extracting anything, compare `ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs` and `docs/ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs` as WHOLE FILES: 100% 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 `ConcurrencyInCSharpCookbook/11Sync/BlockSemaphore.cs:20` 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 (53 lines × 2) ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs:18— ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs:18-70 | docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs:18-70 — before extracting anything, compare `ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs` and `docs/ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs` as WHOLE FILES: 100% 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 (53 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/Exceptional.cs:6— FunctionalCSharp/src/MarsonShine.Functional/Exceptional.cs:6-58 | docs/FunctionalCSharp/src/MarsonShine.Functional/Exceptional.cs:6-58 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/Exceptional.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/Exceptional.cs` as WHOLE FILES: 100% 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 `FunctionalCSharp/src/MarsonShine.Functional/Exceptional.cs:6` 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 (8 lines × 4) DesignPattern/DesignPattern/Visitor/Amativeness.cs:12— DesignPattern/DesignPattern/Visitor/Amativeness.cs:12-19 | DesignPattern/DesignPattern/Visitor/Failing.cs:12-19 | docs/DesignPattern/DesignPattern/Visitor/Amativeness.cs:12-19 | docs/DesignPattern/DesignPattern/Visitor/Failing.cs:12-19 — before extracting anything, compare `DesignPattern/DesignPattern/Visitor/Amativeness.cs` and `DesignPattern/DesignPattern/Visitor/Failing.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) DesignPattern/DesignPatternCore/Visitor/Amativeness.cs:12— DesignPattern/DesignPatternCore/Visitor/Amativeness.cs:12-19 | DesignPattern/DesignPatternCore/Visitor/Failing.cs:12-19 | docs/DesignPattern/DesignPatternCore/Visitor/Amativeness.cs:12-19 | docs/DesignPattern/DesignPatternCore/Visitor/Failing.cs:12-19 — before extracting anything, compare `DesignPattern/DesignPatternCore/Visitor/Amativeness.cs` and `DesignPattern/DesignPatternCore/Visitor/Failing.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (72 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/Validation.cs:7— FunctionalCSharp/src/MarsonShine.Functional/Validation.cs:7-78 | docs/FunctionalCSharp/src/MarsonShine.Functional/Validation.cs:7-78 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/Validation.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/Validation.cs` as WHOLE FILES: 100% 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 `FunctionalCSharp/src/MarsonShine.Functional/Validation.cs:7` 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 (72 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/Program.cs:14— WHPerformanceDotNet/src/MomeryAllocation/Program.cs:14-85 | docs/WHPerformanceDotNet/src/MomeryAllocation/Program.cs:14-85 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/Program.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Off the main sequence: SampleCodeAnalyzer (WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer) WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzer.csproj:1— SampleCodeAnalyzer (WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: SampleCodeAnalyzer (docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer) docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer/SampleCodeAnalyzer.csproj:1— SampleCodeAnalyzer (docs/WHPerformanceDotNet/src/SampleCodeAnalyzer/SampleCodeAnalyzer): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Duplicated block (7 lines × 2 locations) ts/lib/function.js:13— ts/lib/function.js:13 · ts/lib/function.js:23 — 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 locations) ts/lib/function.js:31— ts/lib/function.js:31 · ts/src/function.ts:40 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Sync-over-async (deadlock risk) through `Task.WaitAny` ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:35— `Task.WaitAny` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAny(…)` instead.
Sync-over-async (deadlock risk) through `Task.WaitAny` docs/ConcurrencyInCSharpCookbook/08Collections/BlockingCollections.cs:35— `Task.WaitAny` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAny(…)` instead.
Swallowed exception (empty catch) ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:22— 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) docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:22— 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.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 10 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
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.
prepare_docs._complete_nav (cyclomatic 19) hooks/prepare_docs.py:325— prepare_docs._complete_nav has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Lexer.scan (cyclomatic 18) dragonbook/src/lexer/Lexer.java:21— Lexer.scan has cyclomatic complexity 18 (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.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: 06UnitTest ConcurrencyInCSharpCookbook/06UnitTest/UnitTest1.cs:8— No conventional assertion call was detected in 2 of 2 tests in `06UnitTest` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
prepare_docs._complete_nav (cognitive 30) hooks/prepare_docs.py:325— prepare_docs._complete_nav has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 3, loops 3, ternaries 1 (3 pts) (nesting depth added 12). 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.
Lexer.scan (cognitive 29) dragonbook/src/lexer/Lexer.java:21— Lexer.scan has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 5 (11 pts), boolean chains 2 (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.
D20 · ADR Quality· Title '0001' contains only random junk and no meaningful context or decision · ×1
Title '0001' contains only random junk and no meaningful context or decision WHPerformanceDotNet/src/TPLDataflow/0001.txt— Replace with a real title (e.g. 'Rethink the default layout direction for RTL content') that states the problem and the explicit decision, plus consequences
D20 · ADR Quality· The body is a repeated, garbled string containing only adajdal/...djasdfposdfjkosijufsdijfnkljnckljxhcnqiwurq[werioeritrewtuphvxkjnvxm,npejup] fragments with no context/problem and no explicit decision · ×1
The body is a repeated, garbled string containing only adajdal/...djasdfposdfjkosijufsdijfnkljnckljxhcnqiwurq[werioeritrewtuphvxkjnvxm,npejup] fragments with no context/problem and no explicit decision WHPerformanceDotNet/src/TPLDataflow/0001_1.txt— Replace the garbled content with a real Context/Problem section explaining why an architectural decision is needed, then a Decision statement, followed by Consequences/trade-offs
D20 · ADR Quality· Title '0002' contains no meaningful content and is a noise filler. Context/problem, explicit decision, consequences/trade-offs, and clarity are all absent. · ×1
Title '0002' contains no meaningful content and is a noise filler. Context/problem, explicit decision, consequences/trade-offs, and clarity are all absent. WHPerformanceDotNet/src/TPLDataflow/0002.txt— Replace the title with an informative name (e.g., 'Migrate legacy data to cloud storage') and flesh out each of the four elements: describe the problem driving the change, state the concrete decision (technology/tool/structure), document the trade-offs/downsides, and add a rationale or why it matters.
D20 · ADR Quality· Title '0003' contains only random junk and no meaningful context or decision · ×1
Title '0003' contains only random junk and no meaningful context or decision WHPerformanceDotNet/src/TPLDataflow/0003.txt— Replace with a descriptive title (e.g. "Decide the data source for the new dashboard"), then state the problem, the explicit decision, and its consequences in a single coherent section
D20 · ADR Quality· Title '0004' contains only random junk and no meaningful content (decision and context are both absent), plus the body is a repeated jumbled string with no real decision · ×1
Title '0004' contains only random junk and no meaningful content (decision and context are both absent), plus the body is a repeated jumbled string with no real decision WHPerformanceDotNet/src/TPLDataflow/0004.txt— Delete the title and replace the body with an actual architecture decision: what problem does it solve, what explicit decision is made, and its consequences.
D4 · Code Duplication· Edited copy of a member (175 corresponding lines) · ×1
Edited copy of a member (175 corresponding lines) DesignPattern/DesignPatternCore/Program.cs:24— DesignPattern/DesignPatternCore/Program.cs:24-198 | docs/DesignPattern/DesignPatternCore/Program.cs:24-198 — These two members are one piece of code written twice and then edited apart: 175 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 (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) DesignPattern/DesignPattern/ChainOfResponsibility/CommonManager.cs:16— DesignPattern/DesignPattern/ChainOfResponsibility/CommonManager.cs:16-28 | DesignPattern/DesignPattern/ChainOfResponsibility/Majordomo.cs:16-28 | DesignPattern/DesignPatternCore/ChainOfResponsibility/CommonManager.cs:16-28 | DesignPattern/DesignPatternCore/ChainOfResponsibility/Majordomo.cs:16-28 | docs/DesignPattern/DesignPattern/ChainOfResponsibility/CommonManager.cs:16-28 | docs/DesignPattern/DesignPattern/ChainOfResponsibility/Majordomo.cs:16-28 | docs/DesignPattern/DesignPatternCore/ChainOfResponsibility/CommonManager.cs:16-28 | docs/DesignPattern/DesignPatternCore/ChainOfResponsibility/Majordomo.cs:16-28 — 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 (113 lines × 2) DesignPattern/DesignPatternCore/Program.cs:86— DesignPattern/DesignPatternCore/Program.cs:86-198 | docs/DesignPattern/DesignPatternCore/Program.cs:86-198 — before extracting anything, compare `DesignPattern/DesignPatternCore/Program.cs` and `docs/DesignPattern/DesignPatternCore/Program.cs` as WHOLE FILES: 100% 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. 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 `DesignPattern/DesignPatternCore/Program.cs:86` 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 (100 lines × 2) WHPerformanceDotNet/src/TPLDataflow/Program.cs:37— WHPerformanceDotNet/src/TPLDataflow/Program.cs:37-136 | docs/WHPerformanceDotNet/src/TPLDataflow/Program.cs:37-136 — before extracting anything, compare `WHPerformanceDotNet/src/TPLDataflow/Program.cs` and `docs/WHPerformanceDotNet/src/TPLDataflow/Program.cs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (73 lines × 2) WHPerformanceDotNet/src/GenericOptimization/Program.cs:17— WHPerformanceDotNet/src/GenericOptimization/Program.cs:17-89 | docs/WHPerformanceDotNet/src/GenericOptimization/Program.cs:17-89 — before extracting anything, compare `WHPerformanceDotNet/src/GenericOptimization/Program.cs` and `docs/WHPerformanceDotNet/src/GenericOptimization/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (48 lines × 2) REDACTED:11— REDACTED:11-58 | docs/REDACTED:11-58 — before extracting anything, compare `REDACTED` and `docs/REDACTED` as WHOLE FILES: 100% 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 (42 lines × 2) WHPerformanceDotNet/src/FullGCNotification/Program.cs:29— WHPerformanceDotNet/src/FullGCNotification/Program.cs:29-70 | docs/WHPerformanceDotNet/src/FullGCNotification/Program.cs:29-70 — before extracting anything, compare `WHPerformanceDotNet/src/FullGCNotification/Program.cs` and `docs/WHPerformanceDotNet/src/FullGCNotification/Program.cs` as WHOLE FILES: 100% 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. 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 (41 lines × 2) WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:15— WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:15-55 | docs/WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs:15-55 — before extracting anything, compare `WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs` and `docs/WHPerformanceDotNet/src/MomeryAllocation/MemoryAllocationOfSpan/AvoidMemoryAlloctation.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17–19 lines × 3) WHPerformanceDotNet/src/DynamicGenerateExecutor/Program.cs:78— WHPerformanceDotNet/src/DynamicGenerateExecutor/Program.cs:78-96 | WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:56-72 | docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:56-72 — before extracting anything, compare `WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` and `docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `WHPerformanceDotNet/src/DynamicGenerateExecutor/Program.cs:78` 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 (17 lines × 4) CSharpGuide/performance/strings/Strings.cs:134— CSharpGuide/performance/strings/Strings.cs:134-150 | CSharpGuide/performance/strings/Strings.cs:166-182 | docs/CSharpGuide/performance/strings/Strings.cs:134-150 | docs/CSharpGuide/performance/strings/Strings.cs:166-182 — before extracting anything, compare `CSharpGuide/performance/strings/Strings.cs` and `docs/CSharpGuide/performance/strings/Strings.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/performance/strings/Strings.cs:134` 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 (16 lines × 4) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:60— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:60-75 | CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:64-79 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:60-75 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:64-79 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:60` 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 × 8) DesignPattern/DesignPattern/ChainOfResponsibility/CommonManager.cs:21— DesignPattern/DesignPattern/ChainOfResponsibility/CommonManager.cs:21-28 | DesignPattern/DesignPattern/ChainOfResponsibility/Majordomo.cs:21-28 | DesignPattern/DesignPatternCore/ChainOfResponsibility/CommonManager.cs:21-28 | DesignPattern/DesignPatternCore/ChainOfResponsibility/Majordomo.cs:21-28 | docs/DesignPattern/DesignPattern/ChainOfResponsibility/CommonManager.cs:21-28 | docs/DesignPattern/DesignPattern/ChainOfResponsibility/Majordomo.cs:21-28 | docs/DesignPattern/DesignPatternCore/ChainOfResponsibility/CommonManager.cs:21-28 | docs/DesignPattern/DesignPatternCore/ChainOfResponsibility/Majordomo.cs:21-28 — before extracting anything, compare `DesignPattern/DesignPattern/ChainOfResponsibility/CommonManager.cs` and `DesignPattern/DesignPatternCore/ChainOfResponsibility/CommonManager.cs` as WHOLE FILES: 92% 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 `DesignPattern/DesignPattern/ChainOfResponsibility/CommonManager.cs:21` 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 (11–12 lines × 4) CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:116— CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:116-126 | CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:160-171 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:116-126 | docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:160-171 — before extracting anything, compare `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` and `docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 3) WHPerformanceDotNet/src/DynamicGenerateExecutor/Program.cs:103— WHPerformanceDotNet/src/DynamicGenerateExecutor/Program.cs:103-112 | WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:34-44 | docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs:34-44 — before extracting anything, compare `WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` and `docs/WHPerformanceDotNet/src/DynamicLoadExecutor/Program.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `WHPerformanceDotNet/src/DynamicGenerateExecutor/Program.cs:103` 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 (7 lines × 4) ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:13— ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:13-19 | ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:26-32 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:13-19 | docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs:26-32 — before extracting anything, compare `ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs` and `docs/ConcurrencyInCSharpCookbook/05ReactiveExtensions/ThrottleAndSample.cs` as WHOLE FILES: 100% 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 (37 lines × 2) AsyncInCSharp/TAPs/Program.cs:7— AsyncInCSharp/TAPs/Program.cs:7-43 | docs/AsyncInCSharp/TAPs/Program.cs:7-43 — before extracting anything, compare `AsyncInCSharp/TAPs/Program.cs` and `docs/AsyncInCSharp/TAPs/Program.cs` as WHOLE FILES: 100% 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 (74 lines × 2) CSharpGuide/LanguageVersions/7.2/ReadonlyAndRefStructs.cs:13— CSharpGuide/LanguageVersions/7.2/ReadonlyAndRefStructs.cs:13-86 | docs/CSharpGuide/LanguageVersions/7.2/ReadonlyAndRefStructs.cs:13-86 — before extracting anything, compare `CSharpGuide/LanguageVersions/7.2/ReadonlyAndRefStructs.cs` and `docs/CSharpGuide/LanguageVersions/7.2/ReadonlyAndRefStructs.cs` as WHOLE FILES: 100% 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 `CSharpGuide/LanguageVersions/7.2/ReadonlyAndRefStructs.cs:13` 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 (214 lines × 2) CSharpGuide/LanguageVersions/7.3/RefForeach/Program.cs:20— CSharpGuide/LanguageVersions/7.3/RefForeach/Program.cs:20-233 | docs/CSharpGuide/LanguageVersions/7.3/RefForeach/Program.cs:20-233 — before extracting anything, compare `CSharpGuide/LanguageVersions/7.3/RefForeach/Program.cs` and `docs/CSharpGuide/LanguageVersions/7.3/RefForeach/Program.cs` as WHOLE FILES: 100% 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 `CSharpGuide/LanguageVersions/7.3/RefForeach/Program.cs:20` 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 (85 lines × 2) CSharpGuide/asynclocal/asynclocal/Program.cs:51— CSharpGuide/asynclocal/asynclocal/Program.cs:51-135 | docs/CSharpGuide/asynclocal/asynclocal/Program.cs:51-135 — before extracting anything, compare `CSharpGuide/asynclocal/asynclocal/Program.cs` and `docs/CSharpGuide/asynclocal/asynclocal/Program.cs` as WHOLE FILES: 100% 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 `CSharpGuide/asynclocal/asynclocal/Program.cs:51` 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 (56 lines × 2) CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs:14— CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs:14-69 | docs/CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs:14-69 — before extracting anything, compare `CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs` and `docs/CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs` as WHOLE FILES: 100% 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 `CSharpGuide/net8-guide/CollectionExpression/MyCollection.cs:14` 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 (32 lines × 2) CSharpInDepth/Chapter_3_Generic/Pair.cs:15— CSharpInDepth/Chapter_3_Generic/Pair.cs:15-46 | docs/CSharpInDepth/Chapter_3_Generic/Pair.cs:15-46 — before extracting anything, compare `CSharpInDepth/Chapter_3_Generic/Pair.cs` and `docs/CSharpInDepth/Chapter_3_Generic/Pair.cs` as WHOLE FILES: 100% 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. 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 `CSharpInDepth/Chapter_3_Generic/Pair.cs:15` 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 (77 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/Either.cs:8— FunctionalCSharp/src/MarsonShine.Functional/Either.cs:8-84 | docs/FunctionalCSharp/src/MarsonShine.Functional/Either.cs:8-84 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/Either.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/Either.cs` as WHOLE FILES: 100% 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 `FunctionalCSharp/src/MarsonShine.Functional/Either.cs:8` 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 (84 lines × 2) FunctionalCSharp/src/MarsonShine.Functional/Option.cs:9— FunctionalCSharp/src/MarsonShine.Functional/Option.cs:9-92 | docs/FunctionalCSharp/src/MarsonShine.Functional/Option.cs:9-92 — before extracting anything, compare `FunctionalCSharp/src/MarsonShine.Functional/Option.cs` and `docs/FunctionalCSharp/src/MarsonShine.Functional/Option.cs` as WHOLE FILES: 100% 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 `FunctionalCSharp/src/MarsonShine.Functional/Option.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 (89 lines × 2) CSharpGuide/Program.cs:24— CSharpGuide/Program.cs:24-112 | docs/CSharpGuide/Program.cs:24-112 — before extracting anything, compare `CSharpGuide/Program.cs` and `docs/CSharpGuide/Program.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (52 lines × 2) CSharpInDepth/Chapter_3_Generic/LinkedList_Demo.cs:12— CSharpInDepth/Chapter_3_Generic/LinkedList_Demo.cs:12-63 | docs/CSharpInDepth/Chapter_3_Generic/LinkedList_Demo.cs:12-63 — before extracting anything, compare `CSharpInDepth/Chapter_3_Generic/LinkedList_Demo.cs` and `docs/CSharpInDepth/Chapter_3_Generic/LinkedList_Demo.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (65 lines × 2) CSharpGuide/simd-vector-demo/VectorOperator.cs:60— CSharpGuide/simd-vector-demo/VectorOperator.cs:60-124 | docs/CSharpGuide/simd-vector-demo/VectorOperator.cs:60-124 — before extracting anything, compare `CSharpGuide/simd-vector-demo/VectorOperator.cs` and `docs/CSharpGuide/simd-vector-demo/VectorOperator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Type Safety — 16 typed · 12 plain JS — the untyped files are ts/lib/TypeAssertion.js, ts/lib/anyType.js, ts/lib/declarefile.js, ts/lib/declaresynax.js, ts/lib/extensionGlobalVarious.js, ts/lib/fiveType.js (+6 more).
R10 · Code Duplication· Duplicated block with local edits (11 matched lines × 2 locations) · ×1
Duplicated block with local edits (11 matched lines × 2 locations) ts/lib/declarefile.js:6— ts/lib/declarefile.js:6 · ts/src/declarefile.ts:7 — the two spans are one implementation copied and then locally edited — 94 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
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.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×1
Symbol treated as nullable, then dereferenced unguarded ConcurrencyInCSharpCookbook/10OOP/AsyncInitializeClassPattern.cs:51— This method contradicts itself about `myclass`: line 50 assigns it with `as MyClass`, which hands back null rather than throwing when the value is not a `MyClass`, but line 51 then dereferences it directly as `myclass.Initialization` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `myclass` once before the first use and handle the null case, or cast with `(MyClass)` so the failure is reported where it happens — rather than leaving the two readings side by side.
README/code drift APUE/README.md:857— APUE/README.md documents the environment variable `PROT_EXEC`, but no code, script or configuration file names it. 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 APUE/README.md:858— APUE/README.md documents the environment variable `PROT_NONE`, but no code, script or configuration file names it. 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 APUE/README.md:862— APUE/README.md documents the environment variable `MAP_PRIVATE`, but no code, script or configuration file names it. 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 APUE/README.md:863— APUE/README.md documents the environment variable `MAP_FIXED`, but no code, script or configuration file names it. 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 APUE/README.md:864— APUE/README.md documents the environment variable `MAP_ANONYMOUS`, but no code, script or configuration file names it. 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 APUE/README.md:965— APUE/README.md documents the environment variable `PIPE_BUF`, but no code, script or configuration file names it. 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 APUE/README.md:1096— APUE/README.md documents the environment variable `PTHREAD_PROCESS_SHARED`, but no code, script or configuration file names it. 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 APUE/README.md:1295— APUE/README.md documents the environment variable `SO_REUSEADDR`, but no code, script or configuration file names it. 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 APUE/README.md:1296— APUE/README.md documents the environment variable `SO_KEEPALIVE`, but no code, script or configuration file names it. 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 APUE/README.md:1297— APUE/README.md documents the environment variable `SO_SNDBUF`, but no code, script or configuration file names it. 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 APUE/README.md:1297— APUE/README.md documents the environment variable `SO_RCVBUF`, but no code, script or configuration file names it. 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 APUE/README.md:1298— APUE/README.md documents the environment variable `TCP_NODELAY`, but no code, script or configuration file names it. 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 CurrentProgramming-for-Scalable-WebArchitectures/README.md:7— CurrentProgramming-for-Scalable-WebArchitectures/README.md links to `scalability`, but `CurrentProgramming-for-Scalable-WebArchitectures/scalability` does not exist. 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 Postgresql-In-Internal/README.MD:11— Postgresql-In-Internal/README.MD documents the environment variable `PD_PAGE_FULL`, but no code, script or configuration file names it. 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 Postgresql-In-Internal/README.MD:173— Postgresql-In-Internal/README.MD links to `github.com/reorg/pg_repack`, but `Postgresql-In-Internal/github.com/reorg/pg_repack` does not exist. 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 TheArtOfUnixProgramming/README.md:40— TheArtOfUnixProgramming/README.md links to `[Books/CSAPP/docs/cache-in-deep.md`, but `TheArtOfUnixProgramming/[Books/CSAPP/docs/cache-in-deep.md` does not exist. 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 docs/index.md:4— docs/index.md links to `AsyncInCSharp/docs/`, but `docs/AsyncInCSharp/docs` does not exist. 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 docs/index.md:5— docs/index.md links to `CleanArchitecture/`, but `docs/CleanArchitecture` does not exist. 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 docs/index.md:6— docs/index.md links to `CleanCode/`, but `docs/CleanCode` does not exist. 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 docs/index.md:7— docs/index.md links to `WHPerformanceDotNet/`, but `docs/WHPerformanceDotNet` does not exist. 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 docs/index.md:8— docs/index.md links to `ConcurrencyInCSharpCookbook/03ParallerBasic/`, but `docs/ConcurrencyInCSharpCookbook/03ParallerBasic` does not exist. 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 docs/index.md:9— docs/index.md links to `CSharpGuide/docs/`, but `docs/CSharpGuide/docs` does not exist. 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 docs/index.md:10— docs/index.md links to `CSAPP/`, but `docs/CSAPP` does not exist. 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 docs/index.md:11— docs/index.md links to `CSharpInDepth/`, but `docs/CSharpInDepth` does not exist. 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 docs/index.md:12— docs/index.md links to `DesignPattern/DesignPatternCore/`, but `docs/DesignPattern/DesignPatternCore` does not exist. 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.
Duplicated predicate CSharpGuide/simd-vector-demo/VectorOperator.cs:47— `(index >= 0) && (index < Vector128<T>.Count)` appears character-identically in 2 files — CSharpGuide/simd-vector-demo/VectorOperator.cs, docs/CSharpGuide/simd-vector-demo/VectorOperator.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 CSharpGuide/roslySdkDemo/SemanticQuickStart/Program.cs:67— `SymbolEqualityComparer.Default.Equals(m.ReturnType, stringTypeSymbol) && m.DeclaredAccessibility == Accessibility.Public` appears character-identically in 2 files — CSharpGuide/roslySdkDemo/SemanticQuickStart/Program.cs, docs/CSharpGuide/roslySdkDemo/SemanticQuickStart/Program.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 CSharpGuide/simd-vector-demo/Extensions.cs:38— `Vector.IsHardwareAccelerated && Vector<T>.IsSupported && source.Length > Vector<T>.Count` appears character-identically in 2 files — CSharpGuide/simd-vector-demo/Extensions.cs, docs/CSharpGuide/simd-vector-demo/Extensions.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 CSharpGuide/simd-vector-demo/VectorOperator.cs:60— `Vector128.IsHardwareAccelerated &&haystack.Length >= Vector128<byte>.Count` appears character-identically in 2 files — CSharpGuide/simd-vector-demo/VectorOperator.cs, docs/CSharpGuide/simd-vector-demo/VectorOperator.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 CSharpGuide/simd-vector-demo/VectorOperator.cs:81— `Vector256.IsHardwareAccelerated && haystack.Length >= Vector256<byte>.Count` appears character-identically in 2 files — CSharpGuide/simd-vector-demo/VectorOperator.cs, docs/CSharpGuide/simd-vector-demo/VectorOperator.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 CSharpGuide/simd-vector-demo/VectorOperator.cs:64— `Vector512.IsHardwareAccelerated && haystack.Length >= Vector512<byte>.Count` appears character-identically in 2 files — CSharpGuide/simd-vector-demo/VectorOperator.cs, docs/CSharpGuide/simd-vector-demo/VectorOperator.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 DesignPattern/DesignPatternCore/Specification/OrSpecification.cs:11— `_left.IsSatisfiedBy(o) || _right.IsSatisfiedBy(o)` appears character-identically in 2 files — DesignPattern/DesignPatternCore/Specification/OrSpecification.cs, docs/DesignPattern/DesignPatternCore/Specification/OrSpecification.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 ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs:40— `_task.IsCompletedSuccessfully && _task.Status == TaskStatus.RanToCompletion` appears character-identically in 2 files — ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.cs, docs/ConcurrencyInCSharpCookbook/13PracticalSkills/AsyncDataBind.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 CSharpGuide/memory-mapped-files/Program.cs:30— `c1 == TypeCode.DateTime || c2 == TypeCode.DateTime` appears character-identically in 2 files — CSharpGuide/memory-mapped-files/Program.cs, docs/CSharpGuide/memory-mapped-files/Program.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 CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs:56— `eventPayload.TryGetValue("Mean", out object? value) || eventPayload.TryGetValue("Increment", out value)` appears character-identically in 2 files — CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.cs, docs/CSharpGuide/diagnostics/CollectionMetricDemo/EventListeners/SimpleEventListener.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 CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs:13— `eventSource.Name == "MyCompany-ActivityId-Demo" || eventSource.Name == "MyCompany-ParallelActivityId-Demo"` appears character-identically in 2 files — CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.cs, docs/CSharpGuide/diagnostics/EventSourceDemo/EventListener/ConsoleWriterEventListener.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 CSharpGuide/generics/NoneGenericCallGeneric.cs:32— `isValid && autoPolicyValidator.Validate(auto)` appears character-identically in 2 files — CSharpGuide/generics/NoneGenericCallGeneric.cs, docs/CSharpGuide/generics/NoneGenericCallGeneric.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 CSharpGuide/generics/NoneGenericCallGeneric.cs:36— `isValid && homePolicyValidator.Validate(home)` appears character-identically in 2 files — CSharpGuide/generics/NoneGenericCallGeneric.cs, docs/CSharpGuide/generics/NoneGenericCallGeneric.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 CSharpGuide/generics/NoneGenericCallGeneric.cs:40— `isValid && lifePolicyValidator.Validate(life)` appears character-identically in 2 files — CSharpGuide/generics/NoneGenericCallGeneric.cs, docs/CSharpGuide/generics/NoneGenericCallGeneric.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 CSharpGuide/generics/NoneGenericCallGeneric.cs:52— `isValid && policyValidator.Validate(policy)` appears character-identically in 2 files — CSharpGuide/generics/NoneGenericCallGeneric.cs, docs/CSharpGuide/generics/NoneGenericCallGeneric.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 CSharpGuide/performance/strings/Strings.cs:38— `kvp.Length == 2 && !kvp[0].Equals("instanceId", StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — CSharpGuide/performance/strings/Strings.cs, docs/CSharpGuide/performance/strings/Strings.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 CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:122— `member is IFieldSymbol field && field.ConstantValue is not null` appears character-identically in 4 files — CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs, CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs, docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs, docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.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 CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs:153— `namedArgument.Key == "ExtensionClassName" && namedArgument.Value.Value?.ToString() is { } n` appears character-identically in 2 files — CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs, docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.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 CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs:52— `node is EnumDeclarationSyntax m && m.AttributeLists.Count > 0` appears character-identically in 4 files — CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs, CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.cs, docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums/EnumToGenerator.cs, docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/Enums2/EnumToGenerator.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 CSharpGuide/roslySdkDemo/SyntaxWalker/UsingCollector.cs:17— `node?.Name?.ToString() != "System" && !node!.Name!.ToString().StartsWith("System.")` appears character-identically in 2 files — CSharpGuide/roslySdkDemo/SyntaxWalker/UsingCollector.cs, docs/CSharpGuide/roslySdkDemo/SyntaxWalker/UsingCollector.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 WHPerformanceDotNet/src/MomeryAllocation/Vector.cs:14— `obj == null || GetType() != obj.GetType()` appears character-identically in 2 files — WHPerformanceDotNet/src/MomeryAllocation/Vector.cs, docs/WHPerformanceDotNet/src/MomeryAllocation/Vector.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 CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs:28— `obj is EquatableArray<T> array && Equals(this, array)` appears character-identically in 2 files — CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.cs, docs/CSharpGuide/SourceGeneratorDemo/MySourceGenerator/EquatableArray.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 CSharpInDepth/Chapter_3_Generic/Pair.cs:25— `other != null && FirstComparer.Equals(this.First, other.First) && SecondComparer.Equals(this.Second, other.Second)` appears character-identically in 2 files — CSharpInDepth/Chapter_3_Generic/Pair.cs, docs/CSharpInDepth/Chapter_3_Generic/Pair.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 DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs:21— `request.RequestType == "加薪" && request.Number <=500` appears character-identically in 4 files — DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs, DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.cs, docs/DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs, docs/DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.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 DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs:24— `request.RequestType == "加薪" && request.Number > 500` appears character-identically in 4 files — DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs, DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.cs, docs/DesignPattern/DesignPattern/ChainOfResponsibility/GeneralManager.cs, docs/DesignPattern/DesignPatternCore/ChainOfResponsibility/GeneralManager.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 AsyncInCSharp/AsyncAwaitable/ExampleAwaitable.cs:30— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code REDACTED:33— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code REDACTED:16— 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 REDACTED:17— 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 AsyncInCSharp/PerFormanceComparison/AsyncAndSyncComparison.cs:24— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code AsyncInCSharp/TAPs/Program.cs:17— 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 CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs:27— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code CSharpGuide/LanguageVersions/10.0/LambdaImprovement.cs:32— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code CSharpGuide/LanguageVersions/11.0/csharp11/Program.cs:13— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No security response headers detected CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:2— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected CSharpGuide/diagnostics/DistributedTraceWebDemo/Program.cs:3— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected CSharpGuide/performance/strings/Program.cs:11— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected docs/CSharpGuide/LanguageVersions/9.0/openapi/Program.cs:2— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected docs/CSharpGuide/diagnostics/DistributedTraceWebDemo/Program.cs:3— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected docs/CSharpGuide/performance/strings/Program.cs:11— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
Documentation: no project overview README.md— The README reads as a book index listing only documentation paths (e.g. AsyncInCSharp/docs/) rather than describing what the repository does or what it contains. State what the repository is for and how to use its contents under an overview section.
Documentation: no contributor guidance README.md— The README lists books and AI-LLMs/ directories but does not guide contributors on how to submit changes or contribute. Add a short contributing section covering pull request, issue, and review process.
Documentation: no licence statement README.md— No licence statement appears in the visible content despite the repository's documentation being built with MkDocs. Add a Licence header to the root README or the repo-level docs directory.
Documentation: no project overview SystemPerformance-Enterprise-Cloud/README.md— The document is a USE-performance analysis guide with no overview of what SystemPerformance-Enterprise-Cloud does. State what this directory provides (performance measurement, bottleneck detection) so readers can find it among the many unrelated docs.
Documentation: no project overview TCPIP/README.md— The TCP/IP protocol reference glossary is a reference document; there is no overview of what TCPIP/ does. Add a one-line description of what TCPIP/ covers so readers can find it among the many unrelated docs.
Documentation: no project overview ThinkingInJava/README.md— The README states 'Java 编程思想 in VSCode' and is only four words, giving no context about what this directory contains. State what the ThinkingInJava/ directory provides so readers can find it among the many unrelated docs.
Orphaned file DesignPattern/DesignPatternCore/Program.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED: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 DesignPattern/DesignPattern/Program.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.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 CSharpGuide/roslySdkDemo/SemanticQuickStart/Program.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:16— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
IC1 · Incompleteness & stubs· Empty method body · ×3
Empty method body AsyncInCSharp/ExceptionInAsync/Program.cs:10— `SyncThrowException` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body AsyncInCSharp/PerFormanceComparison/AsyncAndSyncComparison.cs:23— `EmptyAsync` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body AsyncInCSharp/PerFormanceComparison/AsyncAndSyncComparison.cs:27— `Empty` has an empty body — confirm it's an intentional no-op and not an unfinished method.
R7 · Dead Code· Unused module-local declaration 'directions' · ×2
Unused module-local declaration 'directions' ts/lib/index.js:8— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
Unused module-local declaration 'directions' ts/src/index.ts:8— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'options' · ×2
Unused module-local declaration 'options' ts/lib/index.js:9— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
Unused module-local declaration 'options' ts/src/index.ts:9— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
Silent fallback default on parse failure ConcurrencyInCSharpCookbook/13PracticalSkills/ParameterStatusInConcurrent.cs:27— `GetLogicalData` falls back to `default` when `states.TryGetValue(name, out AsyncLocal<object> data)` 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.
Silent fallback default on parse failure docs/ConcurrencyInCSharpCookbook/13PracticalSkills/ParameterStatusInConcurrent.cs:27— `GetLogicalData` falls back to `default` when `states.TryGetValue(name, out AsyncLocal<object> data)` 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.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
D21 · Naming Consistency· Inconsistent spelling of 'Memory' across the codebase. Some symbols use 'Momery' (e.g., MomeryAllocation), while others use 'PerFormance' or 'Performances' (capitalization inconsistency) or 'Performance' (standard spelling). Specifically, 'Momery' appears to be a typo for 'Memory', and 'PerFormance' mixes casing styles. · ×1
Inconsistent spelling of 'Memory' across the codebase. Some symbols use 'Momery' (e.g., MomeryAllocation), while others use 'PerFormance' or 'Performances' (capitalization inconsistency) or 'Performance' (standard spelling). Specifically, 'Momery' appears to be a typo for 'Memory', and 'PerFormance' mixes casing styles. — Standardize to 'Memory' for memory-related allocations and 'Performance' for performance-related comparisons. Fix 'Momery' to 'Memory' and 'PerFormance' to 'Performance'. (symbols: Method: public void MomeryAllocation.Program.RefZeroMiddleValue(int[]), Method: private void MomeryAllocation.ObjectCache.HybirdCache<TKey, TValue>.AttemptADemotion(TKey, MomeryAllocation.ObjectCache.HybirdCache<TKey, TValue>.ValueContainer<TValue>), Type: internal PerFormanceComparison.Program, Type: internal net8_guide.Performances.SearchValueTypes, Namespace: MomeryAllocation, Namespace: MomeryAllocation.PoolableObject)
D21 · Naming Consistency· Inconsistent spelling of 'Partner'. The namespace and type name use 'Patner' (missing 'r'), which is likely a typo for 'Partner'. · ×1
Inconsistent spelling of 'Partner'. The namespace and type name use 'Patner' (missing 'r'), which is likely a typo for 'Partner'. — Rename 'PatnerMatching' to 'PartnerMatching' in the namespace, type, and method names. (symbols: Method: public void Chapter12_Deconstruction_PatnerMatching.PatnerMatching.CheckType<T>(object), Method: public int Chapter12_Deconstruction_PatnerMatching.PatnerMatching.Fib(int), Type: public Chapter12_Deconstruction_PatnerMatching.PatnerMatching)
D21 · Naming Consistency· Inconsistent spelling of 'Prompt'. The parameter 'promt' is missing the second 'p', while 'Messages' is spelled correctly. While 'promt' is a parameter, it suggests a broader typo issue in the codebase's vocabulary. · ×1
Inconsistent spelling of 'Prompt'. The parameter 'promt' is missing the second 'p', while 'Messages' is spelled correctly. While 'promt' is a parameter, it suggests a broader typo issue in the codebase's vocabulary. — Rename parameter 'promt' to 'prompt'. (symbols: Parameter: string promt, Property: public string strings.Strings.Response.Messages)
D21 · Naming Consistency· Typo in type name 'CirCle' (capital C in the middle). · ×1
Typo in type name 'CirCle' (capital C in the middle). — Rename 'CirCle' to 'Circle'. (symbols: Property: public double CSharpGuide.LanguageVersions._10._0.CirCle.Radius, Type: public CSharpGuide.LanguageVersions._10._0.CirCle)
redundant comment docs/CSharpInDepth/Chapter13_HighPerformancePassByReference/RefReturn.cs:43— "申明两个 ref 本地变量引用相同的数组元素" — 弱化为注释，或删除 - the restatement of the code already says this
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 148 project(s) overshoot their size bounds, lowering Project Cohesion to 9.7/10. The most over is `CSharpGuide` (6635 LoC, 175 public types across 38 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 5 of 67 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; 67 of the 427 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: DesignPattern/DesignPatternCore/Program.cs, REDACTED, DesignPattern/DesignPattern/Program.cs, ConcurrencyInCSharpCookbook/09Cancellation/CancellationRx.cs, CSharpGuide/roslySdkDemo/SemanticQuickStart/Program.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.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
Thin README — The root README is 118 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
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'.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 1078 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.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
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 13/121 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Nullable reference types not enabled everywhere — 48/85 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.6 `!` suppressions per 1k syntax nodes — 119 suppression(s) across the 75489 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.
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.
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 — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a16204-88dc-70de-9246-b26b49132dcd · 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 — 34 field(s) across 3 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: 79 · Warnings: 850 · Recommendations: 156 · Info: 116 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 05:10 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.