Public report of Aodaruma/aod-AE-plugin, published 17 November 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.11.4). Assert 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, 17 November 2026, 16:16 UTC · Survey ID cd_be5b1be8a5094e81873563894bc2520a
Aodaruma/aod-AE-plugin
Measured 17 November 2026, 16:15 UTC, at code version ac4c167
First survey, so nothing to compare with yet
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
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: 54,541 lines of product code in 40 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Security and Compliance, 61.4
Findings by how serious they are
14 critical660 serious26 minor
10 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 16:15 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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work 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 ▸
41of 41 dimensions measured by tools.
688of 700 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
41dimensions across 5 lenses, read from 54,541 lines of product code in 40 projects.
Aodaruma/aod-AE-plugin falls short of our standard for production, held back most by its Security and Compliance lens, the code's security and compliance. It scores 68.7 out of 100 and is rated Adequate, and all 14 of its critical findings are security problems in the build pipeline.
Security and Compliance, at 61.4, is the weakest lens and counts most in the score. The best first step is pinning the build actions that handle secrets, worth about 1.9 points. Signing the build's output would lift Security and Compliance itself, worth about 1.4 points. Raising Security and Compliance to 70 would lift the score to about 72.8.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline. Pinning each tool to an exact version and limiting the secret to its own step would close both risks.
The product code is 54,541 lines, about €73,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.
If Security and Compliance rose from 61.4 to 70, the lowest score rated Strong, the score would rise from 68.7 to about 72.8.
Code composition: what the lines of code are
Product code 95%Tests 5%
Rebuild cost: about €73,000 · Estimate
Cost to rebuild
€24,000 to €120,000, for 405 to 1,284 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×1.0 at a score of 69. 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: 54,541 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price 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 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.
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 €73,000 to build again, about 0.5 person-years of work. Its weakest lens is Security and Compliance, at 61.4 (Adequate). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST). Of all the actions in this report, it raises the score most for the work it takes: about 1.9 points for low effort, because it clears the 1 Static Analysis (SAST) findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 17% on every change. The history of the code shows how much it changes: about 29,721 lines over the last 90 days, which is about 120,535 lines a year. At that pace, the extra work comes to an estimated 22.9 to 137.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles 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.
56 modules, with 22 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 16 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
color_boundary_blur uses utils.spectral_wgpu, so a change to utils.spectral_wgpu can break color_boundary_blur, while a change to color_boundary_blur can't break utils.spectral_wgpu.
Position
Below the diagonal: color_boundary_blur uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in color_change uses a type in utils.spectral_wgpu.
The types involved
color_change.Plugin → utils.spectral_wgpu.Params
Direction
color_change uses utils.spectral_wgpu, so a change to utils.spectral_wgpu can break color_change, while a change to color_change can't break utils.spectral_wgpu.
Position
Below the diagonal: color_change uses a module listed above it, which is the healthy direction.
color_composite uses utils.spectral_wgpu, so a change to utils.spectral_wgpu can break color_composite, while a change to color_composite can't break utils.spectral_wgpu.
Position
Below the diagonal: color_composite uses a module listed above it, which is the healthy direction.
color_quantize uses color_quantize.gpu.wgpu, so a change to color_quantize.gpu.wgpu can break color_quantize, while a change to color_quantize can't break color_quantize.gpu.wgpu.
Position
Below the diagonal: color_quantize uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in color_select uses a type in utils.spectral_wgpu.
The types involved
color_select.Plugin → utils.spectral_wgpu.Params
Direction
color_select uses utils.spectral_wgpu, so a change to utils.spectral_wgpu can break color_select, while a change to color_select can't break utils.spectral_wgpu.
Position
Below the diagonal: color_select uses a module listed above it, which is the healthy direction.
differential_generate uses differential_generate.gpu.wgpu, so a change to differential_generate.gpu.wgpu can break differential_generate, while a change to differential_generate can't break differential_generate.gpu.wgpu.
Position
Below the diagonal: differential_generate uses a module listed above it, which is the healthy direction.
eyedropper_mask uses utils.spectral_wgpu, so a change to utils.spectral_wgpu can break eyedropper_mask, while a change to eyedropper_mask can't break utils.spectral_wgpu.
Position
Below the diagonal: eyedropper_mask uses a module listed above it, which is the healthy direction.
fourier_filter uses utils.spectral_wgpu, so a change to utils.spectral_wgpu can break fourier_filter, while a change to fourier_filter can't break utils.spectral_wgpu.
Position
Below the diagonal: fourier_filter uses a module listed above it, which is the healthy direction.
gabor_generate uses gabor_generate.gpu.wgpu, so a change to gabor_generate.gpu.wgpu can break gabor_generate, while a change to gabor_generate can't break gabor_generate.gpu.wgpu.
Position
Below the diagonal: gabor_generate uses a module listed above it, which is the healthy direction.
glass_displace.plugin uses glass_displace.params, so a change to glass_displace.params can break glass_displace.plugin, while a change to glass_displace.plugin can't break glass_displace.params.
Position
Below the diagonal: glass_displace.plugin uses a module listed above it, which is the healthy direction.
glass_displace.render uses glass_displace.glass, so a change to glass_displace.glass can break glass_displace.render, while a change to glass_displace.render can't break glass_displace.glass.
Position
Below the diagonal: glass_displace.render uses a module listed above it, which is the healthy direction.
glass_displace.render uses glass_displace.params, so a change to glass_displace.params can break glass_displace.render, while a change to glass_displace.render can't break glass_displace.params.
Position
Below the diagonal: glass_displace.render uses a module listed above it, which is the healthy direction.
glass_displace.render uses utils.image, so a change to utils.image can break glass_displace.render, while a change to glass_displace.render can't break utils.image.
Position
Below the diagonal: glass_displace.render uses a module listed above it, which is the healthy direction.
pixel_extend.gpu uses pixel_extend, so a change to pixel_extend can break pixel_extend.gpu, while a change to pixel_extend.gpu can't break pixel_extend.
Position
Below the diagonal: pixel_extend.gpu uses a module listed above it, which is the healthy direction.
rainbow_generate uses rainbow_generate.gradient, so a change to rainbow_generate.gradient can break rainbow_generate, while a change to rainbow_generate can't break rainbow_generate.gradient.
Position
Below the diagonal: rainbow_generate uses a module listed above it, which is the healthy direction.
rainbow_generate uses rainbow_generate.params, so a change to rainbow_generate.params can break rainbow_generate, while a change to rainbow_generate can't break rainbow_generate.params.
Position
Below the diagonal: rainbow_generate uses a module listed above it, which is the healthy direction.
singular_value_decompose uses singular_value_decompose.gpu.wgpu, so a change to singular_value_decompose.gpu.wgpu can break singular_value_decompose, while a change to singular_value_decompose can't break singular_value_decompose.gpu.wgpu.
Position
Below the diagonal: singular_value_decompose uses a module listed above it, which is the healthy direction.
voronoi_generate uses voronoi_generate.gpu.wgpu, so a change to voronoi_generate.gpu.wgpu can break voronoi_generate, while a change to voronoi_generate can't break voronoi_generate.gpu.wgpu.
Position
Below the diagonal: voronoi_generate uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 75.7 · Adequate · gated by D2, D4 ·
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
A03:2025 — Software Supply Chain Failures
19
Medium
A05:2025 — Injection
14
High / Critical
Roadmap
Top priorities: 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; Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED; Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.
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.
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 — 14
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 — 660
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 — 26
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
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
This survey 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. All 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 41 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, 688 of 700 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 or a scanner, 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 — We 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 Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We 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 (.rs) and this repository declares a Cargo test suite (repository root, 14 test files), 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.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 214 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D22 Internal API Consistency — not measured this run — We 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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We 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.
D44 Platform End-of-Life — not measured this run — We 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X24 Document value interpolated into markup unescaped — not measured this run — We 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, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
X3 Exception handling — not measured this run — We 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, 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.
X5 Nullable reference types — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 118 further occurrence(s) are not listed individually; the score already reflects all 158.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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.
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.
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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
33 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Plugin::do_render at 91. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being image_calculate::math_op_from_popup at 39 — they are counted neither in the figure above nor in this dimension's score.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with Plugin::do_render (cyclomatic 91), color_composite::blend_channel (cyclomatic 78), Plugin::do_render (cyclomatic 63). — 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 8 together lifts Cyclomatic Complexity from 6.1 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
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.
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with Plugin::do_render (cognitive 277), Plugin::do_render (cognitive 138). — 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 3.4 to about 4.7/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.6 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 38 MethodTooLong finding(s) in God Classes — start with lib.rs (33), mod.rs (4), plugin.rs. — One of this dimension's main actionable groups (38 warning-level).
Resolve the 26 FileTooLong finding(s) in God Classes — start with lib.rs (24), render.rs, gradient.rs. — One of this dimension's main actionable groups (26 warning-level).
Resolve the 14 FunctionTooLong finding(s) in God Classes — start with lib.rs (10), params.rs (2), build-catalog.jsx. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
327 duplicated block group(s) detected. 24.2 % of the production lines (13,201 of 54,541) are in a reported copy. A further 93 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 185 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with lib.rs (12), params.rs (2), mod.rs. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 15 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with lib.rs (12), image.rs (2), mod.rs. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 14 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with lib.rs (13), render.rs. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.8 / 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.
39 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
Off the main sequence: utils
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).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
3 outdated, 1 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Yanked release: imageproc
Outdated: anyhow · ×3
What to do
Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
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 306 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 1 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MPL-2.0, which is its own choice and is not judged here.
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.
Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with build-catalog.jsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_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.
0 deducted task-comment markers across 54541 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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
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).
14 finding(s): 0 critical, 14 high, 0 medium, 0 low. 13 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 2 file(s) — `.github/ISSUE_TEMPLATE/bug_report.yml`, `.github/ISSUE_TEMPLATE/feature_request.yml` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. 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 issue-level).
No action in Static Analysis (SAST) — all 13 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 (13 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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 6 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 55 of the 61 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
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.
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.
Other · Code Health — Unreviewed-generation residue in this repository's Rust: functions whose whole body is still `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Rust: functions whose body is `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, match arms and branches left as `todo!()`, functions that take inputs and return a constant (`Ok(())`, `None`, `Default::default()`, an empty `Vec`) or do nothing, and impls most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
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.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
`Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Cargo.toml:13
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.
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.
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 `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. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`. In Rust, where a guard or permit releases when it is dropped, whether a release written BY HAND — `add_permits` after a forgotten permit, `force_unlock` after a leaked guard, a raw lock's `unlock` — matches the state the function's own acquisitions put the primitive in: not after a try or timed acquire whose failure does not leave, not from a cleanup set up before an acquire that can fail, not skipped by a `?`, `return`, `break` or `continue`, and not on top of a guard that still releases itself.
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.
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 Rust's absent values are handled rather than forced — `Option` and `Result` make absence a value the caller must handle in every crate, and each `.unwrap()` or `.expect()` that no guard on its path proves present is a panic the first time the value is `None` or `Err`.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
`version_parts[0].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×8) — plugins/voronoi-generate/build.rs:20, plugins/space-convert/build.rs:32, plugins/singular-value-decompose/build.rs:20, …
`version_parts[1].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×8) — plugins/voronoi-generate/build.rs:21, plugins/space-convert/build.rs:33, plugins/singular-value-decompose/build.rs:21, …
`version_parts[2].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×7) — plugins/voronoi-generate/build.rs:22, plugins/space-convert/build.rs:34, plugins/singular-value-decompose/build.rs:22, …
`sender.send(v)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `render` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — plugins/voronoi-generate/src/gpu/wgpu/mod.rs:149, plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:127
`std::env::var("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×3) — plugins/space-convert/build.rs:9, plugins/scatter-map/build.rs:12, plugins/rainbow-generate/build.rs:9
`std::fs::write(&pipl_path,pipl)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×3) — plugins/space-convert/build.rs:11, plugins/scatter-map/build.rs:14, plugins/rainbow-generate/build.rs:11
`resource.compile()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×3) — plugins/space-convert/build.rs:16, plugins/scatter-map/build.rs:19, plugins/rainbow-generate/build.rs:16
`pipl::build_pipl(properties())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×3) — plugins/space-convert/build.rs:94, plugins/scatter-map/build.rs:96, plugins/rainbow-generate/build.rs:100
`post_inverse` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `render_coordinates` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — plugins/space-convert/src/lib.rs:1269
`post_inverse` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `backproject` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — plugins/space-convert/src/lib.rs:2085
`mask_region` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `do_render` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — plugins/pixel-extend/src/lib.rs:1165
What to do
Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
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.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 1 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.
X10 Duplicated predicate — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 72 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.
AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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 — no interface, protocol or abstract type declares an operation an implementer must write
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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 field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~2957 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D16 Bus Factor — single-contributor repository — bus factor is not applicable
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.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — N/A — too few peers to establish a naming convention (7101 declarations, no unit with a dominant convention).
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
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+ sibling projects each declaring an entity of their own or taking another project's integration events. 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py, .rs source were not judged.
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 (.rs), 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) — 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.
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.
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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 — Rust suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (68 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner 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
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'.
P2 Observability — This repository's JavaScript/TypeScript, Rust source (40 module(s), 64 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — No web surface: 60 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
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.
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — 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
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — 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
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) 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.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×40
Symbol treated as nullable, then dereferenced unguarded plugins/voronoi-generate/build.rs:20— `version_parts[0].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/voronoi-generate/build.rs:21— `version_parts[1].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/voronoi-generate/build.rs:22— `version_parts[2].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/voronoi-generate/src/gpu/wgpu/mod.rs:149— `sender.send(v)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `render` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/build.rs:9— `std::env::var("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/build.rs:11— `std::fs::write(&pipl_path,pipl)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/build.rs:16— `resource.compile()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/build.rs:32— `version_parts[0].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/build.rs:33— `version_parts[1].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/build.rs:34— `version_parts[2].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/build.rs:94— `pipl::build_pipl(properties())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/src/lib.rs:1269— `post_inverse` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `render_coordinates` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/space-convert/src/lib.rs:2085— `post_inverse` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `backproject` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/singular-value-decompose/build.rs:20— `version_parts[0].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/singular-value-decompose/build.rs:21— `version_parts[1].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/singular-value-decompose/build.rs:22— `version_parts[2].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:127— `sender.send(v)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `render` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/scatter-map/build.rs:12— `std::env::var("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/scatter-map/build.rs:14— `std::fs::write(&pipl_path,pipl)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/scatter-map/build.rs:19— `resource.compile()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `embed_binary_safe_pipl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/scatter-map/build.rs:34— `version_parts[0].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/scatter-map/build.rs:35— `version_parts[1].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/scatter-map/build.rs:36— `version_parts[2].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/scatter-map/build.rs:96— `pipl::build_pipl(properties())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded plugins/region-colorize/build.rs:20— `version_parts[0].parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
MethodTooLong: Plugin.params_setup plugins/displace-scatter/src/lib.rs:282— MethodTooLong — params_setup runs 449 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 349 over it, 4.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.do_render plugins/normal-generate/src/lib.rs:356— MethodTooLong — do_render runs 312 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 212 over it, 3.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/pixel-extend/src/lib.rs:528— MethodTooLong — params_setup runs 312 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 212 over it, 3.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/fourier-filter/src/lib.rs:178— MethodTooLong — params_setup runs 310 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/space-convert/src/lib.rs:338— MethodTooLong — params_setup runs 304 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 204 over it, 3.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/light-wrap/src/lib.rs:165— MethodTooLong — params_setup runs 280 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 180 over it, 2.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.do_render plugins/voronoi-generate/src/lib.rs:687— MethodTooLong — do_render runs 267 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.do_render plugins/color-ajust/src/lib.rs:173— MethodTooLong — do_render runs 259 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/voronoi-generate/src/lib.rs:127— MethodTooLong — params_setup runs 225 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.do_render plugins/region-colorize/src/lib.rs:509— MethodTooLong — do_render runs 207 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/gabor-generate/src/lib.rs:121— MethodTooLong — params_setup runs 201 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.do_render plugins/distance-generate/src/lib.rs:221— MethodTooLong — do_render runs 184 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/normal-generate/src/lib.rs:51— MethodTooLong — params_setup runs 182 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/checker-generate/src/lib.rs:81— MethodTooLong — params_setup runs 177 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WgpuContext.render plugins/pixel-extend/src/gpu/mod.rs:112— MethodTooLong — render runs 176 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/color-boundary-blur/src/lib.rs:99— MethodTooLong — params_setup runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/color-quantize/src/lib.rs:233— MethodTooLong — params_setup runs 172 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.do_render plugins/displace-scatter/src/lib.rs:1142— MethodTooLong — do_render runs 172 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.update_params_ui plugins/displace-scatter/src/lib.rs:911— MethodTooLong — update_params_ui runs 160 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MobiusPlugin.params_setup plugins/mobius-transform/src/lib.rs:192— MethodTooLong — params_setup runs 160 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.do_render plugins/image-calculate/src/lib.rs:510— MethodTooLong — do_render runs 159 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.update_params_ui plugins/fourier-filter/src/lib.rs:624— MethodTooLong — update_params_ui runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.params_setup plugins/image-scaler/src/lib.rs:247— MethodTooLong — params_setup runs 151 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Plugin.do_render plugins/gabor-generate/src/lib.rs:641— MethodTooLong — do_render runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WgpuContext.render plugins/color-quantize/src/gpu/wgpu/mod.rs:102— MethodTooLong — render runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: src/lib.rs plugins/scatter-map/src/lib.rs— FileTooLong — 2633 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 80 free functions. The bar is 500 significant lines; this is 2133 over it, 5.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/image-relight/src/lib.rs— FileTooLong — 2290 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 57 free functions. The bar is 500 significant lines; this is 1790 over it, 4.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/displace-scatter/src/lib.rs— FileTooLong — 2121 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 69 free functions. The bar is 500 significant lines; this is 1621 over it, 4.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/space-convert/src/lib.rs— FileTooLong — 1903 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 48 free functions. The bar is 500 significant lines; this is 1403 over it, 3.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/pixel-extend/src/lib.rs— FileTooLong — 1781 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 59 free functions. The bar is 500 significant lines; this is 1281 over it, 3.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/fourier-filter/src/lib.rs— FileTooLong — 1775 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 34 free functions. The bar is 500 significant lines; this is 1275 over it, 3.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/color-quantize/src/lib.rs— FileTooLong — 1718 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 51 free functions. The bar is 500 significant lines; this is 1218 over it, 3.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/light-wrap/src/lib.rs— FileTooLong — 1443 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 50 free functions. The bar is 500 significant lines; this is 943 over it, 2.89× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/color-composite/src/lib.rs— FileTooLong — 1230 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 32 free functions. The bar is 500 significant lines; this is 730 over it, 2.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/voronoi-generate/src/lib.rs— FileTooLong — 1229 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 67% of them inside a single declaration: Plugin (3 blocks, 109-1154). The bar is 500 significant lines; this is 729 over it, 2.46× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs plugins/image-calculate/src/lib.rs— FileTooLong — 1214 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 32 free functions. The bar is 500 significant lines; this is 714 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/image-scaler/src/lib.rs— FileTooLong — 1200 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 36 free functions. The bar is 500 significant lines; this is 700 over it, 2.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/color-boundary-blur/src/lib.rs— FileTooLong — 1147 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 32 free functions. The bar is 500 significant lines; this is 647 over it, 2.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/mobius-transform/src/lib.rs— FileTooLong — 1094 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: MobiusPlugin (3 blocks, 40-1500). The bar is 500 significant lines; this is 594 over it, 2.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs plugins/image-encrypt-decrypt/src/lib.rs— FileTooLong — 1064 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 51 free functions. The bar is 500 significant lines; this is 564 over it, 2.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/gabor-generate/src/lib.rs— FileTooLong — 995 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 61% of them inside a single declaration: Plugin (3 blocks, 67-884). The bar is 500 significant lines; this is 495 over it, 1.99× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs plugins/channel-remap/src/lib.rs— FileTooLong — 800 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 300 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/region-colorize/src/lib.rs— FileTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: Plugin (3 blocks, 46-776). The bar is 500 significant lines; this is 230 over it, 1.46× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/render.rs plugins/glass-displace/src/render.rs— FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 44 free functions. The bar is 500 significant lines; this is 176 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/checker-generate/src/lib.rs— FileTooLong — 652 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: Plugin (2 blocks, 80-567). The bar is 500 significant lines; this is 152 over it, 1.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs plugins/normal-generate/src/lib.rs— FileTooLong — 626 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 87% of them inside a single declaration: Plugin (2 blocks, 50-824). The bar is 500 significant lines; this is 126 over it, 1.25× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs plugins/image-transform/src/lib.rs— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 87 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/eyedropper-mask/src/lib.rs— FileTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 62% of them inside a single declaration: Plugin (3 blocks, 85-554). The bar is 500 significant lines; this is 57 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/gradient.rs plugins/rainbow-generate/src/gradient.rs— FileTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 44 free functions. The bar is 500 significant lines; this is 55 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs plugins/rainbow-generate/src/lib.rs— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Plugin::do_render (cognitive 277) plugins/normal-generate/src/lib.rs:356— Plugin::do_render has cognitive complexity 277 (threshold 15). Drivers by points: if/else 77 (235 pts), loops 15 (31 pts), boolean chains 7, match/switch 4 (nesting depth added 174). 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.
Plugin::do_render (cognitive 138) plugins/distance-generate/src/lib.rs:221— Plugin::do_render has cognitive complexity 138 (threshold 15). Drivers by points: if/else 38 (113 pts), loops 9 (13 pts), boolean chains 7, match/switch 5 (nesting depth added 79). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Plugin::build_regions_color (cognitive 59) plugins/region-colorize/src/lib.rs:413— Plugin::build_regions_color has cognitive complexity 59 (threshold 15). Drivers by points: if/else 11 (45 pts), loops 5 (9 pts), boolean chains 5 (nesting depth added 38). 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.
Plugin::do_render (cognitive 56) plugins/voronoi-generate/src/lib.rs:687— Plugin::do_render has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (35 pts), loops 3 (12 pts), match/switch 7 (8 pts), boolean chains 1 (nesting depth added 26). 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.
Plugin::do_render (cognitive 52) plugins/region-colorize/src/lib.rs:509— Plugin::do_render has cognitive complexity 52 (threshold 15). Drivers by points: loops 8 (27 pts), if/else 11 (18 pts), match/switch 5 (7 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Plugin::do_render (cognitive 46) plugins/color-ajust/src/lib.rs:173— Plugin::do_render has cognitive complexity 46 (threshold 15). Drivers by points: if/else 29 (35 pts), boolean chains 8, match/switch 3 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Plugin::do_render (cognitive 46) plugins/line-repaint/src/lib.rs:200— Plugin::do_render has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (31 pts), loops 7 (10 pts), boolean chains 4, match/switch 1 (nesting depth added 21). 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.
Plugin::render_auto (cognitive 40) plugins/color-quantize/src/lib.rs:627— Plugin::render_auto has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (25 pts), match/switch 4 (12 pts), boolean chains 3 (nesting depth added 23). 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.
Plugin::do_render (cognitive 31) plugins/contour-generate/src/lib.rs:198— Plugin::do_render has cognitive complexity 31 (threshold 15). Drivers by points: if/else 20 (26 pts), loops 2 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Plugin::do_render (cognitive 31) plugins/eyedropper-mask/src/lib.rs:448— Plugin::do_render has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 6 (10 pts), boolean chains 1, match/switch 1 (nesting depth added 16). 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.
Plugin::build_regions_opacity (cognitive 29) plugins/region-colorize/src/lib.rs:334— Plugin::build_regions_opacity has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 3 (5 pts), match/switch 1 (3 pts) (nesting depth added 16). 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.
Plugin::do_render (cognitive 27) plugins/displace-scatter/src/lib.rs:1142— Plugin::do_render has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 2, 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.
Plugin::update_params_ui (cognitive 27) plugins/fourier-filter/src/lib.rs:624— Plugin::update_params_ui has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 25, if/else 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Plugin::do_render (cognitive 23) plugins/image-calculate/src/lib.rs:510— Plugin::do_render has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 4, match/switch 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Plugin::update_params_ui (cognitive 23) plugins/image-relight/src/lib.rs:1076— Plugin::update_params_ui has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 13, loops 10. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Plugin::do_render (cognitive 22) plugins/gabor-generate/src/lib.rs:641— Plugin::do_render has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, match/switch 3 (4 pts) (nesting depth added 6). 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.
Plugin::render_cell_max_normalized_distance (cognitive 22) plugins/voronoi-generate/src/lib.rs:1021— Plugin::render_cell_max_normalized_distance has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 2 (3 pts), boolean chains 1, match/switch 1 (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.
Plugin::do_render (cognitive 17) plugins/color-boundary-blur/src/lib.rs:495— Plugin::do_render has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, loops 1, match/switch 1 (nesting depth added 4). 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.
Plugin::do_render (cognitive 16) plugins/gradient-blur/src/lib.rs:245— Plugin::do_render has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), match/switch 4, boolean chains 2 (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.
Plugin::update_params_ui (cognitive 16) plugins/rainbow-generate/src/lib.rs:147— Plugin::update_params_ui has cognitive complexity 16 (threshold 15). Drivers by points: loops 8, if/else 5, boolean chains 3. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Plugin::do_render (cyclomatic 91) plugins/normal-generate/src/lib.rs:356— Plugin::do_render has cyclomatic complexity 91 (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.
Plugin::do_render (cyclomatic 63) plugins/distance-generate/src/lib.rs:221— Plugin::do_render has cyclomatic complexity 63 (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.
Plugin::do_render (cyclomatic 57) plugins/voronoi-generate/src/lib.rs:687— Plugin::do_render has cyclomatic complexity 57 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Plugin::do_render (cyclomatic 41) plugins/color-ajust/src/lib.rs:173— Plugin::do_render has cyclomatic complexity 41 (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.
Plugin::do_render (cyclomatic 28) plugins/region-colorize/src/lib.rs:509— Plugin::do_render has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Plugin::update_params_ui (cyclomatic 27) plugins/fourier-filter/src/lib.rs:624— Plugin::update_params_ui has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Plugin::do_render (cyclomatic 26) plugins/line-repaint/src/lib.rs:200— Plugin::do_render has cyclomatic complexity 26 (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.
Plugin::update_params_ui (cyclomatic 24) plugins/image-relight/src/lib.rs:1076— Plugin::update_params_ui has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Plugin::do_render (cyclomatic 22) plugins/image-calculate/src/lib.rs:510— Plugin::do_render has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: image_calculate::math_op_from_popup (cyclomatic 39) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
Plugin::build_regions_color (cyclomatic 22) plugins/region-colorize/src/lib.rs:413— Plugin::build_regions_color has cyclomatic complexity 22 (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.
Plugin::do_render (cyclomatic 20) plugins/contour-generate/src/lib.rs:198— Plugin::do_render has cyclomatic complexity 20 (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.
Plugin::do_render (cyclomatic 19) plugins/gabor-generate/src/lib.rs:641— Plugin::do_render has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Plugin::do_render_wgpu (cyclomatic 19) plugins/voronoi-generate/src/lib.rs:528— Plugin::do_render_wgpu has cyclomatic complexity 19 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Plugin::do_render (cyclomatic 18) plugins/displace-scatter/src/lib.rs:1142— Plugin::do_render has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Plugin::update_params_ui (cyclomatic 18) plugins/glass-displace/src/plugin.rs:193— Plugin::update_params_ui has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Plugin::render_auto (cyclomatic 17) plugins/color-quantize/src/lib.rs:627— Plugin::render_auto 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.
Plugin::do_render_wgpu (cyclomatic 17) plugins/differential-generate/src/lib.rs:235— Plugin::do_render_wgpu has cyclomatic complexity 17 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Plugin::do_render (cyclomatic 16) plugins/eyedropper-mask/src/lib.rs:448— Plugin::do_render has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Plugin::handle_command (cyclomatic 16) plugins/gabor-generate/src/lib.rs:366— Plugin::handle_command has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Duplicated block (11 lines × 2) plugins/checker-generate/src/lib.rs:717— plugins/checker-generate/src/lib.rs:717-727 | plugins/voronoi-generate/src/lib.rs:766-776 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/displace-scatter/src/lib.rs:414— plugins/displace-scatter/src/lib.rs:414-424 | plugins/scatter-map/src/lib.rs:372-382 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:414` 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 (11 lines × 2) plugins/displace-scatter/src/lib.rs:1073— plugins/displace-scatter/src/lib.rs:1073-1083 | plugins/scatter-map/src/lib.rs:964-975 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:1073` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) plugins/displace-scatter/src/lib.rs:2267— plugins/displace-scatter/src/lib.rs:2267-2277 | plugins/displace-scatter/src/lib.rs:2281-2291 — 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 `plugins/displace-scatter/src/lib.rs:2267` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) plugins/eyedropper-mask/src/lib.rs:120— plugins/eyedropper-mask/src/lib.rs:120-130 | plugins/line-repaint/src/lib.rs:78-88 — before extracting anything, compare `plugins/eyedropper-mask/src/lib.rs` and `plugins/line-repaint/src/lib.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/eyedropper-mask/src/lib.rs: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 (11 lines × 2) plugins/image-encrypt-decrypt/src/lib.rs:1047— plugins/image-encrypt-decrypt/src/lib.rs:1047-1057 | plugins/image-encrypt-decrypt/src/lib.rs:1279-1289 — 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 `plugins/image-encrypt-decrypt/src/lib.rs:1047` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) plugins/image-relight/src/lib.rs:2491— plugins/image-relight/src/lib.rs:2491-2501 | plugins/image-relight/src/lib.rs:2504-2514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) plugins/mobius-transform/src/lib.rs:807— plugins/mobius-transform/src/lib.rs:807-817 | plugins/mobius-transform/src/lib.rs:1086-1096 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) plugins/rainbow-generate/src/params.rs:147— plugins/rainbow-generate/src/params.rs:147-157 | plugins/rainbow-generate/src/params.rs:175-185 — 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 `plugins/rainbow-generate/src/params.rs:147` 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 (11 lines × 2) plugins/rainbow-generate/src/params.rs:532— plugins/rainbow-generate/src/params.rs:532-542 | plugins/rainbow-generate/src/params.rs:546-556 — 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 `plugins/rainbow-generate/src/params.rs:532` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) plugins/color-ajust/src/lib.rs:482— plugins/color-ajust/src/lib.rs:482-492 | plugins/color-convert/src/lib.rs:517-527 — before extracting anything, compare `plugins/color-ajust/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-ajust/src/lib.rs:482` 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) plugins/displace-scatter/src/lib.rs:1580— plugins/displace-scatter/src/lib.rs:1580-1590 | plugins/scatter-map/src/lib.rs:1352-1362 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/displace-scatter/src/lib.rs:1610— plugins/displace-scatter/src/lib.rs:1610-1620 | plugins/scatter-map/src/lib.rs:1381-1391 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/color-quantize/src/gpu/wgpu/mod.rs:360— plugins/color-quantize/src/gpu/wgpu/mod.rs:360-370 | plugins/color-quantize/src/gpu/wgpu/mod.rs:374-384 — 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 `plugins/color-quantize/src/gpu/wgpu/mod.rs:360` 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 (11 lines × 2) plugins/color-quantize/src/lib.rs:258— plugins/color-quantize/src/lib.rs:258-268 | plugins/color-quantize/src/lib.rs:270-280 — 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 `plugins/color-quantize/src/lib.rs:258` 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) crates/utils/src/image.rs:327— crates/utils/src/image.rs:327-334 | plugins/image-scaler/src/lib.rs:1100-1107 — 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 `crates/utils/src/image.rs:327` 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) plugins/checker-generate/src/lib.rs:538— plugins/checker-generate/src/lib.rs:538-545 | plugins/gabor-generate/src/lib.rs:600-607 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 10 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/checker-generate/src/lib.rs:538` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) plugins/color-composite/src/lib.rs:943— plugins/color-composite/src/lib.rs:943-950 | plugins/color-composite/src/lib.rs:953-960 — 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 `plugins/color-composite/src/lib.rs:943` 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) plugins/color-composite/src/lib.rs:973— plugins/color-composite/src/lib.rs:973-980 | plugins/color-composite/src/lib.rs:1036-1043 — 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 `plugins/color-composite/src/lib.rs:973` 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) plugins/mobius-transform/src/lib.rs:1287— plugins/mobius-transform/src/lib.rs:1287-1294 | plugins/mobius-transform/src/lib.rs:1381-1388 — 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 `plugins/mobius-transform/src/lib.rs:1287` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) plugins/space-convert/src/lib.rs:1640— plugins/space-convert/src/lib.rs:1640-1647 | plugins/space-convert/src/lib.rs:1688-1695 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) plugins/voronoi-generate/src/lib.rs:1350— plugins/voronoi-generate/src/lib.rs:1350-1357 | plugins/voronoi-generate/src/lib.rs:1361-1368 — 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 `plugins/voronoi-generate/src/lib.rs:1350` 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) crates/utils/src/image.rs:409— crates/utils/src/image.rs:409-416 | plugins/image-scaler/src/lib.rs:1190-1197 — 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) plugins/color-boundary-blur/src/lib.rs:1450— plugins/color-boundary-blur/src/lib.rs:1450-1457 | plugins/space-convert/src/lib.rs:2395-2402 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) plugins/eyedropper-mask/src/lib.rs:747— plugins/eyedropper-mask/src/lib.rs:747-754 | plugins/line-repaint/src/lib.rs:547-554 — before extracting anything, compare `plugins/eyedropper-mask/src/lib.rs` and `plugins/line-repaint/src/lib.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/eyedropper-mask/src/lib.rs:747` 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) plugins/fft/src/lib.rs:318— plugins/fft/src/lib.rs:318-325 | plugins/ifft/src/lib.rs:344-351 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/ifft/src/lib.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 235 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/gradient-blur/src/lib.rs:680— plugins/gradient-blur/src/lib.rs:680-687 | plugins/gradient-displace/src/lib.rs:606-613 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/color-boundary-blur/src/lib.rs:1468— plugins/color-boundary-blur/src/lib.rs:1468-1475 | plugins/pixel-extend/src/lib.rs:2310-2317 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/image-encrypt-decrypt/src/lib.rs:315— plugins/image-encrypt-decrypt/src/lib.rs:315-327 | plugins/scatter-map/src/lib.rs:770-777 — before extracting anything, compare `plugins/image-encrypt-decrypt/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/image-encrypt-decrypt/src/lib.rs:315` 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) plugins/image-relight/src/gpu/mod.rs:65— plugins/image-relight/src/gpu/mod.rs:65-72 | plugins/pixel-extend/src/gpu/mod.rs:92-99 — before extracting anything, compare `plugins/image-relight/src/gpu/mod.rs` and `plugins/pixel-extend/src/gpu/mod.rs` as WHOLE FILES: this scan already matched 7 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 `plugins/image-relight/src/gpu/mod.rs:65` 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, `plugins/image-relight/src/gpu/mod.rs:62` calls `validate_compute_limits` and `plugins/pixel-extend/src/gpu/mod.rs:90` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
FunctionTooLong: rainbow_generate::params::setup plugins/rainbow-generate/src/params.rs:60— FunctionTooLong — rainbow_generate::params::setup runs 440 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 340 over it, 4.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: glass_displace::params::setup plugins/glass-displace/src/params.rs:62— FunctionTooLong — glass_displace::params::setup runs 407 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 307 over it, 4.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: fourier_filter::mode_ui_profile plugins/fourier-filter/src/lib.rs:1066— FunctionTooLong — fourier_filter::mode_ui_profile runs 299 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 199 over it, 2.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: space_convert::render_coordinates plugins/space-convert/src/lib.rs:1190— FunctionTooLong — space_convert::render_coordinates runs 246 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: build-catalog.configureOldEffect docs/catalog/build-catalog.jsx:175— FunctionTooLong — configureOldEffect runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: image_calculate::operation_ui_info plugins/image-calculate/src/lib.rs:791— FunctionTooLong — image_calculate::operation_ui_info runs 158 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: color_composite::blend_rgb plugins/color-composite/src/lib.rs:879— FunctionTooLong — color_composite::blend_rgb runs 151 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: color_composite::blend_channel plugins/color-composite/src/lib.rs:1083— FunctionTooLong — color_composite::blend_channel runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: fourier_filter::filter_gain plugins/fourier-filter/src/lib.rs:1638— FunctionTooLong — fourier_filter::filter_gain runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: color_quantize::gpu::wgpu::create_pipelines plugins/color-quantize/src/gpu/wgpu/mod.rs:487— FunctionTooLong — color_quantize::gpu::wgpu::create_pipelines runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: channel_remap::encode_from_linear plugins/channel-remap/src/lib.rs:921— FunctionTooLong — channel_remap::encode_from_linear runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: image_calculate::encode_from_linear plugins/image-calculate/src/lib.rs:1382— FunctionTooLong — image_calculate::encode_from_linear runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: displace_scatter::read_render_settings plugins/displace-scatter/src/lib.rs:1384— FunctionTooLong — displace_scatter::read_render_settings runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: color_quantize::init_centroids_kmeans_parallel plugins/color-quantize/src/lib.rs:1348— FunctionTooLong — color_quantize::init_centroids_kmeans_parallel runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: MobiusPlugin plugins/mobius-transform/src/lib.rs:40— ClassTooLong — 971 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 36 methods, 3 blocks, lines 40-1500. The bar is 400 significant lines; this is 571 over it, 2.43× 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.
ClassTooLong: Plugin plugins/displace-scatter/src/lib.rs:273— ClassTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 273-1360. The bar is 400 significant lines; this is 482 over it, 2.21× 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.
ClassTooLong: Plugin plugins/voronoi-generate/src/lib.rs:109— ClassTooLong — 823 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 3 blocks, lines 109-1154. The bar is 400 significant lines; this is 423 over it, 2.06× 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.
ClassTooLong: Plugin plugins/fourier-filter/src/lib.rs:157— ClassTooLong — 738 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 3 blocks, lines 157-1064. The bar is 400 significant lines; this is 338 over it, 1.85× 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.
ClassTooLong: Plugin plugins/gabor-generate/src/lib.rs:67— ClassTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 3 blocks, lines 67-884. The bar is 400 significant lines; this is 202 over it, 1.51× 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.
ClassTooLong: Plugin plugins/pixel-extend/src/lib.rs:53— ClassTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 53-1226. The bar is 400 significant lines; this is 171 over it, 1.43× 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.
ClassTooLong: Plugin plugins/region-colorize/src/lib.rs:46— ClassTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 3 blocks, lines 46-776. The bar is 400 significant lines; this is 156 over it, 1.39× 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.
ClassTooLong: Plugin plugins/normal-generate/src/lib.rs:44— ClassTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 2 blocks, lines 50-824. The bar is 400 significant lines; this is 146 over it, 1.37× 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.
ClassTooLong: Plugin plugins/space-convert/src/lib.rs:286— ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 286-945. The bar is 400 significant lines; this is 127 over it, 1.32× 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.
ClassTooLong: Plugin plugins/light-wrap/src/lib.rs:156— ClassTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 156-804. The bar is 400 significant lines; this is 105 over it, 1.26× 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.
ClassTooLong: Plugin plugins/image-calculate/src/lib.rs:127— ClassTooLong — 464 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 3 blocks, lines 127-711. The bar is 400 significant lines; this is 64 over it, 1.16× 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.
ClassTooLong: Plugin plugins/color-quantize/src/lib.rs:122— ClassTooLong — 443 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 3 blocks, lines 122-805. The bar is 400 significant lines; this is 43 over it, 1.11× 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.
ClassTooLong: Plugin plugins/color-convert/src/lib.rs:41— ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 2 blocks, lines 48-597. The bar is 400 significant lines; this is 28 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.
ClassTooLong: Plugin plugins/color-boundary-blur/src/lib.rs:89— ClassTooLong — 418 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 3 blocks, lines 89-623. The bar is 400 significant lines; this is 18 over it, 1.05× 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 (7 lines × 2) plugins/color-boundary-blur/src/lib.rs:1281— plugins/color-boundary-blur/src/lib.rs:1281-1287 | plugins/image-relight/src/lib.rs:2487-2493 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/image-relight/src/lib.rs` as WHOLE FILES: this scan already matched 6 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 `plugins/color-boundary-blur/src/lib.rs:1281` 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) plugins/glass-displace/src/render.rs:769— plugins/glass-displace/src/render.rs:769-775 | plugins/rainbow-generate/src/lib.rs:679-685 — before extracting anything, compare `plugins/glass-displace/src/render.rs` and `plugins/rainbow-generate/src/lib.rs` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/glass-displace/src/render.rs:769` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) plugins/space-convert/src/lib.rs:1649— plugins/space-convert/src/lib.rs:1649-1655 | plugins/space-convert/src/lib.rs:1710-1716 — 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 `plugins/space-convert/src/lib.rs:1649` 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) plugins/color-boundary-blur/src/lib.rs:1108— plugins/color-boundary-blur/src/lib.rs:1108-1114 | plugins/color-boundary-blur/src/lib.rs:1128-1134 — 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 `plugins/color-boundary-blur/src/lib.rs:1108` 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) plugins/displace-scatter/src/lib.rs:2623— plugins/displace-scatter/src/lib.rs:2623-2629 | plugins/displace-scatter/src/lib.rs:2649-2655 — 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 `plugins/displace-scatter/src/lib.rs:2623` 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) plugins/fourier-filter/src/lib.rs:2074— plugins/fourier-filter/src/lib.rs:2074-2080 | plugins/image-scaler/src/lib.rs:1485-1491 — before extracting anything, compare `plugins/fourier-filter/src/lib.rs` and `plugins/image-scaler/src/lib.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fourier-filter/src/lib.rs:2074` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) plugins/image-scaler/src/lib.rs:1094— plugins/image-scaler/src/lib.rs:1094-1100 | plugins/image-scaler/src/lib.rs:1134-1140 — 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 `plugins/image-scaler/src/lib.rs:1094` 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) plugins/voronoi-generate/src/lib.rs:569— plugins/voronoi-generate/src/lib.rs:569-575 | plugins/voronoi-generate/src/lib.rs:726-732 — 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 `plugins/voronoi-generate/src/lib.rs:569` 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) plugins/color-boundary-blur/src/lib.rs:1253— plugins/color-boundary-blur/src/lib.rs:1253-1259 | plugins/color-boundary-blur/src/lib.rs:1269-1275 — 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 `plugins/color-boundary-blur/src/lib.rs:1253` 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) plugins/image-transform/src/lib.rs:93— plugins/image-transform/src/lib.rs:93-99 | plugins/space-convert/src/lib.rs:180-186 — before extracting anything, compare `plugins/image-transform/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) plugins/color-composite/src/lib.rs:1528— plugins/color-composite/src/lib.rs:1528-1534 | plugins/color-select/src/lib.rs:460-466 — before extracting anything, compare `plugins/color-composite/src/lib.rs` and `plugins/color-select/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/gradient-blur/src/lib.rs:220— plugins/gradient-blur/src/lib.rs:220-226 | plugins/gradient-displace/src/lib.rs:207-213 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/image-relight/src/lib.rs:396— plugins/image-relight/src/lib.rs:396-402 | plugins/space-convert/src/lib.rs:305-311 — before extracting anything, compare `plugins/image-relight/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/image-relight/src/lib.rs:1527— plugins/image-relight/src/lib.rs:1527-1533 | plugins/space-convert/src/lib.rs:1085-1091 — before extracting anything, compare `plugins/image-relight/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/checker-generate/src/lib.rs:105— plugins/checker-generate/src/lib.rs:105-114 | plugins/voronoi-generate/src/lib.rs:168-177 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/checker-generate/src/lib.rs:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) plugins/checker-generate/src/lib.rs:120— plugins/checker-generate/src/lib.rs:120-129 | plugins/checker-generate/src/lib.rs:213-222 — 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 `plugins/checker-generate/src/lib.rs:120` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) plugins/distance-generate/src/lib.rs:260— plugins/distance-generate/src/lib.rs:260-269 | plugins/normal-generate/src/lib.rs:384-393 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/normal-generate/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 182 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/gabor-generate/src/lib.rs:277— plugins/gabor-generate/src/lib.rs:277-286 | plugins/voronoi-generate/src/lib.rs:279-288 — before extracting anything, compare `plugins/gabor-generate/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gabor-generate/src/lib.rs:277` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) plugins/glass-displace/src/render.rs:807— plugins/glass-displace/src/render.rs:807-816 | plugins/rainbow-generate/src/lib.rs:528-537 — before extracting anything, compare `plugins/glass-displace/src/render.rs` and `plugins/rainbow-generate/src/lib.rs` as WHOLE FILES: this scan already matched 6 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 (10 lines × 2) plugins/gradient-blur/src/lib.rs:251— plugins/gradient-blur/src/lib.rs:251-260 | plugins/gradient-displace/src/lib.rs:238-247 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/gradient-blur/src/lib.rs:262` calls `get`, `as_slider`, `value` and `plugins/gradient-displace/src/lib.rs:249` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) plugins/gradient-blur/src/lib.rs:497— plugins/gradient-blur/src/lib.rs:497-506 | plugins/gradient-displace/src/lib.rs:423-432 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) plugins/image-calculate/src/lib.rs:559— plugins/image-calculate/src/lib.rs:559-568 | plugins/singular-value-decompose/src/lib.rs:218-227 — before extracting anything, compare `plugins/image-calculate/src/lib.rs` and `plugins/singular-value-decompose/src/lib.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/image-calculate/src/lib.rs:559` 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) plugins/rainbow-generate/src/params.rs:161— plugins/rainbow-generate/src/params.rs:161-170 | plugins/rainbow-generate/src/params.rs:189-198 — 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 `plugins/rainbow-generate/src/params.rs:161` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) plugins/eyedropper-mask/src/lib.rs:635— plugins/eyedropper-mask/src/lib.rs:635-644 | plugins/line-repaint/src/lib.rs:400-409 — before extracting anything, compare `plugins/eyedropper-mask/src/lib.rs` and `plugins/line-repaint/src/lib.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/eyedropper-mask/src/lib.rs:635` 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) plugins/gradient-blur/src/lib.rs:603— plugins/gradient-blur/src/lib.rs:603-612 | plugins/gradient-displace/src/lib.rs:529-538 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/color-quantize/src/lib.rs:467— plugins/color-quantize/src/lib.rs:467-476 | plugins/glass-displace/src/plugin.rs:69-78 — 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 `plugins/color-quantize/src/lib.rs:467` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) plugins/color-composite/src/lib.rs:635— plugins/color-composite/src/lib.rs:635-643 | plugins/color-select/src/lib.rs:288-296 — before extracting anything, compare `plugins/color-composite/src/lib.rs` and `plugins/color-select/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/differential-generate/src/lib.rs:349— plugins/differential-generate/src/lib.rs:349-357 | plugins/fft/src/lib.rs:257-265 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/fft/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/differential-generate/src/lib.rs:349` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) plugins/gabor-generate/src/lib.rs:922— plugins/gabor-generate/src/lib.rs:922-930 | plugins/gabor-generate/src/lib.rs:941-949 — 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 `plugins/gabor-generate/src/lib.rs:922` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) plugins/rainbow-generate/src/params.rs:172— plugins/rainbow-generate/src/params.rs:172-180 | plugins/space-convert/src/lib.rs:575-583 — before extracting anything, compare `plugins/rainbow-generate/src/params.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/rainbow-generate/src/params.rs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) plugins/space-convert/src/lib.rs:1199— plugins/space-convert/src/lib.rs:1199-1207 | plugins/space-convert/src/lib.rs:2065-2073 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/space-convert/src/lib.rs:2064` calls `projection_trigonometry` and `plugins/space-convert/src/lib.rs:1198` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) plugins/channel-remap/src/lib.rs:497— plugins/channel-remap/src/lib.rs:497-505 | plugins/color-composite/src/lib.rs:813-821 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-composite/src/lib.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:497` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) plugins/rainbow-generate/src/gradient.rs:733— plugins/rainbow-generate/src/gradient.rs:733-741 | plugins/rainbow-generate/src/gradient.rs:749-757 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) plugins/displace-scatter/src/lib.rs:1570— plugins/displace-scatter/src/lib.rs:1570-1578 | plugins/scatter-map/src/lib.rs:1342-1350 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/glass-displace/src/render.rs:822— plugins/glass-displace/src/render.rs:822-830 | plugins/rainbow-generate/src/lib.rs:550-558 — before extracting anything, compare `plugins/glass-displace/src/render.rs` and `plugins/rainbow-generate/src/lib.rs` as WHOLE FILES: this scan already matched 6 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 (9 lines × 2) plugins/gradient-blur/src/lib.rs:368— plugins/gradient-blur/src/lib.rs:368-376 | plugins/gradient-displace/src/lib.rs:341-349 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/image-transform/src/lib.rs:63— plugins/image-transform/src/lib.rs:63-71 | plugins/space-convert/src/lib.rs:151-159 — before extracting anything, compare `plugins/image-transform/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/color-boundary-blur/src/lib.rs:1183— plugins/color-boundary-blur/src/lib.rs:1183-1188 | plugins/color-boundary-blur/src/lib.rs:1195-1200 — 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 `plugins/color-boundary-blur/src/lib.rs:1183` 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) plugins/color-boundary-blur/src/lib.rs:1246— plugins/color-boundary-blur/src/lib.rs:1246-1251 | plugins/color-boundary-blur/src/lib.rs:1262-1267 — 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 `plugins/color-boundary-blur/src/lib.rs:1246` 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) plugins/displace-scatter/src/lib.rs:1502— plugins/displace-scatter/src/lib.rs:1502-1507 | plugins/scatter-map/src/lib.rs:1282-1287 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:1502` 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) plugins/displace-scatter/src/lib.rs:2613— plugins/displace-scatter/src/lib.rs:2613-2618 | plugins/displace-scatter/src/lib.rs:2636-2641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) plugins/fft/src/lib.rs:213— plugins/fft/src/lib.rs:213-218 | plugins/singular-value-decompose/src/lib.rs:176-181 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/singular-value-decompose/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/fft/src/lib.rs:213— plugins/fft/src/lib.rs:213-218 | plugins/fourier-filter/src/lib.rs:911-916 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/image-encrypt-decrypt/src/lib.rs:827— plugins/image-encrypt-decrypt/src/lib.rs:827-832 | plugins/image-encrypt-decrypt/src/lib.rs:1370-1375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) plugins/light-wrap/src/lib.rs:982— plugins/light-wrap/src/lib.rs:982-987 | plugins/light-wrap/src/lib.rs:1001-1006 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) plugins/image-transform/src/lib.rs:309— plugins/image-transform/src/lib.rs:309-314 | plugins/space-convert/src/lib.rs:699-704 — before extracting anything, compare `plugins/image-transform/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/image-transform/src/lib.rs:309` 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) crates/utils/src/image.rs:347— crates/utils/src/image.rs:347-352 | plugins/color-boundary-blur/src/lib.rs:1443-1448 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) plugins/color-select/src/lib.rs:468— plugins/color-select/src/lib.rs:468-473 | plugins/eyedropper-mask/src/lib.rs:661-666 — before extracting anything, compare `plugins/color-select/src/lib.rs` and `plugins/eyedropper-mask/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/color-boundary-blur/src/lib.rs:1297— plugins/color-boundary-blur/src/lib.rs:1297-1301 | plugins/image-relight/src/lib.rs:2502-2506 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/image-relight/src/lib.rs` as WHOLE FILES: this scan already matched 6 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 `plugins/color-boundary-blur/src/lib.rs:1297` 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) plugins/displace-scatter/src/lib.rs:1986— plugins/displace-scatter/src/lib.rs:1986-1990 | plugins/displace-scatter/src/lib.rs:2009-2013 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) plugins/gabor-generate/src/lib.rs:673— plugins/gabor-generate/src/lib.rs:673-677 | plugins/gabor-generate/src/lib.rs:679-683 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) plugins/image-relight/src/gpu/mod.rs:377— plugins/image-relight/src/gpu/mod.rs:377-381 | plugins/pixel-extend/src/gpu/mod.rs:566-570 — before extracting anything, compare `plugins/image-relight/src/gpu/mod.rs` and `plugins/pixel-extend/src/gpu/mod.rs` as WHOLE FILES: this scan already matched 7 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 `plugins/image-relight/src/gpu/mod.rs:377` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/pixel-extend/src/gpu/mod.rs:563` calls `buffer_layout_entry` and `plugins/image-relight/src/gpu/mod.rs:375` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) plugins/region-colorize/src/lib.rs:400— plugins/region-colorize/src/lib.rs:400-404 | plugins/region-colorize/src/lib.rs:465-470 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) plugins/voronoi-generate/src/lib.rs:593— plugins/voronoi-generate/src/lib.rs:593-597 | plugins/voronoi-generate/src/lib.rs:745-749 — 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 `plugins/voronoi-generate/src/lib.rs:593` 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 (5 lines × 2) plugins/depth-fog/src/lib.rs:362— plugins/depth-fog/src/lib.rs:362-366 | plugins/displace-scatter/src/lib.rs:2688-2692 — before extracting anything, compare `plugins/depth-fog/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/depth-fog/src/lib.rs:362` 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 (5 lines × 2) plugins/displace-scatter/src/lib.rs:2178— plugins/displace-scatter/src/lib.rs:2178-2182 | plugins/displace-scatter/src/lib.rs:2188-2192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) plugins/image-scaler/src/lib.rs:740— plugins/image-scaler/src/lib.rs:740-744 | plugins/pixel-extend/src/lib.rs:1319-1323 — before extracting anything, compare `plugins/image-scaler/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/scatter-map/src/lib.rs:1974— plugins/scatter-map/src/lib.rs:1974-1978 | plugins/scatter-map/src/lib.rs:1983-1987 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) plugins/channel-remap/src/lib.rs:506— plugins/channel-remap/src/lib.rs:506-517 | plugins/color-convert/src/lib.rs:511-522 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:506` 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 × 2) plugins/color-boundary-blur/src/lib.rs:140— plugins/color-boundary-blur/src/lib.rs:140-151 | plugins/color-select/src/lib.rs:133-144 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/color-select/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/color-select/src/lib.rs:132` calls `set_precision` and `plugins/color-boundary-blur/src/lib.rs:139` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) plugins/displace-scatter/src/lib.rs:743— plugins/displace-scatter/src/lib.rs:743-754 | plugins/scatter-map/src/lib.rs:660-671 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:743` 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 × 2) plugins/image-transform/src/lib.rs:109— plugins/image-transform/src/lib.rs:109-120 | plugins/space-convert/src/lib.rs:196-207 — before extracting anything, compare `plugins/image-transform/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) plugins/rainbow-generate/src/params.rs:297— plugins/rainbow-generate/src/params.rs:297-308 | plugins/space-convert/src/lib.rs:955-966 — before extracting anything, compare `plugins/rainbow-generate/src/params.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 3 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 (12 lines × 2) plugins/scatter-map/src/lib.rs:1636— plugins/scatter-map/src/lib.rs:1636-1647 | plugins/scatter-map/src/lib.rs:2057-2068 — 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 `plugins/scatter-map/src/lib.rs:1636` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) plugins/space-convert/src/lib.rs:1260— plugins/space-convert/src/lib.rs:1260-1271 | plugins/space-convert/src/lib.rs:2076-2087 — 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 `plugins/space-convert/src/lib.rs:1260` 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 × 2) plugins/gradient-blur/src/lib.rs:646— plugins/gradient-blur/src/lib.rs:646-657 | plugins/gradient-displace/src/lib.rs:572-583 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/image-relight/src/gpu/mod.rs:422— plugins/image-relight/src/gpu/mod.rs:422-433 | plugins/pixel-extend/src/gpu/mod.rs:591-602 — before extracting anything, compare `plugins/image-relight/src/gpu/mod.rs` and `plugins/pixel-extend/src/gpu/mod.rs` as WHOLE FILES: this scan already matched 7 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 `plugins/image-relight/src/gpu/mod.rs:422` 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 (14 lines × 2) plugins/displace-scatter/src/lib.rs:409— plugins/displace-scatter/src/lib.rs:409-422 | plugins/gabor-generate/src/lib.rs:199-212 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 171 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:409` 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 (14 lines × 2) plugins/fourier-filter/src/lib.rs:1900— plugins/fourier-filter/src/lib.rs:1900-1913 | plugins/image-scaler/src/lib.rs:1311-1324 — before extracting anything, compare `plugins/fourier-filter/src/lib.rs` and `plugins/image-scaler/src/lib.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) plugins/fourier-filter/src/lib.rs:1915— plugins/fourier-filter/src/lib.rs:1915-1928 | plugins/image-scaler/src/lib.rs:1326-1339 — before extracting anything, compare `plugins/fourier-filter/src/lib.rs` and `plugins/image-scaler/src/lib.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) plugins/fourier-filter/src/lib.rs:1930— plugins/fourier-filter/src/lib.rs:1930-1943 | plugins/image-scaler/src/lib.rs:1341-1354 — before extracting anything, compare `plugins/fourier-filter/src/lib.rs` and `plugins/image-scaler/src/lib.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) plugins/glass-displace/src/render.rs:701— plugins/glass-displace/src/render.rs:701-714 | plugins/rainbow-generate/src/lib.rs:646-659 — before extracting anything, compare `plugins/glass-displace/src/render.rs` and `plugins/rainbow-generate/src/lib.rs` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/glass-displace/src/render.rs:701` 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 (14 lines × 2) plugins/image-transform/src/lib.rs:518— plugins/image-transform/src/lib.rs:518-531 | plugins/space-convert/src/lib.rs:976-989 — before extracting anything, compare `plugins/image-transform/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/image-transform/src/lib.rs:518` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) plugins/mobius-transform/src/lib.rs:936— plugins/mobius-transform/src/lib.rs:936-949 | plugins/mobius-transform/src/lib.rs:1140-1153 — 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 `plugins/mobius-transform/src/lib.rs:936` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) plugins/fourier-filter/src/lib.rs:438— plugins/fourier-filter/src/lib.rs:438-451 | plugins/light-wrap/src/lib.rs:345-358 — before extracting anything, compare `plugins/fourier-filter/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fourier-filter/src/lib.rs:438` 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 (13 lines × 2) plugins/color-composite/src/lib.rs:412— plugins/color-composite/src/lib.rs:412-424 | plugins/color-select/src/lib.rs:141-153 — before extracting anything, compare `plugins/color-composite/src/lib.rs` and `plugins/color-select/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-composite/src/lib.rs:412` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) plugins/displace-scatter/src/lib.rs:895— plugins/displace-scatter/src/lib.rs:895-907 | plugins/scatter-map/src/lib.rs:883-895 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:895` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) plugins/glass-displace/src/params.rs:132— plugins/glass-displace/src/params.rs:132-144 | plugins/glass-displace/src/params.rs:480-492 — 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 `plugins/glass-displace/src/params.rs:132` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) plugins/glass-displace/src/params.rs:342— plugins/glass-displace/src/params.rs:342-354 | plugins/space-convert/src/lib.rs:518-530 — before extracting anything, compare `plugins/glass-displace/src/params.rs` and `plugins/space-convert/src/lib.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/glass-displace/src/params.rs:342` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) plugins/glass-displace/src/plugin.rs:99— plugins/glass-displace/src/plugin.rs:99-111 | plugins/scatter-map/src/lib.rs:782-794 — before extracting anything, compare `plugins/glass-displace/src/plugin.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/gradient-blur/src/lib.rs:560— plugins/gradient-blur/src/lib.rs:560-572 | plugins/gradient-displace/src/lib.rs:486-498 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) plugins/image-relight/src/gpu/mod.rs:191— plugins/image-relight/src/gpu/mod.rs:191-203 | plugins/pixel-extend/src/gpu/mod.rs:299-311 — before extracting anything, compare `plugins/image-relight/src/gpu/mod.rs` and `plugins/pixel-extend/src/gpu/mod.rs` as WHOLE FILES: this scan already matched 7 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 `plugins/image-relight/src/gpu/mod.rs:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) plugins/image-relight/src/lib.rs:405— plugins/image-relight/src/lib.rs:405-417 | plugins/space-convert/src/lib.rs:314-326 — before extracting anything, compare `plugins/image-relight/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×7
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/utils/src/image.rs:436— crates/utils/src/image.rs:436-443 | plugins/color-boundary-blur/src/lib.rs:1459-1466 | plugins/depth-fog/src/lib.rs:462-469 | plugins/pixel-extend/src/lib.rs:2175-2182 — 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) plugins/channel-remap/src/lib.rs:729— plugins/channel-remap/src/lib.rs:729-741 | plugins/color-change/src/lib.rs:402-414 | plugins/color-composite/src/lib.rs:1554-1566 | plugins/color-select/src/lib.rs:475-487 — 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) plugins/checker-generate/src/lib.rs:737— plugins/checker-generate/src/lib.rs:737-787 | plugins/light-wrap/src/lib.rs:1724-1746 | plugins/pixel-extend/src/lib.rs:2221-2237 | plugins/voronoi-generate/src/lib.rs:1432-1505 — 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) plugins/checker-generate/src/lib.rs:789— plugins/checker-generate/src/lib.rs:789-800 | plugins/color-composite/src/lib.rs:1282-1293 | plugins/light-wrap/src/lib.rs:1748-1759 | plugins/voronoi-generate/src/lib.rs:1507-1518 — 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) plugins/color-boundary-blur/src/lib.rs:1380— plugins/color-boundary-blur/src/lib.rs:1380-1395 | plugins/image-scaler/src/lib.rs:884-902 | plugins/pixel-extend/src/lib.rs:2249-2266 | plugins/scatter-map/src/lib.rs:1460-1479 — 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) plugins/differential-generate/src/lib.rs:493— plugins/differential-generate/src/lib.rs:493-510 | plugins/displace-scatter/src/lib.rs:2505-2523 | plugins/gradient-blur/src/lib.rs:574-592 | plugins/gradient-displace/src/lib.rs:500-518 — 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) plugins/fft/src/lib.rs:332— plugins/fft/src/lib.rs:332-351 | plugins/fourier-filter/src/lib.rs:2177-2196 | plugins/ifft/src/lib.rs:394-413 | plugins/singular-value-decompose/src/lib.rs:363-382 — 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 (9 lines × 3) plugins/channel-remap/src/lib.rs:1036— plugins/channel-remap/src/lib.rs:1036-1044 | plugins/color-convert/src/lib.rs:471-479 | plugins/image-calculate/src/lib.rs:1497-1505 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:1036` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) plugins/checker-generate/src/lib.rs:742— plugins/checker-generate/src/lib.rs:742-750 | plugins/pixel-extend/src/lib.rs:2225-2233 | plugins/voronoi-generate/src/lib.rs:1437-1445 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 6 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 (9 lines × 3) plugins/color-boundary-blur/src/lib.rs:146— plugins/color-boundary-blur/src/lib.rs:146-154 | plugins/color-composite/src/lib.rs:410-418 | plugins/color-select/src/lib.rs:139-147 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/color-composite/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/color-composite/src/lib.rs:1400— plugins/color-composite/src/lib.rs:1400-1408 | plugins/color-composite/src/lib.rs:1443-1451 | plugins/voronoi-generate/src/lib.rs:1529-1537 — before extracting anything, compare `plugins/color-composite/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-composite/src/lib.rs:1400` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) plugins/glass-displace/src/render.rs:278— plugins/glass-displace/src/render.rs:278-286 | plugins/image-transform/src/lib.rs:501-509 | plugins/rainbow-generate/src/lib.rs:382-390 — before extracting anything, compare `plugins/glass-displace/src/render.rs` and `plugins/rainbow-generate/src/lib.rs` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/glass-displace/src/render.rs:278` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) plugins/image-scaler/src/lib.rs:1161— plugins/image-scaler/src/lib.rs:1161-1169 | plugins/mobius-transform/src/lib.rs:847-855 | plugins/pixel-extend/src/lib.rs:2116-2124 — before extracting anything, compare `plugins/image-scaler/src/lib.rs` and `plugins/mobius-transform/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/mobius-transform/src/lib.rs:847` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `d` to `f32` in one and `f64` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 3) plugins/image-relight/src/lib.rs:1535— plugins/image-relight/src/lib.rs:1535-1543 | plugins/image-transform/src/lib.rs:657-665 | plugins/space-convert/src/lib.rs:1093-1101 — before extracting anything, compare `plugins/image-relight/src/lib.rs` and `plugins/image-transform/src/lib.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/checker-generate/src/lib.rs:539— plugins/checker-generate/src/lib.rs:539-545 | plugins/displace-scatter/src/lib.rs:1222-1230 | plugins/gabor-generate/src/lib.rs:601-607 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/checker-generate/src/lib.rs:539` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) plugins/color-boundary-blur/src/lib.rs:1188— plugins/color-boundary-blur/src/lib.rs:1188-1194 | plugins/light-wrap/src/lib.rs:1471-1477 | plugins/light-wrap/src/lib.rs:1483-1489 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/color-boundary-blur/src/lib.rs:1188` 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 × 3) plugins/color-boundary-blur/src/lib.rs:1389— plugins/color-boundary-blur/src/lib.rs:1389-1395 | plugins/image-scaler/src/lib.rs:895-902 | plugins/pixel-extend/src/lib.rs:2259-2266 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/image-scaler/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:1389` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) plugins/gradient-blur/src/lib.rs:669— plugins/gradient-blur/src/lib.rs:669-675 | plugins/gradient-displace/src/lib.rs:595-601 | plugins/pixel-extend/src/lib.rs:2290-2296 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/displace-scatter/src/lib.rs:2542— plugins/displace-scatter/src/lib.rs:2542-2548 | plugins/gradient-blur/src/lib.rs:544-550 | plugins/gradient-displace/src/lib.rs:470-476 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 3) plugins/color-boundary-blur/src/lib.rs:392— plugins/color-boundary-blur/src/lib.rs:392-398 | plugins/color-composite/src/lib.rs:613-619 | plugins/color-select/src/lib.rs:266-272 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/color-composite/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/image-relight/src/lib.rs:2860— plugins/image-relight/src/lib.rs:2860-2866 | plugins/light-wrap/src/lib.rs:1894-1900 | plugins/normal-generate/src/lib.rs:859-865 — before extracting anything, compare `plugins/image-relight/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×6
Duplicated block (17 lines × 2) plugins/distance-generate/src/lib.rs:86— plugins/distance-generate/src/lib.rs:86-102 | plugins/pixel-extend/src/lib.rs:568-584 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/distance-generate/src/lib.rs:86` 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) plugins/fourier-filter/src/lib.rs:1963— plugins/fourier-filter/src/lib.rs:1963-1979 | plugins/image-scaler/src/lib.rs:1374-1390 — before extracting anything, compare `plugins/fourier-filter/src/lib.rs` and `plugins/image-scaler/src/lib.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fourier-filter/src/lib.rs:1963` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) plugins/gabor-generate/src/lib.rs:345— plugins/gabor-generate/src/lib.rs:345-361 | plugins/voronoi-generate/src/lib.rs:371-387 — before extracting anything, compare `plugins/gabor-generate/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gabor-generate/src/lib.rs:345` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/voronoi-generate/src/lib.rs:369` calls `Ok` and `plugins/gabor-generate/src/lib.rs:344` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 2) plugins/gradient-blur/src/lib.rs:334— plugins/gradient-blur/src/lib.rs:334-350 | plugins/gradient-displace/src/lib.rs:307-323 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gradient-blur/src/lib.rs:334` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) plugins/mobius-transform/src/lib.rs:986— plugins/mobius-transform/src/lib.rs:986-1002 | plugins/mobius-transform/src/lib.rs:1043-1059 — 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 `plugins/mobius-transform/src/lib.rs:986` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) plugins/mobius-transform/src/lib.rs:1187— plugins/mobius-transform/src/lib.rs:1187-1203 | plugins/mobius-transform/src/lib.rs:1241-1257 — 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 `plugins/mobius-transform/src/lib.rs:1187` 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) plugins/color-composite/src/lib.rs:1435— plugins/color-composite/src/lib.rs:1435-1449 | plugins/voronoi-generate/src/lib.rs:1521-1535 — before extracting anything, compare `plugins/color-composite/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/color-quantize/src/lib.rs:1076— plugins/color-quantize/src/lib.rs:1076-1090 | plugins/color-quantize/src/lib.rs:1124-1138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) plugins/color-select/src/lib.rs:120— plugins/color-select/src/lib.rs:120-134 | plugins/line-repaint/src/lib.rs:71-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 `plugins/color-select/src/lib.rs:120` 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) plugins/displace-scatter/src/lib.rs:2578— plugins/displace-scatter/src/lib.rs:2578-2592 | plugins/scatter-map/src/lib.rs:3368-3382 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) plugins/differential-generate/src/lib.rs:242— plugins/differential-generate/src/lib.rs:242-256 | plugins/differential-generate/src/lib.rs:334-348 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/differential-generate/src/lib.rs:349` calls `world_type` and `plugins/differential-generate/src/lib.rs:257` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) plugins/image-calculate/src/lib.rs:261— plugins/image-calculate/src/lib.rs:261-275 | plugins/voronoi-generate/src/lib.rs:375-389 — before extracting anything, compare `plugins/image-calculate/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/image-calculate/src/lib.rs:261` 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.
color_quantize::init_centroids_kmeans_parallel (cognitive 57) plugins/color-quantize/src/lib.rs:1348— color_quantize::init_centroids_kmeans_parallel has cognitive complexity 57 (threshold 15). Drivers by points: if/else 16 (35 pts), loops 11 (19 pts), boolean chains 3 (nesting depth added 27). 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.
color_quantize::run_kmeans (cognitive 32) plugins/color-quantize/src/lib.rs:1161— color_quantize::run_kmeans has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 7 (10 pts), boolean chains 2 (nesting depth added 14). 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.
color_quantize::run_xmeans (cognitive 21) plugins/color-quantize/src/lib.rs:891— color_quantize::run_xmeans has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (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. This shape REPEATS in the file: one other method here (color_quantize::run_gmeans) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
color_quantize::run_gmeans (cognitive 21) plugins/color-quantize/src/lib.rs:980— color_quantize::run_gmeans has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (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. This shape REPEATS in the file: one other method here (color_quantize::run_xmeans) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
color_quantize::init_centroids_area_based (cognitive 17) plugins/color-quantize/src/lib.rs:1491— color_quantize::init_centroids_area_based has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). 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.
image_relight::region_boundary_distance (cognitive 47) plugins/image-relight/src/lib.rs:1783— image_relight::region_boundary_distance has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (32 pts), boolean chains 8, loops 5 (7 pts) (nesting depth added 21). 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.
image_relight::normals_from_regions (cognitive 36) plugins/image-relight/src/lib.rs:2376— image_relight::normals_from_regions has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (33 pts), loops 2 (3 pts) (nesting depth added 17). 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.
image_relight::solve_poisson_cpu (cognitive 27) plugins/image-relight/src/lib.rs:2231— image_relight::solve_poisson_cpu has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 5 (9 pts), boolean chains 2 (nesting depth added 13). 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.
image_relight::build_surface_maps (cognitive 22) plugins/image-relight/src/lib.rs:1605— image_relight::build_surface_maps has cognitive complexity 22 (threshold 15). Drivers by points: loops 2 (9 pts), if/else 3 (8 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 13). 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.
image_relight::normalize_component_heights (cognitive 18) plugins/image-relight/src/lib.rs:2099— image_relight::normalize_component_heights has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (5 pts), boolean chains 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.
Duplicated block (19 lines × 2) plugins/checker-generate/src/lib.rs:222— plugins/checker-generate/src/lib.rs:222-240 | plugins/light-wrap/src/lib.rs:457-475 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/checker-generate/src/lib.rs:222` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) plugins/color-ajust/src/lib.rs:323— plugins/color-ajust/src/lib.rs:323-341 | plugins/color-ajust/src/lib.rs:347-365 — 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 `plugins/color-ajust/src/lib.rs:323` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) plugins/glass-displace/src/params.rs:355— plugins/glass-displace/src/params.rs:355-373 | plugins/rainbow-generate/src/params.rs:463-481 — before extracting anything, compare `plugins/glass-displace/src/params.rs` and `plugins/rainbow-generate/src/params.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/glass-displace/src/params.rs:355` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) plugins/gradient-blur/src/lib.rs:198— plugins/gradient-blur/src/lib.rs:198-216 | plugins/gradient-displace/src/lib.rs:185-203 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gradient-blur/src/lib.rs:198` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) plugins/gradient-blur/src/lib.rs:660— plugins/gradient-blur/src/lib.rs:660-678 | plugins/gradient-displace/src/lib.rs:586-604 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 3) plugins/color-ajust/src/lib.rs:328— plugins/color-ajust/src/lib.rs:328-339 | plugins/color-ajust/src/lib.rs:352-363 | plugins/color-ajust/src/lib.rs:376-387 — 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 `plugins/color-ajust/src/lib.rs:328` 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 × 3) plugins/color-boundary-blur/src/lib.rs:277— plugins/color-boundary-blur/src/lib.rs:277-288 | plugins/glass-displace/src/params.rs:365-376 | plugins/rainbow-generate/src/params.rs:473-484 — before extracting anything, compare `plugins/glass-displace/src/params.rs` and `plugins/rainbow-generate/src/params.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/distance-generate/src/lib.rs:86— plugins/distance-generate/src/lib.rs:86-97 | plugins/gabor-generate/src/lib.rs:292-303 | plugins/pixel-extend/src/lib.rs:568-579 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/distance-generate/src/lib.rs:86` 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 × 3) plugins/glass-displace/src/plugin.rs:56— plugins/glass-displace/src/plugin.rs:56-67 | plugins/image-encrypt-decrypt/src/lib.rs:302-313 | plugins/scatter-map/src/lib.rs:756-767 — before extracting anything, compare `plugins/glass-displace/src/plugin.rs` and `plugins/image-encrypt-decrypt/src/lib.rs` as WHOLE FILES: this scan already matched 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/glass-displace/src/plugin.rs:56` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/glass-displace/src/plugin.rs:68` calls `set_out_flag2` and `plugins/image-encrypt-decrypt/src/lib.rs:314` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 3) plugins/differential-generate/src/gpu/wgpu/mod.rs:141— plugins/differential-generate/src/gpu/wgpu/mod.rs:141-152 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:152-163 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:132-143 — before extracting anything, compare `plugins/differential-generate/src/gpu/wgpu/mod.rs` and `plugins/gabor-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 193 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/differential-generate/src/gpu/wgpu/mod.rs:141` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:130` calls `calc_out_len` and `plugins/differential-generate/src/gpu/wgpu/mod.rs:138` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) plugins/color-boundary-blur/src/lib.rs:202— plugins/color-boundary-blur/src/lib.rs:202-211 | plugins/gradient-blur/src/lib.rs:92-101 | plugins/light-wrap/src/lib.rs:239-248 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:202` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/gradient-blur/src/lib.rs:88` calls `add` and `plugins/light-wrap/src/lib.rs:235` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) plugins/color-convert/src/lib.rs:576— plugins/color-convert/src/lib.rs:576-585 | plugins/distance-generate/src/lib.rs:474-483 | plugins/voronoi-generate/src/lib.rs:666-675 — before extracting anything, compare `plugins/color-convert/src/lib.rs` and `plugins/distance-generate/src/lib.rs` as WHOLE FILES: this scan already matched 8 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/color-convert/src/lib.rs:576` 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) plugins/displace-scatter/src/lib.rs:801— plugins/displace-scatter/src/lib.rs:801-811 | plugins/glass-displace/src/params.rs:369-378 | plugins/scatter-map/src/lib.rs:716-725 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/glass-displace/src/params.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/displace-scatter/src/lib.rs:801` 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 (10 lines × 3) plugins/mobius-transform/src/lib.rs:930— plugins/mobius-transform/src/lib.rs:930-939 | plugins/mobius-transform/src/lib.rs:981-990 | plugins/mobius-transform/src/lib.rs:1038-1047 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) plugins/mobius-transform/src/lib.rs:1134— plugins/mobius-transform/src/lib.rs:1134-1143 | plugins/mobius-transform/src/lib.rs:1182-1191 | plugins/mobius-transform/src/lib.rs:1236-1245 — 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.
space_convert::render_coordinates (cognitive 114) plugins/space-convert/src/lib.rs:1190— space_convert::render_coordinates has cognitive complexity 114 (threshold 15). Drivers by points: if/else 44 (102 pts), boolean chains 6, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 61). 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.
space_convert::forward_hough_post_transformed (cognitive 32) plugins/space-convert/src/lib.rs:1680— space_convert::forward_hough_post_transformed has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 5 (13 pts) (nesting depth added 17). 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.
space_convert::forward_hough (cognitive 31) plugins/space-convert/src/lib.rs:1815— space_convert::forward_hough has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 5 (13 pts) (nesting depth added 17). 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.
space_convert::backproject (cognitive 17) plugins/space-convert/src/lib.rs:2054— space_convert::backproject has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 6). 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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) plugins/rainbow-generate/src/gradient.rs:730— plugins/rainbow-generate/src/gradient.rs:730-744 | plugins/rainbow-generate/src/gradient.rs:746-760 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) plugins/pixel-extend/src/lib.rs:1847— plugins/pixel-extend/src/lib.rs:1847-1864 | plugins/pixel-extend/src/lib.rs:2045-2059 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) plugins/displace-scatter/src/lib.rs:2555— plugins/displace-scatter/src/lib.rs:2555-2575 | plugins/scatter-map/src/lib.rs:3351-3365 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) plugins/pixel-extend/src/lib.rs:2012— plugins/pixel-extend/src/lib.rs:2012-2033 | plugins/pixel-extend/src/lib.rs:2087-2101 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) plugins/rainbow-generate/src/gradient.rs:479— plugins/rainbow-generate/src/gradient.rs:479-491 | plugins/rainbow-generate/src/gradient.rs:536-548 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) plugins/gabor-generate/src/lib.rs:1029— plugins/gabor-generate/src/lib.rs:1029-1042 | plugins/gabor-generate/src/lib.rs:1143-1155 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) plugins/glass-displace/src/render.rs:792— plugins/glass-displace/src/render.rs:792-804 | plugins/image-encrypt-decrypt/src/lib.rs:642-654 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) plugins/image-encrypt-decrypt/src/lib.rs:981— plugins/image-encrypt-decrypt/src/lib.rs:981-993 | plugins/image-encrypt-decrypt/src/lib.rs:995-1010 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) plugins/channel-remap/src/lib.rs:659— plugins/channel-remap/src/lib.rs:659-676 | plugins/color-composite/src/lib.rs:1502-1513 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) plugins/image-scaler/src/lib.rs:1222— plugins/image-scaler/src/lib.rs:1222-1238 | plugins/scatter-map/src/lib.rs:3295-3306 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) plugins/color-quantize/src/lib.rs:1862— plugins/color-quantize/src/lib.rs:1862-1873 | plugins/color-quantize/src/lib.rs:1879-1896 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) plugins/color-boundary-blur/src/lib.rs:1367— plugins/color-boundary-blur/src/lib.rs:1367-1378 | plugins/image-scaler/src/lib.rs:1240-1252 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) plugins/color-composite/src/lib.rs:1341— plugins/color-composite/src/lib.rs:1341-1348 | plugins/color-composite/src/lib.rs:1350-1357 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) plugins/image-transform/src/lib.rs:92— plugins/image-transform/src/lib.rs:92-99 | plugins/space-convert/src/lib.rs:179-186 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) plugins/image-encrypt-decrypt/src/lib.rs:761— plugins/image-encrypt-decrypt/src/lib.rs:761-768 | plugins/image-encrypt-decrypt/src/lib.rs:776-783 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) plugins/displace-scatter/src/lib.rs:1626— plugins/displace-scatter/src/lib.rs:1626-1634 | plugins/scatter-map/src/lib.rs:1439-1446 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) plugins/mobius-transform/src/lib.rs:779— plugins/mobius-transform/src/lib.rs:779-785 | plugins/mobius-transform/src/lib.rs:893-899 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) plugins/fourier-filter/src/lib.rs:2106— plugins/fourier-filter/src/lib.rs:2106-2113 | plugins/glass-displace/src/glass.rs:555-561 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) plugins/color-change/src/lib.rs:219— plugins/color-change/src/lib.rs:219-225 | plugins/eyedropper-mask/src/lib.rs:332-338 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) plugins/color-boundary-blur/src/lib.rs:1413— plugins/color-boundary-blur/src/lib.rs:1413-1423 | plugins/eyedropper-mask/src/lib.rs:653-659 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (16 lines × 2) plugins/checker-generate/src/lib.rs:257— plugins/checker-generate/src/lib.rs:257-272 | plugins/voronoi-generate/src/lib.rs:353-368 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/checker-generate/src/lib.rs:257` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/voronoi-generate/src/lib.rs:369` calls `Ok` and `plugins/checker-generate/src/lib.rs:274` 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 (16 lines × 2) plugins/color-composite/src/lib.rs:503— plugins/color-composite/src/lib.rs:503-518 | plugins/eyedropper-mask/src/lib.rs:224-239 — before extracting anything, compare `plugins/color-composite/src/lib.rs` and `plugins/eyedropper-mask/src/lib.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-composite/src/lib.rs:503` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) plugins/distance-generate/src/lib.rs:65— plugins/distance-generate/src/lib.rs:65-80 | plugins/voronoi-generate/src/lib.rs:260-275 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/distance-generate/src/lib.rs:65` 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 (16 lines × 2) plugins/color-quantize/src/lib.rs:682— plugins/color-quantize/src/lib.rs:682-697 | plugins/color-quantize/src/lib.rs:743-758 — 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 `plugins/color-quantize/src/lib.rs:682` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 4) plugins/mobius-transform/src/lib.rs:987— plugins/mobius-transform/src/lib.rs:987-995 | plugins/mobius-transform/src/lib.rs:1044-1052 | plugins/mobius-transform/src/lib.rs:1188-1196 | plugins/mobius-transform/src/lib.rs:1242-1250 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/mobius-transform/src/lib.rs:987` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) plugins/mobius-transform/src/lib.rs:998— plugins/mobius-transform/src/lib.rs:998-1006 | plugins/mobius-transform/src/lib.rs:1055-1063 | plugins/mobius-transform/src/lib.rs:1199-1207 | plugins/mobius-transform/src/lib.rs:1253-1261 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/mobius-transform/src/lib.rs:998` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) plugins/color-quantize/src/gpu/wgpu/mod.rs:130— plugins/color-quantize/src/gpu/wgpu/mod.rs:130-138 | plugins/differential-generate/src/gpu/wgpu/mod.rs:89-97 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:85-93 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:86-94 — before extracting anything, compare `plugins/differential-generate/src/gpu/wgpu/mod.rs` and `plugins/gabor-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 193 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-quantize/src/gpu/wgpu/mod.rs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) plugins/channel-remap/src/lib.rs:763— plugins/channel-remap/src/lib.rs:763-771 | plugins/fourier-filter/src/lib.rs:2128-2136 | plugins/image-calculate/src/lib.rs:1195-1203 | plugins/singular-value-decompose/src/lib.rs:348-356 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/channel-remap/src/lib.rs:336— plugins/channel-remap/src/lib.rs:336-343 | plugins/fourier-filter/src/lib.rs:601-608 | plugins/image-scaler/src/lib.rs:481-488 | plugins/light-wrap/src/lib.rs:564-571 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:336` 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) plugins/channel-remap/src/lib.rs:970— plugins/channel-remap/src/lib.rs:970-977 | plugins/color-convert/src/lib.rs:390-397 | plugins/color-quantize/src/lib.rs:1705-1712 | plugins/image-calculate/src/lib.rs:1431-1438 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/color-boundary-blur/src/lib.rs:1184— plugins/color-boundary-blur/src/lib.rs:1184-1191 | plugins/color-boundary-blur/src/lib.rs:1196-1203 | plugins/light-wrap/src/lib.rs:1467-1474 | plugins/light-wrap/src/lib.rs:1479-1486 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/color-boundary-blur/src/lib.rs:1184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) plugins/differential-generate/src/lib.rs:422— plugins/differential-generate/src/lib.rs:422-429 | plugins/displace-scatter/src/lib.rs:1601-1608 | plugins/gradient-blur/src/lib.rs:378-385 | plugins/gradient-displace/src/lib.rs:351-358 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/channel-remap/src/lib.rs:986— plugins/channel-remap/src/lib.rs:986-993 | plugins/color-convert/src/lib.rs:409-416 | plugins/image-calculate/src/lib.rs:1447-1454 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/channel-remap/src/lib.rs:1002— plugins/channel-remap/src/lib.rs:1002-1009 | plugins/color-convert/src/lib.rs:428-435 | plugins/image-calculate/src/lib.rs:1463-1470 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/color-boundary-blur/src/lib.rs:383— plugins/color-boundary-blur/src/lib.rs:383-390 | plugins/color-composite/src/lib.rs:604-611 | plugins/color-select/src/lib.rs:257-264 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/color-composite/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) plugins/image-encrypt-decrypt/src/lib.rs:315— plugins/image-encrypt-decrypt/src/lib.rs:315-326 | plugins/rainbow-generate/src/lib.rs:87-94 | plugins/scatter-map/src/lib.rs:770-777 — before extracting anything, compare `plugins/image-encrypt-decrypt/src/lib.rs` and `plugins/rainbow-generate/src/lib.rs` as WHOLE FILES: this scan already matched 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/image-encrypt-decrypt/src/lib.rs:315` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 4) plugins/fft/src/lib.rs:264— plugins/fft/src/lib.rs:264-270 | plugins/fourier-filter/src/lib.rs:1015-1021 | plugins/ifft/src/lib.rs:282-288 | plugins/singular-value-decompose/src/lib.rs:224-230 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fft/src/lib.rs: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/ifft/src/lib.rs:278` calls `world_type`, `width`, `height` and `plugins/fft/src/lib.rs:262` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 4) crates/utils/src/image.rs:437— crates/utils/src/image.rs:437-443 | plugins/color-boundary-blur/src/lib.rs:1460-1466 | plugins/depth-fog/src/lib.rs:463-469 | plugins/pixel-extend/src/lib.rs:2176-2182 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/depth-fog/src/lib.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines 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 × 4) plugins/fft/src/lib.rs:310— plugins/fft/src/lib.rs:310-316 | plugins/fourier-filter/src/lib.rs:2156-2162 | plugins/ifft/src/lib.rs:336-342 | plugins/singular-value-decompose/src/lib.rs:340-346 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/differential-generate/src/gpu/wgpu/mod.rs:132— plugins/differential-generate/src/gpu/wgpu/mod.rs:132-138 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:138-144 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:122-128 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:144-150 — before extracting anything, compare `plugins/differential-generate/src/gpu/wgpu/mod.rs` and `plugins/gabor-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 193 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:130` calls `calc_out_len` and `plugins/differential-generate/src/gpu/wgpu/mod.rs:140` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
scatter_map::render_gather_layers (cognitive 51) plugins/scatter-map/src/lib.rs:1585— scatter_map::render_gather_layers has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (32 pts), loops 7 (15 pts), boolean chains 4 (nesting depth added 28). 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.
scatter_map::build_swap_permutation_for_partition (cognitive 26) plugins/scatter-map/src/lib.rs:2295— scatter_map::build_swap_permutation_for_partition has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 13). 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.
scatter_map::render_non_overlapping_gather_layer (cognitive 16) plugins/scatter-map/src/lib.rs:1731— scatter_map::render_non_overlapping_gather_layer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (7 pts), boolean chains 1 (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.
color_boundary_blur::detect_boundaries (cognitive 29) plugins/color-boundary-blur/src/lib.rs:763— color_boundary_blur::detect_boundaries has cognitive complexity 29 (threshold 15). Drivers by points: if/else 4 (18 pts), loops 4 (10 pts), boolean chains 1 (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.
color_boundary_blur::gaussian_blur_pixels (cognitive 16) plugins/color-boundary-blur/src/lib.rs:1089— color_boundary_blur::gaussian_blur_pixels has cognitive complexity 16 (threshold 15). Drivers by points: loops 7 (14 pts), if/else 2 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (color_boundary_blur::gaussian_blur_scalar) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
color_boundary_blur::gaussian_blur_scalar (cognitive 16) plugins/color-boundary-blur/src/lib.rs:1170— color_boundary_blur::gaussian_blur_scalar has cognitive complexity 16 (threshold 15). Drivers by points: loops 7 (14 pts), if/else 2 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (color_boundary_blur::gaussian_blur_pixels) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TooManyFields: Settings plugins/image-relight/src/lib.rs:158— TooManyFields — 42 stored fields. The bar is 30 stored fields; this is 12 over it, 1.40× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: RenderSettings plugins/displace-scatter/src/lib.rs:192— TooManyFields — 41 stored fields. The bar is 30 stored fields; this is 11 over it, 1.37× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: RenderSettings plugins/scatter-map/src/lib.rs:153— TooManyFields — 35 stored fields. The bar is 30 stored fields; this is 5 over it, 1.17× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×3
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium vulnerability · ×3
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/utils/src/spectral_wgpu.rs:23— crates/utils/src/spectral_wgpu.rs:23-59 | plugins/differential-generate/src/gpu/wgpu/mod.rs:34-70 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:42-78 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:28-64 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:43-79 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/utils/src/spectral_wgpu.rs:384— crates/utils/src/spectral_wgpu.rs:384-393 | plugins/color-quantize/src/gpu/wgpu/mod.rs:635-644 | plugins/differential-generate/src/gpu/wgpu/mod.rs:306-315 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:296-305 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:298-307 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) plugins/displace-scatter/src/lib.rs:2659— plugins/displace-scatter/src/lib.rs:2659-2666 | plugins/gabor-generate/src/lib.rs:1209-1216 | plugins/gabor-generate/src/lib.rs:1218-1226 | plugins/scatter-map/src/lib.rs:3324-3331 | plugins/voronoi-generate/src/lib.rs:1251-1257 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) plugins/color-composite/src/lib.rs:1434— plugins/color-composite/src/lib.rs:1434-1451 | plugins/voronoi-generate/src/lib.rs:1520-1537 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) plugins/color-composite/src/lib.rs:1391— plugins/color-composite/src/lib.rs:1391-1408 | plugins/pixel-extend/src/lib.rs:2280-2299 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) plugins/fourier-filter/src/lib.rs:1527— plugins/fourier-filter/src/lib.rs:1527-1544 | plugins/fourier-filter/src/lib.rs:1552-1573 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (24 lines × 2) plugins/checker-generate/src/lib.rs:751— plugins/checker-generate/src/lib.rs:751-774 | plugins/voronoi-generate/src/lib.rs:1446-1469 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/gradient-blur/src/lib.rs:443— plugins/gradient-blur/src/lib.rs:443-466 | plugins/gradient-displace/src/lib.rs:369-392 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) plugins/image-relight/src/gpu/mod.rs:335— plugins/image-relight/src/gpu/mod.rs:335-358 | plugins/pixel-extend/src/gpu/mod.rs:447-473 — before extracting anything, compare `plugins/image-relight/src/gpu/mod.rs` and `plugins/pixel-extend/src/gpu/mod.rs` as WHOLE FILES: this scan already matched 7 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 `plugins/image-relight/src/gpu/mod.rs:335` 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 (21 lines × 2) plugins/distance-generate/src/lib.rs:120— plugins/distance-generate/src/lib.rs:120-140 | plugins/normal-generate/src/lib.rs:111-131 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/normal-generate/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 182 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/distance-generate/src/lib.rs: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 (21 lines × 2) plugins/scatter-map/src/lib.rs:1668— plugins/scatter-map/src/lib.rs:1668-1688 | plugins/scatter-map/src/lib.rs:1748-1768 — 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 `plugins/scatter-map/src/lib.rs:1668` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) plugins/space-convert/src/lib.rs:1658— plugins/space-convert/src/lib.rs:1658-1678 | plugins/space-convert/src/lib.rs:1793-1813 — 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 `plugins/space-convert/src/lib.rs:1658` 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) plugins/displace-scatter/src/lib.rs:1664— plugins/displace-scatter/src/lib.rs:1664-1681 | plugins/light-wrap/src/lib.rs:1762-1779 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) plugins/distance-generate/src/lib.rs:99— plugins/distance-generate/src/lib.rs:99-116 | plugins/gabor-generate/src/lib.rs:338-355 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/distance-generate/src/lib.rs:99` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) plugins/gradient-blur/src/lib.rs:469— plugins/gradient-blur/src/lib.rs:469-486 | plugins/gradient-displace/src/lib.rs:395-412 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15–16 lines × 2) plugins/color-ajust/src/lib.rs:92— plugins/color-ajust/src/lib.rs:92-107 | plugins/color-convert/src/lib.rs:81-95 — before extracting anything, compare `plugins/color-ajust/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-ajust/src/lib.rs:92` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 2) plugins/image-transform/src/lib.rs:194— plugins/image-transform/src/lib.rs:194-208 | plugins/pixel-extend/src/lib.rs:884-899 — before extracting anything, compare `plugins/image-transform/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/image-transform/src/lib.rs:194` 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, `plugins/pixel-extend/src/lib.rs:881` calls `set_options` and `plugins/image-transform/src/lib.rs:193` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 2) plugins/space-convert/src/lib.rs:1696— plugins/space-convert/src/lib.rs:1696-1710 | plugins/space-convert/src/lib.rs:1829-1844 — 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 `plugins/space-convert/src/lib.rs:1696` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) plugins/color-boundary-blur/src/lib.rs:281— plugins/color-boundary-blur/src/lib.rs:281-293 | plugins/gradient-blur/src/lib.rs:119-131 | plugins/gradient-displace/src/lib.rs:106-118 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:281` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 3) plugins/color-convert/src/lib.rs:250— plugins/color-convert/src/lib.rs:250-262 | plugins/color-convert/src/lib.rs:268-280 | plugins/color-convert/src/lib.rs:286-298 — 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 `plugins/color-convert/src/lib.rs:250` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) plugins/differential-generate/src/lib.rs:124— plugins/differential-generate/src/lib.rs:124-136 | plugins/gradient-blur/src/lib.rs:125-137 | plugins/gradient-displace/src/lib.rs:112-124 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/differential-generate/src/lib.rs:124` 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 × 4) plugins/channel-remap/src/lib.rs:730— plugins/channel-remap/src/lib.rs:730-741 | plugins/color-change/src/lib.rs:403-414 | plugins/color-composite/src/lib.rs:1555-1566 | plugins/color-select/src/lib.rs:476-487 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-change/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 4) plugins/distance-generate/src/lib.rs:116— plugins/distance-generate/src/lib.rs:116-127 | plugins/light-wrap/src/lib.rs:216-227 | plugins/line-repaint/src/lib.rs:87-98 | plugins/normal-generate/src/lib.rs:107-118 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 4) plugins/fft/src/lib.rs:74— plugins/fft/src/lib.rs:74-85 | plugins/fourier-filter/src/lib.rs:235-246 | plugins/ifft/src/lib.rs:63-74 | plugins/singular-value-decompose/src/lib.rs:71-82 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fft/src/lib.rs:74` 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 (10 lines × 5) crates/utils/src/spectral_wgpu.rs:137— crates/utils/src/spectral_wgpu.rs:137-146 | plugins/differential-generate/src/gpu/wgpu/mod.rs:120-129 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:126-135 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:110-119 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:132-141 — before extracting anything, compare `crates/utils/src/spectral_wgpu.rs` and `plugins/differential-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/src/spectral_wgpu.rs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/differential-generate/src/gpu/wgpu/mod.rs:118` calls `write_buffer`, `cast_slice` and `plugins/gabor-generate/src/gpu/wgpu/mod.rs:124` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 5) crates/utils/src/spectral_wgpu.rs:183— crates/utils/src/spectral_wgpu.rs:183-192 | plugins/differential-generate/src/gpu/wgpu/mod.rs:174-183 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:184-193 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:169-178 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:186-195 — before extracting anything, compare `crates/utils/src/spectral_wgpu.rs` and `plugins/differential-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/src/spectral_wgpu.rs:183` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:166` calls `calc_u_bytes`, `calc_v_bytes` and `plugins/gabor-generate/src/gpu/wgpu/mod.rs:182` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 5) plugins/channel-remap/src/lib.rs:292— plugins/channel-remap/src/lib.rs:292-301 | plugins/displace-scatter/src/lib.rs:845-854 | plugins/eyedropper-mask/src/lib.rs:253-262 | plugins/image-transform/src/lib.rs:303-312 | plugins/pixel-extend/src/lib.rs:920-929 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/channel-remap/src/lib.rs:292` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/image-transform/src/lib.rs:313` calls `set_out_flag2` and `plugins/channel-remap/src/lib.rs:302` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 5) plugins/mobius-transform/src/lib.rs:1066— plugins/mobius-transform/src/lib.rs:1066-1073 | plugins/mobius-transform/src/lib.rs:1081-1088 | plugins/mobius-transform/src/lib.rs:1109-1116 | plugins/mobius-transform/src/lib.rs:1156-1163 | plugins/mobius-transform/src/lib.rs:1210-1217 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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 × 5) plugins/differential-generate/src/lib.rs:512— plugins/differential-generate/src/lib.rs:512-519 | plugins/displace-scatter/src/lib.rs:2525-2532 | plugins/gradient-blur/src/lib.rs:594-601 | plugins/gradient-displace/src/lib.rs:520-527 | plugins/scatter-map/src/lib.rs:3308-3315 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 5) plugins/displace-scatter/src/lib.rs:2668— plugins/displace-scatter/src/lib.rs:2668-2675 | plugins/gabor-generate/src/lib.rs:1228-1235 | plugins/region-colorize/src/lib.rs:975-982 | plugins/scatter-map/src/lib.rs:3333-3340 | plugins/voronoi-generate/src/lib.rs:1259-1266 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 171 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/displace-scatter/src/lib.rs:2664` calls `wrapping_add`, `wrapping_mul` and `plugins/voronoi-generate/src/lib.rs:1255` 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 × 4) crates/utils/src/spectral_wgpu.rs:107— crates/utils/src/spectral_wgpu.rs:107-112 | plugins/color-quantize/src/gpu/wgpu/mod.rs:127-132 | plugins/differential-generate/src/gpu/wgpu/mod.rs:86-91 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:79-84 — before extracting anything, compare `crates/utils/src/spectral_wgpu.rs` and `plugins/differential-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/src/spectral_wgpu.rs:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) plugins/color-boundary-blur/src/lib.rs:1388— plugins/color-boundary-blur/src/lib.rs:1388-1393 | plugins/image-scaler/src/lib.rs:894-899 | plugins/pixel-extend/src/lib.rs:2258-2263 | plugins/scatter-map/src/lib.rs:1468-1473 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/image-scaler/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:1388` 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 × 4) plugins/differential-generate/src/lib.rs:63— plugins/differential-generate/src/lib.rs:63-68 | plugins/gabor-generate/src/lib.rs:113-118 | plugins/singular-value-decompose/src/lib.rs:38-43 | plugins/voronoi-generate/src/lib.rs:119-124 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/displace-scatter/src/lib.rs:2478— plugins/displace-scatter/src/lib.rs:2478-2483 | plugins/gradient-blur/src/lib.rs:525-531 | plugins/gradient-displace/src/lib.rs:451-457 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/fft/src/lib.rs:44— plugins/fft/src/lib.rs:44-49 | plugins/fourier-filter/src/lib.rs:170-175 | plugins/ifft/src/lib.rs:39-44 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 3) plugins/image-encrypt-decrypt/src/lib.rs:314— plugins/image-encrypt-decrypt/src/lib.rs:314-321 | plugins/image-transform/src/lib.rs:314-321 | plugins/space-convert/src/lib.rs:704-709 — before extracting anything, compare `plugins/image-encrypt-decrypt/src/lib.rs` and `plugins/image-transform/src/lib.rs` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/image-encrypt-decrypt/src/lib.rs:314` 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.
color_composite::blend_channel (cyclomatic 78) plugins/color-composite/src/lib.rs:1083— color_composite::blend_channel has cyclomatic complexity 78 (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.
color_composite::blend_rgb (cyclomatic 41) plugins/color-composite/src/lib.rs:879— color_composite::blend_rgb has cyclomatic complexity 41 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
color_quantize::init_centroids_kmeans_parallel (cyclomatic 30) plugins/color-quantize/src/lib.rs:1348— color_quantize::init_centroids_kmeans_parallel has cyclomatic complexity 30 (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.
color_quantize::run_kmeans (cyclomatic 18) plugins/color-quantize/src/lib.rs:1161— color_quantize::run_kmeans has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
color_composite::blend_channel (cognitive 64) plugins/color-composite/src/lib.rs:1083— color_composite::blend_channel has cognitive complexity 64 (threshold 15). Drivers by points: if/else 42 (63 pts), match/switch 1 (nesting depth added 21). 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.
color_composite::blend_rgb (cognitive 22) plugins/color-composite/src/lib.rs:879— color_composite::blend_rgb has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (21 pts), match/switch 1 (nesting depth added 7). 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.
fourier_filter::apply_filter_in_place (cognitive 26) plugins/fourier-filter/src/lib.rs:1575— fourier_filter::apply_filter_in_place has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 14). 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.
fourier_filter::build_mask_gains (cognitive 18) plugins/fourier-filter/src/lib.rs:1775— fourier_filter::build_mask_gains has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (6 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Members sharing a duplicated core (31 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (31 members, 50+ identical tokens) plugins/channel-remap/src/lib.rs:286— plugins/channel-remap/src/lib.rs:286-356 | plugins/checker-generate/src/lib.rs:303-369 | plugins/color-ajust/src/lib.rs:115-169 | plugins/color-boundary-blur/src/lib.rs:316-378 | plugins/color-change/src/lib.rs:137-205 | plugins/color-composite/src/lib.rs:526-591 | plugins/color-convert/src/lib.rs:103-161 | plugins/color-quantize/src/lib.rs:452-523 | plugins/color-select/src/lib.rs:187-252 | plugins/contour-generate/src/lib.rs:136-194 | plugins/depth-fog/src/lib.rs:176-239 | plugins/differential-generate/src/lib.rs:161-230 | plugins/displace-scatter/src/lib.rs:839-907 | plugins/distance-generate/src/lib.rs:159-217 | plugins/eyedropper-mask/src/lib.rs:247-318 | plugins/fft/src/lib.rs:142-194 | plugins/fourier-filter/src/lib.rs:551-620 | plugins/gabor-generate/src/lib.rs:372-455 | plugins/gradient-blur/src/lib.rs:154-216 | plugins/gradient-displace/src/lib.rs:141-203 | plugins/ifft/src/lib.rs:131-183 | plugins/image-calculate/src/lib.rs:304-372 | plugins/image-scaler/src/lib.rs:432-504 | plugins/light-wrap/src/lib.rs:515-586 | plugins/line-repaint/src/lib.rs:144-196 | plugins/mobius-transform/src/lib.rs:392-455 | plugins/normal-generate/src/lib.rs:280-340 | plugins/pixel-extend/src/lib.rs:914-987 | plugins/region-colorize/src/lib.rs:183-252 | plugins/singular-value-decompose/src/lib.rs:105-157 | plugins/voronoi-generate/src/lib.rs:406-482 — These 31 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 31 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 31 times.
Members sharing a duplicated core (31 members, 50+ identical tokens) plugins/checker-generate/src/lib.rs:430— plugins/checker-generate/src/lib.rs:430-566 | plugins/color-ajust/src/lib.rs:180-535 | plugins/color-boundary-blur/src/lib.rs:1397-1411 | plugins/color-convert/src/lib.rs:496-596 | plugins/color-quantize/src/lib.rs:1611-1639 | plugins/contour-generate/src/lib.rs:205-332 | plugins/depth-fog/src/lib.rs:283-380 | plugins/differential-generate/src/lib.rs:241-324 | plugins/differential-generate/src/lib.rs:333-401 | plugins/displace-scatter/src/lib.rs:1149-1359 | plugins/distance-generate/src/lib.rs:228-493 | plugins/eyedropper-mask/src/lib.rs:634-651 | plugins/fft/src/lib.rs:203-296 | plugins/fourier-filter/src/lib.rs:897-1063 | plugins/gabor-generate/src/lib.rs:551-639 | plugins/gabor-generate/src/lib.rs:648-831 | plugins/gradient-blur/src/lib.rs:250-358 | plugins/gradient-displace/src/lib.rs:237-331 | plugins/ifft/src/lib.rs:192-329 | plugins/ifft/src/lib.rs:365-387 | plugins/image-calculate/src/lib.rs:517-710 | plugins/image-relight/src/lib.rs:1263-1365 | plugins/light-wrap/src/lib.rs:700-803 | plugins/line-repaint/src/lib.rs:399-416 | plugins/normal-generate/src/lib.rs:363-823 | plugins/scatter-map/src/lib.rs:1036-1137 | plugins/singular-value-decompose/src/lib.rs:166-256 | plugins/space-convert/src/lib.rs:906-944 | plugins/voronoi-generate/src/lib.rs:535-685 | plugins/voronoi-generate/src/lib.rs:694-1018 | plugins/voronoi-generate/src/lib.rs:1045-1153 — These 31 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 31 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 31 times.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (10 members, 50+ identical tokens) plugins/color-boundary-blur/src/lib.rs:484— plugins/color-boundary-blur/src/lib.rs:484-493 | plugins/glass-displace/src/plugin.rs:328-337 | plugins/gradient-blur/src/lib.rs:232-243 | plugins/gradient-displace/src/lib.rs:219-230 | plugins/image-encrypt-decrypt/src/lib.rs:442-451 | plugins/image-relight/src/lib.rs:1246-1255 | plugins/image-transform/src/lib.rs:450-459 | plugins/pixel-extend/src/lib.rs:1100-1110 | plugins/rainbow-generate/src/lib.rs:284-293 | plugins/space-convert/src/lib.rs:881-890 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) plugins/mobius-transform/src/lib.rs:800— plugins/mobius-transform/src/lib.rs:800-827 | plugins/mobius-transform/src/lib.rs:829-843 | plugins/mobius-transform/src/lib.rs:901-949 | plugins/mobius-transform/src/lib.rs:951-1006 | plugins/mobius-transform/src/lib.rs:1008-1063 | plugins/mobius-transform/src/lib.rs:1065-1078 | plugins/mobius-transform/src/lib.rs:1080-1106 | plugins/mobius-transform/src/lib.rs:1108-1153 | plugins/mobius-transform/src/lib.rs:1155-1207 | plugins/mobius-transform/src/lib.rs:1209-1261 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) plugins/displace-scatter/src/lib.rs:1149— plugins/displace-scatter/src/lib.rs:1149-1359 | plugins/fft/src/lib.rs:203-296 | plugins/fourier-filter/src/lib.rs:897-1063 | plugins/image-encrypt-decrypt/src/lib.rs:496-609 | plugins/image-relight/src/lib.rs:1263-1365 | plugins/singular-value-decompose/src/lib.rs:166-256 | plugins/space-convert/src/lib.rs:906-944 — 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.
Members sharing a duplicated core (7 members, 50+ identical tokens) plugins/fourier-filter/src/lib.rs:183— plugins/fourier-filter/src/lib.rs:183-543 | plugins/glass-displace/src/params.rs:62-524 | plugins/image-scaler/src/lib.rs:252-424 | plugins/light-wrap/src/lib.rs:170-507 | plugins/pixel-extend/src/lib.rs:533-906 | plugins/rainbow-generate/src/params.rs:60-583 | plugins/region-colorize/src/lib.rs:61-175 — 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) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) crates/utils/src/spectral_wgpu.rs:88— crates/utils/src/spectral_wgpu.rs:88-157 | plugins/color-quantize/src/gpu/wgpu/mod.rs:107-302 | plugins/differential-generate/src/gpu/wgpu/mod.rs:76-152 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:80-163 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:71-143 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:81-165 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) plugins/channel-remap/src/lib.rs:743— plugins/channel-remap/src/lib.rs:743-761 | plugins/color-change/src/lib.rs:416-434 | plugins/color-composite/src/lib.rs:1568-1586 | plugins/color-select/src/lib.rs:489-507 | plugins/image-scaler/src/lib.rs:1528-1546 | plugins/pixel-extend/src/lib.rs:2331-2349 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) plugins/color-boundary-blur/src/lib.rs:1279— plugins/color-boundary-blur/src/lib.rs:1279-1311 | plugins/image-relight/src/lib.rs:2485-2516 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) plugins/gabor-generate/src/lib.rs:996— plugins/gabor-generate/src/lib.rs:996-1027 | plugins/gabor-generate/src/lib.rs:1095-1134 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×2
Edited copy of a member (36 corresponding lines) plugins/image-relight/src/gpu/mod.rs:363— plugins/image-relight/src/gpu/mod.rs:363-400 | plugins/pixel-extend/src/gpu/mod.rs:550-585 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) plugins/scatter-map/src/lib.rs:1834— plugins/scatter-map/src/lib.rs:1834-1872 | plugins/scatter-map/src/lib.rs:2121-2156 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×2
Edited copy of a member (33 corresponding lines) plugins/mobius-transform/src/lib.rs:1284— plugins/mobius-transform/src/lib.rs:1284-1316 | plugins/mobius-transform/src/lib.rs:1378-1410 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) plugins/light-wrap/src/lib.rs:1523— plugins/light-wrap/src/lib.rs:1523-1557 | plugins/light-wrap/src/lib.rs:1567-1599 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) plugins/light-wrap/src/lib.rs:1601— plugins/light-wrap/src/lib.rs:1601-1621 | plugins/light-wrap/src/lib.rs:1630-1650 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) plugins/color-change/src/lib.rs:232— plugins/color-change/src/lib.rs:232-254 | plugins/color-select/src/lib.rs:279-299 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) plugins/displace-scatter/src/lib.rs:2612— plugins/displace-scatter/src/lib.rs:2612-2633 | plugins/displace-scatter/src/lib.rs:2635-2657 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) plugins/displace-scatter/src/lib.rs:1663— plugins/displace-scatter/src/lib.rs:1663-1688 | plugins/light-wrap/src/lib.rs:1761-1782 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) plugins/image-encrypt-decrypt/src/lib.rs:707— plugins/image-encrypt-decrypt/src/lib.rs:707-723 | plugins/image-encrypt-decrypt/src/lib.rs:733-749 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) plugins/color-composite/src/lib.rs:1536— plugins/color-composite/src/lib.rs:1536-1552 | plugins/light-wrap/src/lib.rs:1804-1820 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) plugins/color-boundary-blur/src/lib.rs:1150— plugins/color-boundary-blur/src/lib.rs:1150-1168 | plugins/light-wrap/src/lib.rs:1494-1514 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) plugins/displace-scatter/src/lib.rs:1811— plugins/displace-scatter/src/lib.rs:1811-1832 | plugins/displace-scatter/src/lib.rs:1860-1878 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) plugins/image-encrypt-decrypt/src/lib.rs:825— plugins/image-encrypt-decrypt/src/lib.rs:825-834 | plugins/image-encrypt-decrypt/src/lib.rs:1368-1377 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) plugins/image-scaler/src/lib.rs:1160— plugins/image-scaler/src/lib.rs:1160-1169 | plugins/mobius-transform/src/lib.rs:845-855 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) plugins/color-boundary-blur/src/lib.rs:1339— plugins/color-boundary-blur/src/lib.rs:1339-1347 | plugins/displace-scatter/src/lib.rs:2495-2503 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) plugins/image-transform/src/lib.rs:774— plugins/image-transform/src/lib.rs:774-785 | plugins/pixel-extend/src/lib.rs:2239-2247 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (46 lines × 2) plugins/color-quantize/src/lib.rs:892— plugins/color-quantize/src/lib.rs:892-937 | plugins/color-quantize/src/lib.rs:981-1026 — 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 `plugins/color-quantize/src/lib.rs:892` 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 (46 lines × 2) plugins/gradient-blur/src/lib.rs:263— plugins/gradient-blur/src/lib.rs:263-308 | plugins/gradient-displace/src/lib.rs:249-294 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gradient-blur/src/lib.rs:263` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/gradient-blur/src/lib.rs:262` calls `get`, `as_slider`, `value` and `plugins/gradient-displace/src/lib.rs:248` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (35 lines × 2) plugins/color-quantize/src/lib.rs:944— plugins/color-quantize/src/lib.rs:944-978 | plugins/color-quantize/src/lib.rs:1032-1066 — 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 `plugins/color-quantize/src/lib.rs:944` 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 (35 lines × 2) plugins/gradient-blur/src/lib.rs:112— plugins/gradient-blur/src/lib.rs:112-146 | plugins/gradient-displace/src/lib.rs:99-133 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gradient-blur/src/lib.rs:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/gradient-displace/src/lib.rs:98` calls `set_precision` and `plugins/gradient-blur/src/lib.rs:111` 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 (29 lines × 3) plugins/differential-generate/src/lib.rs:82— plugins/differential-generate/src/lib.rs:82-110 | plugins/fft/src/lib.rs:87-115 | plugins/ifft/src/lib.rs:76-104 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/fft/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/differential-generate/src/lib.rs:82` 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 (29 lines × 3) plugins/fft/src/lib.rs:63— plugins/fft/src/lib.rs:63-91 | plugins/fourier-filter/src/lib.rs:224-252 | plugins/singular-value-decompose/src/lib.rs:60-88 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fft/src/lib.rs:63` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (23 lines × 3) plugins/glass-displace/src/params.rs:228— plugins/glass-displace/src/params.rs:228-250 | plugins/glass-displace/src/params.rs:435-457 | plugins/glass-displace/src/params.rs:467-489 — 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 `plugins/glass-displace/src/params.rs:228` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/glass-displace/src/params.rs:227` calls `set_precision` and `plugins/glass-displace/src/params.rs:434` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23 lines × 3) plugins/image-encrypt-decrypt/src/lib.rs:333— plugins/image-encrypt-decrypt/src/lib.rs:333-355 | plugins/image-transform/src/lib.rs:329-351 | plugins/space-convert/src/lib.rs:715-737 — before extracting anything, compare `plugins/image-encrypt-decrypt/src/lib.rs` and `plugins/image-transform/src/lib.rs` as WHOLE FILES: this scan already matched 4 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 (23 lines × 2) plugins/gradient-blur/src/lib.rs:68— plugins/gradient-blur/src/lib.rs:68-90 | plugins/gradient-displace/src/lib.rs:67-89 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gradient-blur/src/lib.rs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) plugins/voronoi-generate/src/lib.rs:542— plugins/voronoi-generate/src/lib.rs:542-564 | plugins/voronoi-generate/src/lib.rs:699-721 — 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 `plugins/voronoi-generate/src/lib.rs:542` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) plugins/gradient-blur/src/lib.rs:615— plugins/gradient-blur/src/lib.rs:615-636 | plugins/gradient-displace/src/lib.rs:541-562 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) plugins/color-boundary-blur/src/lib.rs:204— plugins/color-boundary-blur/src/lib.rs:204-225 | plugins/gradient-blur/src/lib.rs:94-115 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:204` 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 (21 lines × 3) plugins/differential-generate/src/lib.rs:133— plugins/differential-generate/src/lib.rs:133-153 | plugins/fft/src/lib.rs:114-134 | plugins/ifft/src/lib.rs:103-123 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/fft/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/differential-generate/src/lib.rs:133` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 3) plugins/distance-generate/src/lib.rs:506— plugins/distance-generate/src/lib.rs:506-526 | plugins/normal-generate/src/lib.rs:836-856 | plugins/region-colorize/src/lib.rs:889-909 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/normal-generate/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 182 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20–21 lines × 2) plugins/mobius-transform/src/lib.rs:965— plugins/mobius-transform/src/lib.rs:965-985 | plugins/mobius-transform/src/lib.rs:1167-1186 — 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 `plugins/mobius-transform/src/lib.rs:965` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 2) plugins/mobius-transform/src/lib.rs:1022— plugins/mobius-transform/src/lib.rs:1022-1042 | plugins/mobius-transform/src/lib.rs:1221-1240 — 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 `plugins/mobius-transform/src/lib.rs:1022` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 3) plugins/channel-remap/src/lib.rs:901— plugins/channel-remap/src/lib.rs:901-919 | plugins/color-convert/src/lib.rs:312-330 | plugins/image-calculate/src/lib.rs:1362-1380 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:901` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 3) plugins/glass-displace/src/plugin.rs:348— plugins/glass-displace/src/plugin.rs:348-366 | plugins/image-relight/src/lib.rs:1585-1603 | plugins/scatter-map/src/lib.rs:1401-1419 — before extracting anything, compare `plugins/glass-displace/src/plugin.rs` and `plugins/image-relight/src/lib.rs` as WHOLE FILES: this scan already matched 4 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines 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–15 lines × 2) plugins/distance-generate/src/lib.rs:304— plugins/distance-generate/src/lib.rs:304-318 | plugins/normal-generate/src/lib.rs:444-456 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/normal-generate/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 182 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/distance-generate/src/lib.rs:304` 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 (13–15 lines × 2) plugins/image-scaler/src/lib.rs:548— plugins/image-scaler/src/lib.rs:548-562 | plugins/pixel-extend/src/lib.rs:1029-1041 — before extracting anything, compare `plugins/image-scaler/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/image-scaler/src/lib.rs:548` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/pixel-extend/src/lib.rs:1042` calls `set_param_visible`, `set_param_name` and `plugins/image-scaler/src/lib.rs:562` 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 (13–14 lines × 4) plugins/differential-generate/src/gpu/wgpu/mod.rs:93— plugins/differential-generate/src/gpu/wgpu/mod.rs:93-105 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:89-102 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:88-100 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:90-103 — before extracting anything, compare `plugins/differential-generate/src/gpu/wgpu/mod.rs` and `plugins/gabor-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 193 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/differential-generate/src/gpu/wgpu/mod.rs:93` 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–14 lines × 4) plugins/mobius-transform/src/lib.rs:959— plugins/mobius-transform/src/lib.rs:959-972 | plugins/mobius-transform/src/lib.rs:1016-1029 | plugins/mobius-transform/src/lib.rs:1162-1174 | plugins/mobius-transform/src/lib.rs:1216-1228 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/mobius-transform/src/lib.rs:959` 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 (14 lines × 3) plugins/displace-scatter/src/lib.rs:763— plugins/displace-scatter/src/lib.rs:763-776 | plugins/gradient-blur/src/lib.rs:122-135 | plugins/gradient-displace/src/lib.rs:109-122 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:763` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 3) plugins/light-wrap/src/lib.rs:450— plugins/light-wrap/src/lib.rs:450-463 | plugins/pixel-extend/src/lib.rs:707-720 | plugins/voronoi-generate/src/lib.rs:223-236 — before extracting anything, compare `plugins/light-wrap/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/light-wrap/src/lib.rs:450` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13–14 lines × 2) plugins/gabor-generate/src/gpu/wgpu/mod.rs:122— plugins/gabor-generate/src/gpu/wgpu/mod.rs:122-134 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:127-140 — before extracting anything, compare `plugins/gabor-generate/src/gpu/wgpu/mod.rs` and `plugins/voronoi-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gabor-generate/src/gpu/wgpu/mod.rs:122` 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 (13–14 lines × 2) plugins/image-relight/src/lib.rs:571— plugins/image-relight/src/lib.rs:571-583 | plugins/normal-generate/src/lib.rs:64-77 — before extracting anything, compare `plugins/image-relight/src/lib.rs` and `plugins/normal-generate/src/lib.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/image-relight/src/lib.rs:571` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 5) plugins/color-quantize/src/lib.rs:292— plugins/color-quantize/src/lib.rs:292-302 | plugins/displace-scatter/src/lib.rs:744-754 | plugins/gabor-generate/src/lib.rs:309-319 | plugins/region-colorize/src/lib.rs:101-111 | plugins/scatter-map/src/lib.rs:661-671 — before extracting anything, compare `plugins/color-quantize/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 8 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/region-colorize/src/lib.rs:98` calls `empty` and `plugins/color-quantize/src/lib.rs:289` 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 × 5) plugins/color-change/src/lib.rs:151— plugins/color-change/src/lib.rs:151-161 | plugins/displace-scatter/src/lib.rs:856-866 | plugins/image-calculate/src/lib.rs:320-330 | plugins/mobius-transform/src/lib.rs:405-415 | plugins/region-colorize/src/lib.rs:199-209 — before extracting anything, compare `plugins/color-change/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-change/src/lib.rs:151` 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, `plugins/displace-scatter/src/lib.rs:853` calls `set_out_flag2` and `plugins/color-change/src/lib.rs:148` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 15) plugins/glass-displace/src/params.rs:194— plugins/glass-displace/src/params.rs:194-203 | plugins/glass-displace/src/params.rs:208-217 | plugins/glass-displace/src/params.rs:222-231 | plugins/glass-displace/src/params.rs:255-264 | plugins/glass-displace/src/params.rs:269-278 | plugins/glass-displace/src/params.rs:416-425 | plugins/image-scaler/src/lib.rs:397-406 | plugins/image-scaler/src/lib.rs:412-421 | plugins/light-wrap/src/lib.rs:306-315 | plugins/light-wrap/src/lib.rs:321-330 | plugins/light-wrap/src/lib.rs:336-345 | plugins/pixel-extend/src/lib.rs:648-657 | plugins/rainbow-generate/src/params.rs:133-142 | plugins/region-colorize/src/lib.rs:148-157 | plugins/region-colorize/src/lib.rs:163-172 — before extracting anything, compare `plugins/glass-displace/src/params.rs` and `plugins/light-wrap/src/lib.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/glass-displace/src/params.rs:194` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/glass-displace/src/params.rs:279` calls `Ok` and `plugins/light-wrap/src/lib.rs:347` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 15) plugins/channel-remap/src/lib.rs:302— plugins/channel-remap/src/lib.rs:302-311 | plugins/color-boundary-blur/src/lib.rs:331-340 | plugins/color-change/src/lib.rs:150-159 | plugins/color-composite/src/lib.rs:541-550 | plugins/color-select/src/lib.rs:202-211 | plugins/displace-scatter/src/lib.rs:855-864 | plugins/eyedropper-mask/src/lib.rs:263-272 | plugins/fourier-filter/src/lib.rs:567-576 | plugins/image-calculate/src/lib.rs:319-328 | plugins/image-scaler/src/lib.rs:447-456 | plugins/image-transform/src/lib.rs:314-323 | plugins/light-wrap/src/lib.rs:530-539 | plugins/mobius-transform/src/lib.rs:404-413 | plugins/pixel-extend/src/lib.rs:930-939 | plugins/region-colorize/src/lib.rs:198-207 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-boundary-blur/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/channel-remap/src/lib.rs:302` 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, `plugins/channel-remap/src/lib.rs:300` calls `set_out_flag2` and `plugins/color-boundary-blur/src/lib.rs:329` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 5) crates/utils/src/spectral_wgpu.rs:385— crates/utils/src/spectral_wgpu.rs:385-393 | plugins/color-quantize/src/gpu/wgpu/mod.rs:636-644 | plugins/differential-generate/src/gpu/wgpu/mod.rs:307-315 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:297-305 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:299-307 — before extracting anything, compare `crates/utils/src/spectral_wgpu.rs` and `plugins/differential-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 5) plugins/mobius-transform/src/lib.rs:801— plugins/mobius-transform/src/lib.rs:801-809 | plugins/mobius-transform/src/lib.rs:830-838 | plugins/mobius-transform/src/lib.rs:902-910 | plugins/mobius-transform/src/lib.rs:952-960 | plugins/mobius-transform/src/lib.rs:1009-1017 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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–9 lines × 2) plugins/color-change/src/lib.rs:142— plugins/color-change/src/lib.rs:142-150 | plugins/mobius-transform/src/lib.rs:397-404 — before extracting anything, compare `plugins/color-change/src/lib.rs` and `plugins/mobius-transform/src/lib.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/color-change/src/lib.rs:142` 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–9 lines × 2) plugins/light-wrap/src/lib.rs:1830— plugins/light-wrap/src/lib.rs:1830-1838 | plugins/scatter-map/src/lib.rs:3402-3409 — before extracting anything, compare `plugins/light-wrap/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/light-wrap/src/lib.rs:1830` 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 × 7) plugins/checker-generate/src/lib.rs:348— plugins/checker-generate/src/lib.rs:348-354 | plugins/color-change/src/lib.rs:186-193 | plugins/gabor-generate/src/lib.rs:431-437 | plugins/image-calculate/src/lib.rs:352-358 | plugins/mobius-transform/src/lib.rs:437-442 | plugins/region-colorize/src/lib.rs:234-240 | plugins/voronoi-generate/src/lib.rs:463-469 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/color-change/src/lib.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/checker-generate/src/lib.rs:348` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 7) plugins/checker-generate/src/lib.rs:569— plugins/checker-generate/src/lib.rs:569-574 | plugins/displace-scatter/src/lib.rs:1656-1661 | plugins/eyedropper-mask/src/lib.rs:619-624 | plugins/gabor-generate/src/lib.rs:1295-1300 | plugins/image-scaler/src/lib.rs:826-831 | plugins/region-colorize/src/lib.rs:788-793 | plugins/voronoi-generate/src/lib.rs:1156-1161 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 6) plugins/color-ajust/src/lib.rs:519— plugins/color-ajust/src/lib.rs:519-524 | plugins/color-convert/src/lib.rs:581-586 | plugins/contour-generate/src/lib.rs:318-323 | plugins/differential-generate/src/lib.rs:387-392 | plugins/distance-generate/src/lib.rs:479-484 | plugins/voronoi-generate/src/lib.rs:671-676 — before extracting anything, compare `plugins/color-ajust/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-ajust/src/lib.rs:519` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 6) plugins/checker-generate/src/lib.rs:397— plugins/checker-generate/src/lib.rs:397-402 | plugins/displace-scatter/src/lib.rs:1089-1094 | plugins/fourier-filter/src/lib.rs:831-836 | plugins/image-calculate/src/lib.rs:450-455 | plugins/image-scaler/src/lib.rs:618-623 | plugins/pixel-extend/src/lib.rs:1060-1065 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/checker-generate/src/lib.rs:397` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `params` to `&mut Parameters<Params>` in one and `&mut ae::Parameters<Params>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 3) plugins/gabor-generate/src/lib.rs:474— plugins/gabor-generate/src/lib.rs:474-478 | plugins/gabor-generate/src/lib.rs:558-562 | plugins/gabor-generate/src/lib.rs:666-670 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) plugins/region-colorize/src/lib.rs:710— plugins/region-colorize/src/lib.rs:710-714 | plugins/region-colorize/src/lib.rs:725-729 | plugins/region-colorize/src/lib.rs:740-744 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/region-colorize/src/lib.rs:710` 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.
image_calculate::apply_math (cyclomatic 46) plugins/image-calculate/src/lib.rs:1040— image_calculate::apply_math has cyclomatic complexity 46 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
space_convert::render_coordinates (cyclomatic 44) plugins/space-convert/src/lib.rs:1190— space_convert::render_coordinates has cyclomatic complexity 44 (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.
voronoi_generate::blend_channel (cyclomatic 30) plugins/voronoi-generate/src/lib.rs:1432— voronoi_generate::blend_channel has cyclomatic complexity 30 (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.
contour_generate::thin_edges_zhang_suen (cyclomatic 29) plugins/contour-generate/src/lib.rs:343— contour_generate::thin_edges_zhang_suen has cyclomatic complexity 29 (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.
image_relight::region_boundary_distance (cyclomatic 27) plugins/image-relight/src/lib.rs:1783— image_relight::region_boundary_distance has cyclomatic complexity 27 (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.
scatter_map::render_gather_layers (cyclomatic 23) plugins/scatter-map/src/lib.rs:1585— scatter_map::render_gather_layers 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.
checker_generate::blend_channel (cyclomatic 22) plugins/checker-generate/src/lib.rs:737— checker_generate::blend_channel has cyclomatic complexity 22 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
build-catalog.configureOldEffect (cyclomatic 19) docs/catalog/build-catalog.jsx:175— build-catalog.configureOldEffect has cyclomatic complexity 19 (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.
WgpuContext::render (cyclomatic 17) plugins/color-quantize/src/gpu/wgpu/mod.rs:102— WgpuContext::render 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.
line_repaint::apply_edge_erosion (cyclomatic 16) plugins/line-repaint/src/lib.rs:478— line_repaint::apply_edge_erosion has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Yanked release: imageproc — `imageproc` resolves to 0.26.0 in the committed REDACTED, and crates.io reports that release as YANKED. A yanked release is one the publisher has withdrawn and asked you to stop using; it keeps resolving only so existing locks do not break. The current stable release is 0.27.0. Run `cargo update -p imageproc` and commit the updated lock.
Hotspot: docs/catalog/build-catalog.jsx docs/catalog/build-catalog.jsx:175— docs/catalog/build-catalog.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in build-catalog.configureOldEffect at line 175. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:30:38 +09:00' --until='2026-11-16 22:30:38 +09:00' --full-history --no-merges -- docs/catalog/build-catalog.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
contour_generate::thin_edges_zhang_suen (cognitive 68) plugins/contour-generate/src/lib.rs:343— contour_generate::thin_edges_zhang_suen has cognitive complexity 68 (threshold 15). Drivers by points: if/else 14 (41 pts), loops 6 (15 pts), boolean chains 12 (nesting depth added 36). 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.
light_wrap::chamfer_distance (cognitive 37) plugins/light-wrap/src/lib.rs:1316— light_wrap::chamfer_distance has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (30 pts), loops 5 (7 pts) (nesting depth added 23). 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.
voronoi_generate::blend_channel (cognitive 28) plugins/voronoi-generate/src/lib.rs:1432— voronoi_generate::blend_channel has cognitive complexity 28 (threshold 15). Drivers by points: if/else 18 (27 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.
line_repaint::apply_edge_erosion (cognitive 27) plugins/line-repaint/src/lib.rs:478— line_repaint::apply_edge_erosion has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 5 (7 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WgpuContext::render (cognitive 22) plugins/color-quantize/src/gpu/wgpu/mod.rs:102— WgpuContext::render has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 3 (4 pts), boolean chains 3, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
image_calculate::apply_math (cognitive 20) plugins/image-calculate/src/lib.rs:1040— image_calculate::apply_math has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 pts), match/switch 1 (nesting depth added 6). 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.
singular_value_decompose::build_svd_factors (cognitive 19) plugins/singular-value-decompose/src/lib.rs:259— singular_value_decompose::build_svd_factors has cognitive complexity 19 (threshold 15). Drivers by points: loops 6 (14 pts), if/else 3 (5 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
build-catalog.configureOldEffect (cognitive 18) docs/catalog/build-catalog.jsx:175— build-catalog.configureOldEffect has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18. 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.
utils::spectral::fft2_in_place (cognitive 16) crates/utils/src/spectral.rs:75— utils::spectral::fft2_in_place has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (8 pts), if/else 7, boolean chains 1 (nesting depth added 3). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
checker_generate::blend_channel (cognitive 16) plugins/checker-generate/src/lib.rs:737— checker_generate::blend_channel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (nesting depth added 5). 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.
TooManyMethods: MobiusPlugin plugins/mobius-transform/src/lib.rs:40— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Near-duplicate member family (19 members, 11 shared lines) · ×1
Near-duplicate member family (19 members, 11 shared lines) plugins/checker-generate/src/lib.rs:86— plugins/checker-generate/src/lib.rs:86-295 | plugins/color-ajust/src/lib.rs:32-107 | plugins/color-boundary-blur/src/lib.rs:104-308 | plugins/contour-generate/src/lib.rs:36-128 | plugins/displace-scatter/src/lib.rs:287-831 | plugins/distance-generate/src/lib.rs:49-151 | plugins/eyedropper-mask/src/lib.rs:99-239 | plugins/fourier-filter/src/lib.rs:183-543 | plugins/gabor-generate/src/lib.rs:126-364 | plugins/glass-displace/src/params.rs:62-524 | plugins/image-calculate/src/lib.rs:142-296 | plugins/light-wrap/src/lib.rs:170-507 | plugins/line-repaint/src/lib.rs:60-136 | plugins/mobius-transform/src/lib.rs:197-384 | plugins/normal-generate/src/lib.rs:56-272 | plugins/pixel-extend/src/lib.rs:533-906 | plugins/scatter-map/src/lib.rs:300-742 | plugins/space-convert/src/lib.rs:343-681 | plugins/voronoi-generate/src/lib.rs:132-398 — These 19 members are variants of one another: a block of 11 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 19 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 19 times.
D4 · Code Duplication· Near-duplicate member family (13 members, 22 shared lines) · ×1
Near-duplicate member family (13 members, 22 shared lines) plugins/channel-remap/src/lib.rs:286— plugins/channel-remap/src/lib.rs:286-356 | plugins/color-boundary-blur/src/lib.rs:316-378 | plugins/color-composite/src/lib.rs:526-591 | plugins/color-select/src/lib.rs:187-252 | plugins/displace-scatter/src/lib.rs:839-907 | plugins/eyedropper-mask/src/lib.rs:247-318 | plugins/fourier-filter/src/lib.rs:551-620 | plugins/image-calculate/src/lib.rs:304-372 | plugins/image-scaler/src/lib.rs:432-504 | plugins/image-transform/src/lib.rs:297-382 | plugins/light-wrap/src/lib.rs:515-586 | plugins/pixel-extend/src/lib.rs:914-987 | plugins/region-colorize/src/lib.rs:183-252 — These 13 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 37 shared lines) · ×1
Near-duplicate member family (5 members, 37 shared lines) crates/utils/src/spectral_wgpu.rs:180— crates/utils/src/spectral_wgpu.rs:180-269 | plugins/differential-generate/src/gpu/wgpu/mod.rs:171-231 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:181-229 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:164-239 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:183-231 — These 5 members are variants of one another: a block of 37 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 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 26 shared lines) · ×1
Near-duplicate member family (5 members, 26 shared lines) crates/utils/src/spectral_wgpu.rs:279— crates/utils/src/spectral_wgpu.rs:279-359 | plugins/differential-generate/src/gpu/wgpu/mod.rs:242-300 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:242-290 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:248-316 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:244-292 — These 5 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 35 shared lines) · ×1
Near-duplicate member family (4 members, 35 shared lines) plugins/distance-generate/src/lib.rs:49— plugins/distance-generate/src/lib.rs:49-151 | plugins/light-wrap/src/lib.rs:170-507 | plugins/line-repaint/src/lib.rs:60-136 | plugins/normal-generate/src/lib.rs:56-272 — These 4 members are variants of one another: a block of 35 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 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.
D4 · Code Duplication· Near-duplicate member family (3 members, 63 shared lines) · ×1
Near-duplicate member family (3 members, 63 shared lines) plugins/channel-remap/src/lib.rs:806— plugins/channel-remap/src/lib.rs:806-919 | plugins/color-convert/src/lib.rs:214-330 | plugins/image-calculate/src/lib.rs:1267-1380 — These 3 members are variants of one another: a block of 63 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· Near-duplicate member family (3 members, 44 shared lines) · ×1
Near-duplicate member family (3 members, 44 shared lines) plugins/channel-remap/src/lib.rs:921— plugins/channel-remap/src/lib.rs:921-1052 | plugins/color-convert/src/lib.rs:332-487 | plugins/image-calculate/src/lib.rs:1382-1513 — These 3 members are variants of one another: a block of 44 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· Near-duplicate member family (3 members, 6 shared lines) · ×1
Near-duplicate member family (3 members, 6 shared lines) plugins/displace-scatter/src/lib.rs:2473— plugins/displace-scatter/src/lib.rs:2473-2493 | plugins/gradient-blur/src/lib.rs:515-541 | plugins/gradient-displace/src/lib.rs:441-467 — These 3 members are variants of one another: a block of 6 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.
Near-duplicate member pair (59 shared lines) plugins/fourier-filter/src/lib.rs:1854— plugins/fourier-filter/src/lib.rs:1854-1979 | plugins/image-scaler/src/lib.rs:1275-1390 — These two members are variants of one another: 59 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) plugins/image-relight/src/lib.rs:2826— plugins/image-relight/src/lib.rs:2826-2844 | plugins/space-convert/src/lib.rs:2286-2309 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (23 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (23 members, 50+ identical tokens) plugins/channel-remap/src/lib.rs:399— plugins/channel-remap/src/lib.rs:399-419 | plugins/color-boundary-blur/src/lib.rs:449-469 | plugins/color-change/src/lib.rs:300-320 | plugins/color-composite/src/lib.rs:703-723 | plugins/color-quantize/src/lib.rs:580-600 | plugins/color-select/src/lib.rs:326-346 | plugins/displace-scatter/src/lib.rs:1102-1122 | plugins/eyedropper-mask/src/lib.rs:400-420 | plugins/fourier-filter/src/lib.rs:844-864 | plugins/gabor-generate/src/lib.rs:504-524 | plugins/glass-displace/src/plugin.rs:303-321 | plugins/image-calculate/src/lib.rs:463-483 | plugins/image-encrypt-decrypt/src/lib.rs:417-435 | plugins/image-relight/src/lib.rs:1221-1239 | plugins/image-scaler/src/lib.rs:631-651 | plugins/image-transform/src/lib.rs:417-435 | plugins/light-wrap/src/lib.rs:647-667 | plugins/mobius-transform/src/lib.rs:476-496 | plugins/pixel-extend/src/lib.rs:1073-1093 | plugins/rainbow-generate/src/lib.rs:251-269 | plugins/region-colorize/src/lib.rs:294-314 | plugins/scatter-map/src/lib.rs:983-1001 | plugins/space-convert/src/lib.rs:856-874 — These 23 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 23 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 23 times.
D4 · Code Duplication· Members sharing a duplicated core (17 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (17 members, 50+ identical tokens) plugins/channel-remap/src/lib.rs:434— plugins/channel-remap/src/lib.rs:434-445 | plugins/checker-generate/src/lib.rs:408-421 | plugins/color-change/src/lib.rs:327-338 | plugins/color-composite/src/lib.rs:738-749 | plugins/color-quantize/src/lib.rs:615-625 | plugins/color-select/src/lib.rs:361-372 | plugins/depth-fog/src/lib.rs:262-275 | plugins/displace-scatter/src/lib.rs:1129-1140 | plugins/eyedropper-mask/src/lib.rs:435-446 | plugins/fourier-filter/src/lib.rs:879-890 | plugins/gabor-generate/src/lib.rs:531-542 | plugins/image-calculate/src/lib.rs:498-508 | plugins/image-scaler/src/lib.rs:666-677 | plugins/light-wrap/src/lib.rs:682-693 | plugins/mobius-transform/src/lib.rs:503-514 | plugins/region-colorize/src/lib.rs:321-332 | plugins/scatter-map/src/lib.rs:1016-1026 — These 17 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 17 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 17 times.
D4 · Code Duplication· Edited copy of a member (96 corresponding lines) · ×1
Edited copy of a member (96 corresponding lines) plugins/fourier-filter/src/lib.rs:1985— plugins/fourier-filter/src/lib.rs:1985-2080 | plugins/image-scaler/src/lib.rs:1396-1491 — These two members are one piece of code written twice and then edited apart: 96 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (86 corresponding lines) · ×1
Edited copy of a member (86 corresponding lines) plugins/image-encrypt-decrypt/src/lib.rs:296— plugins/image-encrypt-decrypt/src/lib.rs:296-391 | plugins/space-convert/src/lib.rs:689-774 — These two members are one piece of code written twice and then edited apart: 86 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (87 corresponding lines) · ×1
Edited copy of a member (87 corresponding lines) plugins/color-quantize/src/lib.rs:891— plugins/color-quantize/src/lib.rs:891-978 | plugins/color-quantize/src/lib.rs:980-1066 — These two members are one piece of code written twice and then edited apart: 87 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (82 corresponding lines) · ×1
Edited copy of a member (82 corresponding lines) plugins/image-relight/src/lib.rs:966— plugins/image-relight/src/lib.rs:966-1055 | plugins/rainbow-generate/src/lib.rs:62-143 — These two members are one piece of code written twice and then edited apart: 82 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) plugins/color-boundary-blur/src/lib.rs:1095— plugins/color-boundary-blur/src/lib.rs:1095-1148 | plugins/color-boundary-blur/src/lib.rs:1170-1208 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 41+ corresponding lines) · ×1
Edited copies of one member (3 members, 41+ corresponding lines) plugins/color-quantize/src/gpu/wgpu/mod.rs:48— plugins/color-quantize/src/gpu/wgpu/mod.rs:48-100 | plugins/image-relight/src/gpu/mod.rs:41-84 | plugins/pixel-extend/src/gpu/mod.rs:70-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) plugins/glass-displace/src/render.rs:695— plugins/glass-displace/src/render.rs:695-729 | plugins/rainbow-generate/src/lib.rs:642-685 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) plugins/color-quantize/src/lib.rs:1075— plugins/color-quantize/src/lib.rs:1075-1115 | plugins/color-quantize/src/lib.rs:1123-1160 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) crates/utils/src/image.rs:316— crates/utils/src/image.rs:316-345 | plugins/image-scaler/src/lib.rs:1091-1116 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) plugins/gabor-generate/src/lib.rs:959— plugins/gabor-generate/src/lib.rs:959-986 | plugins/gabor-generate/src/lib.rs:1050-1084 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) crates/utils/src/image.rs:279— crates/utils/src/image.rs:279-305 | plugins/image-scaler/src/lib.rs:1132-1158 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) crates/utils/src/spectral.rs:14— crates/utils/src/spectral.rs:14-43 | crates/utils/src/spectral.rs:50-73 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) plugins/image-scaler/src/lib.rs:1171— plugins/image-scaler/src/lib.rs:1171-1188 | plugins/mobius-transform/src/lib.rs:857-875 | plugins/pixel-extend/src/lib.rs:2126-2143 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) crates/utils/src/image.rs:79— crates/utils/src/image.rs:79-90 | plugins/checker-generate/src/lib.rs:802-815 | plugins/scatter-map/src/lib.rs:3397-3409 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) plugins/image-encrypt-decrypt/src/lib.rs:850— plugins/image-encrypt-decrypt/src/lib.rs:850-860 | plugins/image-encrypt-decrypt/src/lib.rs:869-879 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) plugins/image-scaler/src/lib.rs:770— plugins/image-scaler/src/lib.rs:770-793 | plugins/image-scaler/src/lib.rs:801-824 | plugins/image-transform/src/lib.rs:517-536 | plugins/space-convert/src/lib.rs:975-995 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) plugins/image-relight/src/gpu/mod.rs:224— plugins/image-relight/src/gpu/mod.rs:224-239 | plugins/pixel-extend/src/gpu/mod.rs:336-362 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) plugins/displace-scatter/src/lib.rs:2541— plugins/displace-scatter/src/lib.rs:2541-2548 | plugins/gradient-blur/src/lib.rs:543-550 | plugins/gradient-displace/src/lib.rs:469-476 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 9+ corresponding lines) · ×1
Edited copies of one member (5 members, 9+ corresponding lines) plugins/color-boundary-blur/src/lib.rs:382— plugins/color-boundary-blur/src/lib.rs:382-390 | plugins/color-change/src/lib.rs:209-217 | plugins/color-composite/src/lib.rs:603-611 | plugins/color-select/src/lib.rs:256-264 | plugins/eyedropper-mask/src/lib.rs:322-330 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) plugins/image-relight/src/lib.rs:1379— plugins/image-relight/src/lib.rs:1379-1393 | plugins/image-transform/src/lib.rs:547-562 | plugins/space-convert/src/lib.rs:954-968 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) crates/utils/src/image.rs:418— crates/utils/src/image.rs:418-425 | plugins/image-scaler/src/lib.rs:1199-1202 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) plugins/color-boundary-blur/src/lib.rs:1430— plugins/color-boundary-blur/src/lib.rs:1430-1432 | plugins/image-relight/src/lib.rs:2881-2883 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (129 lines × 2) plugins/channel-remap/src/lib.rs:924— plugins/channel-remap/src/lib.rs:924-1052 | plugins/image-calculate/src/lib.rs:1385-1513 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/image-calculate/src/lib.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 393 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:924` 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 (98 lines × 2) plugins/channel-remap/src/lib.rs:809— plugins/channel-remap/src/lib.rs:809-906 | plugins/image-calculate/src/lib.rs:1270-1367 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/image-calculate/src/lib.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 393 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:809` 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 (53–58 lines × 2) plugins/displace-scatter/src/lib.rs:609— plugins/displace-scatter/src/lib.rs:609-666 | plugins/scatter-map/src/lib.rs:603-655 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:609` 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 (50 lines × 2) plugins/space-convert/src/lib.rs:1719— plugins/space-convert/src/lib.rs:1719-1768 | plugins/space-convert/src/lib.rs:1851-1900 — 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 `plugins/space-convert/src/lib.rs:1719` 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 (33–41 lines × 5) crates/utils/src/spectral_wgpu.rs:200— crates/utils/src/spectral_wgpu.rs:200-232 | plugins/differential-generate/src/gpu/wgpu/mod.rs:185-221 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:188-220 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:187-227 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:190-222 — before extracting anything, compare `crates/utils/src/spectral_wgpu.rs` and `plugins/differential-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/src/spectral_wgpu.rs:200` 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 (36 lines × 5) crates/utils/src/spectral_wgpu.rs:24— crates/utils/src/spectral_wgpu.rs:24-59 | plugins/differential-generate/src/gpu/wgpu/mod.rs:35-70 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:43-78 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:29-64 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:44-79 — before extracting anything, compare `crates/utils/src/spectral_wgpu.rs` and `plugins/differential-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (33–35 lines × 2) plugins/displace-scatter/src/lib.rs:774— plugins/displace-scatter/src/lib.rs:774-808 | plugins/scatter-map/src/lib.rs:691-723 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:774` 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 (29 lines × 2) plugins/color-composite/src/lib.rs:1454— plugins/color-composite/src/lib.rs:1454-1482 | plugins/voronoi-generate/src/lib.rs:1540-1568 — before extracting anything, compare `plugins/color-composite/src/lib.rs` and `plugins/voronoi-generate/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26–27 lines × 4) plugins/color-convert/src/lib.rs:135— plugins/color-convert/src/lib.rs:135-161 | plugins/contour-generate/src/lib.rs:169-194 | plugins/distance-generate/src/lib.rs:192-217 | plugins/normal-generate/src/lib.rs:314-340 — before extracting anything, compare `plugins/color-convert/src/lib.rs` and `plugins/contour-generate/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/color-convert/src/lib.rs:135` 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 (27 lines × 3) plugins/fourier-filter/src/lib.rs:1232— plugins/fourier-filter/src/lib.rs:1232-1258 | plugins/fourier-filter/src/lib.rs:1330-1356 | plugins/fourier-filter/src/lib.rs:1366-1392 — 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 `plugins/fourier-filter/src/lib.rs:1232` 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 (27 lines × 2) plugins/image-scaler/src/lib.rs:361— plugins/image-scaler/src/lib.rs:361-387 | plugins/pixel-extend/src/lib.rs:825-851 — before extracting anything, compare `plugins/image-scaler/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/image-scaler/src/lib.rs:361` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/pixel-extend/src/lib.rs:824` calls `empty` and `plugins/image-scaler/src/lib.rs:360` 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 (24–26 lines × 2) plugins/mobius-transform/src/lib.rs:909— plugins/mobius-transform/src/lib.rs:909-934 | plugins/mobius-transform/src/lib.rs:1115-1138 — 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 `plugins/mobius-transform/src/lib.rs:909` 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 (24–25 lines × 2) plugins/scatter-map/src/lib.rs:1693— plugins/scatter-map/src/lib.rs:1693-1717 | plugins/scatter-map/src/lib.rs:1771-1794 — 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 `plugins/scatter-map/src/lib.rs:1693` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–23 lines × 2) plugins/voronoi-generate/src/lib.rs:972— plugins/voronoi-generate/src/lib.rs:972-994 | plugins/voronoi-generate/src/lib.rs:1108-1129 — 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 `plugins/voronoi-generate/src/lib.rs:972` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–22 lines × 31) plugins/channel-remap/src/lib.rs:314— plugins/channel-remap/src/lib.rs:314-334 | plugins/checker-generate/src/lib.rs:326-346 | plugins/color-ajust/src/lib.rs:135-156 | plugins/color-boundary-blur/src/lib.rs:343-362 | plugins/color-change/src/lib.rs:163-184 | plugins/color-composite/src/lib.rs:553-573 | plugins/color-convert/src/lib.rs:122-142 | plugins/color-quantize/src/lib.rs:480-499 | plugins/color-select/src/lib.rs:214-234 | plugins/contour-generate/src/lib.rs:156-177 | plugins/depth-fog/src/lib.rs:198-218 | plugins/differential-generate/src/lib.rs:199-219 | plugins/displace-scatter/src/lib.rs:867-887 | plugins/distance-generate/src/lib.rs:179-200 | plugins/eyedropper-mask/src/lib.rs:276-297 | plugins/fft/src/lib.rs:163-183 | plugins/fourier-filter/src/lib.rs:579-599 | plugins/gabor-generate/src/lib.rs:410-429 | plugins/gradient-blur/src/lib.rs:176-196 | plugins/gradient-displace/src/lib.rs:163-183 | plugins/ifft/src/lib.rs:152-172 | plugins/image-calculate/src/lib.rs:331-350 | plugins/image-scaler/src/lib.rs:459-479 | plugins/light-wrap/src/lib.rs:542-562 | plugins/line-repaint/src/lib.rs:165-185 | plugins/mobius-transform/src/lib.rs:416-435 | plugins/normal-generate/src/lib.rs:301-321 | plugins/pixel-extend/src/lib.rs:942-962 | plugins/region-colorize/src/lib.rs:211-232 | plugins/singular-value-decompose/src/lib.rs:126-146 | plugins/voronoi-generate/src/lib.rs:440-461 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/checker-generate/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:314` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 5) crates/utils/src/spectral_wgpu.rs:339— crates/utils/src/spectral_wgpu.rs:339-359 | plugins/differential-generate/src/gpu/wgpu/mod.rs:280-300 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:270-290 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:296-316 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:272-292 — before extracting anything, compare `crates/utils/src/spectral_wgpu.rs` and `plugins/differential-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/src/spectral_wgpu.rs:339` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) plugins/distance-generate/src/lib.rs:274— plugins/distance-generate/src/lib.rs:274-292 | plugins/normal-generate/src/lib.rs:423-442 — before extracting anything, compare `plugins/distance-generate/src/lib.rs` and `plugins/normal-generate/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 182 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/distance-generate/src/lib.rs: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 (20 lines × 2) plugins/image-relight/src/gpu/mod.rs:42— plugins/image-relight/src/gpu/mod.rs:42-61 | plugins/pixel-extend/src/gpu/mod.rs:71-90 — before extracting anything, compare `plugins/image-relight/src/gpu/mod.rs` and `plugins/pixel-extend/src/gpu/mod.rs` as WHOLE FILES: this scan already matched 7 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/image-relight/src/gpu/mod.rs:62` calls `validate_compute_limits` and `plugins/pixel-extend/src/gpu/mod.rs:91` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 6) plugins/fourier-filter/src/lib.rs:1077— plugins/fourier-filter/src/lib.rs:1077-1095 | plugins/fourier-filter/src/lib.rs:1108-1126 | plugins/fourier-filter/src/lib.rs:1139-1157 | plugins/fourier-filter/src/lib.rs:1170-1188 | plugins/fourier-filter/src/lib.rs:1268-1286 | plugins/fourier-filter/src/lib.rs:1299-1317 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/fourier-filter/src/lib.rs:1077` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 4) plugins/fft/src/lib.rs:333— plugins/fft/src/lib.rs:333-351 | plugins/fourier-filter/src/lib.rs:2178-2196 | plugins/ifft/src/lib.rs:395-413 | plugins/singular-value-decompose/src/lib.rs:364-382 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/fourier-filter/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–19 lines × 3) plugins/checker-generate/src/lib.rs:277— plugins/checker-generate/src/lib.rs:277-295 | plugins/light-wrap/src/lib.rs:489-507 | plugins/scatter-map/src/lib.rs:727-742 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/checker-generate/src/lib.rs:277` 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 (26 lines × 2) plugins/gradient-blur/src/lib.rs:516— plugins/gradient-blur/src/lib.rs:516-541 | plugins/gradient-displace/src/lib.rs:442-467 — before extracting anything, compare `plugins/gradient-blur/src/lib.rs` and `plugins/gradient-displace/src/lib.rs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 501 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 7) plugins/fourier-filter/src/lib.rs:1073— plugins/fourier-filter/src/lib.rs:1073-1090 | plugins/fourier-filter/src/lib.rs:1104-1121 | plugins/fourier-filter/src/lib.rs:1135-1152 | plugins/fourier-filter/src/lib.rs:1228-1245 | plugins/fourier-filter/src/lib.rs:1264-1281 | plugins/fourier-filter/src/lib.rs:1326-1343 | plugins/fourier-filter/src/lib.rs:1362-1379 — 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, `plugins/fourier-filter/src/lib.rs:1246` calls `Some` and `plugins/fourier-filter/src/lib.rs:1091` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 6) plugins/channel-remap/src/lib.rs:744— plugins/channel-remap/src/lib.rs:744-761 | plugins/color-change/src/lib.rs:417-434 | plugins/color-composite/src/lib.rs:1569-1586 | plugins/color-select/src/lib.rs:490-507 | plugins/image-scaler/src/lib.rs:1529-1546 | plugins/pixel-extend/src/lib.rs:2332-2349 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-change/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17–18 lines × 4) plugins/differential-generate/src/lib.rs:494— plugins/differential-generate/src/lib.rs:494-510 | plugins/displace-scatter/src/lib.rs:2506-2523 | plugins/gradient-blur/src/lib.rs:575-592 | plugins/gradient-displace/src/lib.rs:501-518 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17–18 lines × 2) plugins/displace-scatter/src/lib.rs:395— plugins/displace-scatter/src/lib.rs:395-412 | plugins/scatter-map/src/lib.rs:354-370 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/scatter-map/src/lib.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 357 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:395` 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 (14–17 lines × 3) plugins/differential-generate/src/gpu/wgpu/mod.rs:92— plugins/differential-generate/src/gpu/wgpu/mod.rs:92-105 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:88-104 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:89-105 — before extracting anything, compare `plugins/differential-generate/src/gpu/wgpu/mod.rs` and `plugins/gabor-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 193 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/differential-generate/src/gpu/wgpu/mod.rs:92` 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 (16–17 lines × 2) plugins/space-convert/src/lib.rs:1911— plugins/space-convert/src/lib.rs:1911-1927 | plugins/space-convert/src/lib.rs:1973-1988 — 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 `plugins/space-convert/src/lib.rs:1911` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13–16 lines × 5) plugins/color-boundary-blur/src/lib.rs:366— plugins/color-boundary-blur/src/lib.rs:366-378 | plugins/color-change/src/lib.rs:190-205 | plugins/color-composite/src/lib.rs:579-591 | plugins/color-select/src/lib.rs:240-252 | plugins/eyedropper-mask/src/lib.rs:303-318 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/color-change/src/lib.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:366` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) plugins/checker-generate/src/lib.rs:743— plugins/checker-generate/src/lib.rs:743-758 | plugins/light-wrap/src/lib.rs:1728-1743 | plugins/voronoi-generate/src/lib.rs:1438-1453 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/light-wrap/src/lib.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 5) plugins/differential-generate/src/lib.rs:83— plugins/differential-generate/src/lib.rs:83-97 | plugins/distance-generate/src/lib.rs:92-106 | plugins/fft/src/lib.rs:88-102 | plugins/ifft/src/lib.rs:77-91 | plugins/pixel-extend/src/lib.rs:574-588 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/distance-generate/src/lib.rs` as WHOLE FILES: this scan already matched 10 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 `plugins/differential-generate/src/lib.rs:83` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/distance-generate/src/lib.rs:91` calls `set_precision` and `plugins/fft/src/lib.rs:87` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14–15 lines × 3) plugins/color-quantize/src/gpu/wgpu/mod.rs:51— plugins/color-quantize/src/gpu/wgpu/mod.rs:51-64 | plugins/image-relight/src/gpu/mod.rs:43-57 | plugins/pixel-extend/src/gpu/mod.rs:72-86 — before extracting anything, compare `plugins/image-relight/src/gpu/mod.rs` and `plugins/pixel-extend/src/gpu/mod.rs` as WHOLE FILES: this scan already matched 7 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.
Duplicated block (15 lines × 3) plugins/image-scaler/src/lib.rs:1174— plugins/image-scaler/src/lib.rs:1174-1188 | plugins/mobius-transform/src/lib.rs:861-875 | plugins/pixel-extend/src/lib.rs:2129-2143 — before extracting anything, compare `plugins/image-scaler/src/lib.rs` and `plugins/mobius-transform/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/image-scaler/src/lib.rs:1174` 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 × 2) plugins/normal-generate/src/lib.rs:246— plugins/normal-generate/src/lib.rs:246-259 | plugins/pixel-extend/src/lib.rs:892-906 — before extracting anything, compare `plugins/normal-generate/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/normal-generate/src/lib.rs:246` 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 (14 lines × 9) plugins/fourier-filter/src/lib.rs:1077— plugins/fourier-filter/src/lib.rs:1077-1090 | plugins/fourier-filter/src/lib.rs:1108-1121 | plugins/fourier-filter/src/lib.rs:1139-1152 | plugins/fourier-filter/src/lib.rs:1170-1183 | plugins/fourier-filter/src/lib.rs:1232-1245 | plugins/fourier-filter/src/lib.rs:1268-1281 | plugins/fourier-filter/src/lib.rs:1299-1312 | plugins/fourier-filter/src/lib.rs:1330-1343 | plugins/fourier-filter/src/lib.rs:1366-1379 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/fourier-filter/src/lib.rs:1077` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/fourier-filter/src/lib.rs:1246` calls `Some` and `plugins/fourier-filter/src/lib.rs:1091` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 5) plugins/fourier-filter/src/lib.rs:1072— plugins/fourier-filter/src/lib.rs:1072-1085 | plugins/fourier-filter/src/lib.rs:1103-1116 | plugins/fourier-filter/src/lib.rs:1134-1147 | plugins/fourier-filter/src/lib.rs:1196-1209 | plugins/fourier-filter/src/lib.rs:1263-1276 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/fourier-filter/src/lib.rs:1072` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 4) plugins/color-ajust/src/lib.rs:120— plugins/color-ajust/src/lib.rs:120-133 | plugins/color-convert/src/lib.rs:108-121 | plugins/contour-generate/src/lib.rs:141-154 | plugins/distance-generate/src/lib.rs:164-177 — before extracting anything, compare `plugins/color-ajust/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-ajust/src/lib.rs: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 (13 lines × 6) plugins/gabor-generate/src/lib.rs:619— plugins/gabor-generate/src/lib.rs:619-631 | plugins/gabor-generate/src/lib.rs:811-823 | plugins/image-calculate/src/lib.rs:688-700 | plugins/normal-generate/src/lib.rs:801-813 | plugins/voronoi-generate/src/lib.rs:996-1008 | plugins/voronoi-generate/src/lib.rs:1131-1143 — before extracting anything, compare `plugins/gabor-generate/src/lib.rs` and `plugins/image-calculate/src/lib.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gabor-generate/src/lib.rs:619` 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 (13 lines × 5) plugins/fft/src/lib.rs:148— plugins/fft/src/lib.rs:148-160 | plugins/ifft/src/lib.rs:137-149 | plugins/line-repaint/src/lib.rs:150-162 | plugins/normal-generate/src/lib.rs:286-298 | plugins/singular-value-decompose/src/lib.rs:111-123 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/ifft/src/lib.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 235 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fft/src/lib.rs:148` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 4) plugins/color-quantize/src/lib.rs:290— plugins/color-quantize/src/lib.rs:290-302 | plugins/gabor-generate/src/lib.rs:307-319 | plugins/region-colorize/src/lib.rs:99-111 | plugins/voronoi-generate/src/lib.rs:218-230 — before extracting anything, compare `plugins/color-quantize/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-quantize/src/lib.rs:290` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/region-colorize/src/lib.rs:98` calls `empty` and `plugins/color-quantize/src/lib.rs:289` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–13 lines × 4) plugins/depth-fog/src/lib.rs:182— plugins/depth-fog/src/lib.rs:182-193 | plugins/gradient-blur/src/lib.rs:160-171 | plugins/gradient-displace/src/lib.rs:147-158 | plugins/voronoi-generate/src/lib.rs:412-424 — before extracting anything, compare `plugins/depth-fog/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/depth-fog/src/lib.rs:182` 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–13 lines × 3) plugins/fft/src/lib.rs:277— plugins/fft/src/lib.rs:277-288 | plugins/ifft/src/lib.rs:309-321 | plugins/singular-value-decompose/src/lib.rs:237-248 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/ifft/src/lib.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 235 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fft/src/lib.rs:277` 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 (13 lines × 23) plugins/channel-remap/src/lib.rs:404— plugins/channel-remap/src/lib.rs:404-416 | plugins/color-boundary-blur/src/lib.rs:454-466 | plugins/color-change/src/lib.rs:305-317 | plugins/color-composite/src/lib.rs:708-720 | plugins/color-quantize/src/lib.rs:585-597 | plugins/color-select/src/lib.rs:331-343 | plugins/displace-scatter/src/lib.rs:1107-1119 | plugins/eyedropper-mask/src/lib.rs:405-417 | plugins/fourier-filter/src/lib.rs:849-861 | plugins/gabor-generate/src/lib.rs:509-521 | plugins/glass-displace/src/plugin.rs:307-319 | plugins/image-calculate/src/lib.rs:468-480 | plugins/image-encrypt-decrypt/src/lib.rs:421-433 | plugins/image-relight/src/lib.rs:1225-1237 | plugins/image-scaler/src/lib.rs:636-648 | plugins/image-transform/src/lib.rs:421-433 | plugins/light-wrap/src/lib.rs:652-664 | plugins/mobius-transform/src/lib.rs:481-493 | plugins/pixel-extend/src/lib.rs:1078-1090 | plugins/rainbow-generate/src/lib.rs:255-267 | plugins/region-colorize/src/lib.rs:299-311 | plugins/scatter-map/src/lib.rs:987-999 | plugins/space-convert/src/lib.rs:860-872 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-boundary-blur/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `params` to `&mut Parameters<Params>` in one and `&mut ae::Parameters<Params>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10–12 lines × 14) plugins/color-composite/src/lib.rs:502— plugins/color-composite/src/lib.rs:502-512 | plugins/displace-scatter/src/lib.rs:565-575 | plugins/displace-scatter/src/lib.rs:724-734 | plugins/eyedropper-mask/src/lib.rs:223-233 | plugins/image-relight/src/lib.rs:560-569 | plugins/image-transform/src/lib.rs:200-209 | plugins/line-repaint/src/lib.rs:125-136 | plugins/normal-generate/src/lib.rs:148-158 | plugins/normal-generate/src/lib.rs:184-194 | plugins/normal-generate/src/lib.rs:245-255 | plugins/pixel-extend/src/lib.rs:891-901 | plugins/scatter-map/src/lib.rs:484-493 | plugins/voronoi-generate/src/lib.rs:293-303 | plugins/voronoi-generate/src/lib.rs:360-369 — before extracting anything, compare `plugins/color-composite/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/color-composite/src/lib.rs:502` 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 (10–12 lines × 4) plugins/glass-displace/src/params.rs:270— plugins/glass-displace/src/params.rs:270-279 | plugins/image-scaler/src/lib.rs:413-424 | plugins/pixel-extend/src/lib.rs:649-659 | plugins/region-colorize/src/lib.rs:164-175 — before extracting anything, compare `plugins/glass-displace/src/params.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/glass-displace/src/params.rs:270` 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 (10–12 lines × 2) plugins/mobius-transform/src/lib.rs:373— plugins/mobius-transform/src/lib.rs:373-384 | plugins/rainbow-generate/src/params.rs:570-579 — 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 `plugins/mobius-transform/src/lib.rs:373` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 10) plugins/checker-generate/src/lib.rs:556— plugins/checker-generate/src/lib.rs:556-566 | plugins/contour-generate/src/lib.rs:322-332 | plugins/depth-fog/src/lib.rs:370-380 | plugins/differential-generate/src/lib.rs:391-401 | plugins/distance-generate/src/lib.rs:483-493 | plugins/image-calculate/src/lib.rs:700-710 | plugins/normal-generate/src/lib.rs:813-823 | plugins/voronoi-generate/src/lib.rs:675-685 | plugins/voronoi-generate/src/lib.rs:1008-1018 | plugins/voronoi-generate/src/lib.rs:1143-1153 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/contour-generate/src/lib.rs` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/checker-generate/src/lib.rs:556` 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–11 lines × 10) plugins/color-boundary-blur/src/lib.rs:322— plugins/color-boundary-blur/src/lib.rs:322-331 | plugins/color-composite/src/lib.rs:532-541 | plugins/color-quantize/src/lib.rs:458-467 | plugins/color-select/src/lib.rs:193-202 | plugins/fourier-filter/src/lib.rs:557-567 | plugins/gabor-generate/src/lib.rs:378-387 | plugins/image-calculate/src/lib.rs:310-319 | plugins/image-scaler/src/lib.rs:438-447 | plugins/light-wrap/src/lib.rs:521-530 | plugins/region-colorize/src/lib.rs:189-198 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/color-composite/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:322` 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 (11 lines × 9) plugins/channel-remap/src/lib.rs:843— plugins/channel-remap/src/lib.rs:843-853 | plugins/channel-remap/src/lib.rs:860-870 | plugins/channel-remap/src/lib.rs:877-887 | plugins/color-convert/src/lib.rs:252-262 | plugins/color-convert/src/lib.rs:270-280 | plugins/color-convert/src/lib.rs:288-298 | plugins/image-calculate/src/lib.rs:1304-1314 | plugins/image-calculate/src/lib.rs:1321-1331 | plugins/image-calculate/src/lib.rs:1338-1348 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:843` 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–11 lines × 6) plugins/mobius-transform/src/lib.rs:908— plugins/mobius-transform/src/lib.rs:908-918 | plugins/mobius-transform/src/lib.rs:958-968 | plugins/mobius-transform/src/lib.rs:1015-1025 | plugins/mobius-transform/src/lib.rs:1114-1123 | plugins/mobius-transform/src/lib.rs:1161-1170 | plugins/mobius-transform/src/lib.rs:1215-1224 — 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.
Duplicated block (11 lines × 4) plugins/checker-generate/src/lib.rs:790— plugins/checker-generate/src/lib.rs:790-800 | plugins/color-composite/src/lib.rs:1283-1293 | plugins/light-wrap/src/lib.rs:1749-1759 | plugins/voronoi-generate/src/lib.rs:1508-1518 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/color-composite/src/lib.rs` as WHOLE FILES: this scan already matched 4 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines 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–11 lines × 4) plugins/depth-fog/src/lib.rs:66— plugins/depth-fog/src/lib.rs:66-76 | plugins/depth-fog/src/lib.rs:79-89 | plugins/gabor-generate/src/lib.rs:324-334 | plugins/space-convert/src/lib.rs:534-543 — before extracting anything, compare `plugins/depth-fog/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/depth-fog/src/lib.rs:66` 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 (11 lines × 3) plugins/checker-generate/src/lib.rs:687— plugins/checker-generate/src/lib.rs:687-697 | plugins/glass-displace/src/render.rs:702-712 | plugins/rainbow-generate/src/lib.rs:647-657 — before extracting anything, compare `plugins/glass-displace/src/render.rs` and `plugins/rainbow-generate/src/lib.rs` as WHOLE FILES: this scan already matched 6 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 (8–11 lines × 2) plugins/fft/src/lib.rs:266— plugins/fft/src/lib.rs:266-273 | plugins/ifft/src/lib.rs:284-294 — before extracting anything, compare `plugins/fft/src/lib.rs` and `plugins/ifft/src/lib.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 235 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/fft/src/lib.rs:266` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 17) plugins/channel-remap/src/lib.rs:436— plugins/channel-remap/src/lib.rs:436-445 | plugins/checker-generate/src/lib.rs:412-421 | plugins/color-change/src/lib.rs:329-338 | plugins/color-composite/src/lib.rs:740-749 | plugins/color-quantize/src/lib.rs:617-625 | plugins/color-select/src/lib.rs:363-372 | plugins/depth-fog/src/lib.rs:266-275 | plugins/displace-scatter/src/lib.rs:1131-1140 | plugins/eyedropper-mask/src/lib.rs:437-446 | plugins/fourier-filter/src/lib.rs:881-890 | plugins/gabor-generate/src/lib.rs:533-542 | plugins/image-calculate/src/lib.rs:500-508 | plugins/image-scaler/src/lib.rs:668-677 | plugins/light-wrap/src/lib.rs:684-693 | plugins/mobius-transform/src/lib.rs:505-514 | plugins/region-colorize/src/lib.rs:323-332 | plugins/scatter-map/src/lib.rs:1018-1026 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/checker-generate/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:436` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `params` to `&mut ae::Parameters<Params>` in one and `&mut Parameters<Params>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 14) plugins/checker-generate/src/lib.rs:106— plugins/checker-generate/src/lib.rs:106-116 | plugins/color-quantize/src/lib.rs:329-339 | plugins/color-select/src/lib.rs:126-136 | plugins/displace-scatter/src/lib.rs:309-319 | plugins/fourier-filter/src/lib.rs:415-425 | plugins/gabor-generate/src/lib.rs:150-160 | plugins/gabor-generate/src/lib.rs:175-185 | plugins/gabor-generate/src/lib.rs:204-214 | plugins/light-wrap/src/lib.rs:401-411 | plugins/pixel-extend/src/lib.rs:781-791 | plugins/region-colorize/src/lib.rs:74-84 | plugins/region-colorize/src/lib.rs:134-144 | plugins/scatter-map/src/lib.rs:462-471 | plugins/space-convert/src/lib.rs:601-610 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/color-quantize/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/checker-generate/src/lib.rs:106` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9–10 lines × 10) plugins/color-boundary-blur/src/lib.rs:485— plugins/color-boundary-blur/src/lib.rs:485-493 | plugins/glass-displace/src/plugin.rs:329-337 | plugins/gradient-blur/src/lib.rs:235-243 | plugins/gradient-displace/src/lib.rs:222-230 | plugins/image-encrypt-decrypt/src/lib.rs:443-451 | plugins/image-relight/src/lib.rs:1247-1255 | plugins/image-transform/src/lib.rs:451-459 | plugins/pixel-extend/src/lib.rs:1101-1110 | plugins/rainbow-generate/src/lib.rs:285-293 | plugins/space-convert/src/lib.rs:882-890 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/gradient-blur/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/gradient-blur/src/lib.rs:235` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `params` to `&mut ae::Parameters<Params>` in one and `&mut Parameters<Params>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9–10 lines × 8) plugins/mobius-transform/src/lib.rs:803— plugins/mobius-transform/src/lib.rs:803-812 | plugins/mobius-transform/src/lib.rs:904-913 | plugins/mobius-transform/src/lib.rs:954-963 | plugins/mobius-transform/src/lib.rs:1011-1020 | plugins/mobius-transform/src/lib.rs:1083-1091 | plugins/mobius-transform/src/lib.rs:1111-1119 | plugins/mobius-transform/src/lib.rs:1158-1166 | plugins/mobius-transform/src/lib.rs:1212-1220 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 7) plugins/channel-remap/src/lib.rs:808— plugins/channel-remap/src/lib.rs:808-817 | plugins/channel-remap/src/lib.rs:923-932 | plugins/color-convert/src/lib.rs:216-225 | plugins/color-convert/src/lib.rs:334-343 | plugins/fourier-filter/src/lib.rs:1987-1996 | plugins/image-calculate/src/lib.rs:1269-1278 | plugins/image-calculate/src/lib.rs:1384-1393 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:808` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `space` to `CalcColorSpace` in one and `ColorSpace` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9–10 lines × 2) plugins/mobius-transform/src/lib.rs:832— plugins/mobius-transform/src/lib.rs:832-841 | plugins/mobius-transform/src/lib.rs:1068-1076 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–9 lines × 91) plugins/checker-generate/src/lib.rs:155— plugins/checker-generate/src/lib.rs:155-165 | plugins/checker-generate/src/lib.rs:181-191 | plugins/checker-generate/src/lib.rs:264-274 | plugins/color-ajust/src/lib.rs:65-75 | plugins/color-boundary-blur/src/lib.rs:108-118 | plugins/color-boundary-blur/src/lib.rs:121-131 | plugins/color-boundary-blur/src/lib.rs:134-139 | plugins/color-boundary-blur/src/lib.rs:203-213 | plugins/color-boundary-blur/src/lib.rs:228-238 | plugins/color-boundary-blur/src/lib.rs:241-251 | plugins/color-boundary-blur/src/lib.rs:254-264 | plugins/color-boundary-blur/src/lib.rs:267-277 | plugins/color-boundary-blur/src/lib.rs:280-290 | plugins/color-quantize/src/lib.rs:417-427 | plugins/contour-generate/src/lib.rs:41-51 | plugins/contour-generate/src/lib.rs:54-64 | plugins/contour-generate/src/lib.rs:67-77 | plugins/contour-generate/src/lib.rs:80-90 | plugins/depth-fog/src/lib.rs:92-102 | plugins/depth-fog/src/lib.rs:105-115 | plugins/displace-scatter/src/lib.rs:367-377 | plugins/displace-scatter/src/lib.rs:380-390 | plugins/displace-scatter/src/lib.rs:800-810 | plugins/distance-generate/src/lib.rs:72-82 | plugins/distance-generate/src/lib.rs:85-95 | plugins/distance-generate/src/lib.rs:119-129 | plugins/distance-generate/src/lib.rs:132-142 | plugins/eyedropper-mask/src/lib.rs:119-129 | plugins/eyedropper-mask/src/lib.rs:132-142 | plugins/eyedropper-mask/src/lib.rs:145-155 | plugins/fourier-filter/src/lib.rs:280-289 | plugins/fourier-filter/src/lib.rs:292-301 | plugins/fourier-filter/src/lib.rs:304-314 | plugins/fourier-filter/src/lib.rs:317-326 | plugins/fourier-filter/src/lib.rs:329-338 | plugins/fourier-filter/src/lib.rs:341-351 | plugins/fourier-filter/src/lib.rs:354-363 | plugins/fourier-filter/src/lib.rs:366-375 | plugins/fourier-filter/src/lib.rs:378-388 | plugins/fourier-filter/src/lib.rs:391-400 | plugins/fourier-filter/src/lib.rs:403-412 | plugins/fourier-filter/src/lib.rs:460-470 | plugins/fourier-filter/src/lib.rs:499-509 | plugins/fourier-filter/src/lib.rs:512-522 | plugins/gabor-generate/src/lib.rs:291-301 | plugins/glass-displace/src/params.rs:162-171 | plugins/glass-displace/src/params.rs:174-183 | plugins/glass-displace/src/params.rs:304-313 | plugins/glass-displace/src/params.rs:368-377 | plugins/gradient-blur/src/lib.rs:93-103 | plugins/gradient-blur/src/lib.rs:118-128 | plugins/gradient-displace/src/lib.rs:105-115 | plugins/image-calculate/src/lib.rs:249-259 | plugins/image-relight/src/lib.rs:575-584 | plugins/light-wrap/src/lib.rs:198-208 | plugins/light-wrap/src/lib.rs:219-229 | plugins/light-wrap/src/lib.rs:240-250 | plugins/light-wrap/src/lib.rs:275-285 | plugins/light-wrap/src/lib.rs:424-434 | plugins/light-wrap/src/lib.rs:437-447 | plugins/line-repaint/src/lib.rs:77-87 | plugins/line-repaint/src/lib.rs:90-100 | plugins/line-repaint/src/lib.rs:112-122 | plugins/mobius-transform/src/lib.rs:322-332 | plugins/normal-generate/src/lib.rs:69-79 | plugins/normal-generate/src/lib.rs:110-120 | plugins/normal-generate/src/lib.rs:123-133 | plugins/normal-generate/src/lib.rs:171-181 | plugins/normal-generate/src/lib.rs:219-229 | plugins/normal-generate/src/lib.rs:232-242 | plugins/pixel-extend/src/lib.rs:567-577 | plugins/pixel-extend/src/lib.rs:672-682 | plugins/pixel-extend/src/lib.rs:694-704 | plugins/pixel-extend/src/lib.rs:768-778 | plugins/rainbow-generate/src/params.rs:476-485 | plugins/scatter-map/src/lib.rs:314-323 | plugins/scatter-map/src/lib.rs:401-410 | plugins/scatter-map/src/lib.rs:413-422 | plugins/scatter-map/src/lib.rs:425-434 | plugins/scatter-map/src/lib.rs:437-446 | plugins/scatter-map/src/lib.rs:715-724 | plugins/space-convert/src/lib.rs:416-425 | plugins/space-convert/src/lib.rs:428-437 | plugins/space-convert/src/lib.rs:481-490 | plugins/space-convert/src/lib.rs:589-598 | plugins/voronoi-generate/src/lib.rs:169-177 | plugins/voronoi-generate/src/lib.rs:184-194 | plugins/voronoi-generate/src/lib.rs:197-207 | plugins/voronoi-generate/src/lib.rs:210-220 | plugins/voronoi-generate/src/lib.rs:245-255 | plugins/voronoi-generate/src/lib.rs:267-277 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/color-ajust/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/checker-generate/src/lib.rs:155` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/voronoi-generate/src/lib.rs:179` calls `add` and `plugins/checker-generate/src/lib.rs:165` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 34) plugins/differential-generate/src/lib.rs:89— plugins/differential-generate/src/lib.rs:89-97 | plugins/differential-generate/src/lib.rs:102-110 | plugins/displace-scatter/src/lib.rs:401-409 | plugins/displace-scatter/src/lib.rs:759-767 | plugins/distance-generate/src/lib.rs:98-106 | plugins/fft/src/lib.rs:94-102 | plugins/fft/src/lib.rs:107-115 | plugins/gabor-generate/src/lib.rs:239-247 | plugins/gabor-generate/src/lib.rs:252-260 | plugins/gabor-generate/src/lib.rs:265-273 | plugins/gabor-generate/src/lib.rs:278-286 | plugins/gabor-generate/src/lib.rs:337-345 | plugins/glass-displace/src/params.rs:292-300 | plugins/glass-displace/src/params.rs:316-324 | plugins/gradient-displace/src/lib.rs:92-100 | plugins/ifft/src/lib.rs:83-91 | plugins/ifft/src/lib.rs:96-104 | plugins/image-calculate/src/lib.rs:210-218 | plugins/image-calculate/src/lib.rs:236-244 | plugins/image-relight/src/lib.rs:604-612 | plugins/light-wrap/src/lib.rs:253-261 | plugins/mobius-transform/src/lib.rs:202-210 | plugins/mobius-transform/src/lib.rs:214-222 | plugins/mobius-transform/src/lib.rs:228-236 | plugins/mobius-transform/src/lib.rs:240-248 | plugins/mobius-transform/src/lib.rs:254-262 | plugins/mobius-transform/src/lib.rs:266-274 | plugins/mobius-transform/src/lib.rs:280-288 | plugins/mobius-transform/src/lib.rs:292-300 | plugins/pixel-extend/src/lib.rs:580-588 | plugins/scatter-map/src/lib.rs:360-368 | plugins/space-convert/src/lib.rs:546-554 | plugins/space-convert/src/lib.rs:577-585 | plugins/voronoi-generate/src/lib.rs:280-288 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/differential-generate/src/lib.rs:89` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 33) plugins/color-ajust/src/lib.rs:51— plugins/color-ajust/src/lib.rs:51-61 | plugins/color-ajust/src/lib.rs:79-89 | plugins/differential-generate/src/lib.rs:90-99 | plugins/differential-generate/src/lib.rs:103-112 | plugins/displace-scatter/src/lib.rs:402-411 | plugins/displace-scatter/src/lib.rs:760-769 | plugins/distance-generate/src/lib.rs:99-108 | plugins/fft/src/lib.rs:95-104 | plugins/fft/src/lib.rs:108-117 | plugins/gabor-generate/src/lib.rs:240-249 | plugins/gabor-generate/src/lib.rs:253-262 | plugins/gabor-generate/src/lib.rs:266-275 | plugins/gabor-generate/src/lib.rs:279-288 | plugins/gabor-generate/src/lib.rs:338-347 | plugins/glass-displace/src/params.rs:293-301 | plugins/gradient-displace/src/lib.rs:93-102 | plugins/ifft/src/lib.rs:84-93 | plugins/ifft/src/lib.rs:97-106 | plugins/image-calculate/src/lib.rs:237-246 | plugins/image-relight/src/lib.rs:605-613 | plugins/light-wrap/src/lib.rs:254-263 | plugins/mobius-transform/src/lib.rs:203-211 | plugins/mobius-transform/src/lib.rs:215-225 | plugins/mobius-transform/src/lib.rs:229-237 | plugins/mobius-transform/src/lib.rs:241-251 | plugins/mobius-transform/src/lib.rs:255-263 | plugins/mobius-transform/src/lib.rs:267-277 | plugins/mobius-transform/src/lib.rs:281-289 | plugins/mobius-transform/src/lib.rs:293-302 | plugins/scatter-map/src/lib.rs:361-369 | plugins/space-convert/src/lib.rs:547-555 | plugins/space-convert/src/lib.rs:578-586 | plugins/voronoi-generate/src/lib.rs:281-290 — before extracting anything, compare `plugins/color-ajust/src/lib.rs` and `plugins/differential-generate/src/lib.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/color-ajust/src/lib.rs: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.
Duplicated block (9 lines × 8) plugins/channel-remap/src/lib.rs:807— plugins/channel-remap/src/lib.rs:807-815 | plugins/channel-remap/src/lib.rs:922-930 | plugins/color-convert/src/lib.rs:215-223 | plugins/color-convert/src/lib.rs:333-341 | plugins/fourier-filter/src/lib.rs:1855-1863 | plugins/fourier-filter/src/lib.rs:1986-1994 | plugins/image-calculate/src/lib.rs:1268-1276 | plugins/image-calculate/src/lib.rs:1383-1391 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (4–9 lines × 3) plugins/image-relight/src/lib.rs:2831— plugins/image-relight/src/lib.rs:2831-2839 | plugins/image-relight/src/lib.rs:2849-2852 | plugins/space-convert/src/lib.rs:2296-2304 — before extracting anything, compare `plugins/image-relight/src/lib.rs` and `plugins/space-convert/src/lib.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/image-relight/src/lib.rs:2831` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/image-relight/src/lib.rs:2830` calls `floor`, `min` and `plugins/image-relight/src/lib.rs:2849` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 36) plugins/color-ajust/src/lib.rs:51— plugins/color-ajust/src/lib.rs:51-58 | plugins/color-ajust/src/lib.rs:79-86 | plugins/differential-generate/src/lib.rs:89-97 | plugins/differential-generate/src/lib.rs:102-110 | plugins/displace-scatter/src/lib.rs:401-409 | plugins/displace-scatter/src/lib.rs:759-767 | plugins/distance-generate/src/lib.rs:98-106 | plugins/fft/src/lib.rs:94-102 | plugins/fft/src/lib.rs:107-115 | plugins/gabor-generate/src/lib.rs:239-247 | plugins/gabor-generate/src/lib.rs:252-260 | plugins/gabor-generate/src/lib.rs:265-273 | plugins/gabor-generate/src/lib.rs:278-286 | plugins/gabor-generate/src/lib.rs:337-345 | plugins/glass-displace/src/params.rs:292-300 | plugins/glass-displace/src/params.rs:316-324 | plugins/gradient-displace/src/lib.rs:92-100 | plugins/ifft/src/lib.rs:83-91 | plugins/ifft/src/lib.rs:96-104 | plugins/image-calculate/src/lib.rs:210-218 | plugins/image-calculate/src/lib.rs:236-244 | plugins/image-relight/src/lib.rs:604-612 | plugins/light-wrap/src/lib.rs:253-261 | plugins/mobius-transform/src/lib.rs:202-210 | plugins/mobius-transform/src/lib.rs:214-222 | plugins/mobius-transform/src/lib.rs:228-236 | plugins/mobius-transform/src/lib.rs:240-248 | plugins/mobius-transform/src/lib.rs:254-262 | plugins/mobius-transform/src/lib.rs:266-274 | plugins/mobius-transform/src/lib.rs:280-288 | plugins/mobius-transform/src/lib.rs:292-300 | plugins/pixel-extend/src/lib.rs:580-588 | plugins/scatter-map/src/lib.rs:360-368 | plugins/space-convert/src/lib.rs:546-554 | plugins/space-convert/src/lib.rs:577-585 | plugins/voronoi-generate/src/lib.rs:280-288 — before extracting anything, compare `plugins/color-ajust/src/lib.rs` and `plugins/differential-generate/src/lib.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/color-ajust/src/lib.rs:51` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 5) plugins/checker-generate/src/lib.rs:348— plugins/checker-generate/src/lib.rs:348-355 | plugins/gabor-generate/src/lib.rs:431-438 | plugins/image-calculate/src/lib.rs:352-359 | plugins/mobius-transform/src/lib.rs:437-443 | plugins/voronoi-generate/src/lib.rs:463-470 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 10 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/checker-generate/src/lib.rs:348` 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 (2–8 lines × 3) plugins/color-composite/src/lib.rs:923— plugins/color-composite/src/lib.rs:923-930 | plugins/color-composite/src/lib.rs:1020-1027 | plugins/color-composite/src/lib.rs:1029-1030 — 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 `plugins/color-composite/src/lib.rs:923` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (4–8 lines × 3) plugins/color-boundary-blur/src/lib.rs:1385— plugins/color-boundary-blur/src/lib.rs:1385-1388 | plugins/pixel-extend/src/lib.rs:2250-2257 | plugins/scatter-map/src/lib.rs:1461-1467 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/pixel-extend/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:1385` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 19) plugins/color-boundary-blur/src/lib.rs:1405— plugins/color-boundary-blur/src/lib.rs:1405-1411 | plugins/color-quantize/src/lib.rs:1631-1639 | plugins/differential-generate/src/lib.rs:316-324 | plugins/displace-scatter/src/lib.rs:1351-1359 | plugins/eyedropper-mask/src/lib.rs:644-651 | plugins/fft/src/lib.rs:288-296 | plugins/fourier-filter/src/lib.rs:1055-1063 | plugins/gabor-generate/src/lib.rs:631-639 | plugins/gabor-generate/src/lib.rs:823-831 | plugins/gradient-blur/src/lib.rs:350-358 | plugins/gradient-displace/src/lib.rs:323-331 | plugins/ifft/src/lib.rs:321-329 | plugins/ifft/src/lib.rs:380-387 | plugins/image-relight/src/lib.rs:1359-1365 | plugins/light-wrap/src/lib.rs:795-803 | plugins/line-repaint/src/lib.rs:409-416 | plugins/scatter-map/src/lib.rs:1131-1137 | plugins/singular-value-decompose/src/lib.rs:248-256 | plugins/space-convert/src/lib.rs:938-944 — before extracting anything, compare `plugins/color-boundary-blur/src/lib.rs` and `plugins/color-quantize/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-boundary-blur/src/lib.rs:1405` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 13) plugins/channel-remap/src/lib.rs:970— plugins/channel-remap/src/lib.rs:970-976 | plugins/channel-remap/src/lib.rs:986-992 | plugins/channel-remap/src/lib.rs:1002-1008 | plugins/channel-remap/src/lib.rs:1036-1042 | plugins/color-convert/src/lib.rs:390-396 | plugins/color-convert/src/lib.rs:409-415 | plugins/color-convert/src/lib.rs:428-434 | plugins/color-convert/src/lib.rs:471-477 | plugins/color-quantize/src/lib.rs:1705-1711 | plugins/image-calculate/src/lib.rs:1431-1437 | plugins/image-calculate/src/lib.rs:1447-1453 | plugins/image-calculate/src/lib.rs:1463-1469 | plugins/image-calculate/src/lib.rs:1497-1503 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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 × 11) plugins/checker-generate/src/lib.rs:556— plugins/checker-generate/src/lib.rs:556-562 | plugins/color-convert/src/lib.rs:585-591 | plugins/contour-generate/src/lib.rs:322-328 | plugins/depth-fog/src/lib.rs:370-376 | plugins/differential-generate/src/lib.rs:391-397 | plugins/distance-generate/src/lib.rs:483-489 | plugins/image-calculate/src/lib.rs:700-706 | plugins/normal-generate/src/lib.rs:813-819 | plugins/voronoi-generate/src/lib.rs:675-681 | plugins/voronoi-generate/src/lib.rs:1008-1014 | plugins/voronoi-generate/src/lib.rs:1143-1149 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/checker-generate/src/lib.rs:556` 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 × 7) plugins/displace-scatter/src/lib.rs:1150— plugins/displace-scatter/src/lib.rs:1150-1156 | plugins/fft/src/lib.rs:204-210 | plugins/fourier-filter/src/lib.rs:898-904 | plugins/image-encrypt-decrypt/src/lib.rs:497-503 | plugins/image-relight/src/lib.rs:1264-1270 | plugins/singular-value-decompose/src/lib.rs:167-173 | plugins/space-convert/src/lib.rs:908-914 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/fft/src/lib.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/space-convert/src/lib.rs:907` calls `read_settings` and `plugins/displace-scatter/src/lib.rs:1149` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (4–6 lines × 3) crates/utils/src/image.rs:220— crates/utils/src/image.rs:220-223 | crates/utils/src/image.rs:281-286 | crates/utils/src/image.rs:322-327 — 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 `crates/utils/src/image.rs:281` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (2–6 lines × 6) plugins/fourier-filter/src/lib.rs:1641— plugins/fourier-filter/src/lib.rs:1641-1642 | plugins/fourier-filter/src/lib.rs:1649-1650 | plugins/fourier-filter/src/lib.rs:1658-1663 | plugins/fourier-filter/src/lib.rs:1699-1700 | plugins/fourier-filter/src/lib.rs:1734-1739 | plugins/fourier-filter/src/lib.rs:1747-1752 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/fourier-filter/src/lib.rs:1740` calls `value_for_direction`, `clamp` and `plugins/fourier-filter/src/lib.rs:1664` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 12) plugins/checker-generate/src/lib.rs:556— plugins/checker-generate/src/lib.rs:556-560 | plugins/color-ajust/src/lib.rs:523-527 | plugins/color-convert/src/lib.rs:585-589 | plugins/contour-generate/src/lib.rs:322-326 | plugins/depth-fog/src/lib.rs:370-374 | plugins/differential-generate/src/lib.rs:391-395 | plugins/distance-generate/src/lib.rs:483-487 | plugins/image-calculate/src/lib.rs:700-704 | plugins/normal-generate/src/lib.rs:813-817 | plugins/voronoi-generate/src/lib.rs:675-679 | plugins/voronoi-generate/src/lib.rs:1008-1012 | plugins/voronoi-generate/src/lib.rs:1143-1147 — before extracting anything, compare `plugins/checker-generate/src/lib.rs` and `plugins/color-ajust/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/checker-generate/src/lib.rs:556` 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 (5 lines × 9) plugins/color-ajust/src/lib.rs:519— plugins/color-ajust/src/lib.rs:519-523 | plugins/color-convert/src/lib.rs:581-585 | plugins/color-quantize/src/lib.rs:1627-1631 | plugins/contour-generate/src/lib.rs:318-322 | plugins/differential-generate/src/lib.rs:312-316 | plugins/differential-generate/src/lib.rs:387-391 | plugins/distance-generate/src/lib.rs:479-483 | plugins/fourier-filter/src/lib.rs:1051-1055 | plugins/voronoi-generate/src/lib.rs:671-675 — before extracting anything, compare `plugins/color-ajust/src/lib.rs` and `plugins/color-convert/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/color-ajust/src/lib.rs:519` 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 (3–5 lines × 6) plugins/displace-scatter/src/lib.rs:2662— plugins/displace-scatter/src/lib.rs:2662-2666 | plugins/gabor-generate/src/lib.rs:1212-1216 | plugins/gabor-generate/src/lib.rs:1219-1221 | plugins/gabor-generate/src/lib.rs:1222-1226 | plugins/scatter-map/src/lib.rs:3327-3331 | plugins/voronoi-generate/src/lib.rs:1252-1254 — before extracting anything, compare `plugins/displace-scatter/src/lib.rs` and `plugins/gabor-generate/src/lib.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 171 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/displace-scatter/src/lib.rs:2662` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/voronoi-generate/src/lib.rs:1254` calls `wrapping_add`, `wrapping_mul`, `hash_u32` and `plugins/displace-scatter/src/lib.rs:2666` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 6) plugins/differential-generate/src/lib.rs:164— plugins/differential-generate/src/lib.rs:164-177 | plugins/fft/src/lib.rs:145-158 | plugins/ifft/src/lib.rs:134-147 | plugins/line-repaint/src/lib.rs:147-160 | plugins/normal-generate/src/lib.rs:283-296 | plugins/singular-value-decompose/src/lib.rs:108-121 — before extracting anything, compare `plugins/differential-generate/src/lib.rs` and `plugins/fft/src/lib.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/differential-generate/src/lib.rs:164` 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 × 20) plugins/channel-remap/src/lib.rs:288— plugins/channel-remap/src/lib.rs:288-299 | plugins/checker-generate/src/lib.rs:305-316 | plugins/color-boundary-blur/src/lib.rs:318-329 | plugins/color-composite/src/lib.rs:528-539 | plugins/color-quantize/src/lib.rs:454-465 | plugins/color-select/src/lib.rs:189-200 | plugins/depth-fog/src/lib.rs:178-189 | plugins/displace-scatter/src/lib.rs:841-852 | plugins/eyedropper-mask/src/lib.rs:249-260 | plugins/fourier-filter/src/lib.rs:553-564 | plugins/gabor-generate/src/lib.rs:374-385 | plugins/gradient-blur/src/lib.rs:156-167 | plugins/gradient-displace/src/lib.rs:143-154 | plugins/image-calculate/src/lib.rs:306-317 | plugins/image-scaler/src/lib.rs:434-445 | plugins/image-transform/src/lib.rs:299-310 | plugins/light-wrap/src/lib.rs:517-528 | plugins/pixel-extend/src/lib.rs:916-927 | plugins/region-colorize/src/lib.rs:185-196 | plugins/voronoi-generate/src/lib.rs:408-420 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/checker-generate/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `plugins/channel-remap/src/lib.rs:288` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `plugins/channel-remap/src/lib.rs:301` calls `set_out_flag2` and `plugins/color-boundary-blur/src/lib.rs:331` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 8) plugins/channel-remap/src/lib.rs:303— plugins/channel-remap/src/lib.rs:303-313 | plugins/color-boundary-blur/src/lib.rs:332-342 | plugins/color-composite/src/lib.rs:542-552 | plugins/color-select/src/lib.rs:203-213 | plugins/eyedropper-mask/src/lib.rs:264-274 | plugins/fourier-filter/src/lib.rs:568-578 | plugins/image-scaler/src/lib.rs:448-458 | plugins/light-wrap/src/lib.rs:531-541 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/color-boundary-blur/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/channel-remap/src/lib.rs:303` 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, `plugins/channel-remap/src/lib.rs:300` calls `set_out_flag2` and `plugins/color-boundary-blur/src/lib.rs:329` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 8) plugins/channel-remap/src/lib.rs:301— plugins/channel-remap/src/lib.rs:301-308 | plugins/displace-scatter/src/lib.rs:854-861 | plugins/eyedropper-mask/src/lib.rs:262-269 | plugins/glass-displace/src/plugin.rs:68-75 | plugins/image-relight/src/lib.rs:982-988 | plugins/pixel-extend/src/lib.rs:929-936 | plugins/rainbow-generate/src/lib.rs:85-92 | plugins/scatter-map/src/lib.rs:768-775 — before extracting anything, compare `plugins/channel-remap/src/lib.rs` and `plugins/displace-scatter/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/channel-remap/src/lib.rs:301` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/glass-displace/src/plugin.rs:65` calls `set_out_flag2` and `plugins/image-relight/src/lib.rs:979` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 5) crates/utils/src/spectral_wgpu.rs:282— crates/utils/src/spectral_wgpu.rs:282-288 | plugins/differential-generate/src/gpu/wgpu/mod.rs:245-249 | plugins/gabor-generate/src/gpu/wgpu/mod.rs:245-249 | plugins/singular-value-decompose/src/gpu/wgpu/mod.rs:251-255 | plugins/voronoi-generate/src/gpu/wgpu/mod.rs:247-251 — before extracting anything, compare `crates/utils/src/spectral_wgpu.rs` and `plugins/differential-generate/src/gpu/wgpu/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/src/spectral_wgpu.rs:282` 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.
Off the main sequence: utils — utils: abstractness 0.14, instability 0.00, distance 0.86 — zone of pain — concrete and depended on by 38 project(s), so it's rigid to change.
Duplicated predicate plugins/image-transform/src/lib.rs:110— `!determinant.is_finite() || determinant.abs() <= 1.0e-8` appears character-identically in 2 files — plugins/image-transform/src/lib.rs, plugins/space-convert/src/lib.rs. 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 plugins/distance-generate/src/lib.rs:316— `(l != lbl) || (r != lbl) || (u != lbl) || (d != lbl)` appears character-identically in 2 files — plugins/distance-generate/src/lib.rs, plugins/normal-generate/src/lib.rs. 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 plugins/color-boundary-blur/src/lib.rs:407— `changed == Params::AddColor || changed == Params::RemoveColor` appears character-identically in 2 files — plugins/color-boundary-blur/src/lib.rs, plugins/color-change/src/lib.rs. 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 plugins/color-convert/src/lib.rs:144— `in_layer_opt.is_some() && out_layer_opt.is_some()` appears character-identically in 4 files — plugins/color-convert/src/lib.rs, plugins/contour-generate/src/lib.rs, plugins/distance-generate/src/lib.rs, plugins/normal-generate/src/lib.rs. 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 plugins/fft/src/lib.rs:208— `in_w == 0 || in_h == 0 || out_w == 0 || out_h == 0` appears character-identically in 3 files — plugins/fft/src/lib.rs, plugins/fourier-filter/src/lib.rs, plugins/singular-value-decompose/src/lib.rs. 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 crates/utils/src/spectral_wgpu.rs:27— `instance_desc.backends.contains(Backends::DX12) && instance_desc.flags.contains(InstanceFlags::VALIDATION)` appears character-identically in 8 files — crates/utils/src/spectral_wgpu.rs, plugins/color-quantize/src/gpu/wgpu/mod.rs, plugins/differential-generate/src/gpu/wgpu/mod.rs, plugins/gabor-generate/src/gpu/wgpu/mod.rs. 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 plugins/channel-remap/src/lib.rs:667— `layer.width() == 0 || layer.height() == 0` appears character-identically in 2 files — plugins/channel-remap/src/lib.rs, plugins/color-composite/src/lib.rs. 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 plugins/color-boundary-blur/src/lib.rs:788— `nx < 0 || ny < 0 || nx >= width as isize || ny >= height as isize` appears character-identically in 3 files — plugins/color-boundary-blur/src/lib.rs, plugins/eyedropper-mask/src/lib.rs, plugins/line-repaint/src/lib.rs. 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 plugins/channel-remap/src/lib.rs:487— `out_layer.width() == 0 || out_layer.height() == 0` appears character-identically in 4 files — plugins/channel-remap/src/lib.rs, plugins/color-change/src/lib.rs, plugins/color-composite/src/lib.rs, plugins/color-select/src/lib.rs. 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 plugins/glass-displace/src/render.rs:797— `requested_rect && rect.width() == layer.width() as i32 && rect.height() == layer.height() as i32` appears character-identically in 2 files — plugins/glass-displace/src/render.rs, plugins/image-encrypt-decrypt/src/lib.rs. 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 plugins/color-quantize/src/gpu/wgpu/mod.rs:133— `res.out_w != params.out_w || res.out_h != params.out_h` appears character-identically in 4 files — plugins/color-quantize/src/gpu/wgpu/mod.rs, plugins/differential-generate/src/gpu/wgpu/mod.rs, plugins/gabor-generate/src/gpu/wgpu/mod.rs, plugins/voronoi-generate/src/gpu/wgpu/mod.rs. 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 plugins/image-relight/src/lib.rs:408— `self .callbacks .checkin_layer_pixels(self.checkout_ids[self.count]) && first_error.is_none()` appears character-identically in 2 files — plugins/image-relight/src/lib.rs, plugins/space-convert/src/lib.rs. 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 plugins/image-relight/src/lib.rs:1268— `src_width == 0 || src_height == 0 || out_width == 0 || out_height == 0` appears character-identically in 2 files — plugins/image-relight/src/lib.rs, plugins/space-convert/src/lib.rs. 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 plugins/gradient-blur/src/lib.rs:516— `width == 0 || height == 0 || !x.is_finite() || !y.is_finite()` appears character-identically in 3 files — plugins/gradient-blur/src/lib.rs, plugins/gradient-displace/src/lib.rs, plugins/light-wrap/src/lib.rs. 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 plugins/distance-generate/src/lib.rs:307— `x == 0 || y == 0 || x + 1 == w || y + 1 == h` appears character-identically in 2 files — plugins/distance-generate/src/lib.rs, plugins/normal-generate/src/lib.rs. 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 crates/utils/src/image.rs:93— `x >= layer.width() || y >= layer.height()` appears character-identically in 2 files — crates/utils/src/image.rs, plugins/checker-generate/src/lib.rs. 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 ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No dependency-update automation Cargo.toml:13— `Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Outdated: anyhow — `anyhow` is locked at 1.0.101 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/utils/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: bytemuck — `bytemuck` is locked at 1.25.0 but 1.25.2 is the current stable release on crates.io, and it already satisfies the `"1.16.0"` requirement declared in crates/utils/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytemuck` and commit the updated REDACTED.
Outdated: chrono — `chrono` is locked at 0.4.43 but 0.4.45 is the current stable release on crates.io, and it already satisfies the `"0.4.42"` requirement declared in plugins/channel-remap/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p chrono` and commit the updated REDACTED.
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.
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 01a1ea4a-fda3-7a39-b686-5136ec3df937 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 14 · Warnings: 660 · Recommendations: 23 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 16:15 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.