Public report of ReactiveX/RxSwift, published 23 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 23 October 2026, 06:40 UTC · Survey ID cd_83183b5541094ce9867ff302a40b6483
ReactiveX/RxSwift
Measured 23 October 2026, 06:38 UTC, at code version 3e33f90
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
No change 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: 56,305 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Production Readiness, 39
Findings by how serious they are
8 critical534 serious62 minor
15 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 06:38 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 ▸
60of 63 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
590of 604 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
63dimensions across 7 lenses, read from 56,305 lines of product code in 11 projects.
ReactiveX/RxSwift scores 53 out of 100 and is rated Adequate, while six of its seven lenses score higher still: Security and Compliance at 99, rated Exemplary, Domain Modelling at 88 and Performance at 81, both rated Strong, and Architecture at 85, Code Health at 64 and Maturity at 54, all rated Adequate.
The score is lower than those six because the weakest lens counts most, and here that is Production Readiness, which scores 39 and is rated Weak. Its Observability 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 1 No ADRs found finding(s) in ADR Quality and to resolve the 1 Assertions commented out finding(s) in Test Quality, and if Production Readiness rose to 70, the score would rise from 53 to about 63.
Eight findings are critical: four in Static Analysis (SAST), two in Test Quality, one in Rich vs anemic domain model and one in Test isolation.
Watchdog couldn't measure 13 dimensions in this code, among them Code Coverage, Test Reliability and Internal API Consistency, so they are left out of the score. The product code is 56,305 lines, which would take an estimated 0.8 person-years, around €120,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 1 finding
This critical or serious finding was in the previous survey, on 9 October 2026, and is gone from this one.
Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €120,000 · Estimate
Cost to rebuild
€41,000 to €200,000, for 678 to 2,150 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 53. 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: 56,305 lines of product code
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. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
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 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 5 points · Low effort · ADR Quality
2
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with RxExample_macOSUITests.swift.
Raises the score by about 5 points · Low effort · Test Quality
3
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with RxExample_macOSUITests.swift.
Raises the score by about 5 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 €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Production Readiness, at 39 (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 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
7 modules, with 11 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
33 pairs of types, where a type in repository uses a type in RxSwift. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
85 pairs of types, where a type in repository uses a type in RxCocoa. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
1190 pairs of types, where a type in RxSwift uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
166 pairs of types, where a type in RxCocoa uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
51 pairs of types, where a type in AllTestz uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
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
A05:2025 — Injection
5
High / Critical
Roadmap
First, establish observability by logging through the system logger on all error paths to ensure users can provide actionable diagnostic trails. Second, integrate static analysis into the CI pipeline to automatically block security regressions before they land. Third, improve test distribution by expanding coverage beyond unit tests to include integration and end-to-end scenarios. Finally, document significant design decisions in a structured ADR folder to preserve architectural context and resolve current documentation gaps.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
RxSwift/Observables/TakeWithPredicate.swift
7.0
Mixed
Code Duplication: Duplicated block (30 lines × 2)
How the grades work
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 — 8
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 — 534
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 — 62
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 15
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. 60 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 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 — 63 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, 590 of 604 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.
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: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (RxSwift), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — 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. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D22 Internal API Consistency — 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `RxCocoa/Foundation/URLSession+Rx.swift`, `RxSwift/ObservableType+Extensions.swift`, `RxSwift/Observables/Debug.swift`, `RxSwift/Observables/Throttle.swift`, `RxSwift/Traits/PrimitiveSequence/PrimitiveSequence+Concurrency.swift` 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.
AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (Preprocessor/Preprocessor.xcodeproj/project.pbxproj). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
GD1 Unfinished & placeholder code — 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 reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — 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 reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X2 Cancellation propagation — 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 reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (3): D19, D21, 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 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Randomizer.randomize (cyclomatic 23), validate-headers.swift.validateHeader (cyclomatic 18), Changeset.debugDescription (cyclomatic 17). — 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 4 together lifts Cyclomatic Complexity from 9.2 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.
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with Randomizer.randomize (cognitive 46), CommandGenerator.calculateItemMovements (cognitive 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.3 to about 7.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
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 Classes9.7 / 10Stronggated by 3 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 3 TooManyMethods finding(s) in God Classes — start with Reactive.swift, SharedSequence.swift, Completable+AndThen.swift. — One of this dimension's main actionable groups (3 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
472 duplicated block group(s) detected. A further 15 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 2 of the 487 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.
+ 81 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 90 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Merge.swift (4), VirtualTimeScheduler.swift (3), ObserveOn.swift (3). — One of this dimension's main actionable groups (90 warning-level).
Resolve the 34 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with RxTableViewSectionedAnimatedDataSource.swift (3), Multicast.swift (3), CompositeDisposable.swift (2). — One of this dimension's main actionable groups (34 warning-level).
Resolve the 28 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with RxCocoa.swift (2), Catch.swift (2), Rx.swift (2). — One of this dimension's main actionable groups (28 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.3 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
11 production modules (SwiftPM+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 1 module(s) off the main sequence, with abstractness counted on 8 of the 11 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: RxBlocking (SwiftPM)
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 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.
Resolve the 7 Low cohesion finding(s) in Cohesion (LCOM4) — start with Catch.swift (2), RetryWhen.swift (2), TableViewSectionedDataSource.swift. — One of this dimension's main actionable groups (7 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution7.0 / 10Adequate✓ 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.
30 test methods: 23 unit, 0 integration, 0 BDD, 7 e2e.
What to do
Improve Test Distribution — currently 7.0/10. — 30 test methods: 23 unit, 0 integration, 0 BDD, 7 e2e.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.0 / 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, 6 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 30 tests (1 harness-style project(s) excluded from the assertion penalty).
Test project verifies nothing: RxExample-macOSUITestsRxExample/RxExample-macOSUITests/RxExample_macOSUITests.swift:30
No direct assertions: testGitHubSignUp · ×5RxExample/RxExample-iOSUITests/FlowTests.swift:28
What to do
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with RxExample_macOSUITests.swift. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with RxExample_macOSUITests.swift. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 5 No direct assertions finding(s) in Test Quality — start with FlowTests.swift (5). — One of this dimension's main actionable groups (5 recommendation-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.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
1 outdated direct gem(s), 0 pinning defect(s). 1 declaration(s) graded against rubygems.org, 1 of them against a version resolved in a committed Gemfile.lock. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Outdated: danger
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 33 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 33 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is RxSwift/Subjects/ReplaySubject.swift. Counted over 150 of the 652 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
8 deducted task-comment markers across 56305 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 7 TodoComment finding(s) in Explicit Debt — start with DispatchQueueConfiguration.swift (4), RxTest.swift (2), CLLocationManager+RxTests.swift. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with TableViewWithEditingCommandsViewController.swift. — One of this dimension's main actionable groups (1 warning-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.
The repository's root README and its sibling directories (Preprocessor/README.md, RxBlocking/README.md, RxExample/RxDataSources/README.md) each document their own subdirectories, with the root README covering the project as a whole. The architecture/design docs are well represented in markdown form (74 of them). There is no single missing overview, installation, usage, or contribution guide for any one document; instead, each subdirectory's README is self-contained and scoped to its directory. Internal jargon appears only in the Preprocessor/README.md but does not prevent it from being readable. This project's documentation is excellent: every README file under the repository root (RxSwift.html) and its companion architecture/Docs markdown files together provide a complete reference for RxSwift 6.10.1, covering an overview, usage examples in fenced shell blocks, each class with a Class Reference, and extensive design/architecture coverage. The project's documentation is strong: it contains 4 README files (each about its own directory) plus 74 architecture/design markdown documents, and every visible document has a clear heading outline. The main content is the DisposeBag, HistoricalScheduler, MainScheduler, and Observable class references with cross-references to AnyObserver, Binder, Cancelable, ConnectableObservableType, Disposable, Event, GroupedObservable, ImmediateSchedulerType, Observable, ObservableConvertibleType, ObservableType, ObserverType, Reactive, SchedulerType, plus BooleanDisposable, CompositeDisposable, DisposeKey, Disposables, DisposeBag, DisposableBuilder, DisposeBase, RefCountDisposable. The visible content is complete and well-structured.
Documentation: no project overviewdocs/index.html
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
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.
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.
2 of 3 build units (Bundler, Xcode) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
5 finding(s): 0 critical, 4 high, 1 medium, 0 low. 4 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 1 file(s) — `docs/index.html` (lines 436–443) — 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
No action in Static Analysis (SAST) — all 4 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 (4 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.
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.
37 of 150 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is RxExample/RxExample/Feedbacks.swift. Counted over 150 of the 652 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 37 Orphaned file finding(s) in Knowledge Freshness — start with Feedbacks.swift, package-spm.swift, validate-headers.swift. — One of this dimension's main actionable groups (37 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with Completable.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
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 dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation7.5 / 10Strong✓ 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.
`AllTestz` (production) references the test project `RxTest (SwiftPM)`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model7.9 / 10Strong✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour — a data-only reference entity whose logic lives in a foreign service is anemic. Rich models enforce their own invariants.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`String` is a data-only reference entity whose behaviour is DELEGATED to a foreign utility (static methods that take it as their first parameter and hold its logic) — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants rather than being driven from outside. — RxExample/RxExample/Example.swift:26
What to do
Move delegated behaviour onto the domain entity (or make it a value object); keep invariants inside the type.
Other · Domain Modelling — Whether a reference entity protects its own invariants — a class whose identity is a computed content hash but whose hashed fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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 Swift pack (Swift/Xcode) (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 1835 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 Swift pack (Swift/Xcode) — 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 traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether the code 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 70 use(s) across 62,595 production line(s) (~1.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
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.
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.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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 walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone — Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries 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. — Preprocessor/Preprocessor/main.swift:102
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.
Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 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.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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 — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.swift), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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 — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Swift suite
DM1 Aggregate boundaries — not scored for Swift: the sidecar flattens array/collection types (a child COLLECTION = legitimate membership vs a single embedded aggregate is indistinguishable), and aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike) — reported as guidance rather than measured
DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
DM3 Integration-event coupling — not scored for Swift: a cross-SwiftPM-target domain leak cannot be told apart in source from a legitimate shared-kernel/contracts module, and most repositories ship a single module — reported as guidance rather than measured
DM6 Domain ↔ infrastructure boundary — this Swift package maps no type to a persistence framework and declares no domain-model type carrying a method of its own, so DM6's domain↔infrastructure boundary read has no population to be taken over
DM7 Repository granularity — not scored for Swift: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Ruby, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `swift test --enable-code-coverage` (SwiftPM) or `xcodebuild test -scheme <YourScheme> -enableCodeCoverage YES` (an .xcodeproj/.xcworkspace suite), then `xcrun llvm-cov export -format=lcov`) 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
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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 Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger 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.
X7 Silent fallback defaults — 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.
AX8 · Test isolation· Production project references a test project · ×1
Production project references a test project: AllTestz → RxTest (SwiftPM) — `AllTestz` (production) references the test project `RxTest (SwiftPM)`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Assertions commented out: testExample RxExample/RxExample-macOSUITests/RxExample_macOSUITests.swift:30— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: RxExample-macOSUITests RxExample/RxExample-macOSUITests/RxExample_macOSUITests.swift:30— No conventional assertion call was detected in 1 of 1 tests in `RxExample-macOSUITests` — the project as a whole, not one method. 1 of them has its assertions commented out, so this suite did verify conventionally and was switched off — it is not an approval/verifier harness.
DM4 · Rich vs anemic domain model· Anemic domain model · ×1
Anemic domain model: String RxExample/RxExample/Example.swift:26— `String` is a data-only reference entity whose behaviour is DELEGATED to a foreign utility (static methods that take it as their first parameter and hold its logic) — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants rather than being driven from outside.
Duplicated block (5 lines × 2) RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:34— RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:34-38 | RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:52-56 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) RxSwift/Observables/Materialize.swift:38— RxSwift/Observables/Materialize.swift:38-42 | Sources/RxSwift/Materialize.swift:38-42 — before extracting anything, compare `RxSwift/Observables/Materialize.swift` and `Sources/RxSwift/Materialize.swift` 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 (5 lines × 2) RxSwift/Observables/Repeat.swift:34— RxSwift/Observables/Repeat.swift:34-38 | Sources/RxSwift/Repeat.swift:34-38 — before extracting anything, compare `RxSwift/Observables/Repeat.swift` and `Sources/RxSwift/Repeat.swift` 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 (5 lines × 2) RxSwift/Observables/Skip.swift:88— RxSwift/Observables/Skip.swift:88-92 | Sources/RxSwift/Skip.swift:88-92 — before extracting anything, compare `RxSwift/Observables/Skip.swift` and `Sources/RxSwift/Skip.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 60 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) RxSwift/Schedulers/VirtualTimeScheduler.swift:84— RxSwift/Schedulers/VirtualTimeScheduler.swift:84-88 | Sources/RxSwift/VirtualTimeScheduler.swift:84-88 — before extracting anything, compare `RxSwift/Schedulers/VirtualTimeScheduler.swift` and `Sources/RxSwift/VirtualTimeScheduler.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 119 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) RxCocoa/Traits/Signal/Signal.swift:33— RxCocoa/Traits/Signal/Signal.swift:33-37 | Sources/RxCocoa/Signal.swift:33-44 — before extracting anything, compare `RxCocoa/Traits/Signal/Signal.swift` and `Sources/RxCocoa/Signal.swift` 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 `Sources/RxCocoa/Signal.swift:33` 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 (5 lines × 2) RxSwift/Disposables/CompositeDisposable.swift:31— RxSwift/Disposables/CompositeDisposable.swift:31-35 | Sources/RxSwift/CompositeDisposable.swift:31-35 — before extracting anything, compare `RxSwift/Disposables/CompositeDisposable.swift` and `Sources/RxSwift/CompositeDisposable.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Observables/Delay.swift:53— RxSwift/Observables/Delay.swift:53-57 | Sources/RxSwift/Delay.swift:53-57 — before extracting anything, compare `RxSwift/Observables/Delay.swift` and `Sources/RxSwift/Delay.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 97 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) RxSwift/Observables/DistinctUntilChanged.swift:133— RxSwift/Observables/DistinctUntilChanged.swift:133-137 | Sources/RxSwift/DistinctUntilChanged.swift:133-137 — before extracting anything, compare `RxSwift/Observables/DistinctUntilChanged.swift` and `Sources/RxSwift/DistinctUntilChanged.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Observables/Do.swift:59— RxSwift/Observables/Do.swift:59-63 | Sources/RxSwift/Do.swift:59-63 — before extracting anything, compare `RxSwift/Observables/Do.swift` and `Sources/RxSwift/Do.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Observables/Generate.swift:34— RxSwift/Observables/Generate.swift:34-38 | Sources/RxSwift/Generate.swift:34-38 — before extracting anything, compare `RxSwift/Observables/Generate.swift` and `Sources/RxSwift/Generate.swift` as WHOLE FILES: this scan already matched 4 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.
Duplicated block (5 lines × 2) RxSwift/Observables/GroupBy.swift:34— RxSwift/Observables/GroupBy.swift:34-38 | Sources/RxSwift/GroupBy.swift:34-38 — before extracting anything, compare `RxSwift/Observables/GroupBy.swift` and `Sources/RxSwift/GroupBy.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 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) RxSwift/Observables/GroupBy.swift:53— RxSwift/Observables/GroupBy.swift:53-57 | Sources/RxSwift/GroupBy.swift:53-57 — before extracting anything, compare `RxSwift/Observables/GroupBy.swift` and `Sources/RxSwift/GroupBy.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 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) RxSwift/Observables/Just.swift:82— RxSwift/Observables/Just.swift:82-86 | Sources/RxSwift/Just.swift:82-86 — before extracting anything, compare `RxSwift/Observables/Just.swift` and `Sources/RxSwift/Just.swift` 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) RxSwift/Observables/Multicast.swift:422— RxSwift/Observables/Multicast.swift:422-426 | Sources/RxSwift/Multicast.swift:422-426 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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) RxSwift/Observables/ObserveOn.swift:101— RxSwift/Observables/ObserveOn.swift:101-105 | Sources/RxSwift/ObserveOn.swift:101-105 — before extracting anything, compare `RxSwift/Observables/ObserveOn.swift` and `Sources/RxSwift/ObserveOn.swift` as WHOLE FILES: this scan already matched 9 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 (5 lines × 2) RxSwift/Observables/RetryWhen.swift:162— RxSwift/Observables/RetryWhen.swift:162-166 | Sources/RxSwift/RetryWhen.swift:162-166 — before extracting anything, compare `RxSwift/Observables/RetryWhen.swift` and `Sources/RxSwift/RetryWhen.swift` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (5 lines × 2) RxSwift/Observables/RetryWhen.swift:193— RxSwift/Observables/RetryWhen.swift:193-197 | Sources/RxSwift/RetryWhen.swift:193-197 — before extracting anything, compare `RxSwift/Observables/RetryWhen.swift` and `Sources/RxSwift/RetryWhen.swift` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (5 lines × 2) RxSwift/Observables/Sample.swift:93— RxSwift/Observables/Sample.swift:93-97 | Sources/RxSwift/Sample.swift:93-97 — before extracting anything, compare `RxSwift/Observables/Sample.swift` and `Sources/RxSwift/Sample.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 50 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) RxSwift/Observables/Sample.swift:129— RxSwift/Observables/Sample.swift:129-133 | Sources/RxSwift/Sample.swift:129-133 — before extracting anything, compare `RxSwift/Observables/Sample.swift` and `Sources/RxSwift/Sample.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 50 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) RxSwift/Observables/Scan.swift:55— RxSwift/Observables/Scan.swift:55-59 | Sources/RxSwift/Scan.swift:55-59 — before extracting anything, compare `RxSwift/Observables/Scan.swift` and `Sources/RxSwift/Scan.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Observables/Scan.swift:88— RxSwift/Observables/Scan.swift:88-92 | Sources/RxSwift/Scan.swift:88-92 — before extracting anything, compare `RxSwift/Observables/Scan.swift` and `Sources/RxSwift/Scan.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Observables/StartWith.swift:29— RxSwift/Observables/StartWith.swift:29-33 | Sources/RxSwift/StartWith.swift:29-33 — before extracting anything, compare `RxSwift/Observables/StartWith.swift` and `Sources/RxSwift/StartWith.swift` 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) RxSwift/Observables/Switch.swift:84— RxSwift/Observables/Switch.swift:84-88 | Sources/RxSwift/Switch.swift:84-88 — before extracting anything, compare `RxSwift/Observables/Switch.swift` and `Sources/RxSwift/Switch.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 83 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) RxSwift/Observables/Switch.swift:156— RxSwift/Observables/Switch.swift:156-160 | Sources/RxSwift/Switch.swift:156-160 — before extracting anything, compare `RxSwift/Observables/Switch.swift` and `Sources/RxSwift/Switch.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 83 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) RxCocoa/Common/DelegateProxy.swift:226— RxCocoa/Common/DelegateProxy.swift:226-231 | Sources/RxCocoa/DelegateProxy.swift:226-231 — before extracting anything, compare `RxCocoa/Common/DelegateProxy.swift` and `Sources/RxCocoa/DelegateProxy.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 106 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) RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:26— RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:26-31 | RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:48-53 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift: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 (6 lines × 2) RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:31— RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:31-36 | RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:38-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:31` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:51— RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:51-56 | RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:54-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:51` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:49` calls `AnimationConfiguration` and `RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:52` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) RxSwift/Observables/AddRef.swift:37— RxSwift/Observables/AddRef.swift:37-42 | Sources/RxSwift/AddRef.swift:37-42 — before extracting anything, compare `RxSwift/Observables/AddRef.swift` and `Sources/RxSwift/AddRef.swift` 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) RxSwift/Observables/Deferred.swift:68— RxSwift/Observables/Deferred.swift:68-73 | Sources/RxSwift/Deferred.swift:68-73 — before extracting anything, compare `RxSwift/Observables/Deferred.swift` and `Sources/RxSwift/Deferred.swift` 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 (6 lines × 2) RxSwift/Observables/Multicast.swift:366— RxSwift/Observables/Multicast.swift:366-371 | Sources/RxSwift/Multicast.swift:366-371 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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 (6 lines × 2) RxSwift/Observables/StartWith.swift:36— RxSwift/Observables/StartWith.swift:36-41 | Sources/RxSwift/StartWith.swift:36-41 — before extracting anything, compare `RxSwift/Observables/StartWith.swift` and `Sources/RxSwift/StartWith.swift` 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) Sources/AllTestz/Anomalies.swift:94— Sources/AllTestz/Anomalies.swift:94-99 | Sources/AllTestz/Anomalies.swift:172-177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Anomalies.swift:94` 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 (6 lines × 2) Sources/RxCocoa/Signal+Subscription.swift:160— Sources/RxCocoa/Signal+Subscription.swift:160-165 | Sources/RxSwift/Infallible.swift:76-85 — 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 `Sources/RxCocoa/Signal+Subscription.swift:160` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) Sources/RxSwift/Completable.swift:91— Sources/RxSwift/Completable.swift:91-96 | Sources/RxSwift/Single.swift:103-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/RxSwift/Completable.swift:91` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift:33— RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift:33-38 | Sources/RxCocoa/RxScrollViewDelegateProxy.swift:33-38 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift` and `Sources/RxCocoa/RxScrollViewDelegateProxy.swift` 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 (6 lines × 2) RxCocoa/macOS/NSTextView+Rx.swift:46— RxCocoa/macOS/NSTextView+Rx.swift:46-51 | Sources/RxCocoa/NSTextView+Rx.swift:46-51 — before extracting anything, compare `RxCocoa/macOS/NSTextView+Rx.swift` and `Sources/RxCocoa/NSTextView+Rx.swift` 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) RxSwift/Disposables/CompositeDisposable.swift:38— RxSwift/Disposables/CompositeDisposable.swift:38-43 | Sources/RxSwift/CompositeDisposable.swift:38-43 — before extracting anything, compare `RxSwift/Disposables/CompositeDisposable.swift` and `Sources/RxSwift/CompositeDisposable.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Disposables/CompositeDisposable.swift:82— RxSwift/Disposables/CompositeDisposable.swift:82-87 | Sources/RxSwift/CompositeDisposable.swift:82-87 — before extracting anything, compare `RxSwift/Disposables/CompositeDisposable.swift` and `Sources/RxSwift/CompositeDisposable.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Observables/Amb.swift:69— RxSwift/Observables/Amb.swift:69-74 | Sources/RxSwift/Amb.swift:69-74 — before extracting anything, compare `RxSwift/Observables/Amb.swift` and `Sources/RxSwift/Amb.swift` as WHOLE FILES: this scan already matched 4 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) RxSwift/Observables/Debug.swift:66— RxSwift/Observables/Debug.swift:66-71 | Sources/RxSwift/Debug.swift:66-71 — before extracting anything, compare `RxSwift/Observables/Debug.swift` and `Sources/RxSwift/Debug.swift` 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 (6 lines × 2) RxSwift/Observables/ElementAt.swift:47— RxSwift/Observables/ElementAt.swift:47-52 | Sources/RxSwift/ElementAt.swift:47-52 — before extracting anything, compare `RxSwift/Observables/ElementAt.swift` and `Sources/RxSwift/ElementAt.swift` as WHOLE FILES: this scan already matched 4 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 (6 lines × 2) RxSwift/Observables/GroupBy.swift:104— RxSwift/Observables/GroupBy.swift:104-109 | Sources/RxSwift/GroupBy.swift:104-109 — before extracting anything, compare `RxSwift/Observables/GroupBy.swift` and `Sources/RxSwift/GroupBy.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 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) RxSwift/Observables/Multicast.swift:161— RxSwift/Observables/Multicast.swift:161-166 | Sources/RxSwift/Multicast.swift:161-166 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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) RxSwift/Observables/Multicast.swift:214— RxSwift/Observables/Multicast.swift:214-219 | Sources/RxSwift/Multicast.swift:214-219 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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) RxSwift/Observables/Reduce.swift:53— RxSwift/Observables/Reduce.swift:53-58 | Sources/RxSwift/Reduce.swift:53-58 — before extracting anything, compare `RxSwift/Observables/Reduce.swift` and `Sources/RxSwift/Reduce.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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) RxSwift/Observables/Reduce.swift:95— RxSwift/Observables/Reduce.swift:95-100 | Sources/RxSwift/Reduce.swift:95-100 — before extracting anything, compare `RxSwift/Observables/Reduce.swift` and `Sources/RxSwift/Reduce.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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) RxSwift/Observables/Repeat.swift:51— RxSwift/Observables/Repeat.swift:51-56 | Sources/RxSwift/Repeat.swift:51-56 — before extracting anything, compare `RxSwift/Observables/Repeat.swift` and `Sources/RxSwift/Repeat.swift` 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 (6 lines × 2) RxSwift/Observables/RetryWhen.swift:186— RxSwift/Observables/RetryWhen.swift:186-191 | Sources/RxSwift/RetryWhen.swift:186-191 — before extracting anything, compare `RxSwift/Observables/RetryWhen.swift` and `Sources/RxSwift/RetryWhen.swift` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (7 lines × 2) RxCocoa/Common/DelegateProxyType.swift:414— RxCocoa/Common/DelegateProxyType.swift:414-420 | Sources/RxCocoa/DelegateProxyType.swift:414-420 — before extracting anything, compare `RxCocoa/Common/DelegateProxyType.swift` and `Sources/RxCocoa/DelegateProxyType.swift` 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) RxExample/RxExample/Feedbacks.swift:91— RxExample/RxExample/Feedbacks.swift:91-97 | RxExample/RxExample/Feedbacks.swift:118-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `RxExample/RxExample/Feedbacks.swift:91` 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 (7 lines × 2) RxSwift/Observables/DelaySubscription.swift:53— RxSwift/Observables/DelaySubscription.swift:53-59 | Sources/RxSwift/DelaySubscription.swift:53-59 — before extracting anything, compare `RxSwift/Observables/DelaySubscription.swift` and `Sources/RxSwift/DelaySubscription.swift` 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 (7 lines × 2) RxSwift/Observables/Do.swift:92— RxSwift/Observables/Do.swift:92-98 | Sources/RxSwift/Do.swift:92-98 — before extracting anything, compare `RxSwift/Observables/Do.swift` and `Sources/RxSwift/Do.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Observables/Generate.swift:72— RxSwift/Observables/Generate.swift:72-78 | Sources/RxSwift/Generate.swift:72-78 — before extracting anything, compare `RxSwift/Observables/Generate.swift` and `Sources/RxSwift/Generate.swift` as WHOLE FILES: this scan already matched 4 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 (7 lines × 2) scripts/package-spm.swift:209— scripts/package-spm.swift:209-216 | scripts/package-spm.swift:257-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/package-spm.swift:209` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) RxCocoa/RxCocoa.swift:96— RxCocoa/RxCocoa.swift:96-102 | Sources/RxCocoa/RxCocoa.swift:96-102 — before extracting anything, compare `RxCocoa/RxCocoa.swift` and `Sources/RxCocoa/RxCocoa.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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) RxCocoa/RxCocoa.swift:104— RxCocoa/RxCocoa.swift:104-110 | Sources/RxCocoa/RxCocoa.swift:104-110 — before extracting anything, compare `RxCocoa/RxCocoa.swift` and `Sources/RxCocoa/RxCocoa.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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) RxCocoa/iOS/UIBarButtonItem+Rx.swift:45— RxCocoa/iOS/UIBarButtonItem+Rx.swift:45-51 | Sources/RxCocoa/UIBarButtonItem+Rx.swift:45-51 — before extracting anything, compare `RxCocoa/iOS/UIBarButtonItem+Rx.swift` and `Sources/RxCocoa/UIBarButtonItem+Rx.swift` 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) RxExample/Extensions/CLLocationManager+Rx.swift:208— RxExample/Extensions/CLLocationManager+Rx.swift:208-214 | RxExample/Extensions/UIImagePickerController+Rx.swift:39-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) RxSwift/Disposables/CompositeDisposable.swift:112— RxSwift/Disposables/CompositeDisposable.swift:112-118 | Sources/RxSwift/CompositeDisposable.swift:112-118 — before extracting anything, compare `RxSwift/Disposables/CompositeDisposable.swift` and `Sources/RxSwift/CompositeDisposable.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Observables/Catch.swift:165— RxSwift/Observables/Catch.swift:165-171 | Sources/RxSwift/Catch.swift:165-171 — before extracting anything, compare `RxSwift/Observables/Catch.swift` and `Sources/RxSwift/Catch.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 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) RxSwift/Observables/Catch.swift:255— RxSwift/Observables/Catch.swift:255-261 | Sources/RxSwift/Catch.swift:255-261 — before extracting anything, compare `RxSwift/Observables/Catch.swift` and `Sources/RxSwift/Catch.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 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) RxSwift/Observables/GroupBy.swift:59— RxSwift/Observables/GroupBy.swift:59-65 | Sources/RxSwift/GroupBy.swift:59-65 — before extracting anything, compare `RxSwift/Observables/GroupBy.swift` and `Sources/RxSwift/GroupBy.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 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) RxSwift/Observables/Materialize.swift:21— RxSwift/Observables/Materialize.swift:21-27 | Sources/RxSwift/Materialize.swift:21-27 — before extracting anything, compare `RxSwift/Observables/Materialize.swift` and `Sources/RxSwift/Materialize.swift` 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) RxSwift/Observables/ObserveOn.swift:151— RxSwift/Observables/ObserveOn.swift:151-157 | Sources/RxSwift/ObserveOn.swift:151-157 — before extracting anything, compare `RxSwift/Observables/ObserveOn.swift` and `Sources/RxSwift/ObserveOn.swift` as WHOLE FILES: this scan already matched 9 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 (7 lines × 2) RxSwift/Observables/Optional.swift:88— RxSwift/Observables/Optional.swift:88-94 | Sources/RxSwift/Optional.swift:88-94 — before extracting anything, compare `RxSwift/Observables/Optional.swift` and `Sources/RxSwift/Optional.swift` 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) RxSwift/Observables/ShareReplayScope.swift:346— RxSwift/Observables/ShareReplayScope.swift:346-352 | Sources/RxSwift/ShareReplayScope.swift:346-352 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Duplicated block (7 lines × 2) RxSwift/Observables/Window.swift:58— RxSwift/Observables/Window.swift:58-64 | Sources/RxSwift/Window.swift:58-64 — before extracting anything, compare `RxSwift/Observables/Window.swift` and `Sources/RxSwift/Window.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 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) RxSwift/Observables/Zip+Collection.swift:93— RxSwift/Observables/Zip+Collection.swift:93-99 | Sources/RxSwift/Zip+Collection.swift:93-99 — before extracting anything, compare `RxSwift/Observables/Zip+Collection.swift` and `Sources/RxSwift/Zip+Collection.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 154 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) RxSwift/Observables/Zip.swift:99— RxSwift/Observables/Zip.swift:99-105 | Sources/RxSwift/Zip.swift:99-105 — before extracting anything, compare `RxSwift/Observables/Zip.swift` and `Sources/RxSwift/Zip.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 72 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) RxSwift/Rx.swift:52— RxSwift/Rx.swift:52-58 | Sources/RxSwift/Rx.swift:52-58 — before extracting anything, compare `RxSwift/Rx.swift` and `Sources/RxSwift/Rx.swift` as WHOLE FILES: this scan already matched 5 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. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (7 lines × 2) RxSwift/Rx.swift:60— RxSwift/Rx.swift:60-66 | Sources/RxSwift/Rx.swift:60-66 — before extracting anything, compare `RxSwift/Rx.swift` and `Sources/RxSwift/Rx.swift` as WHOLE FILES: this scan already matched 5 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. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (7 lines × 2) RxSwift/Schedulers/MainScheduler.swift:50— RxSwift/Schedulers/MainScheduler.swift:50-56 | Sources/RxSwift/MainScheduler.swift:50-56 — before extracting anything, compare `RxSwift/Schedulers/MainScheduler.swift` and `Sources/RxSwift/MainScheduler.swift` 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) RxSwift/Schedulers/SchedulerServices+Emulation.swift:26— RxSwift/Schedulers/SchedulerServices+Emulation.swift:26-32 | Sources/RxSwift/SchedulerServices+Emulation.swift:26-32 — before extracting anything, compare `RxSwift/Schedulers/SchedulerServices+Emulation.swift` and `Sources/RxSwift/SchedulerServices+Emulation.swift` 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 (9 lines × 2) RxSwift/Disposables/CompositeDisposable.swift:48— RxSwift/Disposables/CompositeDisposable.swift:48-56 | Sources/RxSwift/CompositeDisposable.swift:48-56 — before extracting anything, compare `RxSwift/Disposables/CompositeDisposable.swift` and `Sources/RxSwift/CompositeDisposable.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Observables/SkipUntil.swift:128— RxSwift/Observables/SkipUntil.swift:128-136 | Sources/RxSwift/SkipUntil.swift:128-136 — before extracting anything, compare `RxSwift/Observables/SkipUntil.swift` and `Sources/RxSwift/SkipUntil.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Observables/WithLatestFrom.swift:59— RxSwift/Observables/WithLatestFrom.swift:59-67 | Sources/RxSwift/WithLatestFrom.swift:59-67 — before extracting anything, compare `RxSwift/Observables/WithLatestFrom.swift` and `Sources/RxSwift/WithLatestFrom.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 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) RxSwift/Rx.swift:124— RxSwift/Rx.swift:124-132 | Sources/RxSwift/Rx.swift:124-132 — before extracting anything, compare `RxSwift/Rx.swift` and `Sources/RxSwift/Rx.swift` as WHOLE FILES: this scan already matched 5 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 (9 lines × 2) Sources/RxSwift/Maybe.swift:64— Sources/RxSwift/Maybe.swift:64-72 | Sources/RxSwift/Single.swift:52-60 — before extracting anything, compare `Sources/RxSwift/Maybe.swift` and `Sources/RxSwift/Single.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/RxSwift/Maybe.swift:64` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) RxCocoa/iOS/Proxies/RxNavigationControllerDelegateProxy.swift:27— RxCocoa/iOS/Proxies/RxNavigationControllerDelegateProxy.swift:27-35 | Sources/RxCocoa/RxNavigationControllerDelegateProxy.swift:27-35 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxNavigationControllerDelegateProxy.swift` and `Sources/RxCocoa/RxNavigationControllerDelegateProxy.swift` 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) RxCocoa/iOS/Proxies/RxPickerViewDelegateProxy.swift:26— RxCocoa/iOS/Proxies/RxPickerViewDelegateProxy.swift:26-34 | Sources/RxCocoa/RxPickerViewDelegateProxy.swift:26-34 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxPickerViewDelegateProxy.swift` and `Sources/RxCocoa/RxPickerViewDelegateProxy.swift` 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) RxCocoa/iOS/Proxies/RxSearchBarDelegateProxy.swift:27— RxCocoa/iOS/Proxies/RxSearchBarDelegateProxy.swift:27-35 | Sources/RxCocoa/RxSearchBarDelegateProxy.swift:27-35 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxSearchBarDelegateProxy.swift` and `Sources/RxCocoa/RxSearchBarDelegateProxy.swift` 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) RxCocoa/iOS/Proxies/RxSearchControllerDelegateProxy.swift:27— RxCocoa/iOS/Proxies/RxSearchControllerDelegateProxy.swift:27-35 | Sources/RxCocoa/RxSearchControllerDelegateProxy.swift:27-35 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxSearchControllerDelegateProxy.swift` and `Sources/RxCocoa/RxSearchControllerDelegateProxy.swift` 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) RxCocoa/iOS/Proxies/RxTabBarControllerDelegateProxy.swift:27— RxCocoa/iOS/Proxies/RxTabBarControllerDelegateProxy.swift:27-35 | Sources/RxCocoa/RxTabBarControllerDelegateProxy.swift:27-35 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxTabBarControllerDelegateProxy.swift` and `Sources/RxCocoa/RxTabBarControllerDelegateProxy.swift` 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) RxCocoa/iOS/Proxies/RxTextStorageDelegateProxy.swift:26— RxCocoa/iOS/Proxies/RxTextStorageDelegateProxy.swift:26-34 | Sources/RxCocoa/RxTextStorageDelegateProxy.swift:26-34 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxTextStorageDelegateProxy.swift` and `Sources/RxCocoa/RxTextStorageDelegateProxy.swift` 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) RxBlocking/RunLoopLock.swift:49— RxBlocking/RunLoopLock.swift:49-57 | Sources/RxBlocking/RunLoopLock.swift:49-57 — before extracting anything, compare `RxBlocking/RunLoopLock.swift` and `Sources/RxBlocking/RunLoopLock.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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) RxCocoa/Foundation/NSObject+Rx.swift:397— RxCocoa/Foundation/NSObject+Rx.swift:397-405 | Sources/RxCocoa/NSObject+Rx.swift:397-405 — before extracting anything, compare `RxCocoa/Foundation/NSObject+Rx.swift` and `Sources/RxCocoa/NSObject+Rx.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 96 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) RxSwift/Disposables/CompositeDisposable.swift:72— RxSwift/Disposables/CompositeDisposable.swift:72-80 | Sources/RxSwift/CompositeDisposable.swift:72-80 — before extracting anything, compare `RxSwift/Disposables/CompositeDisposable.swift` and `Sources/RxSwift/CompositeDisposable.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Observables/AddRef.swift:16— RxSwift/Observables/AddRef.swift:16-24 | Sources/RxSwift/AddRef.swift:16-24 — before extracting anything, compare `RxSwift/Observables/AddRef.swift` and `Sources/RxSwift/AddRef.swift` 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 (9 lines × 2) RxSwift/Observables/Amb.swift:59— RxSwift/Observables/Amb.swift:59-67 | Sources/RxSwift/Amb.swift:59-67 — before extracting anything, compare `RxSwift/Observables/Amb.swift` and `Sources/RxSwift/Amb.swift` as WHOLE FILES: this scan already matched 4 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 (9 lines × 2) RxSwift/Observables/Catch.swift:245— RxSwift/Observables/Catch.swift:245-253 | Sources/RxSwift/Catch.swift:245-253 — before extracting anything, compare `RxSwift/Observables/Catch.swift` and `Sources/RxSwift/Catch.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 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) RxSwift/Observables/ElementAt.swift:92— RxSwift/Observables/ElementAt.swift:92-100 | Sources/RxSwift/ElementAt.swift:92-100 — before extracting anything, compare `RxSwift/Observables/ElementAt.swift` and `Sources/RxSwift/ElementAt.swift` as WHOLE FILES: this scan already matched 4 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 (9 lines × 2) RxSwift/Observables/Multicast.swift:168— RxSwift/Observables/Multicast.swift:168-176 | Sources/RxSwift/Multicast.swift:168-176 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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) RxSwift/Observables/ObserveOn.swift:223— RxSwift/Observables/ObserveOn.swift:223-231 | Sources/RxSwift/ObserveOn.swift:223-231 — before extracting anything, compare `RxSwift/Observables/ObserveOn.swift` and `Sources/RxSwift/ObserveOn.swift` as WHOLE FILES: this scan already matched 9 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) RxSwift/Observables/TakeWithPredicate.swift:288— RxSwift/Observables/TakeWithPredicate.swift:288-296 | Sources/RxSwift/TakeWithPredicate.swift:288-296 — before extracting anything, compare `RxSwift/Observables/TakeWithPredicate.swift` and `Sources/RxSwift/TakeWithPredicate.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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) RxSwift/Observables/Timer.swift:85— RxSwift/Observables/Timer.swift:85-93 | Sources/RxSwift/Timer.swift:85-93 — before extracting anything, compare `RxSwift/Observables/Timer.swift` and `Sources/RxSwift/Timer.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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) RxSwift/Schedulers/VirtualTimeScheduler.swift:201— RxSwift/Schedulers/VirtualTimeScheduler.swift:201-209 | Sources/RxSwift/VirtualTimeScheduler.swift:201-209 — before extracting anything, compare `RxSwift/Schedulers/VirtualTimeScheduler.swift` and `Sources/RxSwift/VirtualTimeScheduler.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 119 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) Sources/RxCocoa/ControlEvent+Driver.swift:15— Sources/RxCocoa/ControlEvent+Driver.swift:15-23 | Sources/RxCocoa/ControlProperty+Driver.swift:15-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) RxCocoa/iOS/UIActivityIndicatorView+Rx.swift:16— RxCocoa/iOS/UIActivityIndicatorView+Rx.swift:16-24 | RxCocoa/iOS/UIRefreshControl+Rx.swift:16-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) RxCocoa/Common/ControlTarget.swift:35— RxCocoa/Common/ControlTarget.swift:35-50 | Sources/RxCocoa/ControlTarget.swift:35-50 — before extracting anything, compare `RxCocoa/Common/ControlTarget.swift` and `Sources/RxCocoa/ControlTarget.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 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) RxCocoa/Common/ControlTarget.swift:53— RxCocoa/Common/ControlTarget.swift:53-68 | Sources/RxCocoa/ControlTarget.swift:53-68 — before extracting anything, compare `RxCocoa/Common/ControlTarget.swift` and `Sources/RxCocoa/ControlTarget.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 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) RxCocoa/Common/DelegateProxy.swift:204— RxCocoa/Common/DelegateProxy.swift:204-219 | Sources/RxCocoa/DelegateProxy.swift:204-219 — before extracting anything, compare `RxCocoa/Common/DelegateProxy.swift` and `Sources/RxCocoa/DelegateProxy.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 106 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) RxCocoa/Common/DelegateProxy.swift:265— RxCocoa/Common/DelegateProxy.swift:265-280 | Sources/RxCocoa/DelegateProxy.swift:265-280 — before extracting anything, compare `RxCocoa/Common/DelegateProxy.swift` and `Sources/RxCocoa/DelegateProxy.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 106 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) RxSwift/Binder.swift:29— RxSwift/Binder.swift:29-44 | Sources/RxSwift/Binder.swift:29-44 — before extracting anything, compare `RxSwift/Binder.swift` and `Sources/RxSwift/Binder.swift` 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) RxSwift/Observables/DefaultIfEmpty.swift:33— RxSwift/Observables/DefaultIfEmpty.swift:33-48 | Sources/RxSwift/DefaultIfEmpty.swift:33-48 — before extracting anything, compare `RxSwift/Observables/DefaultIfEmpty.swift` and `Sources/RxSwift/DefaultIfEmpty.swift` 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) RxSwift/Observables/GroupBy.swift:67— RxSwift/Observables/GroupBy.swift:67-82 | Sources/RxSwift/GroupBy.swift:67-82 — before extracting anything, compare `RxSwift/Observables/GroupBy.swift` and `Sources/RxSwift/GroupBy.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 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) RxSwift/Observables/Optional.swift:47— RxSwift/Observables/Optional.swift:47-62 | Sources/RxSwift/Optional.swift:47-62 — before extracting anything, compare `RxSwift/Observables/Optional.swift` and `Sources/RxSwift/Optional.swift` 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 (16 lines × 2) RxSwift/Observables/Producer.swift:52— RxSwift/Observables/Producer.swift:52-67 | Sources/RxSwift/Producer.swift:52-67 — before extracting anything, compare `RxSwift/Observables/Producer.swift` and `Sources/RxSwift/Producer.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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) RxSwift/Observables/ShareReplayScope.swift:280— RxSwift/Observables/ShareReplayScope.swift:280-295 | Sources/RxSwift/ShareReplayScope.swift:280-295 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Duplicated block (16 lines × 2) RxSwift/Observables/ShareReplayScope.swift:421— RxSwift/Observables/ShareReplayScope.swift:421-436 | Sources/RxSwift/ShareReplayScope.swift:421-436 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Duplicated block (16 lines × 2) RxSwift/Observables/Skip.swift:60— RxSwift/Observables/Skip.swift:60-75 | Sources/RxSwift/Skip.swift:60-75 — before extracting anything, compare `RxSwift/Observables/Skip.swift` and `Sources/RxSwift/Skip.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 60 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) RxSwift/Observables/SubscribeOn.swift:73— RxSwift/Observables/SubscribeOn.swift:73-88 | Sources/RxSwift/SubscribeOn.swift:73-88 — before extracting anything, compare `RxSwift/Observables/SubscribeOn.swift` and `Sources/RxSwift/SubscribeOn.swift` 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) RxSwift/Observables/Switch.swift:94— RxSwift/Observables/Switch.swift:94-109 | Sources/RxSwift/Switch.swift:94-109 — before extracting anything, compare `RxSwift/Observables/Switch.swift` and `Sources/RxSwift/Switch.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 83 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) RxSwift/Observables/Zip+Collection.swift:208— RxSwift/Observables/Zip+Collection.swift:208-223 | Sources/RxSwift/Zip+Collection.swift:208-223 — before extracting anything, compare `RxSwift/Observables/Zip+Collection.swift` and `Sources/RxSwift/Zip+Collection.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 154 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 `RxSwift/Observables/Zip+Collection.swift:208` 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 × 2) RxSwift/Schedulers/VirtualTimeScheduler.swift:111— RxSwift/Schedulers/VirtualTimeScheduler.swift:111-126 | Sources/RxSwift/VirtualTimeScheduler.swift:111-126 — before extracting anything, compare `RxSwift/Schedulers/VirtualTimeScheduler.swift` and `Sources/RxSwift/VirtualTimeScheduler.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 119 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) RxSwift/Subjects/AsyncSubject.swift:59— RxSwift/Subjects/AsyncSubject.swift:59-74 | Sources/RxSwift/AsyncSubject.swift:59-74 — before extracting anything, compare `RxSwift/Subjects/AsyncSubject.swift` and `Sources/RxSwift/AsyncSubject.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (16 lines × 2) RxSwift/Subjects/BehaviorSubject.swift:109— RxSwift/Subjects/BehaviorSubject.swift:109-124 | Sources/RxSwift/BehaviorSubject.swift:109-124 — before extracting anything, compare `RxSwift/Subjects/BehaviorSubject.swift` and `Sources/RxSwift/BehaviorSubject.swift` as WHOLE FILES: this scan already matched 4 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 (16 lines × 2) RxSwift/Schedulers/Internal/ScheduledItem.swift:20— RxSwift/Schedulers/Internal/ScheduledItem.swift:20-35 | Sources/RxSwift/ScheduledItem.swift:20-35 — before extracting anything, compare `RxSwift/Schedulers/Internal/ScheduledItem.swift` and `Sources/RxSwift/ScheduledItem.swift` 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) RxSwift/Observables/SkipUntil.swift:111— RxSwift/Observables/SkipUntil.swift:111-126 | Sources/RxSwift/SkipUntil.swift:111-126 — before extracting anything, compare `RxSwift/Observables/SkipUntil.swift` and `Sources/RxSwift/SkipUntil.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 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) RxCocoa/Foundation/NSObject+Rx.swift:439— RxCocoa/Foundation/NSObject+Rx.swift:439-450 | Sources/RxCocoa/NSObject+Rx.swift:439-450 — before extracting anything, compare `RxCocoa/Foundation/NSObject+Rx.swift` and `Sources/RxCocoa/NSObject+Rx.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 96 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) RxSwift/Observables/Sequence.swift:60— RxSwift/Observables/Sequence.swift:60-71 | Sources/RxSwift/Sequence.swift:60-71 — before extracting anything, compare `RxSwift/Observables/Sequence.swift` and `Sources/RxSwift/Sequence.swift` 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) RxSwift/Observables/SkipUntil.swift:67— RxSwift/Observables/SkipUntil.swift:67-78 | Sources/RxSwift/SkipUntil.swift:67-78 — before extracting anything, compare `RxSwift/Observables/SkipUntil.swift` and `Sources/RxSwift/SkipUntil.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Observables/TakeWithPredicate.swift:152— RxSwift/Observables/TakeWithPredicate.swift:152-163 | Sources/RxSwift/TakeWithPredicate.swift:152-163 — before extracting anything, compare `RxSwift/Observables/TakeWithPredicate.swift` and `Sources/RxSwift/TakeWithPredicate.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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) RxSwift/Observables/Using.swift:55— RxSwift/Observables/Using.swift:55-66 | Sources/RxSwift/Using.swift:55-66 — before extracting anything, compare `RxSwift/Observables/Using.swift` and `Sources/RxSwift/Using.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Subjects/ReplaySubject.swift:206— RxSwift/Subjects/ReplaySubject.swift:206-217 | Sources/RxSwift/ReplaySubject.swift:206-217 — before extracting anything, compare `RxSwift/Subjects/ReplaySubject.swift` and `Sources/RxSwift/ReplaySubject.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 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) RxSwift/Traits/PrimitiveSequence/Completable+AndThen.swift:94— RxSwift/Traits/PrimitiveSequence/Completable+AndThen.swift:94-105 | Sources/RxSwift/Completable+AndThen.swift:94-105 — before extracting anything, compare `RxSwift/Traits/PrimitiveSequence/Completable+AndThen.swift` and `Sources/RxSwift/Completable+AndThen.swift` 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.
Duplicated block (12 lines × 2) Sources/AllTestz/Completable+AndThen.swift:238— Sources/AllTestz/Completable+AndThen.swift:238-249 | Sources/AllTestz/Completable+AndThen.swift:268-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:238` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Sources/AllTestz/Completable+AndThen.swift:364— Sources/AllTestz/Completable+AndThen.swift:364-375 | Sources/AllTestz/Completable+AndThen.swift:394-405 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:364` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Sources/AllTestz/Completable+AndThen.swift:518— Sources/AllTestz/Completable+AndThen.swift:518-529 | Sources/AllTestz/Completable+AndThen.swift:548-559 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:518` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Sources/RxCocoa/Signal+Subscription.swift:134— Sources/RxCocoa/Signal+Subscription.swift:134-145 | Sources/RxSwift/Infallible.swift:50-61 — 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 `Sources/RxCocoa/Signal+Subscription.swift:134` 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) RxSwift/Observables/Catch.swift:228— RxSwift/Observables/Catch.swift:228-239 | Sources/RxSwift/Catch.swift:228-239 — before extracting anything, compare `RxSwift/Observables/Catch.swift` and `Sources/RxSwift/Catch.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 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) RxSwift/Observables/Debounce.swift:90— RxSwift/Observables/Debounce.swift:90-101 | Sources/RxSwift/Debounce.swift:90-101 — before extracting anything, compare `RxSwift/Observables/Debounce.swift` and `Sources/RxSwift/Debounce.swift` as WHOLE FILES: this scan already matched 5 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) RxSwift/Observables/Deferred.swift:44— RxSwift/Observables/Deferred.swift:44-55 | Sources/RxSwift/Deferred.swift:44-55 — before extracting anything, compare `RxSwift/Observables/Deferred.swift` and `Sources/RxSwift/Deferred.swift` 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 (12 lines × 2) RxSwift/Observables/Sample.swift:110— RxSwift/Observables/Sample.swift:110-121 | Sources/RxSwift/Sample.swift:110-121 — before extracting anything, compare `RxSwift/Observables/Sample.swift` and `Sources/RxSwift/Sample.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 50 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) RxSwift/Observables/SwitchIfEmpty.swift:95— RxSwift/Observables/SwitchIfEmpty.swift:95-106 | Sources/RxSwift/SwitchIfEmpty.swift:95-106 — before extracting anything, compare `RxSwift/Observables/SwitchIfEmpty.swift` and `Sources/RxSwift/SwitchIfEmpty.swift` 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 (12 lines × 2) RxSwift/Observables/Take.swift:145— RxSwift/Observables/Take.swift:145-156 | Sources/RxSwift/Take.swift:145-156 — before extracting anything, compare `RxSwift/Observables/Take.swift` and `Sources/RxSwift/Take.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 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) RxSwift/Observables/TakeWithPredicate.swift:194— RxSwift/Observables/TakeWithPredicate.swift:194-205 | Sources/RxSwift/TakeWithPredicate.swift:194-205 — before extracting anything, compare `RxSwift/Observables/TakeWithPredicate.swift` and `Sources/RxSwift/TakeWithPredicate.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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) RxSwift/Schedulers/VirtualTimeScheduler.swift:157— RxSwift/Schedulers/VirtualTimeScheduler.swift:157-168 | Sources/RxSwift/VirtualTimeScheduler.swift:157-168 — before extracting anything, compare `RxSwift/Schedulers/VirtualTimeScheduler.swift` and `Sources/RxSwift/VirtualTimeScheduler.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 119 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) RxCocoa/Common/ControlTarget.swift:77— RxCocoa/Common/ControlTarget.swift:77-86 | Sources/RxCocoa/ControlTarget.swift:77-86 — before extracting anything, compare `RxCocoa/Common/ControlTarget.swift` and `Sources/RxCocoa/ControlTarget.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 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) RxCocoa/iOS/UINavigationController+Rx.swift:25— RxCocoa/iOS/UINavigationController+Rx.swift:25-34 | RxCocoa/iOS/UINavigationController+Rx.swift:37-46 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `RxCocoa/iOS/UINavigationController+Rx.swift: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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) RxExample/RxExample/Services/Randomizer.swift:127— RxExample/RxExample/Services/Randomizer.swift:127-136 | RxExample/RxExample/Services/Randomizer.swift:169-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `RxExample/RxExample/Services/Randomizer.swift:127` 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) RxSwift/Observables/SwitchIfEmpty.swift:32— RxSwift/Observables/SwitchIfEmpty.swift:32-41 | Sources/RxSwift/SwitchIfEmpty.swift:32-41 — before extracting anything, compare `RxSwift/Observables/SwitchIfEmpty.swift` and `Sources/RxSwift/SwitchIfEmpty.swift` 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 (10 lines × 2) RxSwift/Observables/Timer.swift:108— RxSwift/Observables/Timer.swift:108-117 | Sources/RxSwift/Timer.swift:108-117 — before extracting anything, compare `RxSwift/Observables/Timer.swift` and `Sources/RxSwift/Timer.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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) RxSwift/Observers/AnonymousObserver.swift:14— RxSwift/Observers/AnonymousObserver.swift:14-23 | Sources/RxSwift/AnonymousObserver.swift:14-23 — before extracting anything, compare `RxSwift/Observers/AnonymousObserver.swift` and `Sources/RxSwift/AnonymousObserver.swift` 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) RxCocoa/Common/DelegateProxy.swift:233— RxCocoa/Common/DelegateProxy.swift:233-242 | Sources/RxCocoa/DelegateProxy.swift:233-242 — before extracting anything, compare `RxCocoa/Common/DelegateProxy.swift` and `Sources/RxCocoa/DelegateProxy.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 106 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) RxCocoa/Traits/ControlProperty.swift:96— RxCocoa/Traits/ControlProperty.swift:96-105 | Sources/RxCocoa/ControlProperty.swift:96-105 — before extracting anything, compare `RxCocoa/Traits/ControlProperty.swift` and `Sources/RxCocoa/ControlProperty.swift` 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) RxCocoa/iOS/Proxies/RxCollectionViewDataSourcePrefetchingProxy.swift:52— RxCocoa/iOS/Proxies/RxCollectionViewDataSourcePrefetchingProxy.swift:52-61 | Sources/RxCocoa/RxCollectionViewDataSourcePrefetchingProxy.swift:52-61 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxCollectionViewDataSourcePrefetchingProxy.swift` and `Sources/RxCocoa/RxCollectionViewDataSourcePrefetchingProxy.swift` 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 (10 lines × 2) RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift:44— RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift:44-53 | Sources/RxCocoa/RxScrollViewDelegateProxy.swift:44-53 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift` and `Sources/RxCocoa/RxScrollViewDelegateProxy.swift` 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 (10 lines × 2) RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift:56— RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift:56-65 | Sources/RxCocoa/RxScrollViewDelegateProxy.swift:56-65 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxScrollViewDelegateProxy.swift` and `Sources/RxCocoa/RxScrollViewDelegateProxy.swift` 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 (10 lines × 2) RxCocoa/iOS/Proxies/RxTableViewDataSourcePrefetchingProxy.swift:52— RxCocoa/iOS/Proxies/RxTableViewDataSourcePrefetchingProxy.swift:52-61 | Sources/RxCocoa/RxTableViewDataSourcePrefetchingProxy.swift:52-61 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxTableViewDataSourcePrefetchingProxy.swift` and `Sources/RxCocoa/RxTableViewDataSourcePrefetchingProxy.swift` 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 (10 lines × 2) RxSwift/Disposables/DisposeBag.swift:70— RxSwift/Disposables/DisposeBag.swift:70-79 | Sources/RxSwift/DisposeBag.swift:70-79 — before extracting anything, compare `RxSwift/Disposables/DisposeBag.swift` and `Sources/RxSwift/DisposeBag.swift` 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) RxSwift/Observables/Buffer.swift:78— RxSwift/Observables/Buffer.swift:78-87 | Sources/RxSwift/Buffer.swift:78-87 — before extracting anything, compare `RxSwift/Observables/Buffer.swift` and `Sources/RxSwift/Buffer.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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) RxSwift/Observables/Catch.swift:141— RxSwift/Observables/Catch.swift:141-150 | Sources/RxSwift/Catch.swift:141-150 — before extracting anything, compare `RxSwift/Observables/Catch.swift` and `Sources/RxSwift/Catch.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 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) RxSwift/Observables/Deferred.swift:33— RxSwift/Observables/Deferred.swift:33-42 | Sources/RxSwift/Deferred.swift:33-42 — before extracting anything, compare `RxSwift/Observables/Deferred.swift` and `Sources/RxSwift/Deferred.swift` 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) RxSwift/Observables/RetryWhen.swift:168— RxSwift/Observables/RetryWhen.swift:168-177 | Sources/RxSwift/RetryWhen.swift:168-177 — before extracting anything, compare `RxSwift/Observables/RetryWhen.swift` and `Sources/RxSwift/RetryWhen.swift` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (10 lines × 2) RxSwift/Observables/Timeout.swift:63— RxSwift/Observables/Timeout.swift:63-72 | Sources/RxSwift/Timeout.swift:63-72 — before extracting anything, compare `RxSwift/Observables/Timeout.swift` and `Sources/RxSwift/Timeout.swift` 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.
Duplicated block (8 lines × 2) RxCocoa/Foundation/NSObject+Rx.swift:363— RxCocoa/Foundation/NSObject+Rx.swift:363-370 | Sources/RxCocoa/NSObject+Rx.swift:363-370 — before extracting anything, compare `RxCocoa/Foundation/NSObject+Rx.swift` and `Sources/RxCocoa/NSObject+Rx.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 96 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) RxCocoa/iOS/UITabBar+Rx.swift:42— RxCocoa/iOS/UITabBar+Rx.swift:42-49 | RxCocoa/iOS/UITabBar+Rx.swift:54-61 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `RxCocoa/iOS/UITabBar+Rx.swift:42` 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 (8 lines × 2) RxExample/RxExample/Feedbacks.swift:121— RxExample/RxExample/Feedbacks.swift:121-128 | RxExample/RxExample/Feedbacks.swift:257-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `RxExample/RxExample/Feedbacks.swift:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) RxSwift/Disposables/SubscriptionDisposable.swift:13— RxSwift/Disposables/SubscriptionDisposable.swift:13-20 | Sources/RxSwift/SubscriptionDisposable.swift:13-20 — before extracting anything, compare `RxSwift/Disposables/SubscriptionDisposable.swift` and `Sources/RxSwift/SubscriptionDisposable.swift` 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) RxSwift/Schedulers/Internal/InvocableScheduledItem.swift:13— RxSwift/Schedulers/Internal/InvocableScheduledItem.swift:13-20 | Sources/RxSwift/InvocableScheduledItem.swift:13-20 — before extracting anything, compare `RxSwift/Schedulers/Internal/InvocableScheduledItem.swift` and `Sources/RxSwift/InvocableScheduledItem.swift` 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) RxSwift/Observables/Error.swift:17— RxSwift/Observables/Error.swift:17-32 | Sources/RxSwift/Error.swift:25-32 — before extracting anything, compare `RxSwift/Observables/Error.swift` and `Sources/RxSwift/Error.swift` 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 `RxSwift/Observables/Error.swift:17` 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 × 2) RxCocoa/RxCocoa.swift:66— RxCocoa/RxCocoa.swift:66-73 | Sources/RxCocoa/RxCocoa.swift:66-73 — before extracting anything, compare `RxCocoa/RxCocoa.swift` and `Sources/RxCocoa/RxCocoa.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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) RxCocoa/RxCocoa.swift:124— RxCocoa/RxCocoa.swift:124-131 | Sources/RxCocoa/RxCocoa.swift:124-131 — before extracting anything, compare `RxCocoa/RxCocoa.swift` and `Sources/RxCocoa/RxCocoa.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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) RxCocoa/RxCocoa.swift:133— RxCocoa/RxCocoa.swift:133-140 | Sources/RxCocoa/RxCocoa.swift:133-140 — before extracting anything, compare `RxCocoa/RxCocoa.swift` and `Sources/RxCocoa/RxCocoa.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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) RxSwift/Observables/Debug.swift:41— RxSwift/Observables/Debug.swift:41-48 | Sources/RxSwift/Debug.swift:41-48 — before extracting anything, compare `RxSwift/Observables/Debug.swift` and `Sources/RxSwift/Debug.swift` 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 (8 lines × 2) RxSwift/Observables/Multicast.swift:404— RxSwift/Observables/Multicast.swift:404-411 | Sources/RxSwift/Multicast.swift:404-411 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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) RxSwift/Observables/ObserveOn.swift:57— RxSwift/Observables/ObserveOn.swift:57-64 | Sources/RxSwift/ObserveOn.swift:57-64 — before extracting anything, compare `RxSwift/Observables/ObserveOn.swift` and `Sources/RxSwift/ObserveOn.swift` as WHOLE FILES: this scan already matched 9 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 (8 lines × 2) RxSwift/Observables/TakeWithPredicate.swift:207— RxSwift/Observables/TakeWithPredicate.swift:207-214 | Sources/RxSwift/TakeWithPredicate.swift:207-214 — before extracting anything, compare `RxSwift/Observables/TakeWithPredicate.swift` and `Sources/RxSwift/TakeWithPredicate.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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) RxSwift/Observables/Timer.swift:65— RxSwift/Observables/Timer.swift:65-72 | Sources/RxSwift/Timer.swift:65-72 — before extracting anything, compare `RxSwift/Observables/Timer.swift` and `Sources/RxSwift/Timer.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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) RxSwift/Observables/Window.swift:49— RxSwift/Observables/Window.swift:49-56 | Sources/RxSwift/Window.swift:49-56 — before extracting anything, compare `RxSwift/Observables/Window.swift` and `Sources/RxSwift/Window.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 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) RxCocoa/iOS/UICollectionView+Rx.swift:356— RxCocoa/iOS/UICollectionView+Rx.swift:356-363 | RxCocoa/iOS/UITableView+Rx.swift:400-407 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `RxCocoa/iOS/UICollectionView+Rx.swift:356` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) RxExample/RxDataSources/Differentiator/Utilities.swift:16— RxExample/RxDataSources/Differentiator/Utilities.swift:16-23 | RxExample/RxDataSources/RxDataSources/DataSources.swift:15-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) Sources/RxCocoa/ObservableConvertibleType+Driver.swift:31— Sources/RxCocoa/ObservableConvertibleType+Driver.swift:31-38 | Sources/RxCocoa/ObservableConvertibleType+Signal.swift:31-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) RxCocoa/Common/DelegateProxyType.swift:391— RxCocoa/Common/DelegateProxyType.swift:391-401 | Sources/RxCocoa/DelegateProxyType.swift:391-401 — before extracting anything, compare `RxCocoa/Common/DelegateProxyType.swift` and `Sources/RxCocoa/DelegateProxyType.swift` 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 (11 lines × 2) RxCocoa/Common/DelegateProxyType.swift:422— RxCocoa/Common/DelegateProxyType.swift:422-432 | Sources/RxCocoa/DelegateProxyType.swift:422-432 — before extracting anything, compare `RxCocoa/Common/DelegateProxyType.swift` and `Sources/RxCocoa/DelegateProxyType.swift` 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 (11 lines × 2) RxCocoa/Foundation/NSObject+Rx.swift:407— RxCocoa/Foundation/NSObject+Rx.swift:407-417 | Sources/RxCocoa/NSObject+Rx.swift:407-417 — before extracting anything, compare `RxCocoa/Foundation/NSObject+Rx.swift` and `Sources/RxCocoa/NSObject+Rx.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 96 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) RxCocoa/RxCocoa.swift:112— RxCocoa/RxCocoa.swift:112-122 | Sources/RxCocoa/RxCocoa.swift:112-122 — before extracting anything, compare `RxCocoa/RxCocoa.swift` and `Sources/RxCocoa/RxCocoa.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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) RxCocoa/Traits/SharedSequence/SchedulerType+SharedSequence.swift:52— RxCocoa/Traits/SharedSequence/SchedulerType+SharedSequence.swift:52-62 | Sources/RxCocoa/SchedulerType+SharedSequence.swift:52-62 — before extracting anything, compare `RxCocoa/Traits/SharedSequence/SchedulerType+SharedSequence.swift` and `Sources/RxCocoa/SchedulerType+SharedSequence.swift` 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) RxSwift/Observables/Do.swift:101— RxSwift/Observables/Do.swift:101-111 | Sources/RxSwift/Do.swift:101-111 — before extracting anything, compare `RxSwift/Observables/Do.swift` and `Sources/RxSwift/Do.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Observables/Just.swift:46— RxSwift/Observables/Just.swift:46-56 | Sources/RxSwift/Just.swift:46-56 — before extracting anything, compare `RxSwift/Observables/Just.swift` and `Sources/RxSwift/Just.swift` 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 (11 lines × 2) RxSwift/Observables/Range.swift:61— RxSwift/Observables/Range.swift:61-71 | Sources/RxSwift/Range.swift:61-71 — before extracting anything, compare `RxSwift/Observables/Range.swift` and `Sources/RxSwift/Range.swift` 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 (11 lines × 2) RxSwift/Observables/WithLatestFrom.swift:120— RxSwift/Observables/WithLatestFrom.swift:120-130 | Sources/RxSwift/WithLatestFrom.swift:120-130 — before extracting anything, compare `RxSwift/Observables/WithLatestFrom.swift` and `Sources/RxSwift/WithLatestFrom.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 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) RxSwift/Schedulers/ConcurrentDispatchQueueScheduler.swift:37— RxSwift/Schedulers/ConcurrentDispatchQueueScheduler.swift:37-47 | Sources/RxSwift/ConcurrentDispatchQueueScheduler.swift:37-47 — before extracting anything, compare `RxSwift/Schedulers/ConcurrentDispatchQueueScheduler.swift` and `Sources/RxSwift/ConcurrentDispatchQueueScheduler.swift` 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) Sources/AllTestz/Completable+AndThen.swift:446— Sources/AllTestz/Completable+AndThen.swift:446-456 | Sources/AllTestz/Completable+AndThen.swift:600-610 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:446` 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) RxSwift/Observable.swift:16— RxSwift/Observable.swift:16-26 | Sources/RxSwift/Observable.swift:16-26 — before extracting anything, compare `RxSwift/Observable.swift` and `Sources/RxSwift/Observable.swift` 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) RxCocoa/iOS/UIBarButtonItem+Rx.swift:53— RxCocoa/iOS/UIBarButtonItem+Rx.swift:53-63 | Sources/RxCocoa/UIBarButtonItem+Rx.swift:53-63 — before extracting anything, compare `RxCocoa/iOS/UIBarButtonItem+Rx.swift` and `Sources/RxCocoa/UIBarButtonItem+Rx.swift` 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) RxSwift/Disposables/DisposeBag.swift:49— RxSwift/Disposables/DisposeBag.swift:49-59 | Sources/RxSwift/DisposeBag.swift:49-59 — before extracting anything, compare `RxSwift/Disposables/DisposeBag.swift` and `Sources/RxSwift/DisposeBag.swift` 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) RxSwift/Observables/Merge.swift:153— RxSwift/Observables/Merge.swift:153-163 | Sources/RxSwift/Merge.swift:153-163 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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) RxSwift/Observables/Multicast.swift:240— RxSwift/Observables/Multicast.swift:240-250 | Sources/RxSwift/Multicast.swift:240-250 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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) RxSwift/Disposables/SingleAssignmentDisposable.swift:55— RxSwift/Disposables/SingleAssignmentDisposable.swift:55-69 | Sources/RxSwift/SingleAssignmentDisposable.swift:55-69 — before extracting anything, compare `RxSwift/Disposables/SingleAssignmentDisposable.swift` and `Sources/RxSwift/SingleAssignmentDisposable.swift` 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 (15 lines × 2) RxSwift/Observables/Debug.swift:50— RxSwift/Observables/Debug.swift:50-64 | Sources/RxSwift/Debug.swift:50-64 — before extracting anything, compare `RxSwift/Observables/Debug.swift` and `Sources/RxSwift/Debug.swift` 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 (15 lines × 2) RxSwift/Observables/Dematerialize.swift:21— RxSwift/Observables/Dematerialize.swift:21-35 | Sources/RxSwift/Dematerialize.swift:21-35 — before extracting anything, compare `RxSwift/Observables/Dematerialize.swift` and `Sources/RxSwift/Dematerialize.swift` 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 (15 lines × 2) RxSwift/Observables/First.swift:12— RxSwift/Observables/First.swift:12-26 | Sources/RxSwift/First.swift:12-26 — before extracting anything, compare `RxSwift/Observables/First.swift` and `Sources/RxSwift/First.swift` 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 (15 lines × 2) RxSwift/Observables/ShareReplayScope.swift:187— RxSwift/Observables/ShareReplayScope.swift:187-201 | Sources/RxSwift/ShareReplayScope.swift:187-201 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Duplicated block (15 lines × 2) RxSwift/Subjects/BehaviorSubject.swift:85— RxSwift/Subjects/BehaviorSubject.swift:85-99 | Sources/RxSwift/BehaviorSubject.swift:85-99 — before extracting anything, compare `RxSwift/Subjects/BehaviorSubject.swift` and `Sources/RxSwift/BehaviorSubject.swift` as WHOLE FILES: this scan already matched 4 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 (15 lines × 2) RxSwift/Subjects/ReplaySubject.swift:142— RxSwift/Subjects/ReplaySubject.swift:142-156 | Sources/RxSwift/ReplaySubject.swift:142-156 — before extracting anything, compare `RxSwift/Subjects/ReplaySubject.swift` and `Sources/RxSwift/ReplaySubject.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 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) Sources/AllTestz/Completable+AndThen.swift:75— Sources/AllTestz/Completable+AndThen.swift:75-89 | Sources/AllTestz/Completable+AndThen.swift:102-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:75` 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 (15 lines × 2) Sources/AllTestz/Completable+AndThen.swift:273— Sources/AllTestz/Completable+AndThen.swift:273-287 | Sources/AllTestz/Completable+AndThen.swift:300-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:273` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AllTestz/Completable+AndThen.swift:315` calls `Subscription` and `Sources/AllTestz/Completable+AndThen.swift:288` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) Sources/AllTestz/Completable+AndThen.swift:399— Sources/AllTestz/Completable+AndThen.swift:399-413 | Sources/AllTestz/Completable+AndThen.swift:426-440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:399` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AllTestz/Completable+AndThen.swift:441` calls `Subscription` and `Sources/AllTestz/Completable+AndThen.swift:414` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) Sources/AllTestz/Completable+AndThen.swift:553— Sources/AllTestz/Completable+AndThen.swift:553-567 | Sources/AllTestz/Completable+AndThen.swift:580-594 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:553` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AllTestz/Completable+AndThen.swift:595` calls `Subscription` and `Sources/AllTestz/Completable+AndThen.swift:568` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) RxBlocking/Resources.swift:13— RxBlocking/Resources.swift:13-27 | Sources/RxBlocking/Resources.swift:13-27 — before extracting anything, compare `RxBlocking/Resources.swift` and `Sources/RxBlocking/Resources.swift` 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) RxSwift/Disposables/RefCountDisposable.swift:32— RxSwift/Disposables/RefCountDisposable.swift:32-46 | Sources/RxSwift/RefCountDisposable.swift:32-46 — before extracting anything, compare `RxSwift/Disposables/RefCountDisposable.swift` and `Sources/RxSwift/RefCountDisposable.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 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) RxSwift/Observables/Zip+Collection.swift:184— RxSwift/Observables/Zip+Collection.swift:184-198 | Sources/RxSwift/Zip+Collection.swift:184-198 — before extracting anything, compare `RxSwift/Observables/Zip+Collection.swift` and `Sources/RxSwift/Zip+Collection.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 154 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) RxSwift/Observables/Zip.swift:66— RxSwift/Observables/Zip.swift:66-80 | Sources/RxSwift/Zip.swift:66-80 — before extracting anything, compare `RxSwift/Observables/Zip.swift` and `Sources/RxSwift/Zip.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 72 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) RxBlocking/RunLoopLock.swift:35— RxBlocking/RunLoopLock.swift:35-47 | Sources/RxBlocking/RunLoopLock.swift:35-47 — before extracting anything, compare `RxBlocking/RunLoopLock.swift` and `Sources/RxBlocking/RunLoopLock.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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) RxCocoa/Common/DelegateProxy.swift:35— RxCocoa/Common/DelegateProxy.swift:35-47 | Sources/RxCocoa/DelegateProxy.swift:35-47 — before extracting anything, compare `RxCocoa/Common/DelegateProxy.swift` and `Sources/RxCocoa/DelegateProxy.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 106 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) RxCocoa/Common/DelegateProxy.swift:91— RxCocoa/Common/DelegateProxy.swift:91-103 | Sources/RxCocoa/DelegateProxy.swift:91-103 — before extracting anything, compare `RxCocoa/Common/DelegateProxy.swift` and `Sources/RxCocoa/DelegateProxy.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 106 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) RxCocoa/Common/DelegateProxy.swift:147— RxCocoa/Common/DelegateProxy.swift:147-159 | Sources/RxCocoa/DelegateProxy.swift:147-159 — before extracting anything, compare `RxCocoa/Common/DelegateProxy.swift` and `Sources/RxCocoa/DelegateProxy.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 106 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) RxCocoa/iOS/UIGestureRecognizer+Rx.swift:23— RxCocoa/iOS/UIGestureRecognizer+Rx.swift:23-35 | Sources/RxCocoa/UIGestureRecognizer+Rx.swift:23-35 — before extracting anything, compare `RxCocoa/iOS/UIGestureRecognizer+Rx.swift` and `Sources/RxCocoa/UIGestureRecognizer+Rx.swift` 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) RxSwift/Observables/Range.swift:30— RxSwift/Observables/Range.swift:30-42 | Sources/RxSwift/Range.swift:30-42 — before extracting anything, compare `RxSwift/Observables/Range.swift` and `Sources/RxSwift/Range.swift` 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 (13 lines × 2) RxSwift/Observables/RetryWhen.swift:86— RxSwift/Observables/RetryWhen.swift:86-98 | Sources/RxSwift/RetryWhen.swift:86-98 — before extracting anything, compare `RxSwift/Observables/RetryWhen.swift` and `Sources/RxSwift/RetryWhen.swift` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (13 lines × 2) RxSwift/Observables/ToArray.swift:38— RxSwift/Observables/ToArray.swift:38-50 | Sources/RxSwift/ToArray.swift:38-50 — before extracting anything, compare `RxSwift/Observables/ToArray.swift` and `Sources/RxSwift/ToArray.swift` 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) RxSwift/Subjects/ReplaySubject.swift:159— RxSwift/Subjects/ReplaySubject.swift:159-171 | Sources/RxSwift/ReplaySubject.swift:159-171 — before extracting anything, compare `RxSwift/Subjects/ReplaySubject.swift` and `Sources/RxSwift/ReplaySubject.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 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) Sources/AllTestz/Anomalies.swift:234— Sources/AllTestz/Anomalies.swift:234-246 | Sources/AllTestz/Anomalies.swift:249-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) Sources/AllTestz/Anomalies.swift:264— Sources/AllTestz/Anomalies.swift:264-276 | Sources/AllTestz/Anomalies.swift:279-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) RxCocoa/Traits/SharedSequence/SchedulerType+SharedSequence.swift:31— RxCocoa/Traits/SharedSequence/SchedulerType+SharedSequence.swift:31-43 | Sources/RxCocoa/SchedulerType+SharedSequence.swift:31-43 — before extracting anything, compare `RxCocoa/Traits/SharedSequence/SchedulerType+SharedSequence.swift` and `Sources/RxCocoa/SchedulerType+SharedSequence.swift` 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (13 lines × 2) RxSwift/Observables/Do.swift:65— RxSwift/Observables/Do.swift:65-77 | Sources/RxSwift/Do.swift:65-77 — before extracting anything, compare `RxSwift/Observables/Do.swift` and `Sources/RxSwift/Do.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Subjects/BehaviorSubject.swift:60— RxSwift/Subjects/BehaviorSubject.swift:60-72 | Sources/RxSwift/BehaviorSubject.swift:60-72 — before extracting anything, compare `RxSwift/Subjects/BehaviorSubject.swift` and `Sources/RxSwift/BehaviorSubject.swift` as WHOLE FILES: this scan already matched 4 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 (13 lines × 2) RxExample/RxExample/Examples/GitHubSignup/UsingDriver/GitHubSignupViewController2.swift:69— RxExample/RxExample/Examples/GitHubSignup/UsingDriver/GitHubSignupViewController2.swift:69-81 | RxExample/RxExample/Examples/GitHubSignup/UsingVanillaObservables/GitHubSignupViewController1.swift:69-81 — 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 `RxExample/RxExample/Examples/GitHubSignup/UsingDriver/GitHubSignupViewController2.swift:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) RxSwift/Disposables/RefCountDisposable.swift:49— RxSwift/Disposables/RefCountDisposable.swift:49-66 | Sources/RxSwift/RefCountDisposable.swift:49-66 — before extracting anything, compare `RxSwift/Disposables/RefCountDisposable.swift` and `Sources/RxSwift/RefCountDisposable.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 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) RxSwift/Extensions/Bag+Rx.swift:32— RxSwift/Extensions/Bag+Rx.swift:32-49 | Sources/RxSwift/Bag+Rx.swift:32-49 — before extracting anything, compare `RxSwift/Extensions/Bag+Rx.swift` and `Sources/RxSwift/Bag+Rx.swift` 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 (18 lines × 2) RxSwift/Observables/Create.swift:40— RxSwift/Observables/Create.swift:40-57 | Sources/RxSwift/Create.swift:40-57 — before extracting anything, compare `RxSwift/Observables/Create.swift` and `Sources/RxSwift/Create.swift` 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (18 lines × 2) RxSwift/Observables/Map.swift:38— RxSwift/Observables/Map.swift:38-55 | Sources/RxSwift/Map.swift:38-55 — before extracting anything, compare `RxSwift/Observables/Map.swift` and `Sources/RxSwift/Map.swift` 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 (18 lines × 2) RxSwift/Observables/Multicast.swift:221— RxSwift/Observables/Multicast.swift:221-238 | Sources/RxSwift/Multicast.swift:221-238 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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) RxSwift/Observables/Multicast.swift:331— RxSwift/Observables/Multicast.swift:331-348 | Sources/RxSwift/Multicast.swift:331-348 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (18 lines × 2) RxSwift/Observables/ObserveOn.swift:189— RxSwift/Observables/ObserveOn.swift:189-206 | Sources/RxSwift/ObserveOn.swift:189-206 — before extracting anything, compare `RxSwift/Observables/ObserveOn.swift` and `Sources/RxSwift/ObserveOn.swift` as WHOLE FILES: this scan already matched 9 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) RxSwift/Observables/Producer.swift:14— RxSwift/Observables/Producer.swift:14-31 | Sources/RxSwift/Producer.swift:14-31 — before extracting anything, compare `RxSwift/Observables/Producer.swift` and `Sources/RxSwift/Producer.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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) RxSwift/Observables/Scan.swift:61— RxSwift/Observables/Scan.swift:61-78 | Sources/RxSwift/Scan.swift:61-78 — before extracting anything, compare `RxSwift/Observables/Scan.swift` and `Sources/RxSwift/Scan.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Observables/SwitchIfEmpty.swift:63— RxSwift/Observables/SwitchIfEmpty.swift:63-80 | Sources/RxSwift/SwitchIfEmpty.swift:63-80 — before extracting anything, compare `RxSwift/Observables/SwitchIfEmpty.swift` and `Sources/RxSwift/SwitchIfEmpty.swift` 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 (18 lines × 2) RxSwift/Observables/TakeLast.swift:41— RxSwift/Observables/TakeLast.swift:41-58 | Sources/RxSwift/TakeLast.swift:41-58 — before extracting anything, compare `RxSwift/Observables/TakeLast.swift` and `Sources/RxSwift/TakeLast.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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) RxSwift/Subjects/AsyncSubject.swift:115— RxSwift/Subjects/AsyncSubject.swift:115-132 | Sources/RxSwift/AsyncSubject.swift:115-132 — before extracting anything, compare `RxSwift/Subjects/AsyncSubject.swift` and `Sources/RxSwift/AsyncSubject.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) Sources/RxSwift/Completable.swift:132— Sources/RxSwift/Completable.swift:132-149 | Sources/RxSwift/Maybe.swift:150-167 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/RxSwift/Completable.swift:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/RxSwift/Maybe.swift:147` calls `success`, `dispose` and `Sources/RxSwift/Completable.swift:131` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) RxSwift/Disposables/BooleanDisposable.swift:15— RxSwift/Disposables/BooleanDisposable.swift:15-32 | Sources/RxSwift/BooleanDisposable.swift:15-32 — before extracting anything, compare `RxSwift/Disposables/BooleanDisposable.swift` and `Sources/RxSwift/BooleanDisposable.swift` 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×11
Members sharing a duplicated core (4 members, 50+ identical tokens) Platform/DataStructures/Bag.swift:63— Platform/DataStructures/Bag.swift:63-89 | RxSwift/Platform/DataStructures/Bag.swift:63-89 | Sources/AllTestz/Bag.swift:63-89 | Sources/RxSwift/Bag.swift:63-89 — 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) Platform/DataStructures/Bag.swift:112— Platform/DataStructures/Bag.swift:112-131 | RxSwift/Platform/DataStructures/Bag.swift:112-131 | Sources/AllTestz/Bag.swift:112-131 | Sources/RxSwift/Bag.swift:112-131 — 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) Platform/DataStructures/PriorityQueue.swift:66— Platform/DataStructures/PriorityQueue.swift:66-78 | RxSwift/Platform/DataStructures/PriorityQueue.swift:66-78 | Sources/AllTestz/PriorityQueue.swift:66-78 | Sources/RxSwift/PriorityQueue.swift:66-78 — 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) Platform/DataStructures/PriorityQueue.swift:80— Platform/DataStructures/PriorityQueue.swift:80-104 | RxSwift/Platform/DataStructures/PriorityQueue.swift:80-104 | Sources/AllTestz/PriorityQueue.swift:80-104 | Sources/RxSwift/PriorityQueue.swift:80-104 — 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) Platform/DataStructures/Queue.swift:57— Platform/DataStructures/Queue.swift:57-76 | RxSwift/Platform/DataStructures/Queue.swift:57-76 | Sources/AllTestz/Queue.swift:57-76 | Sources/RxSwift/Queue.swift:57-76 — 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) RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:26— RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:26-46 | RxExample/RxDataSources/RxDataSources/RxTableViewSectionedAnimatedDataSource.swift:48-64 | RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:34-50 | RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:52-64 — 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) RxSwift/Observables/AsMaybe.swift:14— RxSwift/Observables/AsMaybe.swift:14-33 | RxSwift/Observables/AsSingle.swift:14-35 | Sources/RxSwift/AsMaybe.swift:14-33 | Sources/RxSwift/AsSingle.swift:14-35 — 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) RxSwift/Observables/CombineLatest+Collection.swift:56— RxSwift/Observables/CombineLatest+Collection.swift:56-68 | RxSwift/Observables/Zip+Collection.swift:75-87 | Sources/RxSwift/CombineLatest+Collection.swift:56-68 | Sources/RxSwift/Zip+Collection.swift:75-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) RxSwift/Observables/CombineLatest+Collection.swift:118— RxSwift/Observables/CombineLatest+Collection.swift:118-145 | RxSwift/Observables/Zip+Collection.swift:205-223 | Sources/RxSwift/CombineLatest+Collection.swift:118-145 | Sources/RxSwift/Zip+Collection.swift:205-223 — 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) RxSwift/Observables/Merge.swift:341— RxSwift/Observables/Merge.swift:341-366 | RxSwift/Observables/Merge.swift:561-586 | Sources/RxSwift/Merge.swift:341-366 | Sources/RxSwift/Merge.swift:561-586 — 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) RxSwift/Observables/Skip.swift:129— RxSwift/Observables/Skip.swift:129-138 | RxSwift/Observables/Take.swift:165-174 | Sources/RxSwift/Skip.swift:129-138 | Sources/RxSwift/Take.swift:165-174 — 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 (19 lines × 2) RxCocoa/Common/DelegateProxy.swift:161— RxCocoa/Common/DelegateProxy.swift:161-179 | Sources/RxCocoa/DelegateProxy.swift:161-179 — before extracting anything, compare `RxCocoa/Common/DelegateProxy.swift` and `Sources/RxCocoa/DelegateProxy.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 106 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) RxSwift/Extensions/Bag+Rx.swift:11— RxSwift/Extensions/Bag+Rx.swift:11-29 | Sources/RxSwift/Bag+Rx.swift:11-29 — before extracting anything, compare `RxSwift/Extensions/Bag+Rx.swift` and `Sources/RxSwift/Bag+Rx.swift` 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) RxSwift/Observables/AsMaybe.swift:15— RxSwift/Observables/AsMaybe.swift:15-33 | Sources/RxSwift/AsMaybe.swift:15-33 — before extracting anything, compare `RxSwift/Observables/AsMaybe.swift` and `Sources/RxSwift/AsMaybe.swift` 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 (19 lines × 2) RxSwift/Observables/CompactMap.swift:37— RxSwift/Observables/CompactMap.swift:37-55 | Sources/RxSwift/CompactMap.swift:37-55 — before extracting anything, compare `RxSwift/Observables/CompactMap.swift` and `Sources/RxSwift/CompactMap.swift` 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) RxSwift/Observables/Enumerated.swift:27— RxSwift/Observables/Enumerated.swift:27-45 | Sources/RxSwift/Enumerated.swift:27-45 — before extracting anything, compare `RxSwift/Observables/Enumerated.swift` and `Sources/RxSwift/Enumerated.swift` 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) RxSwift/Observables/GroupBy.swift:84— RxSwift/Observables/GroupBy.swift:84-102 | Sources/RxSwift/GroupBy.swift:84-102 — before extracting anything, compare `RxSwift/Observables/GroupBy.swift` and `Sources/RxSwift/GroupBy.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 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) RxSwift/Observables/Merge.swift:478— RxSwift/Observables/Merge.swift:478-496 | Sources/RxSwift/Merge.swift:478-496 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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) RxSwift/Observables/Using.swift:35— RxSwift/Observables/Using.swift:35-53 | Sources/RxSwift/Using.swift:35-53 — before extracting anything, compare `RxSwift/Observables/Using.swift` and `Sources/RxSwift/Using.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Schedulers/VirtualTimeScheduler.swift:42— RxSwift/Schedulers/VirtualTimeScheduler.swift:42-60 | Sources/RxSwift/VirtualTimeScheduler.swift:42-60 — before extracting anything, compare `RxSwift/Schedulers/VirtualTimeScheduler.swift` and `Sources/RxSwift/VirtualTimeScheduler.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 119 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) RxCocoa/Common/RxTarget.swift:18— RxCocoa/Common/RxTarget.swift:18-36 | Sources/RxCocoa/RxTarget.swift:18-36 — before extracting anything, compare `RxCocoa/Common/RxTarget.swift` and `Sources/RxCocoa/RxTarget.swift` 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) RxCocoa/iOS/Proxies/RxTabBarDelegateProxy.swift:27— RxCocoa/iOS/Proxies/RxTabBarDelegateProxy.swift:27-45 | Sources/RxCocoa/RxTabBarDelegateProxy.swift:27-45 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxTabBarDelegateProxy.swift` and `Sources/RxCocoa/RxTabBarDelegateProxy.swift` 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) RxCocoa/Foundation/URLSession+Rx.swift:78— RxCocoa/Foundation/URLSession+Rx.swift:78-97 | Sources/RxCocoa/URLSession+Rx.swift:78-97 — before extracting anything, compare `RxCocoa/Foundation/URLSession+Rx.swift` and `Sources/RxCocoa/URLSession+Rx.swift` 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) RxSwift/Observables/Buffer.swift:93— RxSwift/Observables/Buffer.swift:93-112 | Sources/RxSwift/Buffer.swift:93-112 — before extracting anything, compare `RxSwift/Observables/Buffer.swift` and `Sources/RxSwift/Buffer.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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 (20 lines × 2) RxSwift/Observables/Catch.swift:173— RxSwift/Observables/Catch.swift:173-192 | Sources/RxSwift/Catch.swift:173-192 — before extracting anything, compare `RxSwift/Observables/Catch.swift` and `Sources/RxSwift/Catch.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 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 (20 lines × 2) RxSwift/Observables/Merge.swift:611— RxSwift/Observables/Merge.swift:611-630 | Sources/RxSwift/Merge.swift:611-630 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 (20 lines × 2) RxSwift/Observables/Multicast.swift:178— RxSwift/Observables/Multicast.swift:178-197 | Sources/RxSwift/Multicast.swift:178-197 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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 (20 lines × 2) RxSwift/Observables/ShareReplayScope.swift:259— RxSwift/Observables/ShareReplayScope.swift:259-278 | Sources/RxSwift/ShareReplayScope.swift:259-278 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Duplicated block (20 lines × 2) RxSwift/Observables/WithLatestFrom.swift:73— RxSwift/Observables/WithLatestFrom.swift:73-92 | Sources/RxSwift/WithLatestFrom.swift:73-92 — before extracting anything, compare `RxSwift/Observables/WithLatestFrom.swift` and `Sources/RxSwift/WithLatestFrom.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 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 (20 lines × 2) RxSwift/Observables/Zip.swift:40— RxSwift/Observables/Zip.swift:40-59 | Sources/RxSwift/Zip.swift:40-59 — before extracting anything, compare `RxSwift/Observables/Zip.swift` and `Sources/RxSwift/Zip.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 72 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 (20 lines × 2) RxSwift/Observers/ObserverBase.swift:12— RxSwift/Observers/ObserverBase.swift:12-31 | Sources/RxSwift/ObserverBase.swift:12-31 — before extracting anything, compare `RxSwift/Observers/ObserverBase.swift` and `Sources/RxSwift/ObserverBase.swift` 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) RxSwift/Disposables/SingleAssignmentDisposable.swift:39— RxSwift/Disposables/SingleAssignmentDisposable.swift:39-52 | Sources/RxSwift/SingleAssignmentDisposable.swift:39-52 — before extracting anything, compare `RxSwift/Disposables/SingleAssignmentDisposable.swift` and `Sources/RxSwift/SingleAssignmentDisposable.swift` 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) RxSwift/Observables/Debug.swift:79— RxSwift/Observables/Debug.swift:79-92 | Sources/RxSwift/Debug.swift:79-92 — before extracting anything, compare `RxSwift/Observables/Debug.swift` and `Sources/RxSwift/Debug.swift` 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 (14 lines × 2) RxSwift/Observables/ShareReplayScope.swift:406— RxSwift/Observables/ShareReplayScope.swift:406-419 | Sources/RxSwift/ShareReplayScope.swift:406-419 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Duplicated block (14 lines × 2) RxSwift/Subjects/PublishSubject.swift:97— RxSwift/Subjects/PublishSubject.swift:97-110 | Sources/RxSwift/PublishSubject.swift:97-110 — before extracting anything, compare `RxSwift/Subjects/PublishSubject.swift` and `Sources/RxSwift/PublishSubject.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 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) RxSwift/Observables/ShareReplayScope.swift:327— RxSwift/Observables/ShareReplayScope.swift:327-340 | Sources/RxSwift/ShareReplayScope.swift:327-340 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Duplicated block (14 lines × 2) RxSwift/Observables/Skip.swift:110— RxSwift/Observables/Skip.swift:110-123 | Sources/RxSwift/Skip.swift:110-123 — before extracting anything, compare `RxSwift/Observables/Skip.swift` and `Sources/RxSwift/Skip.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 60 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) RxSwift/Observables/Throttle.swift:122— RxSwift/Observables/Throttle.swift:122-135 | Sources/RxSwift/Throttle.swift:122-135 — before extracting anything, compare `RxSwift/Observables/Throttle.swift` and `Sources/RxSwift/Throttle.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 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) RxSwift/Subjects/ReplaySubject.swift:232— RxSwift/Subjects/ReplaySubject.swift:232-245 | Sources/RxSwift/ReplaySubject.swift:232-245 — before extracting anything, compare `RxSwift/Subjects/ReplaySubject.swift` and `Sources/RxSwift/ReplaySubject.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 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.
TodoComment RxExample/RxExample-iOSTests/CLLocationManager+RxTests.swift:323— // TODO: This crashes on Xcode 8.0 beta version — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment RxSwift/Schedulers/Internal/DispatchQueueConfiguration.swift:40— // 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 RxSwift/Schedulers/Internal/DispatchQueueConfiguration.swift:74— // 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 Sources/RxSwift/DispatchQueueConfiguration.swift:40— // 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 Sources/RxSwift/DispatchQueueConfiguration.swift:74— // 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 Sources/AllTestz/RxTest.swift:30— // TODO: Implement PerformanceTests.swift for Linux — 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 Tests/RxTest.swift:30— // TODO: Implement PerformanceTests.swift for Linux — 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 (26 lines × 2) RxSwift/Disposables/RefCountDisposable.swift:68— RxSwift/Disposables/RefCountDisposable.swift:68-93 | Sources/RxSwift/RefCountDisposable.swift:68-93 — before extracting anything, compare `RxSwift/Disposables/RefCountDisposable.swift` and `Sources/RxSwift/RefCountDisposable.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 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 (26 lines × 2) RxSwift/ObservableType+Extensions.swift:42— RxSwift/ObservableType+Extensions.swift:42-67 | Sources/RxSwift/Maybe.swift:95-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (26 lines × 2) RxSwift/Observables/Debounce.swift:63— RxSwift/Observables/Debounce.swift:63-88 | Sources/RxSwift/Debounce.swift:63-88 — before extracting anything, compare `RxSwift/Observables/Debounce.swift` and `Sources/RxSwift/Debounce.swift` as WHOLE FILES: this scan already matched 5 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 (26 lines × 2) RxSwift/Observables/DistinctUntilChanged.swift:97— RxSwift/Observables/DistinctUntilChanged.swift:97-122 | Sources/RxSwift/DistinctUntilChanged.swift:97-122 — before extracting anything, compare `RxSwift/Observables/DistinctUntilChanged.swift` and `Sources/RxSwift/DistinctUntilChanged.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) RxSwift/Schedulers/VirtualTimeScheduler.swift:173— RxSwift/Schedulers/VirtualTimeScheduler.swift:173-198 | Sources/RxSwift/VirtualTimeScheduler.swift:173-198 — before extracting anything, compare `RxSwift/Schedulers/VirtualTimeScheduler.swift` and `Sources/RxSwift/VirtualTimeScheduler.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 119 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 (26 lines × 2) RxCocoa/Traits/ControlEvent.swift:46— RxCocoa/Traits/ControlEvent.swift:46-71 | Sources/RxCocoa/ControlEvent.swift:46-71 — before extracting anything, compare `RxCocoa/Traits/ControlEvent.swift` and `Sources/RxCocoa/ControlEvent.swift` 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) RxSwift/Disposables/ScheduledDisposable.swift:24— RxSwift/Disposables/ScheduledDisposable.swift:24-49 | Sources/RxSwift/ScheduledDisposable.swift:24-49 — before extracting anything, compare `RxSwift/Disposables/ScheduledDisposable.swift` and `Sources/RxSwift/ScheduledDisposable.swift` 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) RxCocoa/Foundation/URLSession+Rx.swift:52— RxCocoa/Foundation/URLSession+Rx.swift:52-76 | Sources/RxCocoa/URLSession+Rx.swift:52-76 — before extracting anything, compare `RxCocoa/Foundation/URLSession+Rx.swift` and `Sources/RxCocoa/URLSession+Rx.swift` 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 (25 lines × 2) RxSwift/Observables/CombineLatest+Collection.swift:121— RxSwift/Observables/CombineLatest+Collection.swift:121-145 | Sources/RxSwift/CombineLatest+Collection.swift:121-145 — before extracting anything, compare `RxSwift/Observables/CombineLatest+Collection.swift` and `Sources/RxSwift/CombineLatest+Collection.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 107 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 `RxSwift/Observables/CombineLatest+Collection.swift:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (25 lines × 2) RxSwift/Observables/Switch.swift:166— RxSwift/Observables/Switch.swift:166-190 | Sources/RxSwift/Switch.swift:166-190 — before extracting anything, compare `RxSwift/Observables/Switch.swift` and `Sources/RxSwift/Switch.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 83 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 (25 lines × 2) RxSwift/Observables/Timeout.swift:107— RxSwift/Observables/Timeout.swift:107-131 | Sources/RxSwift/Timeout.swift:107-131 — before extracting anything, compare `RxSwift/Observables/Timeout.swift` and `Sources/RxSwift/Timeout.swift` 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.
Duplicated block (25 lines × 2) RxSwift/Observables/Zip+Collection.swift:158— RxSwift/Observables/Zip+Collection.swift:158-182 | Sources/RxSwift/Zip+Collection.swift:158-182 — before extracting anything, compare `RxSwift/Observables/Zip+Collection.swift` and `Sources/RxSwift/Zip+Collection.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 154 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 (25 lines × 2) RxRelay/PublishRelay.swift:18— RxRelay/PublishRelay.swift:18-42 | Sources/RxRelay/PublishRelay.swift:18-42 — before extracting anything, compare `RxRelay/PublishRelay.swift` and `Sources/RxRelay/PublishRelay.swift` 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) RxSwift/Disposables/BinaryDisposable.swift:18— RxSwift/Disposables/BinaryDisposable.swift:18-49 | Sources/RxSwift/BinaryDisposable.swift:18-42 — before extracting anything, compare `RxSwift/Disposables/BinaryDisposable.swift` and `Sources/RxSwift/BinaryDisposable.swift` 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 `RxSwift/Disposables/BinaryDisposable.swift: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 (17 lines × 2) RxSwift/Observables/Filter.swift:51— RxSwift/Observables/Filter.swift:51-67 | Sources/RxSwift/Filter.swift:51-67 — before extracting anything, compare `RxSwift/Observables/Filter.swift` and `Sources/RxSwift/Filter.swift` 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 (17 lines × 2) RxSwift/Observables/Multicast.swift:386— RxSwift/Observables/Multicast.swift:386-402 | Sources/RxSwift/Multicast.swift:386-402 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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) RxSwift/Observables/ObserveOn.swift:107— RxSwift/Observables/ObserveOn.swift:107-123 | Sources/RxSwift/ObserveOn.swift:107-123 — before extracting anything, compare `RxSwift/Observables/ObserveOn.swift` and `Sources/RxSwift/ObserveOn.swift` as WHOLE FILES: this scan already matched 9 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 (17 lines × 2) RxSwift/Observables/Sample.swift:54— RxSwift/Observables/Sample.swift:54-70 | Sources/RxSwift/Sample.swift:54-70 — before extracting anything, compare `RxSwift/Observables/Sample.swift` and `Sources/RxSwift/Sample.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 50 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) RxSwift/Schedulers/ConcurrentMainScheduler.swift:45— RxSwift/Schedulers/ConcurrentMainScheduler.swift:45-61 | Sources/RxSwift/ConcurrentMainScheduler.swift:45-61 — before extracting anything, compare `RxSwift/Schedulers/ConcurrentMainScheduler.swift` and `Sources/RxSwift/ConcurrentMainScheduler.swift` 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) RxSwift/Schedulers/OperationQueueScheduler.swift:35— RxSwift/Schedulers/OperationQueueScheduler.swift:35-51 | Sources/RxSwift/OperationQueueScheduler.swift:35-51 — before extracting anything, compare `RxSwift/Schedulers/OperationQueueScheduler.swift` and `Sources/RxSwift/OperationQueueScheduler.swift` 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) RxCocoa/iOS/Proxies/RxWKNavigationDelegateProxy.swift:23— RxCocoa/iOS/Proxies/RxWKNavigationDelegateProxy.swift:23-39 | Sources/RxCocoa/RxWKNavigationDelegateProxy.swift:23-39 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxWKNavigationDelegateProxy.swift` and `Sources/RxCocoa/RxWKNavigationDelegateProxy.swift` 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.
Low cohesion: TableViewSectionedDataSource (LCOM4 9) RxExample/RxDataSources/RxDataSources/TableViewSectionedDataSource.swift:15— TableViewSectionedDataSource's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CollectionViewSectionedDataSource (LCOM4 5) RxExample/RxDataSources/RxDataSources/CollectionViewSectionedDataSource.swift:15— CollectionViewSectionedDataSource's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CatchSequenceSink (LCOM4 4) Sources/RxSwift/Catch.swift:215— CatchSequenceSink's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RetryWhenSequenceSink (LCOM4 4) Sources/RxSwift/RetryWhen.swift:147— RetryWhenSequenceSink's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CatchSequenceSink (LCOM4 4) RxSwift/Observables/Catch.swift:215— CatchSequenceSink's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RetryWhenSequenceSink (LCOM4 4) RxSwift/Observables/RetryWhen.swift:147— RetryWhenSequenceSink's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TableViewWithEditingCommandsViewController (LCOM4 4) RxExample/RxExample/Examples/TableViewWithEditingCommands/TableViewWithEditingCommandsViewController.swift:54— TableViewWithEditingCommandsViewController's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (31 lines × 2) RxSwift/Observables/ElementAt.swift:54— RxSwift/Observables/ElementAt.swift:54-84 | Sources/RxSwift/ElementAt.swift:54-84 — before extracting anything, compare `RxSwift/Observables/ElementAt.swift` and `Sources/RxSwift/ElementAt.swift` as WHOLE FILES: this scan already matched 4 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 (31 lines × 2) RxSwift/Observables/Merge.swift:529— RxSwift/Observables/Merge.swift:529-559 | Sources/RxSwift/Merge.swift:529-559 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 (31 lines × 2) RxSwift/Schedulers/RecursiveScheduler.swift:173— RxSwift/Schedulers/RecursiveScheduler.swift:173-203 | Sources/RxSwift/RecursiveScheduler.swift:173-203 — before extracting anything, compare `RxSwift/Schedulers/RecursiveScheduler.swift` and `Sources/RxSwift/RecursiveScheduler.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `RxSwift/Schedulers/RecursiveScheduler.swift:173` 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 (31 lines × 2) Sources/AllTestz/Anomalies.swift:461— Sources/AllTestz/Anomalies.swift:461-491 | Sources/AllTestz/Anomalies.swift:525-555 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Anomalies.swift:461` 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 (31 lines × 2) RxCocoa/macOS/NSTextField+Rx.swift:28— RxCocoa/macOS/NSTextField+Rx.swift:28-58 | Sources/RxCocoa/NSTextField+Rx.swift:28-58 — before extracting anything, compare `RxCocoa/macOS/NSTextField+Rx.swift` and `Sources/RxCocoa/NSTextField+Rx.swift` 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) RxRelay/BehaviorRelay.swift:18— RxRelay/BehaviorRelay.swift:18-48 | Sources/RxRelay/BehaviorRelay.swift:18-48 — before extracting anything, compare `RxRelay/BehaviorRelay.swift` and `Sources/RxRelay/BehaviorRelay.swift` 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 (27 lines × 2) RxBlocking/RunLoopLock.swift:59— RxBlocking/RunLoopLock.swift:59-85 | Sources/RxBlocking/RunLoopLock.swift:59-85 — before extracting anything, compare `RxBlocking/RunLoopLock.swift` and `Sources/RxBlocking/RunLoopLock.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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 (27 lines × 2) RxSwift/Observables/Buffer.swift:114— RxSwift/Observables/Buffer.swift:114-140 | Sources/RxSwift/Buffer.swift:114-140 — before extracting anything, compare `RxSwift/Observables/Buffer.swift` and `Sources/RxSwift/Buffer.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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 (27 lines × 2) RxSwift/Observables/Merge.swift:220— RxSwift/Observables/Merge.swift:220-246 | Sources/RxSwift/Merge.swift:220-246 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 (27 lines × 2) RxSwift/Observables/Switch.swift:111— RxSwift/Observables/Switch.swift:111-137 | Sources/RxSwift/Switch.swift:111-137 — before extracting anything, compare `RxSwift/Observables/Switch.swift` and `Sources/RxSwift/Switch.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 83 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 (27 lines × 2) Sources/AllTestz/Anomalies.swift:432— Sources/AllTestz/Anomalies.swift:432-458 | Sources/AllTestz/Anomalies.swift:496-522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Anomalies.swift:432` 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 (22 lines × 2) RxSwift/Observables/Generate.swift:40— RxSwift/Observables/Generate.swift:40-61 | Sources/RxSwift/Generate.swift:40-61 — before extracting anything, compare `RxSwift/Observables/Generate.swift` and `Sources/RxSwift/Generate.swift` as WHOLE FILES: this scan already matched 4 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.
Duplicated block (22 lines × 2) RxSwift/Observables/Merge.swift:588— RxSwift/Observables/Merge.swift:588-609 | Sources/RxSwift/Merge.swift:588-609 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 (22 lines × 2) RxSwift/Observables/Producer.swift:69— RxSwift/Observables/Producer.swift:69-90 | Sources/RxSwift/Producer.swift:69-90 — before extracting anything, compare `RxSwift/Observables/Producer.swift` and `Sources/RxSwift/Producer.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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 (22 lines × 2) RxSwift/Schedulers/VirtualTimeScheduler.swift:134— RxSwift/Schedulers/VirtualTimeScheduler.swift:134-155 | Sources/RxSwift/VirtualTimeScheduler.swift:134-155 — before extracting anything, compare `RxSwift/Schedulers/VirtualTimeScheduler.swift` and `Sources/RxSwift/VirtualTimeScheduler.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 119 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 (22 lines × 2) RxSwift/Subjects/ReplaySubject.swift:247— RxSwift/Subjects/ReplaySubject.swift:247-268 | Sources/RxSwift/ReplaySubject.swift:247-268 — before extracting anything, compare `RxSwift/Subjects/ReplaySubject.swift` and `Sources/RxSwift/ReplaySubject.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 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 (21 lines × 2) RxSwift/Observables/AsSingle.swift:15— RxSwift/Observables/AsSingle.swift:15-35 | Sources/RxSwift/AsSingle.swift:15-35 — before extracting anything, compare `RxSwift/Observables/AsSingle.swift` and `Sources/RxSwift/AsSingle.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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) RxSwift/Observables/SkipWhile.swift:48— RxSwift/Observables/SkipWhile.swift:48-68 | Sources/RxSwift/SkipWhile.swift:48-68 — before extracting anything, compare `RxSwift/Observables/SkipWhile.swift` and `Sources/RxSwift/SkipWhile.swift` 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) RxSwift/Observables/Take.swift:80— RxSwift/Observables/Take.swift:80-100 | Sources/RxSwift/Take.swift:80-100 — before extracting anything, compare `RxSwift/Observables/Take.swift` and `Sources/RxSwift/Take.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 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 (21 lines × 2) RxSwift/Schedulers/MainScheduler.swift:58— RxSwift/Schedulers/MainScheduler.swift:58-78 | Sources/RxSwift/MainScheduler.swift:58-78 — before extracting anything, compare `RxSwift/Schedulers/MainScheduler.swift` and `Sources/RxSwift/MainScheduler.swift` 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) RxSwift/Subjects/PublishSubject.swift:65— RxSwift/Subjects/PublishSubject.swift:65-85 | Sources/RxSwift/PublishSubject.swift:65-85 — before extracting anything, compare `RxSwift/Subjects/PublishSubject.swift` and `Sources/RxSwift/PublishSubject.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 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 × 4) RxSwift/Observables/CombineLatest+Collection.swift:155— RxSwift/Observables/CombineLatest+Collection.swift:155-159 | RxSwift/Observables/Zip+Collection.swift:233-237 | Sources/RxSwift/CombineLatest+Collection.swift:155-159 | Sources/RxSwift/Zip+Collection.swift:233-237 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (5 lines × 4) RxSwift/Observables/Debounce.swift:47— RxSwift/Observables/Debounce.swift:47-51 | RxSwift/Observables/Throttle.swift:51-55 | Sources/RxSwift/Debounce.swift:47-51 | Sources/RxSwift/Throttle.swift:51-55 — before extracting anything, compare `RxSwift/Observables/Debounce.swift` and `Sources/RxSwift/Debounce.swift` as WHOLE FILES: this scan already matched 5 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 (5 lines × 4) RxSwift/Observables/ShareReplayScope.swift:215— RxSwift/Observables/ShareReplayScope.swift:215-219 | RxSwift/Observables/ShareReplayScope.swift:362-366 | Sources/RxSwift/ShareReplayScope.swift:215-219 | Sources/RxSwift/ShareReplayScope.swift:362-366 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Duplicated block (5 lines × 4) RxSwift/Observables/Skip.swift:54— RxSwift/Observables/Skip.swift:54-58 | RxSwift/Observables/Take.swift:74-78 | Sources/RxSwift/Skip.swift:54-58 | Sources/RxSwift/Take.swift:74-78 — before extracting anything, compare `RxSwift/Observables/Skip.swift` and `Sources/RxSwift/Skip.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 60 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 × 4) RxSwift/Observables/Merge.swift:18— RxSwift/Observables/Merge.swift:18-22 | RxSwift/Observables/Merge.swift:35-39 | RxSwift/Observables/Merge.swift:131-135 | RxSwift/Observables/Switch.swift:22-26 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13 lines × 4) Platform/DataStructures/PriorityQueue.swift:66— Platform/DataStructures/PriorityQueue.swift:66-78 | RxSwift/Platform/DataStructures/PriorityQueue.swift:66-78 | Sources/AllTestz/PriorityQueue.swift:66-78 | Sources/RxSwift/PriorityQueue.swift:66-78 — before extracting anything, compare `Platform/DataStructures/PriorityQueue.swift` and `RxSwift/Platform/DataStructures/PriorityQueue.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 × 4) Platform/DataStructures/PriorityQueue.swift:52— Platform/DataStructures/PriorityQueue.swift:52-64 | RxSwift/Platform/DataStructures/PriorityQueue.swift:52-64 | Sources/AllTestz/PriorityQueue.swift:52-64 | Sources/RxSwift/PriorityQueue.swift:52-64 — before extracting anything, compare `Platform/DataStructures/PriorityQueue.swift` and `RxSwift/Platform/DataStructures/PriorityQueue.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 × 4) Platform/DataStructures/Queue.swift:81— Platform/DataStructures/Queue.swift:81-93 | RxSwift/Platform/DataStructures/Queue.swift:81-93 | Sources/AllTestz/Queue.swift:81-93 | Sources/RxSwift/Queue.swift:81-93 — before extracting anything, compare `Platform/DataStructures/Queue.swift` and `RxSwift/Platform/DataStructures/Queue.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 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 × 4) RxSwift/Observables/Merge.swift:372— RxSwift/Observables/Merge.swift:372-384 | RxSwift/Observables/Merge.swift:636-648 | Sources/RxSwift/Merge.swift:372-384 | Sources/RxSwift/Merge.swift:636-648 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 × 4) Platform/DataStructures/Bag.swift:98— Platform/DataStructures/Bag.swift:98-104 | RxSwift/Platform/DataStructures/Bag.swift:98-104 | Sources/AllTestz/Bag.swift:98-104 | Sources/RxSwift/Bag.swift:98-104 — before extracting anything, compare `Platform/DataStructures/Bag.swift` and `RxSwift/Platform/DataStructures/Bag.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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 × 4) RxSwift/Observables/Merge.swift:212— RxSwift/Observables/Merge.swift:212-218 | RxSwift/Observables/Merge.swift:666-673 | Sources/RxSwift/Merge.swift:212-218 | Sources/RxSwift/Merge.swift:666-673 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 × 4) RxSwift/Observables/Take.swift:107— RxSwift/Observables/Take.swift:107-113 | RxSwift/Observables/TakeLast.swift:65-71 | Sources/RxSwift/Take.swift:107-113 | Sources/RxSwift/TakeLast.swift:65-71 — before extracting anything, compare `RxSwift/Observables/Take.swift` and `Sources/RxSwift/Take.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 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 × 4) RxSwift/Subjects/BehaviorSubject.swift:77— RxSwift/Subjects/BehaviorSubject.swift:77-83 | RxSwift/Subjects/PublishSubject.swift:57-63 | Sources/RxSwift/BehaviorSubject.swift:77-83 | Sources/RxSwift/PublishSubject.swift:57-63 — before extracting anything, compare `RxSwift/Subjects/BehaviorSubject.swift` and `Sources/RxSwift/BehaviorSubject.swift` as WHOLE FILES: this scan already matched 4 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. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
TooManyMethods: Reactive RxSwift/Reactive.swift:26— TooManyMethods — 44 methods, declared across 16 files: iOS/UICollectionView+Rx.swift (8), Foundation/NSObject+Rx.swift (6), Foundation/URLSession+Rx.swift (4), iOS/UIButton+Rx.swift (4), +12 more file(s). The bar is 30 methods; this is 14 over it, 1.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SharedSequence Sources/RxCocoa/SharedSequence.swift:22— TooManyMethods — 36 methods, declared across 3 files: RxCocoa/SharedSequence.swift (16), RxCocoa/SharedSequence+Operators+arity.swift (14), RxCocoa/SharedSequence+Operators.swift (6). The bar is 30 methods; this is 6 over it, 1.20× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CompletableAndThenTest Sources/AllTestz/Completable+AndThen.swift:13— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (34 lines × 2) RxSwift/Observables/SingleAsync.swift:52— RxSwift/Observables/SingleAsync.swift:52-85 | Sources/RxSwift/SingleAsync.swift:52-85 — before extracting anything, compare `RxSwift/Observables/SingleAsync.swift` and `Sources/RxSwift/SingleAsync.swift` 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 (34 lines × 2) RxSwift/Observables/Window.swift:116— RxSwift/Observables/Window.swift:116-149 | Sources/RxSwift/Window.swift:116-149 — before extracting anything, compare `RxSwift/Observables/Window.swift` and `Sources/RxSwift/Window.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 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 (34 lines × 2) RxSwift/Rx.swift:89— RxSwift/Rx.swift:89-122 | Sources/RxSwift/Rx.swift:89-122 — before extracting anything, compare `RxSwift/Rx.swift` and `Sources/RxSwift/Rx.swift` as WHOLE FILES: this scan already matched 5 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 (30 lines × 2) RxSwift/Observables/TakeWithPredicate.swift:249— RxSwift/Observables/TakeWithPredicate.swift:249-278 | Sources/RxSwift/TakeWithPredicate.swift:249-278 — before extracting anything, compare `RxSwift/Observables/TakeWithPredicate.swift` and `Sources/RxSwift/TakeWithPredicate.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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 (30 lines × 2) RxSwift/Subjects/AsyncSubject.swift:76— RxSwift/Subjects/AsyncSubject.swift:76-105 | Sources/RxSwift/AsyncSubject.swift:76-105 — before extracting anything, compare `RxSwift/Subjects/AsyncSubject.swift` and `Sources/RxSwift/AsyncSubject.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (30 lines × 2) Sources/AllTestz/Completable+AndThen.swift:126— Sources/AllTestz/Completable+AndThen.swift:126-155 | Sources/AllTestz/Completable+AndThen.swift:162-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:126` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (29 lines × 2) RxSwift/Observables/Delay.swift:118— RxSwift/Observables/Delay.swift:118-146 | Sources/RxSwift/Delay.swift:118-146 — before extracting anything, compare `RxSwift/Observables/Delay.swift` and `Sources/RxSwift/Delay.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 97 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) RxSwift/Observables/Merge.swift:248— RxSwift/Observables/Merge.swift:248-276 | Sources/RxSwift/Merge.swift:248-276 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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) RxSwift/Disposables/AnonymousDisposable.swift:19— RxSwift/Disposables/AnonymousDisposable.swift:19-56 | Sources/RxSwift/AnonymousDisposable.swift:19-47 — before extracting anything, compare `RxSwift/Disposables/AnonymousDisposable.swift` and `Sources/RxSwift/AnonymousDisposable.swift` 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 `RxSwift/Disposables/AnonymousDisposable.swift:19` 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) RxSwift/Observables/ObserveOn.swift:126— RxSwift/Observables/ObserveOn.swift:126-149 | Sources/RxSwift/ObserveOn.swift:126-149 — before extracting anything, compare `RxSwift/Observables/ObserveOn.swift` and `Sources/RxSwift/ObserveOn.swift` as WHOLE FILES: this scan already matched 9 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting 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) RxSwift/Observables/Reduce.swift:60— RxSwift/Observables/Reduce.swift:60-83 | Sources/RxSwift/Reduce.swift:60-83 — before extracting anything, compare `RxSwift/Observables/Reduce.swift` and `Sources/RxSwift/Reduce.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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 (24 lines × 2) RxSwift/Observables/Zip.swift:111— RxSwift/Observables/Zip.swift:111-134 | Sources/RxSwift/Zip.swift:111-134 — before extracting anything, compare `RxSwift/Observables/Zip.swift` and `Sources/RxSwift/Zip.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 72 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) RxSwift/Observables/RetryWhen.swift:117— RxSwift/Observables/RetryWhen.swift:117-139 | Sources/RxSwift/RetryWhen.swift:117-139 — before extracting anything, compare `RxSwift/Observables/RetryWhen.swift` and `Sources/RxSwift/RetryWhen.swift` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (23 lines × 2) RxSwift/Schedulers/SchedulerServices+Emulation.swift:38— RxSwift/Schedulers/SchedulerServices+Emulation.swift:38-60 | Sources/RxSwift/SchedulerServices+Emulation.swift:38-60 — before extracting anything, compare `RxSwift/Schedulers/SchedulerServices+Emulation.swift` and `Sources/RxSwift/SchedulerServices+Emulation.swift` 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 (23 lines × 2) RxSwift/Subjects/ReplaySubject.swift:118— RxSwift/Subjects/ReplaySubject.swift:118-140 | Sources/RxSwift/ReplaySubject.swift:118-140 — before extracting anything, compare `RxSwift/Subjects/ReplaySubject.swift` and `Sources/RxSwift/ReplaySubject.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 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 (20 lines × 4) Platform/DataStructures/Bag.swift:112— Platform/DataStructures/Bag.swift:112-131 | RxSwift/Platform/DataStructures/Bag.swift:112-131 | Sources/AllTestz/Bag.swift:112-131 | Sources/RxSwift/Bag.swift:112-131 — before extracting anything, compare `Platform/DataStructures/Bag.swift` and `RxSwift/Platform/DataStructures/Bag.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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 (20 lines × 4) Platform/DataStructures/Queue.swift:57— Platform/DataStructures/Queue.swift:57-76 | RxSwift/Platform/DataStructures/Queue.swift:57-76 | Sources/AllTestz/Queue.swift:57-76 | Sources/RxSwift/Queue.swift:57-76 — before extracting anything, compare `Platform/DataStructures/Queue.swift` and `RxSwift/Platform/DataStructures/Queue.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 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 (20 lines × 4) RxSwift/Observables/Merge.swift:347— RxSwift/Observables/Merge.swift:347-366 | RxSwift/Observables/Merge.swift:567-586 | Sources/RxSwift/Merge.swift:347-366 | Sources/RxSwift/Merge.swift:567-586 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 `RxSwift/Observables/Merge.swift:347` 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 (8 lines × 4) Platform/DataStructures/InfiniteSequence.swift:15— Platform/DataStructures/InfiniteSequence.swift:15-22 | RxSwift/Platform/DataStructures/InfiniteSequence.swift:15-22 | Sources/AllTestz/InfiniteSequence.swift:15-22 | Sources/RxSwift/InfiniteSequence.swift:15-22 — before extracting anything, compare `Platform/DataStructures/InfiniteSequence.swift` and `RxSwift/Platform/DataStructures/InfiniteSequence.swift` 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 × 4) Platform/DataStructures/PriorityQueue.swift:43— Platform/DataStructures/PriorityQueue.swift:43-50 | RxSwift/Platform/DataStructures/PriorityQueue.swift:43-50 | Sources/AllTestz/PriorityQueue.swift:43-50 | Sources/RxSwift/PriorityQueue.swift:43-50 — before extracting anything, compare `Platform/DataStructures/PriorityQueue.swift` and `RxSwift/Platform/DataStructures/PriorityQueue.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 × 4) RxSwift/Observables/ShareReplayScope.swift:173— RxSwift/Observables/ShareReplayScope.swift:173-180 | RxSwift/Observables/ShareReplayScope.swift:313-320 | Sources/RxSwift/ShareReplayScope.swift:173-180 | Sources/RxSwift/ShareReplayScope.swift:313-320 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
DelaySink.drainQueue (cognitive 27) Sources/RxSwift/Delay.swift:64— DelaySink.drainQueue has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 11). 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.
DelaySink.drainQueue (cognitive 27) RxSwift/Observables/Delay.swift:64— DelaySink.drainQueue has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TailRecursiveSink.moveNextCommand (cognitive 21) Sources/RxSwift/TailRecursiveSink.swift:71— TailRecursiveSink.moveNextCommand has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TailRecursiveSink.moveNextCommand (cognitive 21) RxSwift/Observers/TailRecursiveSink.swift:71— TailRecursiveSink.moveNextCommand has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZipCollectionTypeSink.nextAction (cognitive 20) Sources/RxSwift/Zip+Collection.swift:101— ZipCollectionTypeSink.nextAction has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZipCollectionTypeSink.nextAction (cognitive 20) RxSwift/Observables/Zip+Collection.swift:101— ZipCollectionTypeSink.nextAction has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CombineLatestCollectionTypeSink.on (cognitive 18) Sources/RxSwift/CombineLatest+Collection.swift:70— CombineLatestCollectionTypeSink.on has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 1 (3 pts), error handling 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CombineLatestCollectionTypeSink.on (cognitive 18) RxSwift/Observables/CombineLatest+Collection.swift:70— CombineLatestCollectionTypeSink.on has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 1 (3 pts), error handling 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MergeLimitedSink.nextElementArrived (cognitive 16) Sources/RxSwift/Merge.swift:282— MergeLimitedSink.nextElementArrived has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MergeLimitedSink.nextElementArrived (cognitive 16) RxSwift/Observables/Merge.swift:282— MergeLimitedSink.nextElementArrived has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (56 lines × 2) RxCocoa/Foundation/NSObject+Rx.swift:475— RxCocoa/Foundation/NSObject+Rx.swift:475-530 | Sources/RxCocoa/NSObject+Rx.swift:475-530 — before extracting anything, compare `RxCocoa/Foundation/NSObject+Rx.swift` and `Sources/RxCocoa/NSObject+Rx.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 96 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 (56 lines × 2) RxSwift/Observables/Zip+Collection.swift:101— RxSwift/Observables/Zip+Collection.swift:101-156 | Sources/RxSwift/Zip+Collection.swift:101-156 — before extracting anything, compare `RxSwift/Observables/Zip+Collection.swift` and `Sources/RxSwift/Zip+Collection.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 154 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 (47 lines × 2) RxSwift/Observables/CombineLatest+Collection.swift:70— RxSwift/Observables/CombineLatest+Collection.swift:70-116 | Sources/RxSwift/CombineLatest+Collection.swift:70-116 — before extracting anything, compare `RxSwift/Observables/CombineLatest+Collection.swift` and `Sources/RxSwift/CombineLatest+Collection.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 107 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 (47 lines × 2) RxSwift/Observables/Throttle.swift:67— RxSwift/Observables/Throttle.swift:67-113 | Sources/RxSwift/Throttle.swift:67-113 — before extracting anything, compare `RxSwift/Observables/Throttle.swift` and `Sources/RxSwift/Throttle.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 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 × 4) RxSwift/Observables/AsMaybe.swift:14— RxSwift/Observables/AsMaybe.swift:14-28 | RxSwift/Observables/AsSingle.swift:14-28 | Sources/RxSwift/AsMaybe.swift:14-28 | Sources/RxSwift/AsSingle.swift:14-28 — before extracting anything, compare `RxSwift/Observables/AsMaybe.swift` and `Sources/RxSwift/AsMaybe.swift` 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 `RxSwift/Observables/AsMaybe.swift: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.
Duplicated block (15 lines × 4) RxSwift/Observables/Merge.swift:386— RxSwift/Observables/Merge.swift:386-400 | RxSwift/Observables/Merge.swift:650-664 | Sources/RxSwift/Merge.swift:386-400 | Sources/RxSwift/Merge.swift:650-664 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 × 3) Sources/AllTestz/Completable+AndThen.swift:234— Sources/AllTestz/Completable+AndThen.swift:234-245 | Sources/AllTestz/Completable+AndThen.swift:360-371 | Sources/AllTestz/Completable+AndThen.swift:514-525 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:234` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) Sources/AllTestz/Completable+AndThen.swift:264— Sources/AllTestz/Completable+AndThen.swift:264-275 | Sources/AllTestz/Completable+AndThen.swift:390-401 | Sources/AllTestz/Completable+AndThen.swift:544-555 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:264` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) RxSwift/Observables/CombineLatest+Collection.swift:59— RxSwift/Observables/CombineLatest+Collection.swift:59-68 | RxSwift/Observables/Zip+Collection.swift:78-87 | Sources/RxSwift/CombineLatest+Collection.swift:59-68 | Sources/RxSwift/Zip+Collection.swift:78-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `RxSwift/Observables/CombineLatest+Collection.swift:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) RxSwift/Observables/Skip.swift:129— RxSwift/Observables/Skip.swift:129-138 | RxSwift/Observables/Take.swift:165-174 | Sources/RxSwift/Skip.swift:129-138 | Sources/RxSwift/Take.swift:165-174 — before extracting anything, compare `RxSwift/Observables/Skip.swift` and `Sources/RxSwift/Skip.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 60 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 (35 lines × 2) RxCocoa/iOS/Proxies/RxPickerViewDataSourceProxy.swift:21— RxCocoa/iOS/Proxies/RxPickerViewDataSourceProxy.swift:21-55 | Sources/RxCocoa/RxPickerViewDataSourceProxy.swift:21-69 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxPickerViewDataSourceProxy.swift` and `Sources/RxCocoa/RxPickerViewDataSourceProxy.swift` 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 `RxCocoa/iOS/Proxies/RxPickerViewDataSourceProxy.swift: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 (35 lines × 2) RxCocoa/iOS/Proxies/RxTableViewDataSourceProxy.swift:24— RxCocoa/iOS/Proxies/RxTableViewDataSourceProxy.swift:24-58 | Sources/RxCocoa/RxTableViewDataSourceProxy.swift:24-70 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxTableViewDataSourceProxy.swift` and `Sources/RxCocoa/RxTableViewDataSourceProxy.swift` 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 `RxCocoa/iOS/Proxies/RxTableViewDataSourceProxy.swift:24` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 4) Platform/DataStructures/Queue.swift:111— Platform/DataStructures/Queue.swift:111-124 | RxSwift/Platform/DataStructures/Queue.swift:111-124 | Sources/AllTestz/Queue.swift:111-124 | Sources/RxSwift/Queue.swift:111-124 — before extracting anything, compare `Platform/DataStructures/Queue.swift` and `RxSwift/Platform/DataStructures/Queue.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (14 lines × 4) RxSwift/Observables/ShareReplayScope.swift:221— RxSwift/Observables/ShareReplayScope.swift:221-234 | RxSwift/Observables/ShareReplayScope.swift:368-381 | Sources/RxSwift/ShareReplayScope.swift:221-234 | Sources/RxSwift/ShareReplayScope.swift:368-381 — before extracting anything, compare `RxSwift/Observables/ShareReplayScope.swift` and `Sources/RxSwift/ShareReplayScope.swift` as WHOLE FILES: this scan already matched 10 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.
Randomizer.randomize (cyclomatic 23) RxExample/RxExample/Services/Randomizer.swift:43— Randomizer.randomize has cyclomatic complexity 23 (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.
validate-headers.swift.validateHeader (cyclomatic 18) scripts/validate-headers.swift:98— validate-headers.swift.validateHeader has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Changeset.debugDescription (cyclomatic 17) RxExample/RxDataSources/Differentiator/Changeset.swift:79— Changeset.debugDescription has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CommandGenerator.calculateItemMovements (cyclomatic 17) RxExample/RxDataSources/Differentiator/Diff.swift:417— CommandGenerator.calculateItemMovements has cyclomatic complexity 17 (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.
HackComment RxExample/RxExample/Examples/TableViewWithEditingCommands/TableViewWithEditingCommandsViewController.swift:142— // hacky I know :) — 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.
Randomizer.randomize (cognitive 46) RxExample/RxExample/Services/Randomizer.swift:43— Randomizer.randomize has cognitive complexity 46 (threshold 15). Drivers by points: if/else 19 (37 pts), loops 7 (9 pts) (nesting depth added 20). 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.
CommandGenerator.calculateItemMovements (cognitive 31) RxExample/RxDataSources/Differentiator/Diff.swift:417— CommandGenerator.calculateItemMovements has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 5 (7 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 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.
package-spm.swift.packageRelativePath (cognitive 23) scripts/package-spm.swift:95— package-spm.swift.packageRelativePath has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 2 (5 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 11). 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.
CommandGenerator.calculateSectionMovements (cognitive 22) RxExample/RxDataSources/Differentiator/Diff.swift:511— CommandGenerator.calculateSectionMovements has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 5, ternaries 1 (3 pts) (nesting depth added 8). 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.
CommandGenerator.generateInsertAndMoveSections (cognitive 22) RxExample/RxDataSources/Differentiator/Diff.swift:648— CommandGenerator.generateInsertAndMoveSections has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (4 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 7). 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.
package-spm.swift.buildAllTestsTarget (cognitive 20) scripts/package-spm.swift:147— package-spm.swift.buildAllTestsTarget has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 5 (7 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate-headers.swift.validateHeader (cognitive 18) scripts/validate-headers.swift:98— validate-headers.swift.validateHeader has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 3, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Changeset.debugDescription (cognitive 16) RxExample/RxDataSources/Differentiator/Changeset.swift:79— Changeset.debugDescription has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 10, boolean chains 6. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CommandGenerator.generateDeleteSectionsDeletedItemsAndUpdatedItems (cognitive 16) RxExample/RxDataSources/Differentiator/Diff.swift:593— CommandGenerator.generateDeleteSectionsDeletedItemsAndUpdatedItems has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 7). 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.
Change coupling clique: Completable.swift, Maybe.swift, Single.swift RxSwift/Traits/PrimitiveSequence/Completable.swift— 3 files — `RxSwift/Traits/PrimitiveSequence/Completable.swift`, `RxSwift/Traits/PrimitiveSequence/Maybe.swift`, `RxSwift/Traits/PrimitiveSequence/Single.swift` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication· Near-duplicate member family (6 members, 38 shared lines) · ×1
Near-duplicate member family (6 members, 38 shared lines) RxSwift/Schedulers/RecursiveScheduler.swift:38— RxSwift/Schedulers/RecursiveScheduler.swift:38-83 | RxSwift/Schedulers/RecursiveScheduler.swift:88-133 | RxSwift/Schedulers/RecursiveScheduler.swift:163-208 | Sources/RxSwift/RecursiveScheduler.swift:38-83 | Sources/RxSwift/RecursiveScheduler.swift:88-133 | Sources/RxSwift/RecursiveScheduler.swift:163-208 — These 6 members are variants of one another: a block of 38 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 14 shared lines) · ×1
Near-duplicate member family (3 members, 14 shared lines) RxSwift/ObservableType+Extensions.swift:42— RxSwift/ObservableType+Extensions.swift:42-67 | Sources/RxSwift/Maybe.swift:95-120 | Sources/RxSwift/Single.swift:100-120 — These 3 members are variants of one another: a block of 14 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:14— Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:14-33 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:35-58 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:60-87 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:89-120 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:122-157 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:159-198 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:200-243 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) RxCocoa/RxCocoa.swift:85— RxCocoa/RxCocoa.swift:85-91 | RxRelay/Utils.swift:11-17 | RxSwift/Rx.swift:44-50 | Sources/RxCocoa/RxCocoa.swift:85-91 | Sources/RxRelay/Utils.swift:11-17 | Sources/RxSwift/Rx.swift:44-50 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (60 lines × 2) RxSwift/Observers/TailRecursiveSink.swift:71— RxSwift/Observers/TailRecursiveSink.swift:71-130 | Sources/RxSwift/TailRecursiveSink.swift:71-130 — before extracting anything, compare `RxSwift/Observers/TailRecursiveSink.swift` and `Sources/RxSwift/TailRecursiveSink.swift` 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 (58 lines × 2) RxSwift/Observables/Merge.swift:282— RxSwift/Observables/Merge.swift:282-339 | Sources/RxSwift/Merge.swift:282-339 — before extracting anything, compare `RxSwift/Observables/Merge.swift` and `Sources/RxSwift/Merge.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 293 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 (53 lines × 2) RxSwift/Observables/Delay.swift:64— RxSwift/Observables/Delay.swift:64-116 | Sources/RxSwift/Delay.swift:64-116 — before extracting anything, compare `RxSwift/Observables/Delay.swift` and `Sources/RxSwift/Delay.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 97 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 (51 lines × 2) RxSwift/Observables/Multicast.swift:279— RxSwift/Observables/Multicast.swift:279-329 | Sources/RxSwift/Multicast.swift:279-329 — before extracting anything, compare `RxSwift/Observables/Multicast.swift` and `Sources/RxSwift/Multicast.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 180 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 (43 lines × 2) RxSwift/Observables/Amb.swift:99— RxSwift/Observables/Amb.swift:99-141 | Sources/RxSwift/Amb.swift:99-141 — before extracting anything, compare `RxSwift/Observables/Amb.swift` and `Sources/RxSwift/Amb.swift` as WHOLE FILES: this scan already matched 4 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 (40 lines × 2) RxSwift/Schedulers/CurrentThreadScheduler.swift:90— RxSwift/Schedulers/CurrentThreadScheduler.swift:90-129 | Sources/RxSwift/CurrentThreadScheduler.swift:90-129 — before extracting anything, compare `RxSwift/Schedulers/CurrentThreadScheduler.swift` and `Sources/RxSwift/CurrentThreadScheduler.swift` 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (38 lines × 2) RxSwift/Observables/Window.swift:77— RxSwift/Observables/Window.swift:77-114 | Sources/RxSwift/Window.swift:77-114 — before extracting anything, compare `RxSwift/Observables/Window.swift` and `Sources/RxSwift/Window.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 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 (32 lines × 2) RxSwift/Observables/Timeout.swift:74— RxSwift/Observables/Timeout.swift:74-105 | Sources/RxSwift/Timeout.swift:74-105 — before extracting anything, compare `RxSwift/Observables/Timeout.swift` and `Sources/RxSwift/Timeout.swift` 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.
Duplicated block (31 lines × 4) RxSwift/Schedulers/RecursiveScheduler.swift:48— RxSwift/Schedulers/RecursiveScheduler.swift:48-78 | RxSwift/Schedulers/RecursiveScheduler.swift:98-128 | Sources/RxSwift/RecursiveScheduler.swift:48-78 | Sources/RxSwift/RecursiveScheduler.swift:98-128 — before extracting anything, compare `RxSwift/Schedulers/RecursiveScheduler.swift` and `Sources/RxSwift/RecursiveScheduler.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `RxSwift/Schedulers/RecursiveScheduler.swift:48` 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 (27 lines × 4) Platform/DataStructures/Bag.swift:63— Platform/DataStructures/Bag.swift:63-89 | RxSwift/Platform/DataStructures/Bag.swift:63-89 | Sources/AllTestz/Bag.swift:63-89 | Sources/RxSwift/Bag.swift:63-89 — before extracting anything, compare `Platform/DataStructures/Bag.swift` and `RxSwift/Platform/DataStructures/Bag.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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 (25 lines × 4) Platform/DataStructures/PriorityQueue.swift:80— Platform/DataStructures/PriorityQueue.swift:80-104 | RxSwift/Platform/DataStructures/PriorityQueue.swift:80-104 | Sources/AllTestz/PriorityQueue.swift:80-104 | Sources/RxSwift/PriorityQueue.swift:80-104 — before extracting anything, compare `Platform/DataStructures/PriorityQueue.swift` and `RxSwift/Platform/DataStructures/PriorityQueue.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 (20 lines × 6) RxSwift/Schedulers/RecursiveScheduler.swift:43— RxSwift/Schedulers/RecursiveScheduler.swift:43-62 | RxSwift/Schedulers/RecursiveScheduler.swift:93-112 | RxSwift/Schedulers/RecursiveScheduler.swift:168-187 | Sources/RxSwift/RecursiveScheduler.swift:43-62 | Sources/RxSwift/RecursiveScheduler.swift:93-112 | Sources/RxSwift/RecursiveScheduler.swift:168-187 — before extracting anything, compare `RxSwift/Schedulers/RecursiveScheduler.swift` and `Sources/RxSwift/RecursiveScheduler.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `RxSwift/Schedulers/RecursiveScheduler.swift:43` 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 × 6) RxSwift/Schedulers/RecursiveScheduler.swift:66— RxSwift/Schedulers/RecursiveScheduler.swift:66-83 | RxSwift/Schedulers/RecursiveScheduler.swift:116-133 | RxSwift/Schedulers/RecursiveScheduler.swift:191-208 | Sources/RxSwift/RecursiveScheduler.swift:66-83 | Sources/RxSwift/RecursiveScheduler.swift:116-133 | Sources/RxSwift/RecursiveScheduler.swift:191-208 — before extracting anything, compare `RxSwift/Schedulers/RecursiveScheduler.swift` and `Sources/RxSwift/RecursiveScheduler.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `RxSwift/Schedulers/RecursiveScheduler.swift:66` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 4) RxSwift/Observables/CombineLatest+Collection.swift:118— RxSwift/Observables/CombineLatest+Collection.swift:118-132 | RxSwift/Observables/Zip+Collection.swift:205-218 | Sources/RxSwift/CombineLatest+Collection.swift:118-132 | Sources/RxSwift/Zip+Collection.swift:205-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `RxSwift/Observables/CombineLatest+Collection.swift:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 3) RxSwift/ObservableType+Extensions.swift:47— RxSwift/ObservableType+Extensions.swift:47-60 | Sources/RxSwift/Maybe.swift:100-113 | Sources/RxSwift/Single.swift:104-118 — before extracting anything, compare `Sources/RxSwift/Maybe.swift` and `Sources/RxSwift/Single.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `RxSwift/ObservableType+Extensions.swift:47` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 3) RxRelay/Observable+Bind.swift:44— RxRelay/Observable+Bind.swift:44-56 | RxRelay/Observable+Bind.swift:90-102 | RxRelay/Observable+Bind.swift:136-148 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 6) Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:37— Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:37-47 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:62-72 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:91-101 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:124-134 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:161-171 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:202-212 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:74` calls `createColdObservable`, `next`, `asInfallible` and `Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:49` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) Sources/AllTestz/Completable+AndThen.swift:292— Sources/AllTestz/Completable+AndThen.swift:292-302 | Sources/AllTestz/Completable+AndThen.swift:418-428 | Sources/AllTestz/Completable+AndThen.swift:572-582 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:292` 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–11 lines × 2) scripts/package-spm.swift:274— scripts/package-spm.swift:274-283 | scripts/package-spm.swift:297-307 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/package-spm.swift:274` 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 × 7) Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:16— Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:16-25 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:41-50 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:70-79 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:103-112 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:140-149 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:181-190 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:226-235 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) Sources/AllTestz/Completable+AndThen.swift:210— Sources/AllTestz/Completable+AndThen.swift:210-219 | Sources/AllTestz/Completable+AndThen.swift:336-345 | Sources/AllTestz/Completable+AndThen.swift:490-499 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AllTestz/Completable+AndThen.swift:210` 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–9 lines × 3) Sources/RxSwift/Completable.swift:120— Sources/RxSwift/Completable.swift:120-128 | Sources/RxSwift/Maybe.swift:136-143 | Sources/RxSwift/Single.swift:134-142 — before extracting anything, compare `Sources/RxSwift/Maybe.swift` and `Sources/RxSwift/Single.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/RxSwift/Completable.swift:120` 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 × 7) Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:15— Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:15-22 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:36-43 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:61-68 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:90-97 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:123-130 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:160-167 | Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:201-208 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:45` calls `createColdObservable`, `next`, `asInfallible` and `Sources/AllTestz/Infallible+CombineLatestTests+arity.swift:24` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 6) RxCocoa/RxCocoa.swift:86— RxCocoa/RxCocoa.swift:86-91 | RxRelay/Utils.swift:12-17 | RxSwift/Rx.swift:45-50 | Sources/RxCocoa/RxCocoa.swift:86-91 | Sources/RxRelay/Utils.swift:12-17 | Sources/RxSwift/Rx.swift:45-50 — before extracting anything, compare `RxCocoa/RxCocoa.swift` and `Sources/RxCocoa/RxCocoa.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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 `RxCocoa/RxCocoa.swift:86` 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 (59 lines × 6) Platform/AtomicInt.swift:17— Platform/AtomicInt.swift:17-75 | RxBlocking/Platform/AtomicInt.swift:17-75 | RxSwift/Platform/AtomicInt.swift:17-75 | Sources/AllTestz/AtomicInt.swift:17-75 | Sources/RxBlocking/AtomicInt.swift:17-75 | Sources/RxSwift/AtomicInt.swift:17-75 — before extracting anything, compare `Platform/AtomicInt.swift` and `RxBlocking/Platform/AtomicInt.swift` 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 `Platform/AtomicInt.swift:17` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 6) Platform/RecursiveLock.swift:13— Platform/RecursiveLock.swift:13-26 | RxBlocking/Platform/RecursiveLock.swift:13-26 | RxSwift/Platform/RecursiveLock.swift:13-26 | Sources/AllTestz/RecursiveLock.swift:13-26 | Sources/RxBlocking/RecursiveLock.swift:13-26 | Sources/RxSwift/RecursiveLock.swift:13-26 — before extracting anything, compare `Platform/RecursiveLock.swift` and `RxBlocking/Platform/RecursiveLock.swift` 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 (87 lines × 2) RxCocoa/iOS/DataSources/RxCollectionViewReactiveArrayDataSource.swift:19— RxCocoa/iOS/DataSources/RxCollectionViewReactiveArrayDataSource.swift:19-105 | Sources/RxCocoa/RxCollectionViewReactiveArrayDataSource.swift:19-105 — before extracting anything, compare `RxCocoa/iOS/DataSources/RxCollectionViewReactiveArrayDataSource.swift` and `Sources/RxCocoa/RxCollectionViewReactiveArrayDataSource.swift` 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 `RxCocoa/iOS/DataSources/RxCollectionViewReactiveArrayDataSource.swift:19` 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 (74 lines × 2) RxCocoa/iOS/DataSources/RxPickerViewAdapter.swift:17— RxCocoa/iOS/DataSources/RxPickerViewAdapter.swift:17-90 | Sources/RxCocoa/RxPickerViewAdapter.swift:17-90 — before extracting anything, compare `RxCocoa/iOS/DataSources/RxPickerViewAdapter.swift` and `Sources/RxCocoa/RxPickerViewAdapter.swift` 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 `RxCocoa/iOS/DataSources/RxPickerViewAdapter.swift:17` 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 (81 lines × 2) RxCocoa/iOS/DataSources/RxTableViewReactiveArrayDataSource.swift:19— RxCocoa/iOS/DataSources/RxTableViewReactiveArrayDataSource.swift:19-99 | Sources/RxCocoa/RxTableViewReactiveArrayDataSource.swift:19-99 — before extracting anything, compare `RxCocoa/iOS/DataSources/RxTableViewReactiveArrayDataSource.swift` and `Sources/RxCocoa/RxTableViewReactiveArrayDataSource.swift` 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 `RxCocoa/iOS/DataSources/RxTableViewReactiveArrayDataSource.swift:19` 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 (36 lines × 2) RxCocoa/iOS/Proxies/RxCollectionViewDataSourceProxy.swift:24— RxCocoa/iOS/Proxies/RxCollectionViewDataSourceProxy.swift:24-59 | Sources/RxCocoa/RxCollectionViewDataSourceProxy.swift:24-71 — before extracting anything, compare `RxCocoa/iOS/Proxies/RxCollectionViewDataSourceProxy.swift` and `Sources/RxCocoa/RxCollectionViewDataSourceProxy.swift` 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 `RxCocoa/iOS/Proxies/RxCollectionViewDataSourceProxy.swift:24` 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 (39 lines × 2) RxRelay/ReplayRelay.swift:18— RxRelay/ReplayRelay.swift:18-56 | Sources/RxRelay/ReplayRelay.swift:18-56 — before extracting anything, compare `RxRelay/ReplayRelay.swift` and `Sources/RxRelay/ReplayRelay.swift` 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 (143 lines × 2) RxSwift/Concurrency/AsyncLock.swift:46— RxSwift/Concurrency/AsyncLock.swift:46-188 | Sources/RxSwift/AsyncLock.swift:46-188 — before extracting anything, compare `RxSwift/Concurrency/AsyncLock.swift` and `Sources/RxSwift/AsyncLock.swift` 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 (54 lines × 2) RxSwift/Disposables/SerialDisposable.swift:18— RxSwift/Disposables/SerialDisposable.swift:18-71 | Sources/RxSwift/SerialDisposable.swift:18-71 — before extracting anything, compare `RxSwift/Disposables/SerialDisposable.swift` and `Sources/RxSwift/SerialDisposable.swift` 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 (61 lines × 2) RxSwift/GroupedObservable.swift:67— RxSwift/GroupedObservable.swift:67-127 | Sources/RxSwift/GroupedObservable.swift:67-127 — before extracting anything, compare `RxSwift/GroupedObservable.swift` and `Sources/RxSwift/GroupedObservable.swift` 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 (66 lines × 2) RxSwift/Observables/Sink.swift:18— RxSwift/Observables/Sink.swift:18-83 | Sources/RxSwift/Sink.swift:18-83 — before extracting anything, compare `RxSwift/Observables/Sink.swift` and `Sources/RxSwift/Sink.swift` 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 `RxSwift/Observables/Sink.swift: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. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (44 lines × 2) RxSwift/Schedulers/HistoricalSchedulerTimeConverter.swift:23— RxSwift/Schedulers/HistoricalSchedulerTimeConverter.swift:23-66 | Sources/RxSwift/HistoricalSchedulerTimeConverter.swift:23-66 — before extracting anything, compare `RxSwift/Schedulers/HistoricalSchedulerTimeConverter.swift` and `Sources/RxSwift/HistoricalSchedulerTimeConverter.swift` 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 (99 lines × 2) RxSwift/Schedulers/SerialDispatchQueueScheduler.swift:34— RxSwift/Schedulers/SerialDispatchQueueScheduler.swift:34-132 | Sources/RxSwift/SerialDispatchQueueScheduler.swift:34-132 — before extracting anything, compare `RxSwift/Schedulers/SerialDispatchQueueScheduler.swift` and `Sources/RxSwift/SerialDispatchQueueScheduler.swift` 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 (45 lines × 2) RxSwift/Observables/Concat.swift:18— RxSwift/Observables/Concat.swift:18-130 | Sources/RxSwift/Concat.swift:86-130 — before extracting anything, compare `RxSwift/Observables/Concat.swift` and `Sources/RxSwift/Concat.swift` 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 `RxSwift/Observables/Concat.swift: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 (12 lines × 4) Platform/DataStructures/Queue.swift:95— Platform/DataStructures/Queue.swift:95-106 | RxSwift/Platform/DataStructures/Queue.swift:95-106 | Sources/AllTestz/Queue.swift:95-106 | Sources/RxSwift/Queue.swift:95-106 — before extracting anything, compare `Platform/DataStructures/Queue.swift` and `RxSwift/Platform/DataStructures/Queue.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (21 lines × 4) Platform/DataStructures/Queue.swift:127— Platform/DataStructures/Queue.swift:127-147 | RxSwift/Platform/DataStructures/Queue.swift:127-147 | Sources/AllTestz/Queue.swift:127-147 | Sources/RxSwift/Queue.swift:127-147 — before extracting anything, compare `Platform/DataStructures/Queue.swift` and `RxSwift/Platform/DataStructures/Queue.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (6 lines × 4) RxSwift/Observables/Buffer.swift:37— RxSwift/Observables/Buffer.swift:37-42 | RxSwift/Observables/Window.swift:158-163 | Sources/RxSwift/Buffer.swift:37-42 | Sources/RxSwift/Window.swift:158-163 — before extracting anything, compare `RxSwift/Observables/Buffer.swift` and `Sources/RxSwift/Buffer.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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 × 8) RxSwift/Observables/Debounce.swift:109— RxSwift/Observables/Debounce.swift:109-113 | RxSwift/Observables/Delay.swift:159-163 | RxSwift/Observables/DelaySubscription.swift:46-50 | RxSwift/Observables/Skip.swift:146-150 | Sources/RxSwift/Debounce.swift:109-113 | Sources/RxSwift/Delay.swift:159-163 | Sources/RxSwift/DelaySubscription.swift:46-50 | Sources/RxSwift/Skip.swift:146-150 — before extracting anything, compare `RxSwift/Observables/Debounce.swift` and `Sources/RxSwift/Debounce.swift` as WHOLE FILES: this scan already matched 5 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.
Off the main sequence: RxBlocking (SwiftPM) — RxBlocking (SwiftPM): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Swallowed exception (empty catch) Preprocessor/Preprocessor/main.swift:102— 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.
Orphaned file RxExample/RxExample/Feedbacks.swift: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 scripts/package-spm.swift: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 scripts/validate-headers.swift: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 RxExample/RxExample/Services/Randomizer.swift: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 RxExample/RxExample/Observable+Extensions.swift: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 RxCocoa/iOS/UIScrollView+Rx.swift: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 RxCocoa/iOS/UISearchBar+Rx.swift: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 RxCocoa/RxCocoa.swift: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 RxExample/RxDataSources/RxDataSources/RxCollectionViewSectionedAnimatedDataSource.swift: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 RxSwift/Schedulers/CurrentThreadScheduler.swift: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 Platform/DataStructures/Bag.swift: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 RxSwift/GroupedObservable.swift: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 Platform/DataStructures/Queue.swift: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 RxTest/Event+Equatable.swift: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 Preprocessor/Preprocessor/main.swift: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 RxSwift/Observables/Sequence.swift: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 RxExample/RxDataSources/Differentiator/Changeset.swift: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 RxExample/RxExample/Services/ImageService.swift: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 Platform/DataStructures/PriorityQueue.swift: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 RxCocoa/iOS/Proxies/RxCollectionViewDataSourcePrefetchingProxy.swift: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 RxTest/Recorded+Event.swift: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 RxSwift/Schedulers/Internal/DispatchQueueConfiguration.swift: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 RxCocoa/iOS/Proxies/RxTableViewDataSourcePrefetchingProxy.swift: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 RxSwift/Schedulers/VirtualTimeConverterType.swift: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 RxSwift/Observables/Producer.swift: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.
Duplicated predicate Package.swift:8— `(ProcessInfo.processInfo.environment["ANDROID_DATA"] != nil) || (ProcessInfo.processInfo.environment["ANDROID_ROOT"] != nil)` appears character-identically in 2 files — Package.swift, Package@swift-5.9.swift. 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 RxSwift/Observables/Debug.swift:54— `(eventText.count > maxEventTextLength) && parent.trimOutput` appears character-identically in 2 files — RxSwift/Observables/Debug.swift, Sources/RxSwift/Debug.swift. 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 RxCocoa/Common/RxCocoaObjCRuntimeError+Extensions.swift:9— `SWIFT_PACKAGE && !DISABLE_SWIZZLING && !os(Linux)` appears character-identically in 4 files — RxCocoa/Common/RxCocoaObjCRuntimeError+Extensions.swift, RxCocoa/Foundation/NSObject+Rx.swift, Sources/RxCocoa/NSObject+Rx.swift, Sources/RxCocoa/RxCocoaObjCRuntimeError+Extensions.swift. 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 RxCocoa/Common/DelegateProxyType.swift:235— `delegate == nil || proxy._forwardToDelegate() === delegate` appears character-identically in 2 files — RxCocoa/Common/DelegateProxyType.swift, Sources/RxCocoa/DelegateProxyType.swift. 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 RxCocoa/Common/ControlTarget.swift:9— `os(iOS) || os(tvOS) || os(visionOS) || os(macOS)` appears character-identically in 2 files — RxCocoa/Common/ControlTarget.swift, Sources/RxCocoa/ControlTarget.swift. 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 RxSwift/Observables/Merge.swift:532— `self.stopped || self.terminating || !self.subscribeNext` appears character-identically in 2 files — RxSwift/Observables/Merge.swift, Sources/RxSwift/Merge.swift. 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 RxSwift/Observables/Merge.swift:369— `stopped && activeCount == 0 && !terminating` appears character-identically in 2 files — RxSwift/Observables/Merge.swift, Sources/RxSwift/Merge.swift. 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 RxCocoa/Common/DelegateProxy.swift:230— `voidDelegateMethodsContain(aSelector) && hasObservers(selector: aSelector)` appears character-identically in 2 files — RxCocoa/Common/DelegateProxy.swift, Sources/RxCocoa/DelegateProxy.swift. 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.
No direct assertions: testGitHubSignUp RxExample/RxExample-iOSUITests/FlowTests.swift:28— No conventional assertion call was detected, and 5 of 6 tests in `RxExample-iOSUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testSearchWikipedia RxExample/RxExample-iOSUITests/FlowTests.swift:53— No conventional assertion call was detected, and 5 of 6 tests in `RxExample-iOSUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testMasterDetail RxExample/RxExample-iOSUITests/FlowTests.swift:68— No conventional assertion call was detected, and 5 of 6 tests in `RxExample-iOSUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testAnimatedPartialUpdates RxExample/RxExample-iOSUITests/FlowTests.swift:97— No conventional assertion call was detected, and 5 of 6 tests in `RxExample-iOSUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testControls RxExample/RxExample-iOSUITests/FlowTests.swift:130— No conventional assertion call was detected, and 5 of 6 tests in `RxExample-iOSUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: RxSwift/Subjects/ReplaySubject.swift. Pair on, review, or document these before any departure.
Documentation: no project overview docs/index.html— The document begins with 'RxSwift 6.10.1 Docs' but no paragraph states what the project is or does; it reads like a class reference rather than an overview. Add an opening paragraph describing RxSwift's purpose and scope so readers know what this docs set covers.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 3 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (49650 LoC, 604 module-visible types across 38 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 37 of 150 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; 150 of the 652 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: RxExample/RxExample/Feedbacks.swift, scripts/package-spm.swift, scripts/validate-headers.swift, RxExample/RxExample/Services/Randomizer.swift, RxExample/RxExample/Observable+Extensions.swift, RxCocoa/iOS/UIScrollView+Rx.swift, RxCocoa/iOS/UISearchBar+Rx.swift, RxCocoa/RxCocoa.swift (and 29 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (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 1835 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types· Ruby's type checker does not check nil everywhere · ×1
Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
Outdated: danger — `danger` is resolved to 8.2.3 in the committed Gemfile.lock but 9.6.1 is the current release on rubygems.org, and Gemfile declares no version requirement for it, so nothing but the lockfile is holding it back. This build is therefore missing every fix published since, including any security fix. This crosses a major version, so read the changelog before taking it. Run `bundle update danger` and commit the updated Gemfile.lock.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 5 file(s) — `RxCocoa/Foundation/URLSession+Rx.swift`, `RxSwift/ObservableType+Extensions.swift`, `RxSwift/Observables/Debug.swift`, `RxSwift/Observables/Throttle.swift`, `RxSwift/Traits/PrimitiveSequence/PrimitiveSequence+Concurrency.swift` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1677b-25a6-7ae9-9fea-fe5d2a6faf16 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 8 · Warnings: 534 · Recommendations: 61 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 06:38 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.