Public report of vulkano-rs/vulkano, published 14 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, 14 November 2026, 19:15 UTC · Survey ID cd_1b65bf5097b4483eb7fdb70c33726192
vulkano-rs/vulkano
Measured 14 November 2026, 19:13 UTC, at code version f197585
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 5 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 165,588 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 1.5 person-years · Weakest lens: Production Readiness, 52
Findings by how serious they are
38 critical1637 serious62 minor
20 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
14 November 2026, 19:13 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 ▸
39of 39 dimensions measured by tools.
1721of 1737 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
39dimensions across 5 lenses, read from 165,588 lines of product code in 6 projects.
vulkano-rs/vulkano falls short of our standard for a preview release, in part because we found no logging, tracing or health checks in the code. It scores 63 out of 100 and is rated Adequate, and ten of its 38 critical findings are security problems in the build pipeline.
Production Readiness, at 52, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 6 points. Adding tests for untested code would lift Production Readiness itself, worth about 11 points. Raising Production Readiness to 62 would lift the score to about 68.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-eight parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version and having someone learn the forgotten files would close both risks.
The product code is 165,588 lines, about €220,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 Production Readiness rose from 52 to 62, the lowest score rated Strong, the score would rise from 63 to about 68.
Code composition: what the lines of code are
Product code 87%Tests 13%
New since the last survey: 483 findings
These 483 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Near-duplicate member family (3 members, 252 shared lines) vulkano/src/command_buffer/commands/sync.rs
Code Duplication · Near-duplicate member family (3 members, 68 shared lines) vulkano/src/command_buffer/commands/copy.rs
Code Duplication · Near-duplicate member pair (92 shared lines) vulkano-taskgraph/src/graph/execute.rs
Code Duplication · Near-duplicate member pair (51 shared lines) vulkano/src/command_buffer/commands/clear.rs
Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) vulkano/src/device/physical.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) vulkano/src/buffer/sys.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) vulkano/src/descriptor_set/allocator.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/pipeline/mod.rs
Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/format.rs
Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/pipeline/mod.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/format.rs
Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/image/aspect.rs
Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/image/aspect.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/image/aspect.rs
Code Duplication · Edited copy of a member (81 corresponding lines) autogen/src/extensions.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/memory/device_memory.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/device/queue.rs
Code Duplication · Edited copy of a member (125 corresponding lines) vulkano/src/memory/allocator/mod.rs
Code Duplication · Edited copy of a member (79 corresponding lines) vulkano/src/memory/allocator/mod.rs
Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/device/queue.rs
Code Duplication · Edited copy of a member (74 corresponding lines) vulkano/src/command_buffer/auto/commands/render_pass.rs
Code Duplication · Edited copy of a member (91 corresponding lines) vulkano/src/device/physical.rs
Code Duplication · Edited copy of a member (58 corresponding lines) vulkano/src/buffer/subbuffer.rs
Code Duplication · Edited copy of a member (69 corresponding lines) vulkano/src/command_buffer/commands/clear.rs
Code Duplication · Edited copy of a member (65 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs
Code Duplication · Edited copy of a member (72 corresponding lines) vulkano/src/command_buffer/commands/copy.rs
Code Duplication · Edited copies of one member (3 members, 69+ corresponding lines) vulkano/src/image/mod.rs
Code Duplication · Edited copy of a member (43 corresponding lines) autogen/src/features.rs
Code Duplication · Edited copy of a member (55 corresponding lines) vulkano/src/memory/sparse.rs
Code Duplication · Edited copy of a member (41 corresponding lines) vulkano-taskgraph/src/lib.rs
Code Duplication · Edited copy of a member (58 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs
Code Duplication · Edited copy of a member (47 corresponding lines) vulkano-taskgraph/src/graph/execute.rs
Code Duplication · Edited copy of a member (63 corresponding lines) vulkano-taskgraph/src/graph/mod.rs
Code Duplication · Edited copy of a member (53 corresponding lines) autogen/src/spirv_parse.rs
Code Duplication · Edited copy of a member (58 corresponding lines) vulkano/src/command_buffer/allocator.rs
Code Duplication · Edited copy of a member (38 corresponding lines) vulkano-taskgraph/src/graph/execute.rs
Code Duplication · Edited copy of a member (48 corresponding lines) vulkano/src/command_buffer/auto/commands/render_pass.rs
Code Duplication · Edited copy of a member (37 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs
Code Duplication · Edited copy of a member (48 corresponding lines) vulkano-taskgraph/src/command_buffer/commands/clear.rs
Code Duplication · Edited copy of a member (45 corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/sync/fence.rs
Code Duplication · Edited copies of one member (5 members, 75+ corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs
Code Duplication · Edited copy of a member (40 corresponding lines) vulkano/src/buffer/mod.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/display.rs
Code Duplication · Edited copy of a member (33 corresponding lines) vulkano/src/device/mod.rs
Code Duplication · Edited copy of a member (38 corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs
Code Duplication · Edited copies of one member (4 members, 44+ corresponding lines) vulkano/src/sync/fence.rs
Code Duplication · Edited copy of a member (34 corresponding lines) vulkano/src/command_buffer/commands/sync.rs
Code Duplication · Edited copy of a member (36 corresponding lines) vulkano/src/device/physical.rs
Code Duplication · Edited copies of one member (3 members, 33+ corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs
Code Duplication · Edited copy of a member (32 corresponding lines) vulkano/src/command_buffer/allocator.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/descriptor_set/pool.rs
Code Duplication · Edited copy of a member (31 corresponding lines) vulkano/src/pipeline/graphics/mod.rs
Code Duplication · Edited copy of a member (41 corresponding lines) vulkano/src/command_buffer/auto/commands/clear.rs
Code Duplication · Edited copy of a member (28 corresponding lines) vulkano/src/command_buffer/traits.rs
Code Duplication · Edited copy of a member (38 corresponding lines) vulkano/src/command_buffer/commands/copy.rs
Code Duplication · Edited copy of a member (25 corresponding lines) vulkano/src/descriptor_set/allocator.rs
Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) vulkano/src/sync/future/join.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/buffer/mod.rs
Code Duplication · Edited copy of a member (28 corresponding lines) vulkano/src/image/mod.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/render_pass/mod.rs
Code Duplication · Edited copy of a member (47 corresponding lines) vulkano/src/render_pass/mod.rs
Code Duplication · Edited copy of a member (29 corresponding lines) vulkano/src/command_buffer/auto/commands/pipeline.rs
Code Duplication · Edited copy of a member (41 corresponding lines) vulkano/src/memory/sparse.rs
Code Duplication · Edited copy of a member (29 corresponding lines) vulkano/src/sync/semaphore.rs
Code Duplication · Edited copy of a member (1 corresponding lines) vulkano/src/image/sampler/mod.rs
Code Duplication · Edited copies of one member (3 members, 32+ corresponding lines) vulkano-taskgraph/src/graph/execute.rs
Code Duplication · Edited copy of a member (38 corresponding lines) vulkano/src/device/mod.rs
Code Duplication · Edited copy of a member (24 corresponding lines) vulkano/src/command_buffer/commands/copy.rs
Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) vulkano/src/command_buffer/commands/render_pass.rs
Code Duplication · Edited copy of a member (26 corresponding lines) vulkano/src/device/mod.rs
Code Duplication · Edited copy of a member (32 corresponding lines) vulkano-taskgraph/src/graph/execute.rs
Code Duplication · Edited copies of one member (6 members, 30+ corresponding lines) vulkano/src/command_buffer/auto/commands/pipeline.rs
Code Duplication · Edited copy of a member (31 corresponding lines) vulkano/src/sync/event.rs
Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/buffer/mod.rs
Code Duplication · Edited copy of a member (34 corresponding lines) vulkano/src/command_buffer/auto/builder.rs
Code Duplication · Edited copy of a member (17 corresponding lines) vulkano-util/src/window.rs
Code Duplication · Edited copy of a member (35 corresponding lines) vulkano/src/buffer/allocator.rs
Code Duplication · Edited copy of a member (25 corresponding lines) vulkano/src/cache.rs
Code Duplication · Edited copy of a member (25 corresponding lines) vulkano/src/lib.rs
Code Duplication · Edited copy of a member (29 corresponding lines) vulkano/src/command_buffer/commands/render_pass.rs
Code Duplication · Edited copy of a member (23 corresponding lines) vulkano/src/command_buffer/commands/sync.rs
Code Duplication · Edited copy of a member (18 corresponding lines) vulkano/src/shader/reflect.rs
Code Duplication · Edited copy of a member (20 corresponding lines) vulkano-shaders/src/lib.rs
Code Duplication · Edited copy of a member (25 corresponding lines) vulkano/src/command_buffer/auto/commands/pipeline.rs
Code Duplication · Edited copy of a member (27 corresponding lines) vulkano/src/pipeline/mod.rs
Code Duplication · Edited copy of a member (23 corresponding lines) vulkano/src/pipeline/shader/inout_interface.rs
Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) vulkano/src/sync/semaphore.rs
Code Duplication · Edited copies of one member (3 members, 40+ corresponding lines) vulkano/src/device/physical.rs
Code Duplication · Edited copy of a member (22 corresponding lines) vulkano/src/command_buffer/allocator.rs
Code Duplication · Edited copy of a member (27 corresponding lines) vulkano/src/device/private_data.rs
Code Duplication · Edited copy of a member (22 corresponding lines) vulkano/src/acceleration_structure.rs
Code Duplication · Edited copy of a member (18 corresponding lines) vulkano/src/buffer/mod.rs
Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) vulkano/src/image/sys.rs
Code Duplication · Edited copy of a member (25 corresponding lines) vulkano/src/display.rs
Code Duplication · Edited copy of a member (23 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs
Code Duplication · Edited copies of one member (4 members, 28+ corresponding lines) vulkano/src/command_buffer/commands/sync.rs
Code Duplication · Edited copy of a member (27 corresponding lines) vulkano-taskgraph/src/collector.rs
Code Duplication · Edited copy of a member (20 corresponding lines) vulkano/src/command_buffer/auto/commands/render_pass.rs
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 125 findings
These 125 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one. The first 100 are listed here.
Code Duplication · Near-duplicate member family (3 members, 251 shared lines) vulkano/src/command_buffer/commands/sync.rs
Code Duplication · Near-duplicate member family (3 members, 43 shared lines) vulkano/src/command_buffer/commands/copy.rs
Code Duplication · Near-duplicate member pair (92 shared lines) vulkano-taskgraph/src/graph/execute.rs
Code Duplication · Near-duplicate member pair (49 shared lines) vulkano/src/command_buffer/commands/clear.rs
Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) vulkano/src/device/physical.rs
€72,000 to €360,000, for 1,200 to 3,807 hours of work, about 1.5 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 165,588 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 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 6 points · Low effort · ADR Quality
2
Resolve the 153 Low coverage finding(s) in Code Coverage — start with mod.rs (23), lib.rs (4), pipeline.rs (4).
Raises the score by about 11 points · High effort · Code Coverage
3
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag.
Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Raises the score by about 8 points · Medium effort · Observability
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Files that change often carry extra risk · Combined risk
2 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (2 files) · Code Coverage (93 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: mod.rs and queue.rs
What to do: Add tests to these files and have a second person review every change to them, starting with mod.rs and queue.rs.
Where the investment is most exposed · Value at risk
This code would cost about €220,000 to build again, about 1.5 person-years of work. Its weakest lens is Production Readiness, at 52 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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 6.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 10% on every change. The history of the code shows how much it changes: about 13,251 lines over the last 90 days, which is about 53,740 lines a year. At that pace, the extra work comes to an estimated 5.9 to 35.7 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.
162 modules, with 971 dependencies between them. 6 loops run through 115 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 122 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.
vulkano.format uses vulkano.version, so a change to vulkano.version can break vulkano.format, while a change to vulkano.format can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→25 vulkano.format uses vulkano.instancepart of a loop✕
Connections
1 pair of types, where a type in vulkano.format uses a type in vulkano.instance.
vulkano.format uses vulkano.instance, so a change to vulkano.instance can break vulkano.format, while a change to vulkano.format can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→27 vulkano.format uses vulkano.device.physicalpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.format uses a type in vulkano.device.physical.
vulkano.format uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.format, while a change to vulkano.format can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→29 vulkano.format uses vulkano.devicepart of a loop✕
Connections
2 pairs of types, where a type in vulkano.format uses a type in vulkano.device.
vulkano.format uses vulkano.device, so a change to vulkano.device can break vulkano.format, while a change to vulkano.format can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→24 vulkano.image.layout uses vulkano.versionpart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.layout uses a type in vulkano.version.
vulkano.image.layout uses vulkano.version, so a change to vulkano.version can break vulkano.image.layout, while a change to vulkano.image.layout can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→25 vulkano.image.layout uses vulkano.instancepart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.layout uses a type in vulkano.instance.
vulkano.image.layout uses vulkano.instance, so a change to vulkano.instance can break vulkano.image.layout, while a change to vulkano.image.layout can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→27 vulkano.image.layout uses vulkano.device.physicalpart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.layout uses a type in vulkano.device.physical.
vulkano.image.layout uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.image.layout, while a change to vulkano.image.layout can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→29 vulkano.image.layout uses vulkano.devicepart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.layout uses a type in vulkano.device.
vulkano.image.layout uses vulkano.device, so a change to vulkano.device can break vulkano.image.layout, while a change to vulkano.image.layout can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→6 vulkano.image.sampler uses vulkano.image.viewpart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.sampler uses a type in vulkano.image.view.
vulkano.image.sampler uses vulkano.image.view, so a change to vulkano.image.view can break vulkano.image.sampler, while a change to vulkano.image.sampler can't break vulkano.image.view.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→24 vulkano.image.sampler uses vulkano.versionpart of a loop✕
Connections
6 pairs of types, where a type in vulkano.image.sampler uses a type in vulkano.version.
vulkano.image.sampler uses vulkano.version, so a change to vulkano.version can break vulkano.image.sampler, while a change to vulkano.image.sampler can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→25 vulkano.image.sampler uses vulkano.instancepart of a loop✕
Connections
7 pairs of types, where a type in vulkano.image.sampler uses a type in vulkano.instance.
vulkano.image.sampler uses vulkano.instance, so a change to vulkano.instance can break vulkano.image.sampler, while a change to vulkano.image.sampler can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→27 vulkano.image.sampler uses vulkano.device.physicalpart of a loop✕
Connections
6 pairs of types, where a type in vulkano.image.sampler uses a type in vulkano.device.physical.
vulkano.image.sampler uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.image.sampler, while a change to vulkano.image.sampler can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→29 vulkano.image.sampler uses vulkano.devicepart of a loop✕
Connections
11 pairs of types, where a type in vulkano.image.sampler uses a type in vulkano.device.
vulkano.image.sampler uses vulkano.device, so a change to vulkano.device can break vulkano.image.sampler, while a change to vulkano.image.sampler can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→34 vulkano.image.sampler uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.image.sampler uses a type in vulkano.
vulkano.image.sampler uses vulkano, so a change to vulkano can break vulkano.image.sampler, while a change to vulkano.image.sampler can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→23 vulkano.memory.alignment uses vulkano.displaypart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory.alignment uses a type in vulkano.display.
vulkano.memory.alignment uses vulkano.display, so a change to vulkano.display can break vulkano.memory.alignment, while a change to vulkano.memory.alignment can't break vulkano.display.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.image.view uses vulkano.format, so a change to vulkano.format can break vulkano.image.view, while a change to vulkano.image.view can't break vulkano.format.
Position
Below the diagonal: vulkano.image.view uses a module listed above it, which is the healthy direction.
vulkano.image.view uses vulkano.image.sampler, so a change to vulkano.image.sampler can break vulkano.image.view, while a change to vulkano.image.view can't break vulkano.image.sampler.
Position
Below the diagonal: vulkano.image.view uses a module listed above it, which is the healthy direction.
6→20 vulkano.image.view uses vulkano.imagepart of a loop✕
Connections
6 pairs of types, where a type in vulkano.image.view uses a type in vulkano.image.
vulkano.image.view uses vulkano.image, so a change to vulkano.image can break vulkano.image.view, while a change to vulkano.image.view can't break vulkano.image.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→24 vulkano.image.view uses vulkano.versionpart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.view uses a type in vulkano.version.
vulkano.image.view uses vulkano.version, so a change to vulkano.version can break vulkano.image.view, while a change to vulkano.image.view can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→25 vulkano.image.view uses vulkano.instancepart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.view uses a type in vulkano.instance.
vulkano.image.view uses vulkano.instance, so a change to vulkano.instance can break vulkano.image.view, while a change to vulkano.image.view can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→27 vulkano.image.view uses vulkano.device.physicalpart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.view uses a type in vulkano.device.physical.
vulkano.image.view uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.image.view, while a change to vulkano.image.view can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→29 vulkano.image.view uses vulkano.devicepart of a loop✕
Connections
5 pairs of types, where a type in vulkano.image.view uses a type in vulkano.device.
vulkano.image.view uses vulkano.device, so a change to vulkano.device can break vulkano.image.view, while a change to vulkano.image.view can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→34 vulkano.image.view uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.image.view uses a type in vulkano.
vulkano.memory.allocator.suballocator uses vulkano.memory.alignment, so a change to vulkano.memory.alignment can break vulkano.memory.allocator.suballocator, while a change to vulkano.memory.allocator.suballocator can't break vulkano.memory.alignment.
Position
Below the diagonal: vulkano.memory.allocator.suballocator uses a module listed above it, which is the healthy direction.
7→20 vulkano.memory.allocator.suballocator uses vulkano.imagepart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory.allocator.suballocator uses a type in vulkano.image.
vulkano.memory.allocator.suballocator uses vulkano.image, so a change to vulkano.image can break vulkano.memory.allocator.suballocator, while a change to vulkano.memory.allocator.suballocator can't break vulkano.image.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→23 vulkano.memory.allocator.suballocator uses vulkano.displaypart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory.allocator.suballocator uses a type in vulkano.display.
vulkano.memory.allocator.suballocator uses vulkano.display, so a change to vulkano.display can break vulkano.memory.allocator.suballocator, while a change to vulkano.memory.allocator.suballocator can't break vulkano.display.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→30 vulkano.memory.allocator.suballocator uses vulkano.buffer.allocatorpart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory.allocator.suballocator uses a type in vulkano.buffer.allocator.
vulkano.memory.allocator.suballocator uses vulkano.buffer.allocator, so a change to vulkano.buffer.allocator can break vulkano.memory.allocator.suballocator, while a change to vulkano.memory.allocator.suballocator can't break vulkano.buffer.allocator.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.memory.device_memory uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.memory.device_memory, while a change to vulkano.memory.device_memory can't break vulkano.range_map.
Position
Below the diagonal: vulkano.memory.device_memory uses a module listed above it, which is the healthy direction.
vulkano.memory.device_memory uses vulkano.memory.alignment, so a change to vulkano.memory.alignment can break vulkano.memory.device_memory, while a change to vulkano.memory.device_memory can't break vulkano.memory.alignment.
Position
Below the diagonal: vulkano.memory.device_memory uses a module listed above it, which is the healthy direction.
8→11 vulkano.memory.device_memory uses vulkano.memorypart of a loop✕
Connections
2 pairs of types, where a type in vulkano.memory.device_memory uses a type in vulkano.memory.
vulkano.memory.device_memory uses vulkano.memory, so a change to vulkano.memory can break vulkano.memory.device_memory, while a change to vulkano.memory.device_memory can't break vulkano.memory.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→24 vulkano.memory.device_memory uses vulkano.versionpart of a loop✕
Connections
4 pairs of types, where a type in vulkano.memory.device_memory uses a type in vulkano.version.
vulkano.memory.device_memory uses vulkano.version, so a change to vulkano.version can break vulkano.memory.device_memory, while a change to vulkano.memory.device_memory can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→25 vulkano.memory.device_memory uses vulkano.instancepart of a loop✕
Connections
5 pairs of types, where a type in vulkano.memory.device_memory uses a type in vulkano.instance.
vulkano.memory.device_memory uses vulkano.instance, so a change to vulkano.instance can break vulkano.memory.device_memory, while a change to vulkano.memory.device_memory can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→27 vulkano.memory.device_memory uses vulkano.device.physicalpart of a loop✕
Connections
4 pairs of types, where a type in vulkano.memory.device_memory uses a type in vulkano.device.physical.
vulkano.memory.device_memory uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.memory.device_memory, while a change to vulkano.memory.device_memory can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→29 vulkano.memory.device_memory uses vulkano.devicepart of a loop✕
Connections
10 pairs of types, where a type in vulkano.memory.device_memory uses a type in vulkano.device.
vulkano.memory.device_memory uses vulkano.device, so a change to vulkano.device can break vulkano.memory.device_memory, while a change to vulkano.memory.device_memory can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→34 vulkano.memory.device_memory uses vulkanopart of a loop✕
Connections
5 pairs of types, where a type in vulkano.memory.device_memory uses a type in vulkano.
vulkano.memory.device_memory uses vulkano, so a change to vulkano can break vulkano.memory.device_memory, while a change to vulkano.memory.device_memory can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.memory.allocator uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.range_map.
Position
Below the diagonal: vulkano.memory.allocator uses a module listed above it, which is the healthy direction.
vulkano.memory.allocator uses vulkano.memory.alignment, so a change to vulkano.memory.alignment can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.memory.alignment.
Position
Below the diagonal: vulkano.memory.allocator uses a module listed above it, which is the healthy direction.
vulkano.memory.allocator uses vulkano.memory.allocator.suballocator, so a change to vulkano.memory.allocator.suballocator can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.memory.allocator.suballocator.
Position
Below the diagonal: vulkano.memory.allocator uses a module listed above it, which is the healthy direction.
vulkano.memory.allocator uses vulkano.memory.device_memory, so a change to vulkano.memory.device_memory can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.memory.device_memory.
Position
Below the diagonal: vulkano.memory.allocator uses a module listed above it, which is the healthy direction.
9→11 vulkano.memory.allocator uses vulkano.memorypart of a loop✕
Connections
6 pairs of types, where a type in vulkano.memory.allocator uses a type in vulkano.memory.
vulkano.memory.allocator uses vulkano.memory, so a change to vulkano.memory can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.memory.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→23 vulkano.memory.allocator uses vulkano.displaypart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory.allocator uses a type in vulkano.display.
vulkano.memory.allocator uses vulkano.display, so a change to vulkano.display can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.display.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→25 vulkano.memory.allocator uses vulkano.instancepart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory.allocator uses a type in vulkano.instance.
vulkano.memory.allocator uses vulkano.instance, so a change to vulkano.instance can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→29 vulkano.memory.allocator uses vulkano.devicepart of a loop✕
Connections
3 pairs of types, where a type in vulkano.memory.allocator uses a type in vulkano.device.
vulkano.memory.allocator uses vulkano.device, so a change to vulkano.device can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→30 vulkano.memory.allocator uses vulkano.buffer.allocatorpart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory.allocator uses a type in vulkano.buffer.allocator.
vulkano.memory.allocator uses vulkano.buffer.allocator, so a change to vulkano.buffer.allocator can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.buffer.allocator.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→34 vulkano.memory.allocator uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.memory.allocator uses a type in vulkano.
vulkano.memory.allocator uses vulkano, so a change to vulkano can break vulkano.memory.allocator, while a change to vulkano.memory.allocator can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.shader uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.shader, while a change to vulkano.shader can't break vulkano.range_map.
Position
Below the diagonal: vulkano.shader uses a module listed above it, which is the healthy direction.
vulkano.shader uses vulkano.format, so a change to vulkano.format can break vulkano.shader, while a change to vulkano.shader can't break vulkano.format.
Position
Below the diagonal: vulkano.shader uses a module listed above it, which is the healthy direction.
vulkano.shader uses vulkano.image.view, so a change to vulkano.image.view can break vulkano.shader, while a change to vulkano.shader can't break vulkano.image.view.
Position
Below the diagonal: vulkano.shader uses a module listed above it, which is the healthy direction.
10→24 vulkano.shader uses vulkano.versionpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.shader uses a type in vulkano.version.
vulkano.shader uses vulkano.version, so a change to vulkano.version can break vulkano.shader, while a change to vulkano.shader can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→25 vulkano.shader uses vulkano.instancepart of a loop✕
Connections
3 pairs of types, where a type in vulkano.shader uses a type in vulkano.instance.
vulkano.shader uses vulkano.instance, so a change to vulkano.instance can break vulkano.shader, while a change to vulkano.shader can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→27 vulkano.shader uses vulkano.device.physicalpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.shader uses a type in vulkano.device.physical.
vulkano.shader uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.shader, while a change to vulkano.shader can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→28 vulkano.shader uses vulkano.descriptor_set.layoutpart of a loop✕
Connections
1 pair of types, where a type in vulkano.shader uses a type in vulkano.descriptor_set.layout.
vulkano.shader uses vulkano.descriptor_set.layout, so a change to vulkano.descriptor_set.layout can break vulkano.shader, while a change to vulkano.shader can't break vulkano.descriptor_set.layout.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→29 vulkano.shader uses vulkano.devicepart of a loop✕
Connections
7 pairs of types, where a type in vulkano.shader uses a type in vulkano.device.
vulkano.shader uses vulkano.device, so a change to vulkano.device can break vulkano.shader, while a change to vulkano.shader can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.memory uses vulkano.memory.alignment, so a change to vulkano.memory.alignment can break vulkano.memory, while a change to vulkano.memory can't break vulkano.memory.alignment.
Position
Below the diagonal: vulkano.memory uses a module listed above it, which is the healthy direction.
vulkano.memory uses vulkano.memory.allocator.suballocator, so a change to vulkano.memory.allocator.suballocator can break vulkano.memory, while a change to vulkano.memory can't break vulkano.memory.allocator.suballocator.
Position
Below the diagonal: vulkano.memory uses a module listed above it, which is the healthy direction.
vulkano.memory uses vulkano.memory.device_memory, so a change to vulkano.memory.device_memory can break vulkano.memory, while a change to vulkano.memory can't break vulkano.memory.device_memory.
Position
Below the diagonal: vulkano.memory uses a module listed above it, which is the healthy direction.
vulkano.memory uses vulkano.memory.allocator, so a change to vulkano.memory.allocator can break vulkano.memory, while a change to vulkano.memory can't break vulkano.memory.allocator.
Position
Below the diagonal: vulkano.memory uses a module listed above it, which is the healthy direction.
11→20 vulkano.memory uses vulkano.imagepart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory uses a type in vulkano.image.
vulkano.memory uses vulkano.version, so a change to vulkano.version can break vulkano.memory, while a change to vulkano.memory can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→25 vulkano.memory uses vulkano.instancepart of a loop✕
Connections
2 pairs of types, where a type in vulkano.memory uses a type in vulkano.instance.
vulkano.memory uses vulkano.instance, so a change to vulkano.instance can break vulkano.memory, while a change to vulkano.memory can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→27 vulkano.memory uses vulkano.device.physicalpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.memory uses a type in vulkano.device.physical.
vulkano.memory uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.memory, while a change to vulkano.memory can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→29 vulkano.memory uses vulkano.devicepart of a loop✕
Connections
5 pairs of types, where a type in vulkano.memory uses a type in vulkano.device.
vulkano.memory uses vulkano.device, so a change to vulkano.device can break vulkano.memory, while a change to vulkano.memory can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→30 vulkano.memory uses vulkano.buffer.allocatorpart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory uses a type in vulkano.buffer.allocator.
vulkano.memory uses vulkano.buffer.allocator, so a change to vulkano.buffer.allocator can break vulkano.memory, while a change to vulkano.memory can't break vulkano.buffer.allocator.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→33 vulkano.memory uses vulkano.bufferpart of a loop✕
Connections
1 pair of types, where a type in vulkano.memory uses a type in vulkano.buffer.
vulkano.memory uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.memory, while a change to vulkano.memory can't break vulkano.buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.pipeline.graphics uses vulkano.shader, so a change to vulkano.shader can break vulkano.pipeline.graphics, while a change to vulkano.pipeline.graphics can't break vulkano.shader.
Position
Below the diagonal: vulkano.pipeline.graphics uses a module listed above it, which is the healthy direction.
12→15 vulkano.pipeline.graphics uses vulkano.pipelinepart of a loop✕
Connections
4 pairs of types, where a type in vulkano.pipeline.graphics uses a type in vulkano.pipeline.
vulkano.pipeline.graphics uses vulkano.pipeline, so a change to vulkano.pipeline can break vulkano.pipeline.graphics, while a change to vulkano.pipeline.graphics can't break vulkano.pipeline.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→25 vulkano.pipeline.graphics uses vulkano.instancepart of a loop✕
Connections
1 pair of types, where a type in vulkano.pipeline.graphics uses a type in vulkano.instance.
vulkano.pipeline.graphics uses vulkano.instance, so a change to vulkano.instance can break vulkano.pipeline.graphics, while a change to vulkano.pipeline.graphics can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→29 vulkano.pipeline.graphics uses vulkano.devicepart of a loop✕
Connections
4 pairs of types, where a type in vulkano.pipeline.graphics uses a type in vulkano.device.
vulkano.pipeline.graphics uses vulkano.device, so a change to vulkano.device can break vulkano.pipeline.graphics, while a change to vulkano.pipeline.graphics can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→34 vulkano.pipeline.graphics uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.pipeline.graphics uses a type in vulkano.
vulkano.pipeline.graphics uses vulkano, so a change to vulkano can break vulkano.pipeline.graphics, while a change to vulkano.pipeline.graphics can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.sync.pipeline uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.range_map.
Position
Below the diagonal: vulkano.sync.pipeline uses a module listed above it, which is the healthy direction.
vulkano.sync.pipeline uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.image.layout.
Position
Below the diagonal: vulkano.sync.pipeline uses a module listed above it, which is the healthy direction.
vulkano.sync.pipeline uses vulkano.shader, so a change to vulkano.shader can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.shader.
Position
Below the diagonal: vulkano.sync.pipeline uses a module listed above it, which is the healthy direction.
13→20 vulkano.sync.pipeline uses vulkano.imagepart of a loop✕
Connections
2 pairs of types, where a type in vulkano.sync.pipeline uses a type in vulkano.image.
vulkano.sync.pipeline uses vulkano.image, so a change to vulkano.image can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.image.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→24 vulkano.sync.pipeline uses vulkano.versionpart of a loop✕
Connections
4 pairs of types, where a type in vulkano.sync.pipeline uses a type in vulkano.version.
vulkano.sync.pipeline uses vulkano.version, so a change to vulkano.version can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→25 vulkano.sync.pipeline uses vulkano.instancepart of a loop✕
Connections
4 pairs of types, where a type in vulkano.sync.pipeline uses a type in vulkano.instance.
vulkano.sync.pipeline uses vulkano.instance, so a change to vulkano.instance can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→26 vulkano.sync.pipeline uses vulkano.device.queuepart of a loop✕
Connections
1 pair of types, where a type in vulkano.sync.pipeline uses a type in vulkano.device.queue.
vulkano.sync.pipeline uses vulkano.device.queue, so a change to vulkano.device.queue can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.device.queue.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→27 vulkano.sync.pipeline uses vulkano.device.physicalpart of a loop✕
Connections
4 pairs of types, where a type in vulkano.sync.pipeline uses a type in vulkano.device.physical.
vulkano.sync.pipeline uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→28 vulkano.sync.pipeline uses vulkano.descriptor_set.layoutpart of a loop✕
Connections
1 pair of types, where a type in vulkano.sync.pipeline uses a type in vulkano.descriptor_set.layout.
vulkano.sync.pipeline uses vulkano.descriptor_set.layout, so a change to vulkano.descriptor_set.layout can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.descriptor_set.layout.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→29 vulkano.sync.pipeline uses vulkano.devicepart of a loop✕
Connections
4 pairs of types, where a type in vulkano.sync.pipeline uses a type in vulkano.device.
vulkano.sync.pipeline uses vulkano.device, so a change to vulkano.device can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→33 vulkano.sync.pipeline uses vulkano.bufferpart of a loop✕
Connections
1 pair of types, where a type in vulkano.sync.pipeline uses a type in vulkano.buffer.
vulkano.sync.pipeline uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→34 vulkano.sync.pipeline uses vulkanopart of a loop✕
Connections
4 pairs of types, where a type in vulkano.sync.pipeline uses a type in vulkano.
vulkano.sync.pipeline uses vulkano, so a change to vulkano can break vulkano.sync.pipeline, while a change to vulkano.sync.pipeline can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.image.sys uses vulkano.format, so a change to vulkano.format can break vulkano.image.sys, while a change to vulkano.image.sys can't break vulkano.format.
Position
Below the diagonal: vulkano.image.sys uses a module listed above it, which is the healthy direction.
vulkano.image.sys uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano.image.sys, while a change to vulkano.image.sys can't break vulkano.image.layout.
Position
Below the diagonal: vulkano.image.sys uses a module listed above it, which is the healthy direction.
vulkano.image.sys uses vulkano.memory.device_memory, so a change to vulkano.memory.device_memory can break vulkano.image.sys, while a change to vulkano.image.sys can't break vulkano.memory.device_memory.
Position
Below the diagonal: vulkano.image.sys uses a module listed above it, which is the healthy direction.
vulkano.image.sys uses vulkano.memory, so a change to vulkano.memory can break vulkano.image.sys, while a change to vulkano.image.sys can't break vulkano.memory.
Position
Below the diagonal: vulkano.image.sys uses a module listed above it, which is the healthy direction.
14→20 vulkano.image.sys uses vulkano.imagepart of a loop✕
Connections
13 pairs of types, where a type in vulkano.image.sys uses a type in vulkano.image.
vulkano.image.sys uses vulkano.image, so a change to vulkano.image can break vulkano.image.sys, while a change to vulkano.image.sys can't break vulkano.image.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→25 vulkano.image.sys uses vulkano.instancepart of a loop✕
Connections
1 pair of types, where a type in vulkano.image.sys uses a type in vulkano.instance.
vulkano.image.sys uses vulkano.instance, so a change to vulkano.instance can break vulkano.image.sys, while a change to vulkano.image.sys can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→29 vulkano.image.sys uses vulkano.devicepart of a loop✕
Connections
3 pairs of types, where a type in vulkano.image.sys uses a type in vulkano.device.
vulkano.image.sys uses vulkano.device, so a change to vulkano.device can break vulkano.image.sys, while a change to vulkano.image.sys can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→34 vulkano.image.sys uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.image.sys uses a type in vulkano.
vulkano.pipeline uses vulkano.shader, so a change to vulkano.shader can break vulkano.pipeline, while a change to vulkano.pipeline can't break vulkano.shader.
Position
Below the diagonal: vulkano.pipeline uses a module listed above it, which is the healthy direction.
vulkano.pipeline uses vulkano.pipeline.graphics, so a change to vulkano.pipeline.graphics can break vulkano.pipeline, while a change to vulkano.pipeline can't break vulkano.pipeline.graphics.
Position
Below the diagonal: vulkano.pipeline uses a module listed above it, which is the healthy direction.
15→24 vulkano.pipeline uses vulkano.versionpart of a loop✕
Connections
3 pairs of types, where a type in vulkano.pipeline uses a type in vulkano.version.
vulkano.pipeline uses vulkano.version, so a change to vulkano.version can break vulkano.pipeline, while a change to vulkano.pipeline can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→25 vulkano.pipeline uses vulkano.instancepart of a loop✕
Connections
3 pairs of types, where a type in vulkano.pipeline uses a type in vulkano.instance.
vulkano.pipeline uses vulkano.instance, so a change to vulkano.instance can break vulkano.pipeline, while a change to vulkano.pipeline can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→27 vulkano.pipeline uses vulkano.device.physicalpart of a loop✕
Connections
3 pairs of types, where a type in vulkano.pipeline uses a type in vulkano.device.physical.
vulkano.pipeline uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.pipeline, while a change to vulkano.pipeline can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→29 vulkano.pipeline uses vulkano.devicepart of a loop✕
Connections
5 pairs of types, where a type in vulkano.pipeline uses a type in vulkano.device.
vulkano.pipeline uses vulkano.device, so a change to vulkano.device can break vulkano.pipeline, while a change to vulkano.pipeline can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→34 vulkano.pipeline uses vulkanopart of a loop✕
Connections
1 pair of types, where a type in vulkano.pipeline uses a type in vulkano.
The types involved
vulkano.pipeline.Pipeline → vulkano.VulkanObject
Direction
vulkano.pipeline uses vulkano, so a change to vulkano can break vulkano.pipeline, while a change to vulkano.pipeline can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.render_pass uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.range_map.
Position
Below the diagonal: vulkano.render_pass uses a module listed above it, which is the healthy direction.
vulkano.render_pass uses vulkano.format, so a change to vulkano.format can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.format.
Position
Below the diagonal: vulkano.render_pass uses a module listed above it, which is the healthy direction.
vulkano.render_pass uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.image.layout.
Position
Below the diagonal: vulkano.render_pass uses a module listed above it, which is the healthy direction.
vulkano.render_pass uses vulkano.sync.pipeline, so a change to vulkano.sync.pipeline can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.sync.pipeline.
Position
Below the diagonal: vulkano.render_pass uses a module listed above it, which is the healthy direction.
16→20 vulkano.render_pass uses vulkano.imagepart of a loop✕
Connections
2 pairs of types, where a type in vulkano.render_pass uses a type in vulkano.image.
vulkano.render_pass uses vulkano.image, so a change to vulkano.image can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.image.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→24 vulkano.render_pass uses vulkano.versionpart of a loop✕
Connections
7 pairs of types, where a type in vulkano.render_pass uses a type in vulkano.version.
vulkano.render_pass uses vulkano.version, so a change to vulkano.version can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→25 vulkano.render_pass uses vulkano.instancepart of a loop✕
Connections
8 pairs of types, where a type in vulkano.render_pass uses a type in vulkano.instance.
vulkano.render_pass uses vulkano.instance, so a change to vulkano.instance can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→27 vulkano.render_pass uses vulkano.device.physicalpart of a loop✕
Connections
7 pairs of types, where a type in vulkano.render_pass uses a type in vulkano.device.physical.
vulkano.render_pass uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→29 vulkano.render_pass uses vulkano.devicepart of a loop✕
Connections
14 pairs of types, where a type in vulkano.render_pass uses a type in vulkano.device.
vulkano.render_pass uses vulkano.device, so a change to vulkano.device can break vulkano.render_pass, while a change to vulkano.render_pass can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→34 vulkano.render_pass uses vulkanopart of a loop✕
Connections
6 pairs of types, where a type in vulkano.render_pass uses a type in vulkano.
vulkano.command_buffer.sys uses vulkano.sync.pipeline, so a change to vulkano.sync.pipeline can break vulkano.command_buffer.sys, while a change to vulkano.command_buffer.sys can't break vulkano.sync.pipeline.
Position
Below the diagonal: vulkano.command_buffer.sys uses a module listed above it, which is the healthy direction.
vulkano.command_buffer.sys uses vulkano.pipeline, so a change to vulkano.pipeline can break vulkano.command_buffer.sys, while a change to vulkano.command_buffer.sys can't break vulkano.pipeline.
Position
Below the diagonal: vulkano.command_buffer.sys uses a module listed above it, which is the healthy direction.
17→18 vulkano.command_buffer.sys uses vulkano.command_bufferpart of a loop✕
Connections
11 pairs of types, where a type in vulkano.command_buffer.sys uses a type in vulkano.command_buffer.
vulkano.command_buffer.sys uses vulkano.command_buffer, so a change to vulkano.command_buffer can break vulkano.command_buffer.sys, while a change to vulkano.command_buffer.sys can't break vulkano.command_buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→26 vulkano.command_buffer.sys uses vulkano.device.queuepart of a loop✕
Connections
1 pair of types, where a type in vulkano.command_buffer.sys uses a type in vulkano.device.queue.
vulkano.command_buffer.sys uses vulkano.device.queue, so a change to vulkano.device.queue can break vulkano.command_buffer.sys, while a change to vulkano.command_buffer.sys can't break vulkano.device.queue.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→29 vulkano.command_buffer.sys uses vulkano.devicepart of a loop✕
Connections
5 pairs of types, where a type in vulkano.command_buffer.sys uses a type in vulkano.device.
vulkano.command_buffer.sys uses vulkano.device, so a change to vulkano.device can break vulkano.command_buffer.sys, while a change to vulkano.command_buffer.sys can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→33 vulkano.command_buffer.sys uses vulkano.bufferpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.command_buffer.sys uses a type in vulkano.buffer.
vulkano.command_buffer.sys uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.command_buffer.sys, while a change to vulkano.command_buffer.sys can't break vulkano.buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→34 vulkano.command_buffer.sys uses vulkanopart of a loop✕
Connections
3 pairs of types, where a type in vulkano.command_buffer.sys uses a type in vulkano.
vulkano.command_buffer.sys uses vulkano, so a change to vulkano can break vulkano.command_buffer.sys, while a change to vulkano.command_buffer.sys can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.command_buffer uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.range_map.
Position
Below the diagonal: vulkano.command_buffer uses a module listed above it, which is the healthy direction.
vulkano.command_buffer uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.image.layout.
Position
Below the diagonal: vulkano.command_buffer uses a module listed above it, which is the healthy direction.
vulkano.command_buffer uses vulkano.sync.pipeline, so a change to vulkano.sync.pipeline can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.sync.pipeline.
Position
Below the diagonal: vulkano.command_buffer uses a module listed above it, which is the healthy direction.
vulkano.command_buffer uses vulkano.render_pass, so a change to vulkano.render_pass can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.render_pass.
Position
Below the diagonal: vulkano.command_buffer uses a module listed above it, which is the healthy direction.
vulkano.command_buffer uses vulkano.command_buffer.sys, so a change to vulkano.command_buffer.sys can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.command_buffer.sys.
Position
Below the diagonal: vulkano.command_buffer uses a module listed above it, which is the healthy direction.
18→20 vulkano.command_buffer uses vulkano.imagepart of a loop✕
Connections
4 pairs of types, where a type in vulkano.command_buffer uses a type in vulkano.image.
vulkano.command_buffer uses vulkano.image, so a change to vulkano.image can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.image.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→24 vulkano.command_buffer uses vulkano.versionpart of a loop✕
Connections
1 pair of types, where a type in vulkano.command_buffer uses a type in vulkano.version.
vulkano.command_buffer uses vulkano.version, so a change to vulkano.version can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→25 vulkano.command_buffer uses vulkano.instancepart of a loop✕
Connections
1 pair of types, where a type in vulkano.command_buffer uses a type in vulkano.instance.
vulkano.command_buffer uses vulkano.instance, so a change to vulkano.instance can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→27 vulkano.command_buffer uses vulkano.device.physicalpart of a loop✕
Connections
1 pair of types, where a type in vulkano.command_buffer uses a type in vulkano.device.physical.
vulkano.command_buffer uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→29 vulkano.command_buffer uses vulkano.devicepart of a loop✕
Connections
7 pairs of types, where a type in vulkano.command_buffer uses a type in vulkano.device.
vulkano.command_buffer uses vulkano.device, so a change to vulkano.device can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→32 vulkano.command_buffer uses vulkano.buffer.subbufferpart of a loop✕
Connections
1 pair of types, where a type in vulkano.command_buffer uses a type in vulkano.buffer.subbuffer.
vulkano.command_buffer uses vulkano.buffer.subbuffer, so a change to vulkano.buffer.subbuffer can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.buffer.subbuffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→33 vulkano.command_buffer uses vulkano.bufferpart of a loop✕
Connections
1 pair of types, where a type in vulkano.command_buffer uses a type in vulkano.buffer.
vulkano.command_buffer uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→34 vulkano.command_buffer uses vulkanopart of a loop✕
Connections
4 pairs of types, where a type in vulkano.command_buffer uses a type in vulkano.
vulkano.command_buffer uses vulkano, so a change to vulkano can break vulkano.command_buffer, while a change to vulkano.command_buffer can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.command_buffer.auto.builder uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.image.layout.
Position
Below the diagonal: vulkano.command_buffer.auto.builder uses a module listed above it, which is the healthy direction.
vulkano.command_buffer.auto.builder uses vulkano.image.view, so a change to vulkano.image.view can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.image.view.
Position
Below the diagonal: vulkano.command_buffer.auto.builder uses a module listed above it, which is the healthy direction.
vulkano.command_buffer.auto.builder uses vulkano.pipeline.graphics, so a change to vulkano.pipeline.graphics can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.pipeline.graphics.
Position
Below the diagonal: vulkano.command_buffer.auto.builder uses a module listed above it, which is the healthy direction.
vulkano.command_buffer.auto.builder uses vulkano.sync.pipeline, so a change to vulkano.sync.pipeline can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.sync.pipeline.
Position
Below the diagonal: vulkano.command_buffer.auto.builder uses a module listed above it, which is the healthy direction.
vulkano.command_buffer.auto.builder uses vulkano.pipeline, so a change to vulkano.pipeline can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.pipeline.
Position
Below the diagonal: vulkano.command_buffer.auto.builder uses a module listed above it, which is the healthy direction.
vulkano.command_buffer.auto.builder uses vulkano.render_pass, so a change to vulkano.render_pass can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.render_pass.
Position
Below the diagonal: vulkano.command_buffer.auto.builder uses a module listed above it, which is the healthy direction.
vulkano.command_buffer.auto.builder uses vulkano.command_buffer.sys, so a change to vulkano.command_buffer.sys can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.command_buffer.sys.
Position
Below the diagonal: vulkano.command_buffer.auto.builder uses a module listed above it, which is the healthy direction.
vulkano.command_buffer.auto.builder uses vulkano.command_buffer, so a change to vulkano.command_buffer can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.command_buffer.
Position
Below the diagonal: vulkano.command_buffer.auto.builder uses a module listed above it, which is the healthy direction.
19→20 vulkano.command_buffer.auto.builder uses vulkano.imagepart of a loop✕
Connections
2 pairs of types, where a type in vulkano.command_buffer.auto.builder uses a type in vulkano.image.
vulkano.command_buffer.auto.builder uses vulkano.image, so a change to vulkano.image can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.image.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→29 vulkano.command_buffer.auto.builder uses vulkano.devicepart of a loop✕
Connections
3 pairs of types, where a type in vulkano.command_buffer.auto.builder uses a type in vulkano.device.
vulkano.command_buffer.auto.builder uses vulkano.device, so a change to vulkano.device can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→32 vulkano.command_buffer.auto.builder uses vulkano.buffer.subbufferpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.command_buffer.auto.builder uses a type in vulkano.buffer.subbuffer.
vulkano.command_buffer.auto.builder uses vulkano.buffer.subbuffer, so a change to vulkano.buffer.subbuffer can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.buffer.subbuffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→33 vulkano.command_buffer.auto.builder uses vulkano.bufferpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.command_buffer.auto.builder uses a type in vulkano.buffer.
vulkano.command_buffer.auto.builder uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.command_buffer.auto.builder, while a change to vulkano.command_buffer.auto.builder can't break vulkano.buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.image uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.image, while a change to vulkano.image can't break vulkano.range_map.
Position
Below the diagonal: vulkano.image uses a module listed above it, which is the healthy direction.
vulkano.image uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano.image, while a change to vulkano.image can't break vulkano.image.layout.
Position
Below the diagonal: vulkano.image uses a module listed above it, which is the healthy direction.
vulkano.image uses vulkano.image.view, so a change to vulkano.image.view can break vulkano.image, while a change to vulkano.image can't break vulkano.image.view.
Position
Below the diagonal: vulkano.image uses a module listed above it, which is the healthy direction.
vulkano.image uses vulkano.memory.device_memory, so a change to vulkano.memory.device_memory can break vulkano.image, while a change to vulkano.image can't break vulkano.memory.device_memory.
Position
Below the diagonal: vulkano.image uses a module listed above it, which is the healthy direction.
vulkano.image uses vulkano.memory.allocator, so a change to vulkano.memory.allocator can break vulkano.image, while a change to vulkano.image can't break vulkano.memory.allocator.
Position
Below the diagonal: vulkano.image uses a module listed above it, which is the healthy direction.
vulkano.image uses vulkano.image.sys, so a change to vulkano.image.sys can break vulkano.image, while a change to vulkano.image can't break vulkano.image.sys.
Position
Below the diagonal: vulkano.image uses a module listed above it, which is the healthy direction.
vulkano.image uses vulkano.command_buffer.auto.builder, so a change to vulkano.command_buffer.auto.builder can break vulkano.image, while a change to vulkano.image can't break vulkano.command_buffer.auto.builder.
Position
Below the diagonal: vulkano.image uses a module listed above it, which is the healthy direction.
20→21 vulkano.image uses vulkano.swapchainpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.image uses a type in vulkano.swapchain.
vulkano.image uses vulkano.swapchain, so a change to vulkano.swapchain can break vulkano.image, while a change to vulkano.image can't break vulkano.swapchain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→23 vulkano.image uses vulkano.displaypart of a loop✕
Connections
1 pair of types, where a type in vulkano.image uses a type in vulkano.display.
vulkano.image uses vulkano.display, so a change to vulkano.display can break vulkano.image, while a change to vulkano.image can't break vulkano.display.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→24 vulkano.image uses vulkano.versionpart of a loop✕
Connections
6 pairs of types, where a type in vulkano.image uses a type in vulkano.version.
vulkano.image uses vulkano.version, so a change to vulkano.version can break vulkano.image, while a change to vulkano.image can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→25 vulkano.image uses vulkano.instancepart of a loop✕
Connections
6 pairs of types, where a type in vulkano.image uses a type in vulkano.instance.
vulkano.image uses vulkano.instance, so a change to vulkano.instance can break vulkano.image, while a change to vulkano.image can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→27 vulkano.image uses vulkano.device.physicalpart of a loop✕
Connections
9 pairs of types, where a type in vulkano.image uses a type in vulkano.device.physical.
vulkano.image uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.image, while a change to vulkano.image can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→29 vulkano.image uses vulkano.devicepart of a loop✕
Connections
10 pairs of types, where a type in vulkano.image uses a type in vulkano.device.
vulkano.swapchain uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.swapchain, while a change to vulkano.swapchain can't break vulkano.range_map.
Position
Below the diagonal: vulkano.swapchain uses a module listed above it, which is the healthy direction.
vulkano.swapchain uses vulkano.image, so a change to vulkano.image can break vulkano.swapchain, while a change to vulkano.swapchain can't break vulkano.image.
Position
Below the diagonal: vulkano.swapchain uses a module listed above it, which is the healthy direction.
21→22 vulkano.swapchain uses vulkano.swapchain.surfacepart of a loop✕
Connections
9 pairs of types, where a type in vulkano.swapchain uses a type in vulkano.swapchain.surface.
vulkano.swapchain uses vulkano.swapchain.surface, so a change to vulkano.swapchain.surface can break vulkano.swapchain, while a change to vulkano.swapchain can't break vulkano.swapchain.surface.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→24 vulkano.swapchain uses vulkano.versionpart of a loop✕
Connections
6 pairs of types, where a type in vulkano.swapchain uses a type in vulkano.version.
vulkano.swapchain uses vulkano.version, so a change to vulkano.version can break vulkano.swapchain, while a change to vulkano.swapchain can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→25 vulkano.swapchain uses vulkano.instancepart of a loop✕
Connections
7 pairs of types, where a type in vulkano.swapchain uses a type in vulkano.instance.
vulkano.swapchain uses vulkano.instance, so a change to vulkano.instance can break vulkano.swapchain, while a change to vulkano.swapchain can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→27 vulkano.swapchain uses vulkano.device.physicalpart of a loop✕
Connections
6 pairs of types, where a type in vulkano.swapchain uses a type in vulkano.device.physical.
vulkano.swapchain uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.swapchain, while a change to vulkano.swapchain can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→29 vulkano.swapchain uses vulkano.devicepart of a loop✕
Connections
9 pairs of types, where a type in vulkano.swapchain uses a type in vulkano.device.
vulkano.swapchain uses vulkano.device, so a change to vulkano.device can break vulkano.swapchain, while a change to vulkano.swapchain can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→34 vulkano.swapchain uses vulkanopart of a loop✕
Connections
3 pairs of types, where a type in vulkano.swapchain uses a type in vulkano.
vulkano.swapchain.surface uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.swapchain.surface, while a change to vulkano.swapchain.surface can't break vulkano.range_map.
Position
Below the diagonal: vulkano.swapchain.surface uses a module listed above it, which is the healthy direction.
vulkano.swapchain.surface uses vulkano.swapchain, so a change to vulkano.swapchain can break vulkano.swapchain.surface, while a change to vulkano.swapchain.surface can't break vulkano.swapchain.
Position
Below the diagonal: vulkano.swapchain.surface uses a module listed above it, which is the healthy direction.
22→23 vulkano.swapchain.surface uses vulkano.displaypart of a loop✕
Connections
3 pairs of types, where a type in vulkano.swapchain.surface uses a type in vulkano.display.
vulkano.swapchain.surface uses vulkano.display, so a change to vulkano.display can break vulkano.swapchain.surface, while a change to vulkano.swapchain.surface can't break vulkano.display.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→24 vulkano.swapchain.surface uses vulkano.versionpart of a loop✕
Connections
6 pairs of types, where a type in vulkano.swapchain.surface uses a type in vulkano.version.
vulkano.swapchain.surface uses vulkano.version, so a change to vulkano.version can break vulkano.swapchain.surface, while a change to vulkano.swapchain.surface can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→25 vulkano.swapchain.surface uses vulkano.instancepart of a loop✕
Connections
8 pairs of types, where a type in vulkano.swapchain.surface uses a type in vulkano.instance.
vulkano.swapchain.surface uses vulkano.instance, so a change to vulkano.instance can break vulkano.swapchain.surface, while a change to vulkano.swapchain.surface can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→27 vulkano.swapchain.surface uses vulkano.device.physicalpart of a loop✕
Connections
9 pairs of types, where a type in vulkano.swapchain.surface uses a type in vulkano.device.physical.
vulkano.swapchain.surface uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.swapchain.surface, while a change to vulkano.swapchain.surface can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→29 vulkano.swapchain.surface uses vulkano.devicepart of a loop✕
Connections
6 pairs of types, where a type in vulkano.swapchain.surface uses a type in vulkano.device.
vulkano.swapchain.surface uses vulkano.device, so a change to vulkano.device can break vulkano.swapchain.surface, while a change to vulkano.swapchain.surface can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→34 vulkano.swapchain.surface uses vulkanopart of a loop✕
Connections
4 pairs of types, where a type in vulkano.swapchain.surface uses a type in vulkano.
vulkano.swapchain.surface uses vulkano, so a change to vulkano can break vulkano.swapchain.surface, while a change to vulkano.swapchain.surface can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.display uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.display, while a change to vulkano.display can't break vulkano.range_map.
Position
Below the diagonal: vulkano.display uses a module listed above it, which is the healthy direction.
vulkano.display uses vulkano.swapchain.surface, so a change to vulkano.swapchain.surface can break vulkano.display, while a change to vulkano.display can't break vulkano.swapchain.surface.
Position
Below the diagonal: vulkano.display uses a module listed above it, which is the healthy direction.
23→24 vulkano.display uses vulkano.versionpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.display uses a type in vulkano.version.
vulkano.display uses vulkano.version, so a change to vulkano.version can break vulkano.display, while a change to vulkano.display can't break vulkano.version.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→25 vulkano.display uses vulkano.instancepart of a loop✕
Connections
8 pairs of types, where a type in vulkano.display uses a type in vulkano.instance.
vulkano.display uses vulkano.instance, so a change to vulkano.instance can break vulkano.display, while a change to vulkano.display can't break vulkano.instance.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→27 vulkano.display uses vulkano.device.physicalpart of a loop✕
Connections
4 pairs of types, where a type in vulkano.display uses a type in vulkano.device.physical.
vulkano.display uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.display, while a change to vulkano.display can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→29 vulkano.display uses vulkano.devicepart of a loop✕
Connections
2 pairs of types, where a type in vulkano.display uses a type in vulkano.device.
vulkano.display uses vulkano.device, so a change to vulkano.device can break vulkano.display, while a change to vulkano.display can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in vulkano.version uses a type in vulkano.display.
The types involved
vulkano.version.Version → vulkano.display.Display
Direction
vulkano.version uses vulkano.display, so a change to vulkano.display can break vulkano.version, while a change to vulkano.version can't break vulkano.display.
Position
Below the diagonal: vulkano.version uses a module listed above it, which is the healthy direction.
vulkano.instance uses vulkano.version, so a change to vulkano.version can break vulkano.instance, while a change to vulkano.instance can't break vulkano.version.
Position
Below the diagonal: vulkano.instance uses a module listed above it, which is the healthy direction.
25→27 vulkano.instance uses vulkano.device.physicalpart of a loop✕
Connections
1 pair of types, where a type in vulkano.instance uses a type in vulkano.device.physical.
vulkano.instance uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.instance, while a change to vulkano.instance can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→29 vulkano.instance uses vulkano.devicepart of a loop✕
Connections
1 pair of types, where a type in vulkano.instance uses a type in vulkano.device.
vulkano.instance uses vulkano.device, so a change to vulkano.device can break vulkano.instance, while a change to vulkano.instance can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→34 vulkano.instance uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.instance uses a type in vulkano.
vulkano.device.queue uses vulkano.version, so a change to vulkano.version can break vulkano.device.queue, while a change to vulkano.device.queue can't break vulkano.version.
Position
Below the diagonal: vulkano.device.queue uses a module listed above it, which is the healthy direction.
vulkano.device.queue uses vulkano.instance, so a change to vulkano.instance can break vulkano.device.queue, while a change to vulkano.device.queue can't break vulkano.instance.
Position
Below the diagonal: vulkano.device.queue uses a module listed above it, which is the healthy direction.
26→27 vulkano.device.queue uses vulkano.device.physicalpart of a loop✕
Connections
1 pair of types, where a type in vulkano.device.queue uses a type in vulkano.device.physical.
vulkano.device.queue uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.device.queue, while a change to vulkano.device.queue can't break vulkano.device.physical.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→29 vulkano.device.queue uses vulkano.devicepart of a loop✕
Connections
5 pairs of types, where a type in vulkano.device.queue uses a type in vulkano.device.
vulkano.device.queue uses vulkano.device, so a change to vulkano.device can break vulkano.device.queue, while a change to vulkano.device.queue can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→34 vulkano.device.queue uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.device.queue uses a type in vulkano.
vulkano.device.physical uses vulkano.format, so a change to vulkano.format can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.format.
Position
Below the diagonal: vulkano.device.physical uses a module listed above it, which is the healthy direction.
vulkano.device.physical uses vulkano.memory, so a change to vulkano.memory can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.memory.
Position
Below the diagonal: vulkano.device.physical uses a module listed above it, which is the healthy direction.
vulkano.device.physical uses vulkano.image, so a change to vulkano.image can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.image.
Position
Below the diagonal: vulkano.device.physical uses a module listed above it, which is the healthy direction.
vulkano.device.physical uses vulkano.swapchain.surface, so a change to vulkano.swapchain.surface can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.swapchain.surface.
Position
Below the diagonal: vulkano.device.physical uses a module listed above it, which is the healthy direction.
vulkano.device.physical uses vulkano.display, so a change to vulkano.display can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.display.
Position
Below the diagonal: vulkano.device.physical uses a module listed above it, which is the healthy direction.
vulkano.device.physical uses vulkano.version, so a change to vulkano.version can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.version.
Position
Below the diagonal: vulkano.device.physical uses a module listed above it, which is the healthy direction.
vulkano.device.physical uses vulkano.instance, so a change to vulkano.instance can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.instance.
Position
Below the diagonal: vulkano.device.physical uses a module listed above it, which is the healthy direction.
vulkano.device.physical uses vulkano.device.queue, so a change to vulkano.device.queue can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.device.queue.
Position
Below the diagonal: vulkano.device.physical uses a module listed above it, which is the healthy direction.
27→29 vulkano.device.physical uses vulkano.devicepart of a loop✕
Connections
13 pairs of types, where a type in vulkano.device.physical uses a type in vulkano.device.
vulkano.device.physical uses vulkano.device, so a change to vulkano.device can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→33 vulkano.device.physical uses vulkano.bufferpart of a loop✕
Connections
2 pairs of types, where a type in vulkano.device.physical uses a type in vulkano.buffer.
vulkano.device.physical uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→34 vulkano.device.physical uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.device.physical uses a type in vulkano.
vulkano.device.physical uses vulkano, so a change to vulkano can break vulkano.device.physical, while a change to vulkano.device.physical can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.descriptor_set.layout uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano.descriptor_set.layout, while a change to vulkano.descriptor_set.layout can't break vulkano.image.layout.
Position
Below the diagonal: vulkano.descriptor_set.layout uses a module listed above it, which is the healthy direction.
vulkano.descriptor_set.layout uses vulkano.image.sampler, so a change to vulkano.image.sampler can break vulkano.descriptor_set.layout, while a change to vulkano.descriptor_set.layout can't break vulkano.image.sampler.
Position
Below the diagonal: vulkano.descriptor_set.layout uses a module listed above it, which is the healthy direction.
vulkano.descriptor_set.layout uses vulkano.shader, so a change to vulkano.shader can break vulkano.descriptor_set.layout, while a change to vulkano.descriptor_set.layout can't break vulkano.shader.
Position
Below the diagonal: vulkano.descriptor_set.layout uses a module listed above it, which is the healthy direction.
vulkano.descriptor_set.layout uses vulkano.version, so a change to vulkano.version can break vulkano.descriptor_set.layout, while a change to vulkano.descriptor_set.layout can't break vulkano.version.
Position
Below the diagonal: vulkano.descriptor_set.layout uses a module listed above it, which is the healthy direction.
vulkano.descriptor_set.layout uses vulkano.instance, so a change to vulkano.instance can break vulkano.descriptor_set.layout, while a change to vulkano.descriptor_set.layout can't break vulkano.instance.
Position
Below the diagonal: vulkano.descriptor_set.layout uses a module listed above it, which is the healthy direction.
vulkano.descriptor_set.layout uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.descriptor_set.layout, while a change to vulkano.descriptor_set.layout can't break vulkano.device.physical.
Position
Below the diagonal: vulkano.descriptor_set.layout uses a module listed above it, which is the healthy direction.
28→29 vulkano.descriptor_set.layout uses vulkano.devicepart of a loop✕
Connections
8 pairs of types, where a type in vulkano.descriptor_set.layout uses a type in vulkano.device.
vulkano.descriptor_set.layout uses vulkano.device, so a change to vulkano.device can break vulkano.descriptor_set.layout, while a change to vulkano.descriptor_set.layout can't break vulkano.device.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→34 vulkano.descriptor_set.layout uses vulkanopart of a loop✕
Connections
3 pairs of types, where a type in vulkano.descriptor_set.layout uses a type in vulkano.
vulkano.descriptor_set.layout uses vulkano, so a change to vulkano can break vulkano.descriptor_set.layout, while a change to vulkano.descriptor_set.layout can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.device uses vulkano.memory.device_memory, so a change to vulkano.memory.device_memory can break vulkano.device, while a change to vulkano.device can't break vulkano.memory.device_memory.
Position
Below the diagonal: vulkano.device uses a module listed above it, which is the healthy direction.
vulkano.device uses vulkano.memory, so a change to vulkano.memory can break vulkano.device, while a change to vulkano.device can't break vulkano.memory.
Position
Below the diagonal: vulkano.device uses a module listed above it, which is the healthy direction.
vulkano.device uses vulkano.image.sys, so a change to vulkano.image.sys can break vulkano.device, while a change to vulkano.device can't break vulkano.image.sys.
Position
Below the diagonal: vulkano.device uses a module listed above it, which is the healthy direction.
vulkano.device uses vulkano.version, so a change to vulkano.version can break vulkano.device, while a change to vulkano.device can't break vulkano.version.
Position
Below the diagonal: vulkano.device uses a module listed above it, which is the healthy direction.
vulkano.device uses vulkano.instance, so a change to vulkano.instance can break vulkano.device, while a change to vulkano.device can't break vulkano.instance.
Position
Below the diagonal: vulkano.device uses a module listed above it, which is the healthy direction.
vulkano.device uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.device, while a change to vulkano.device can't break vulkano.device.physical.
Position
Below the diagonal: vulkano.device uses a module listed above it, which is the healthy direction.
vulkano.device uses vulkano.descriptor_set.layout, so a change to vulkano.descriptor_set.layout can break vulkano.device, while a change to vulkano.device can't break vulkano.descriptor_set.layout.
Position
Below the diagonal: vulkano.device uses a module listed above it, which is the healthy direction.
vulkano.buffer.allocator uses vulkano.memory.alignment, so a change to vulkano.memory.alignment can break vulkano.buffer.allocator, while a change to vulkano.buffer.allocator can't break vulkano.memory.alignment.
Position
Below the diagonal: vulkano.buffer.allocator uses a module listed above it, which is the healthy direction.
vulkano.buffer.allocator uses vulkano.memory.allocator.suballocator, so a change to vulkano.memory.allocator.suballocator can break vulkano.buffer.allocator, while a change to vulkano.buffer.allocator can't break vulkano.memory.allocator.suballocator.
Position
Below the diagonal: vulkano.buffer.allocator uses a module listed above it, which is the healthy direction.
vulkano.buffer.allocator uses vulkano.memory.allocator, so a change to vulkano.memory.allocator can break vulkano.buffer.allocator, while a change to vulkano.buffer.allocator can't break vulkano.memory.allocator.
Position
Below the diagonal: vulkano.buffer.allocator uses a module listed above it, which is the healthy direction.
vulkano.buffer.allocator uses vulkano.device, so a change to vulkano.device can break vulkano.buffer.allocator, while a change to vulkano.buffer.allocator can't break vulkano.device.
Position
Below the diagonal: vulkano.buffer.allocator uses a module listed above it, which is the healthy direction.
30→33 vulkano.buffer.allocator uses vulkano.bufferpart of a loop✕
Connections
3 pairs of types, where a type in vulkano.buffer.allocator uses a type in vulkano.buffer.
vulkano.buffer.allocator uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.buffer.allocator, while a change to vulkano.buffer.allocator can't break vulkano.buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→34 vulkano.buffer.allocator uses vulkanopart of a loop✕
Connections
2 pairs of types, where a type in vulkano.buffer.allocator uses a type in vulkano.
vulkano.buffer.allocator uses vulkano, so a change to vulkano can break vulkano.buffer.allocator, while a change to vulkano.buffer.allocator can't break vulkano.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano_taskgraph.graph.execute uses vulkano.format, so a change to vulkano.format can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano.format.
Position
Below the diagonal: vulkano_taskgraph.graph.execute uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph.execute uses vulkano.sync.pipeline, so a change to vulkano.sync.pipeline can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano.sync.pipeline.
Position
Below the diagonal: vulkano_taskgraph.graph.execute uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph.execute uses vulkano.render_pass, so a change to vulkano.render_pass can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano.render_pass.
Position
Below the diagonal: vulkano_taskgraph.graph.execute uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph.execute uses vulkano.command_buffer.sys, so a change to vulkano.command_buffer.sys can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano.command_buffer.sys.
Position
Below the diagonal: vulkano_taskgraph.graph.execute uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph.execute uses vulkano.display, so a change to vulkano.display can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano.display.
Position
Below the diagonal: vulkano_taskgraph.graph.execute uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph.execute uses vulkano.device, so a change to vulkano.device can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano.device.
Position
Below the diagonal: vulkano_taskgraph.graph.execute uses a module listed above it, which is the healthy direction.
31→37 vulkano_taskgraph.graph.execute uses vulkano_taskgraph.graphpart of a loop✕
Connections
6 pairs of types, where a type in vulkano_taskgraph.graph.execute uses a type in vulkano_taskgraph.graph.
vulkano_taskgraph.graph.execute uses vulkano_taskgraph.graph, so a change to vulkano_taskgraph.graph can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano_taskgraph.graph.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→39 vulkano_taskgraph.graph.execute uses vulkano_taskgraph.command_bufferpart of a loop✕
Connections
4 pairs of types, where a type in vulkano_taskgraph.graph.execute uses a type in vulkano_taskgraph.command_buffer.
vulkano_taskgraph.graph.execute uses vulkano_taskgraph.command_buffer, so a change to vulkano_taskgraph.command_buffer can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano_taskgraph.command_buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→40 vulkano_taskgraph.graph.execute uses vulkano_taskgraphpart of a loop✕
Connections
4 pairs of types, where a type in vulkano_taskgraph.graph.execute uses a type in vulkano_taskgraph.
vulkano_taskgraph.graph.execute uses vulkano_taskgraph, so a change to vulkano_taskgraph can break vulkano_taskgraph.graph.execute, while a change to vulkano_taskgraph.graph.execute can't break vulkano_taskgraph.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.buffer.subbuffer uses vulkano.memory.alignment, so a change to vulkano.memory.alignment can break vulkano.buffer.subbuffer, while a change to vulkano.buffer.subbuffer can't break vulkano.memory.alignment.
Position
Below the diagonal: vulkano.buffer.subbuffer uses a module listed above it, which is the healthy direction.
vulkano.buffer.subbuffer uses vulkano.device, so a change to vulkano.device can break vulkano.buffer.subbuffer, while a change to vulkano.buffer.subbuffer can't break vulkano.device.
Position
Below the diagonal: vulkano.buffer.subbuffer uses a module listed above it, which is the healthy direction.
vulkano.buffer.subbuffer uses vulkano.buffer.allocator, so a change to vulkano.buffer.allocator can break vulkano.buffer.subbuffer, while a change to vulkano.buffer.subbuffer can't break vulkano.buffer.allocator.
Position
Below the diagonal: vulkano.buffer.subbuffer uses a module listed above it, which is the healthy direction.
32→33 vulkano.buffer.subbuffer uses vulkano.bufferpart of a loop✕
Connections
1 pair of types, where a type in vulkano.buffer.subbuffer uses a type in vulkano.buffer.
vulkano.buffer.subbuffer uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.buffer.subbuffer, while a change to vulkano.buffer.subbuffer can't break vulkano.buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano.buffer uses vulkano.range_map, so a change to vulkano.range_map can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.range_map.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.memory.device_memory, so a change to vulkano.memory.device_memory can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.memory.device_memory.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.memory.allocator, so a change to vulkano.memory.allocator can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.memory.allocator.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.memory, so a change to vulkano.memory can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.memory.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.display, so a change to vulkano.display can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.display.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.version, so a change to vulkano.version can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.version.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.instance, so a change to vulkano.instance can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.instance.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.device.physical, so a change to vulkano.device.physical can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.device.physical.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.device, so a change to vulkano.device can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.device.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.buffer uses vulkano.buffer.subbuffer, so a change to vulkano.buffer.subbuffer can break vulkano.buffer, while a change to vulkano.buffer can't break vulkano.buffer.subbuffer.
Position
Below the diagonal: vulkano.buffer uses a module listed above it, which is the healthy direction.
vulkano.sync.future uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano.sync.future, while a change to vulkano.sync.future can't break vulkano.image.layout.
Position
Below the diagonal: vulkano.sync.future uses a module listed above it, which is the healthy direction.
vulkano.sync.future uses vulkano.command_buffer, so a change to vulkano.command_buffer can break vulkano.sync.future, while a change to vulkano.sync.future can't break vulkano.command_buffer.
Position
Below the diagonal: vulkano.sync.future uses a module listed above it, which is the healthy direction.
vulkano.sync.future uses vulkano.image, so a change to vulkano.image can break vulkano.sync.future, while a change to vulkano.sync.future can't break vulkano.image.
Position
Below the diagonal: vulkano.sync.future uses a module listed above it, which is the healthy direction.
vulkano.sync.future uses vulkano.swapchain, so a change to vulkano.swapchain can break vulkano.sync.future, while a change to vulkano.sync.future can't break vulkano.swapchain.
Position
Below the diagonal: vulkano.sync.future uses a module listed above it, which is the healthy direction.
vulkano.sync.future uses vulkano.display, so a change to vulkano.display can break vulkano.sync.future, while a change to vulkano.sync.future can't break vulkano.display.
Position
Below the diagonal: vulkano.sync.future uses a module listed above it, which is the healthy direction.
vulkano.sync.future uses vulkano.device.queue, so a change to vulkano.device.queue can break vulkano.sync.future, while a change to vulkano.sync.future can't break vulkano.device.queue.
Position
Below the diagonal: vulkano.sync.future uses a module listed above it, which is the healthy direction.
vulkano.sync.future uses vulkano.device, so a change to vulkano.device can break vulkano.sync.future, while a change to vulkano.sync.future can't break vulkano.device.
Position
Below the diagonal: vulkano.sync.future uses a module listed above it, which is the healthy direction.
vulkano.sync.future uses vulkano.buffer, so a change to vulkano.buffer can break vulkano.sync.future, while a change to vulkano.sync.future can't break vulkano.buffer.
Position
Below the diagonal: vulkano.sync.future uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.image.layout.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.memory.allocator, so a change to vulkano.memory.allocator can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.memory.allocator.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.sync.pipeline, so a change to vulkano.sync.pipeline can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.sync.pipeline.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.image.sys, so a change to vulkano.image.sys can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.image.sys.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.image, so a change to vulkano.image can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.image.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.swapchain, so a change to vulkano.swapchain can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.swapchain.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.swapchain.surface, so a change to vulkano.swapchain.surface can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.swapchain.surface.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.device, so a change to vulkano.device can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.device.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.resource uses vulkano.buffer, so a change to vulkano.buffer can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano.buffer.
Position
Below the diagonal: vulkano_taskgraph.resource uses a module listed above it, which is the healthy direction.
36→38 vulkano_taskgraph.resource uses vulkano_taskgraph.descriptor_setpart of a loop✕
Connections
2 pairs of types, where a type in vulkano_taskgraph.resource uses a type in vulkano_taskgraph.descriptor_set.
vulkano_taskgraph.resource uses vulkano_taskgraph.descriptor_set, so a change to vulkano_taskgraph.descriptor_set can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano_taskgraph.descriptor_set.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→40 vulkano_taskgraph.resource uses vulkano_taskgraphpart of a loop✕
Connections
5 pairs of types, where a type in vulkano_taskgraph.resource uses a type in vulkano_taskgraph.
vulkano_taskgraph.resource uses vulkano_taskgraph, so a change to vulkano_taskgraph can break vulkano_taskgraph.resource, while a change to vulkano_taskgraph.resource can't break vulkano_taskgraph.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano_taskgraph.graph uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.image.layout.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano.image.sampler, so a change to vulkano.image.sampler can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.image.sampler.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano.sync.pipeline, so a change to vulkano.sync.pipeline can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.sync.pipeline.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano.image.sys, so a change to vulkano.image.sys can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.image.sys.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano.render_pass, so a change to vulkano.render_pass can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.render_pass.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano.image, so a change to vulkano.image can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.image.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano.swapchain, so a change to vulkano.swapchain can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.swapchain.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano.display, so a change to vulkano.display can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.display.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano.device, so a change to vulkano.device can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano.device.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano_taskgraph.graph.execute, so a change to vulkano_taskgraph.graph.execute can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano_taskgraph.graph.execute.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.graph uses vulkano_taskgraph.resource, so a change to vulkano_taskgraph.resource can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano_taskgraph.resource.
Position
Below the diagonal: vulkano_taskgraph.graph uses a module listed above it, which is the healthy direction.
37→39 vulkano_taskgraph.graph uses vulkano_taskgraph.command_bufferpart of a loop✕
Connections
2 pairs of types, where a type in vulkano_taskgraph.graph uses a type in vulkano_taskgraph.command_buffer.
vulkano_taskgraph.graph uses vulkano_taskgraph.command_buffer, so a change to vulkano_taskgraph.command_buffer can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano_taskgraph.command_buffer.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→40 vulkano_taskgraph.graph uses vulkano_taskgraphpart of a loop✕
Connections
10 pairs of types, where a type in vulkano_taskgraph.graph uses a type in vulkano_taskgraph.
vulkano_taskgraph.graph uses vulkano_taskgraph, so a change to vulkano_taskgraph can break vulkano_taskgraph.graph, while a change to vulkano_taskgraph.graph can't break vulkano_taskgraph.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano_taskgraph.descriptor_set uses vulkano.image.layout, so a change to vulkano.image.layout can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.image.layout.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano.image.sampler, so a change to vulkano.image.sampler can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.image.sampler.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano.image.view, so a change to vulkano.image.view can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.image.view.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano.shader, so a change to vulkano.shader can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.shader.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano.instance, so a change to vulkano.instance can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.instance.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano.descriptor_set.layout, so a change to vulkano.descriptor_set.layout can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.descriptor_set.layout.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano.device, so a change to vulkano.device can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.device.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano.buffer, so a change to vulkano.buffer can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.buffer.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano, so a change to vulkano can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano_taskgraph.resource, so a change to vulkano_taskgraph.resource can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano_taskgraph.resource.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.descriptor_set uses vulkano_taskgraph.graph, so a change to vulkano_taskgraph.graph can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano_taskgraph.graph.
Position
Below the diagonal: vulkano_taskgraph.descriptor_set uses a module listed above it, which is the healthy direction.
38→40 vulkano_taskgraph.descriptor_set uses vulkano_taskgraphpart of a loop✕
Connections
5 pairs of types, where a type in vulkano_taskgraph.descriptor_set uses a type in vulkano_taskgraph.
vulkano_taskgraph.descriptor_set uses vulkano_taskgraph, so a change to vulkano_taskgraph can break vulkano_taskgraph.descriptor_set, while a change to vulkano_taskgraph.descriptor_set can't break vulkano_taskgraph.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano_taskgraph.command_buffer uses vulkano.pipeline, so a change to vulkano.pipeline can break vulkano_taskgraph.command_buffer, while a change to vulkano_taskgraph.command_buffer can't break vulkano.pipeline.
Position
Below the diagonal: vulkano_taskgraph.command_buffer uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.command_buffer uses vulkano.image, so a change to vulkano.image can break vulkano_taskgraph.command_buffer, while a change to vulkano_taskgraph.command_buffer can't break vulkano.image.
Position
Below the diagonal: vulkano_taskgraph.command_buffer uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.command_buffer uses vulkano.device, so a change to vulkano.device can break vulkano_taskgraph.command_buffer, while a change to vulkano_taskgraph.command_buffer can't break vulkano.device.
Position
Below the diagonal: vulkano_taskgraph.command_buffer uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.command_buffer uses vulkano_taskgraph.graph.execute, so a change to vulkano_taskgraph.graph.execute can break vulkano_taskgraph.command_buffer, while a change to vulkano_taskgraph.command_buffer can't break vulkano_taskgraph.graph.execute.
Position
Below the diagonal: vulkano_taskgraph.command_buffer uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.command_buffer uses vulkano.buffer, so a change to vulkano.buffer can break vulkano_taskgraph.command_buffer, while a change to vulkano_taskgraph.command_buffer can't break vulkano.buffer.
Position
Below the diagonal: vulkano_taskgraph.command_buffer uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.command_buffer uses vulkano, so a change to vulkano can break vulkano_taskgraph.command_buffer, while a change to vulkano_taskgraph.command_buffer can't break vulkano.
Position
Below the diagonal: vulkano_taskgraph.command_buffer uses a module listed above it, which is the healthy direction.
vulkano_taskgraph.command_buffer uses vulkano_taskgraph.descriptor_set, so a change to vulkano_taskgraph.descriptor_set can break vulkano_taskgraph.command_buffer, while a change to vulkano_taskgraph.command_buffer can't break vulkano_taskgraph.descriptor_set.
Position
Below the diagonal: vulkano_taskgraph.command_buffer uses a module listed above it, which is the healthy direction.
39→40 vulkano_taskgraph.command_buffer uses vulkano_taskgraphpart of a loop✕
Connections
2 pairs of types, where a type in vulkano_taskgraph.command_buffer uses a type in vulkano_taskgraph.
vulkano_taskgraph.command_buffer uses vulkano_taskgraph, so a change to vulkano_taskgraph can break vulkano_taskgraph.command_buffer, while a change to vulkano_taskgraph.command_buffer can't break vulkano_taskgraph.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vulkano_taskgraph uses vulkano.format, so a change to vulkano.format can break vulkano_taskgraph, while a change to vulkano_taskgraph can't break vulkano.format.
Position
Below the diagonal: vulkano_taskgraph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph uses vulkano.command_buffer.sys, so a change to vulkano.command_buffer.sys can break vulkano_taskgraph, while a change to vulkano_taskgraph can't break vulkano.command_buffer.sys.
Position
Below the diagonal: vulkano_taskgraph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph uses vulkano.display, so a change to vulkano.display can break vulkano_taskgraph, while a change to vulkano_taskgraph can't break vulkano.display.
Position
Below the diagonal: vulkano_taskgraph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph uses vulkano_taskgraph.graph.execute, so a change to vulkano_taskgraph.graph.execute can break vulkano_taskgraph, while a change to vulkano_taskgraph can't break vulkano_taskgraph.graph.execute.
Position
Below the diagonal: vulkano_taskgraph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph uses vulkano_taskgraph.graph, so a change to vulkano_taskgraph.graph can break vulkano_taskgraph, while a change to vulkano_taskgraph can't break vulkano_taskgraph.graph.
Position
Below the diagonal: vulkano_taskgraph uses a module listed above it, which is the healthy direction.
vulkano_taskgraph uses vulkano_taskgraph.command_buffer, so a change to vulkano_taskgraph.command_buffer can break vulkano_taskgraph, while a change to vulkano_taskgraph can't break vulkano_taskgraph.command_buffer.
Position
Below the diagonal: vulkano_taskgraph uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
10
High / Critical
A03:2025 — Software Supply Chain Failures
3
Medium
Roadmap
Top priorities: Resolve the 153 Low coverage finding(s) in Code Coverage — start with mod.rs (23), lib.rs (4), pipeline.rs (4); Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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.
God Classes: MethodTooLong: RecordingCommandBuffer.pipeline_barrier_unchecked
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 38
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 — 1637
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 62
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 20
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 39 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 — 39 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, 1721 of 1737 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.
D15 Churn × Complexity Hotspots — 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. A hotspot's complexity is meant to be the worst body its churn actually touched. For vulkano/src/device/queue.rs, vulkano/src/pipeline/mod.rs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
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 on C# first (docs/plans/deterministic-engine.md, P5): 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
GD1 Unfinished & placeholder code — 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, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — 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, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
X12 Unreachable branch — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin 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.
X13 Undrained process stream — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin 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.
X16 Unfloored truncation loop — 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, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin 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.
X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin 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.
X18 Disposal-pattern correctness — 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, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP 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.
X19 Unrestored process-global state — 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, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP 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.
X22 Contradicted release guard — 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 Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — 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, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP 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.
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.
X25 Inert configuration knob — 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, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby 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 — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality 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.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
120 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was GraphicsPipelineCreateInfo::validate at 186. A further 18 function(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 PipelineStages::from at 99 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: autogen/src/properties.rs (autogen::properties::c_type_to_vulkano_type::vulkano_type_basic at 34), vulkano-shaders/src/lib.rs (ShaderFields::parse_ty at 17), vulkano/src/image/layout.rs (ImageLayout::try_from at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 76 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with GraphicsPipelineCreateInfo::validate (cyclomatic 186), ImageCreateInfo::validate (cyclomatic 149), WriteDescriptorSet::validate (cyclomatic 125). — 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 5 together lifts Cyclomatic Complexity from 5.4 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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.
+ 108 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 14 bodies over 120 down to 120 or less in Cognitive Complexity — start with RuntimeValidator::validate_function (cognitive 317), WriteDescriptorSet::validate (cognitive 296), GraphicsPipelineCreateInfo::validate (cognitive 283). — 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 14 together lifts Cognitive Complexity from 4.8 to about 5.8/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 Classes7.4 / 10Strong✓ 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 90 MethodTooLong finding(s) in God Classes — start with mod.rs (20), copy.rs (13), sync.rs (8). — One of this dimension's main actionable groups (90 warning-level).
Resolve the 73 FileTooLong finding(s) in God Classes — start with mod.rs (17), pipeline.rs (4), copy.rs (3). — One of this dimension's main actionable groups (73 warning-level).
Resolve the 33 ClassTooLong finding(s) in God Classes — start with mod.rs (10), copy.rs (5), sys.rs (2). — One of this dimension's main actionable groups (33 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D4 · Code Duplication4.8 / 10Weak✓ Tool-verified
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.
498 duplicated block group(s) detected. 13.1 % of the production lines (21,684 of 165,588) are in a reported copy. A further 231 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 235 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 31 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with sync.rs (10), fence.rs (5), mod.rs (3). — One of this dimension's main actionable groups (31 warning-level).
Resolve the 29 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with mod.rs (8), copy.rs (5), clear.rs (2). — One of this dimension's main actionable groups (29 warning-level).
Resolve the 28 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with copy.rs (7), mod.rs (7), clear.rs (3). — One of this dimension's main actionable groups (28 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.7 / 10Strong✓ 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.
6 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, with abstractness counted on 4 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: vulkano
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: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 4.3% — 153 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 175 production file(s), 6 test binaries and 84 doc-test binaries).
Resolve the 153 Low coverage finding(s) in Code Coverage — start with mod.rs (23), lib.rs (4), pipeline.rs (4). — One of this dimension's main actionable groups (153 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether 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.
9 outdated, 0 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.
Outdated: bytemuck · ×9
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 245 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 MIT OR Apache-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 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs, queue.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.0 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
16 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is vulkano-taskgraph/src/graph/compile.rs. Counted over 158 of the 175 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
599 deducted task-comment markers across 165588 LoC (0.4/KLoC) → score 9.3. 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.
TodoComment repeated across 21 filesvulkano-taskgraph/src/lib.rs:830
TodoComment repeated across 26 filesvulkano/src/acceleration_structure.rs:393
What to do
Resolve the 185 TodoComment finding(s) in Explicit Debt — start with mod.rs (32), validate_runtime.rs (13), render_pass.rs (11). — One of this dimension's main actionable groups (185 warning-level).
Resolve the 35 FixmeComment finding(s) in Explicit Debt — start with execute.rs (11), mod.rs (5), compile.rs (4). — One of this dimension's main actionable groups (35 warning-level).
Resolve the 6 HackComment finding(s) in Explicit Debt — start with state.rs (2), derive_buffer_contents.rs (2), context.rs. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: 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.
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
1 of 6 build units (Cargo) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
10 finding(s): 0 critical, 10 high, 0 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `vulkano/src/swapchain/surface.rs` (line 134, line 162) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
What to do
No action in Static Analysis (SAST) — all 10 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 (10 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 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
58 of 158 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is vulkano/src/render_pass/mod.rs. Counted over 158 of the 175 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 28 Orphaned knowledge finding(s) in Knowledge Freshness — start with mod.rs (5), layout.rs (2), validate_runtime.rs. — One of this dimension's main actionable groups (28 issue-level).
Resolve the 30 Orphaned file finding(s) in Knowledge Freshness — start with usage.rs (2), viewport.rs, depth_stencil.rs. — One of this dimension's main actionable groups (30 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with traits.rs, fence_signal.rs, compute.rs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. 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.
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
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
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.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 17 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 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 — Not applicable: 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.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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 — ~24490 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.
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.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# 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 — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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.
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
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (126 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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the 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 data present for 175 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
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: 172 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
X12 Unreachable branch — 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
X13 Undrained process stream — 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
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
X16 Unfloored truncation loop — 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
X17 Uncapped recursion over a caller-supplied document — 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
X18 Disposal-pattern correctness — 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
X19 Unrestored process-global state — 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
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.
X22 Contradicted release guard — 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
X23 Unguarded diagnostic materialisation — 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
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 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
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. Not a gap in the analyzer and not a finding about your code.
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
X29 Per-element action decided by a fixed element — 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
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.
X5 Nullable reference types — 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
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.
Orphaned knowledge vulkano/src/render_pass/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/pipeline/shader/validate_runtime.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/sync/pipeline.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/command_buffer/commands/dynamic_state.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/shader/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/image/sampler/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/pipeline/layout.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/descriptor_set/layout.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/memory/sparse.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/shader/reflect.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/sync/fence.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/pipeline/graphics/color_blend.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge autogen/src/features.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/render_pass/framebuffer.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge autogen/src/formats.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge autogen/src/properties.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/image/sampler/ycbcr.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/pipeline/graphics/vertex_input/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/pipeline/shader/inout_interface.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge autogen/src/extensions.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/macros.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/query.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge vulkano/src/shader/spirv/specialization.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/pipeline/graphics/rasterization.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge vulkano/src/display.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
TodoComment vulkano-taskgraph/src/collector.rs:1100— // TODO: `Queue::push` is quadratic in isolation. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-taskgraph/src/lib.rs:136— // Potentially TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-taskgraph/src/graph/compile.rs:504— // TODO: Cull redundant semaphores. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-taskgraph/src/graph/compile.rs:1362— // TODO: What do we do about non-framebuffer-space subpass self-dependencies? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-taskgraph/src/graph/compile.rs:2353— // TODO: This semaphore is redundant. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-taskgraph/src/graph/compile.rs:2422— // TODO: This semaphore is redundant. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-taskgraph/src/graph/compile.rs:2497— // TODO: This could be brought down to 3 submissions with task reordering. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-taskgraph/src/graph/execute.rs:717— // TODO: Could there be a use case for keeping the old image contents? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-taskgraph/src/command_buffer/mod.rs:29— /// and can therefore validate resource accesses. (TODO) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-shaders/src/lib.rs:757— // TODO: Use a variable set by cargo for the working directory of rustc invocations once it's — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano-shaders/src/structs.rs:1102— // TODO: Replace with the `ArrayWindows` iterator once it is stabilized. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:497— // TODO: allow user to specify — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:1039— // TODO: `vulkan_enum!` can't generate non-public types. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:1620— // TODO: unsafe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:1623— // TODO: unsafe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:1703— // TODO: unsafe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:1706— // TODO: unsafe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:1788— // TODO: unsafe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:1791— // TODO: unsafe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/acceleration_structure.rs:1794— // TODO: unsafe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/cache.rs:27— // TODO: make const — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/cache.rs:112— // TODO: make const — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/sync/pipeline.rs:1752— // TODO: make const — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/pipeline/graphics/vertex_input/mod.rs:139— // TODO: make const — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vulkano/src/command_buffer/commands/render_pass.rs:913— // TODO: make const — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
MethodTooLong: GraphicsPipelineCreateInfo.validate vulkano/src/pipeline/graphics/mod.rs:806— MethodTooLong — validate runs 1073 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 973 over it, 10.73× 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: ImageCreateInfo.validate vulkano/src/image/sys.rs:1788— MethodTooLong — validate runs 920 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 820 over it, 9.20× 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: CopyImageInfo.validate vulkano/src/command_buffer/commands/copy.rs:1564— MethodTooLong — validate runs 906 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 806 over it, 9.06× 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: WriteDescriptorSet.validate vulkano/src/descriptor_set/update.rs:204— MethodTooLong — validate runs 861 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 761 over it, 8.61× 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: ImageMemoryBarrier.validate vulkano/src/command_buffer/commands/sync.rs:2655— MethodTooLong — validate runs 712 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 612 over it, 7.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: RuntimeValidator.validate_function vulkano/src/pipeline/shader/validate_runtime.rs:1946— MethodTooLong — validate_function runs 669 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 569 over it, 6.69× 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: AutoCommandBufferBuilder.validate_pipeline_graphics_dynamic_state vulkano/src/command_buffer/auto/commands/pipeline.rs:2516— MethodTooLong — validate_pipeline_graphics_dynamic_state runs 622 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 522 over it, 6.22× 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: RuntimeValidator.validate_global_variables vulkano/src/pipeline/shader/validate_runtime.rs:1046— MethodTooLong — validate_global_variables runs 617 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 517 over it, 6.17× 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: RuntimeValidator.validate_execution_modes vulkano/src/pipeline/shader/validate_runtime.rs:160— MethodTooLong — validate_execution_modes runs 606 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 506 over it, 6.06× 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: RenderPassCreateInfo.validate vulkano/src/render_pass/mod.rs:984— MethodTooLong — validate runs 586 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 486 over it, 5.86× 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: BlitImageInfo.validate vulkano/src/command_buffer/commands/copy.rs:4926— MethodTooLong — validate runs 538 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 438 over it, 5.38× 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: SubpassDescription.validate vulkano/src/render_pass/mod.rs:2969— MethodTooLong — validate runs 468 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 368 over it, 4.68× 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: RenderingInfo.validate vulkano/src/command_buffer/commands/render_pass.rs:1360— MethodTooLong — validate runs 436 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 336 over it, 4.36× 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: BufferMemoryBarrier.validate vulkano/src/command_buffer/commands/sync.rs:1903— MethodTooLong — validate runs 434 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 334 over it, 4.34× 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: AutoCommandBufferBuilder.validate_pipeline_descriptor_sets vulkano/src/command_buffer/auto/commands/pipeline.rs:1724— MethodTooLong — validate_pipeline_descriptor_sets runs 417 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 317 over it, 4.17× 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: CopyBufferToImageInfo.validate vulkano/src/command_buffer/commands/copy.rs:3227— MethodTooLong — validate runs 402 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 302 over it, 4.02× 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: CopyImageToBufferInfo.validate vulkano/src/command_buffer/commands/copy.rs:3945— MethodTooLong — validate runs 402 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 302 over it, 4.02× 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: ResolveImageInfo.validate vulkano/src/command_buffer/commands/copy.rs:6059— MethodTooLong — validate runs 388 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 288 over it, 3.88× 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: ImageView.validate_new vulkano/src/image/view.rs:83— MethodTooLong — validate_new runs 384 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 284 over it, 3.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: PipelineLayoutCreateInfo.validate vulkano/src/pipeline/layout.rs:600— MethodTooLong — validate runs 354 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 254 over it, 3.54× 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: MemoryBarrier.validate vulkano/src/command_buffer/commands/sync.rs:1349— MethodTooLong — validate runs 329 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 229 over it, 3.29× 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: Swapchain.validate_new_inner vulkano/src/swapchain/mod.rs:586— MethodTooLong — validate_new_inner 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: AttachmentDescription.validate vulkano/src/render_pass/mod.rs:2277— MethodTooLong — validate 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.
MethodTooLong: PipelineShaderStageCreateInfo.validate vulkano/src/pipeline/shader/mod.rs:61— MethodTooLong — validate runs 290 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 190 over it, 2.90× 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: Spirv.new vulkano/src/shader/spirv/mod.rs:47— MethodTooLong — new runs 288 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 188 over it, 2.88× 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: commands/copy.rs vulkano/src/command_buffer/commands/copy.rs— FileTooLong — 4694 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 4194 over it, 9.39× 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: render_pass/mod.rs vulkano/src/render_pass/mod.rs— FileTooLong — 3077 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 2577 over it, 6.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: commands/sync.rs vulkano/src/command_buffer/commands/sync.rs— FileTooLong — 2584 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 2084 over it, 5.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: commands/pipeline.rs vulkano/src/command_buffer/auto/commands/pipeline.rs— FileTooLong — 2545 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 98% of them inside a single declaration: AutoCommandBufferBuilder (57-3797). The bar is 500 significant lines; this is 2045 over it, 5.09× 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: device/physical.rs vulkano/src/device/physical.rs— FileTooLong — 2283 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: PhysicalDevice (5 blocks, 61-3522). The bar is 500 significant lines; this is 1783 over it, 4.57× 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: image/sys.rs vulkano/src/image/sys.rs— FileTooLong — 2080 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 1580 over it, 4.16× 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: shader/validate_runtime.rs vulkano/src/pipeline/shader/validate_runtime.rs— FileTooLong — 2028 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 98% of them inside a single declaration: RuntimeValidator (2 blocks, 61-2913). The bar is 500 significant lines; this is 1528 over it, 4.06× 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: graph/execute.rs vulkano-taskgraph/src/graph/execute.rs— FileTooLong — 1954 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 1454 over it, 3.91× 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: graphics/mod.rs vulkano/src/pipeline/graphics/mod.rs— FileTooLong — 1826 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: GraphicsPipelineCreateInfo (2 blocks, 652-2726). The bar is 500 significant lines; this is 1326 over it, 3.65× 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: commands/dynamic_state.rs vulkano/src/command_buffer/commands/dynamic_state.rs— FileTooLong — 1734 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 99% of them inside a single declaration: RecordingCommandBuffer (18-2504). The bar is 500 significant lines; this is 1234 over it, 3.47× 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: swapchain/surface.rs vulkano/src/swapchain/surface.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), about 65% of them inside a single declaration: Surface (6 blocks, 38-2063). The bar is 500 significant lines; this is 1218 over it, 3.44× 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: image/mod.rs vulkano/src/image/mod.rs— FileTooLong — 1634 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 1134 over it, 3.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: commands/render_pass.rs vulkano/src/command_buffer/commands/render_pass.rs— FileTooLong — 1607 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 1107 over it, 3.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: device/mod.rs vulkano/src/device/mod.rs— FileTooLong — 1504 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: Device (6 blocks, 171-1847). The bar is 500 significant lines; this is 1004 over it, 3.01× 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: swapchain/mod.rs vulkano/src/swapchain/mod.rs— FileTooLong — 1436 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: Swapchain (5 blocks, 378-2060). The bar is 500 significant lines; this is 936 over it, 2.87× 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: descriptor_set/update.rs vulkano/src/descriptor_set/update.rs— FileTooLong — 1428 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: WriteDescriptorSet (2 blocks, 35-1577). The bar is 500 significant lines; this is 928 over it, 2.86× 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: memory/device_memory.rs vulkano/src/memory/device_memory.rs— FileTooLong — 1415 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 915 over it, 2.83× 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: sync/semaphore.rs vulkano/src/sync/semaphore.rs— FileTooLong — 1325 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 825 over it, 2.65× 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: commands/pipeline.rs vulkano/src/command_buffer/commands/pipeline.rs— FileTooLong — 1300 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 99% of them inside a single declaration: RecordingCommandBuffer (13-1779). The bar is 500 significant lines; this is 800 over it, 2.60× 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: auto/builder.rs vulkano/src/command_buffer/auto/builder.rs— FileTooLong — 1277 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 777 over it, 2.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: graph/compile.rs vulkano-taskgraph/src/graph/compile.rs— FileTooLong — 1163 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 663 over it, 2.33× 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: sync/pipeline.rs vulkano/src/sync/pipeline.rs— FileTooLong — 1157 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 657 over it, 2.31× 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: resource/mod.rs vulkano-taskgraph/src/resource/mod.rs— FileTooLong — 1122 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 622 over it, 2.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: memory/sparse.rs vulkano/src/memory/sparse.rs— FileTooLong — 1050 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 550 over it, 2.10× 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: commands/copy.rs vulkano-taskgraph/src/command_buffer/commands/copy.rs— FileTooLong — 1018 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 75% of them inside a single declaration: RecordingCommandBuffer (17-1148). The bar is 500 significant lines; this is 518 over it, 2.04× 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.
FixmeComment vulkano-taskgraph/src/descriptor_set.rs:1119— // FIXME: allocation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/resource/mod.rs:44— // FIXME: Custom collector — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/resource/state.rs:907— // FIXME: imported/exported fences — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/compile.rs:1— // FIXME: host read barriers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/compile.rs:1301— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/compile.rs:1399— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:861— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:867— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:880— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:1026— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:1069— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:1111— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:1282— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:1639— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:1683— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:1726— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/execute.rs:1905— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/mod.rs:547— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/compile.rs:1315— // FIXME: subpass dependency chains — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano-taskgraph/src/graph/mod.rs:1232— // FIXME: Initial queue family ownership transfers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano/src/sync/future/semaphore_signal.rs:155— // FIXME: problematic because if we return an error and flush() is called again, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano/src/shader/reflect.rs:1075— // FIXME: row-major or column-major — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano/src/shader/reflect.rs:1076— // FIXME: `MatrixStride` applies to a struct member containing the matrix, not the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano/src/pipeline/cache.rs:318— // FIXME: vkMergePipelineCaches is not thread safe for the destination cache — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment vulkano/src/pipeline/shader/validate_runtime.rs:55— // FIXME: validator.validate_global_variables()?; — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
ClassTooLong: PhysicalDevice vulkano/src/device/physical.rs:61— ClassTooLong — 2035 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 109 methods, 5 blocks, lines 61-3522. The bar is 400 significant lines; this is 1635 over it, 5.09× 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: RuntimeValidator vulkano/src/pipeline/shader/validate_runtime.rs:61— ClassTooLong — 1984 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, 2 blocks, lines 61-2913. The bar is 400 significant lines; this is 1584 over it, 4.96× 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: GraphicsPipelineCreateInfo vulkano/src/pipeline/graphics/mod.rs:652— ClassTooLong — 1388 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, 2 blocks, lines 652-2726. The bar is 400 significant lines; this is 988 over it, 3.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Surface vulkano/src/swapchain/surface.rs:38— ClassTooLong — 1117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 78 methods, 6 blocks, lines 38-2063. The bar is 400 significant lines; this is 717 over it, 2.79× 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: ImageCreateInfo vulkano/src/image/sys.rs:1608— ClassTooLong — 1068 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 1608-3239. The bar is 400 significant lines; this is 668 over it, 2.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WriteDescriptorSet vulkano/src/descriptor_set/update.rs:35— ClassTooLong — 1034 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 2 blocks, lines 35-1577. The bar is 400 significant lines; this is 634 over it, 2.59× 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: CopyImageInfo vulkano/src/command_buffer/commands/copy.rs:1511— ClassTooLong — 1007 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, 2 blocks, lines 1511-2968. The bar is 400 significant lines; this is 607 over it, 2.52× 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: RawImage vulkano/src/image/sys.rs:50— ClassTooLong — 975 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 45 methods, 5 blocks, lines 50-1602. The bar is 400 significant lines; this is 575 over it, 2.44× 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: Device vulkano/src/device/mod.rs:171— ClassTooLong — 968 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 59 methods, 6 blocks, lines 171-1847. The bar is 400 significant lines; this is 568 over it, 2.42× 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: Swapchain vulkano/src/swapchain/mod.rs:378— ClassTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 56 methods, 5 blocks, lines 378-2060. The bar is 400 significant lines; this is 516 over it, 2.29× 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: RenderPassCreateInfo vulkano/src/render_pass/mod.rs:923— ClassTooLong — 868 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 11 methods, 3 blocks, lines 923-2117. The bar is 400 significant lines; this is 468 over it, 2.17× 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: ImageMemoryBarrier vulkano/src/command_buffer/commands/sync.rs:2584— ClassTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 2 blocks, lines 2584-3727. The bar is 400 significant lines; this is 391 over it, 1.98× 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: SubpassDescription vulkano/src/render_pass/mod.rs:2839— ClassTooLong — 744 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 2839-3966. The bar is 400 significant lines; this is 344 over it, 1.86× 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: Semaphore vulkano/src/sync/semaphore.rs:85— ClassTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 50 methods, 5 blocks, lines 85-1362. The bar is 400 significant lines; this is 290 over it, 1.73× 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: BlitImageInfo vulkano/src/command_buffer/commands/copy.rs:4865— ClassTooLong — 633 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, 2 blocks, lines 4865-5807. The bar is 400 significant lines; this is 233 over it, 1.58× 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: RenderingInfo vulkano/src/command_buffer/commands/render_pass.rs:1184— 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 1184-2038. 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: ImageView vulkano/src/image/view.rs:33— ClassTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 20 methods, 5 blocks, lines 33-856. The bar is 400 significant lines; this is 147 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: AutoSyncState vulkano/src/command_buffer/auto/builder.rs:542— ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 2 blocks, lines 542-1344. The bar is 400 significant lines; this is 119 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GenericMemoryAllocator vulkano/src/memory/allocator/mod.rs:1026— ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 4 blocks, lines 1026-2152. The bar is 400 significant lines; this is 114 over it, 1.29× 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: DeviceMemory vulkano/src/memory/device_memory.rs:47— ClassTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 46 methods, 5 blocks, lines 47-1032. The bar is 400 significant lines; this is 113 over it, 1.28× 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: BufferMemoryBarrier vulkano/src/command_buffer/commands/sync.rs:1848— ClassTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 2 blocks, lines 1848-2580. The bar is 400 significant lines; this is 107 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ResolveImageInfo vulkano/src/command_buffer/commands/copy.rs:6006— ClassTooLong — 489 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, 2 blocks, lines 6006-6733. The bar is 400 significant lines; this is 89 over it, 1.22× 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: RenderPass vulkano/src/render_pass/mod.rs:105— ClassTooLong — 488 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 5 blocks, lines 105-819. The bar is 400 significant lines; this is 88 over it, 1.22× 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: Fence vulkano/src/sync/fence.rs:52— ClassTooLong — 483 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 47 methods, 6 blocks, lines 52-1019. The bar is 400 significant lines; this is 83 over it, 1.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: CopyBufferToImageInfo vulkano/src/command_buffer/commands/copy.rs:3184— ClassTooLong — 483 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, 2 blocks, lines 3184-3892. The bar is 400 significant lines; this is 83 over it, 1.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.
Duplicated block (6 lines × 2) vulkano-shaders/src/lib.rs:952— vulkano-shaders/src/lib.rs:952-957 | vulkano-shaders/src/lib.rs:1085-1090 — 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 `vulkano-shaders/src/lib.rs:952` it does not close everything it opens, so those exact lines 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) vulkano-taskgraph/src/command_buffer/commands/sync.rs:111— vulkano-taskgraph/src/command_buffer/commands/sync.rs:111-116 | vulkano/src/command_buffer/commands/sync.rs:3684-3689 — 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) vulkano-taskgraph/src/graph/execute.rs:1072— vulkano-taskgraph/src/graph/execute.rs:1072-1077 | vulkano-taskgraph/src/graph/execute.rs:1229-1235 — 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 `vulkano-taskgraph/src/graph/execute.rs:1072` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) vulkano/src/buffer/mod.rs:789— vulkano/src/buffer/mod.rs:789-794 | vulkano/src/image/mod.rs:803-808 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:789` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/commands/sync.rs:850— vulkano/src/command_buffer/commands/sync.rs:850-855 | vulkano/src/command_buffer/mod.rs:1443-1448 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:850` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/command_buffer/commands/sync.rs:881— vulkano/src/command_buffer/commands/sync.rs:881-886 | vulkano/src/command_buffer/mod.rs:1474-1479 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:881` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/command_buffer/commands/sync.rs:894— vulkano/src/command_buffer/commands/sync.rs:894-899 | vulkano/src/command_buffer/mod.rs:1487-1492 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:894` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/command_buffer/commands/sync.rs:907— vulkano/src/command_buffer/commands/sync.rs:907-912 | vulkano/src/command_buffer/mod.rs:1500-1505 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:907` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/command_buffer/commands/sync.rs:920— vulkano/src/command_buffer/commands/sync.rs:920-925 | vulkano/src/command_buffer/mod.rs:1512-1517 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:920` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/command_buffer/commands/sync.rs:933— vulkano/src/command_buffer/commands/sync.rs:933-938 | vulkano/src/command_buffer/mod.rs:1524-1529 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:933` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/command_buffer/commands/sync.rs:964— vulkano/src/command_buffer/commands/sync.rs:964-969 | vulkano/src/command_buffer/mod.rs:1552-1557 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:964` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/command_buffer/commands/sync.rs:977— vulkano/src/command_buffer/commands/sync.rs:977-982 | vulkano/src/command_buffer/mod.rs:1565-1570 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:977` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/command_buffer/commands/sync.rs:992— vulkano/src/command_buffer/commands/sync.rs:992-997 | vulkano/src/command_buffer/mod.rs:1579-1584 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:992` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) vulkano/src/shader/reflect.rs:1183— vulkano/src/shader/reflect.rs:1183-1188 | vulkano/src/shader/reflect.rs:1202-1207 — 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 `vulkano/src/shader/reflect.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) vulkano/src/pipeline/shader/inout_interface.rs:358— vulkano/src/pipeline/shader/inout_interface.rs:358-363 | vulkano/src/pipeline/shader/inout_interface.rs:364-369 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) vulkano/src/acceleration_structure.rs:139— vulkano/src/acceleration_structure.rs:139-144 | vulkano/src/shader/mod.rs:479-484 — 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 `vulkano/src/acceleration_structure.rs:139` 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 `create_info` to `&AccelerationStructureCreateInfo<'_>` in one and `&ShaderModuleCreateInfo<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) vulkano/src/buffer/mod.rs:414— vulkano/src/buffer/mod.rs:414-419 | vulkano/src/command_buffer/sys.rs:66-71 — 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 `vulkano/src/buffer/mod.rs:414` 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 × 2) vulkano/src/descriptor_set/sys.rs:62— vulkano/src/descriptor_set/sys.rs:62-67 | vulkano/src/image/mod.rs:167-172 — 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 `vulkano/src/descriptor_set/sys.rs:62` 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 `allocator` to `Arc<dyn DescriptorSetAllocator>` in one and `Arc<dyn MemoryAllocator>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) vulkano/src/device/mod.rs:324— vulkano/src/device/mod.rs:324-329 | vulkano/src/instance/mod.rs:395-400 — 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 `vulkano/src/device/mod.rs:324` 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 `create_fn` to `impl FnOnce(&vk::DeviceCreateInfo<'_>) -> Result<vk::Device` in one and `impl FnOnce(&vk::InstanceCreateInfo<'_>) -> Result<vk::Instance` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) vulkano/src/memory/device_memory.rs:686— vulkano/src/memory/device_memory.rs:686-691 | vulkano/src/memory/mod.rs:371-376 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/memory/device_memory.rs:686` 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 × 2) vulkano/src/memory/device_memory.rs:766— vulkano/src/memory/device_memory.rs:766-771 | vulkano/src/memory/mod.rs:443-448 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/memory/device_memory.rs:766` 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 × 2) vulkano/src/sync/event.rs:212— vulkano/src/sync/event.rs:212-217 | vulkano/src/sync/fence.rs:228-233 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) vulkano/src/sync/event.rs:302— vulkano/src/sync/event.rs:302-307 | vulkano/src/sync/fence.rs:425-430 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) vulkano/src/sync/fence.rs:324— vulkano/src/sync/fence.rs:324-329 | vulkano/src/sync/semaphore.rs:525-530 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/semaphore.rs:525` 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 × 2) vulkano/src/sync/fence.rs:550— vulkano/src/sync/fence.rs:550-555 | vulkano/src/sync/semaphore.rs:637-642 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/fence.rs:550` 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 `handle_type` to `ExternalFenceHandleType` in one and `ExternalSemaphoreHandleType` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) vulkano-taskgraph/src/command_buffer/commands/clear.rs:46— vulkano-taskgraph/src/command_buffer/commands/clear.rs:46-56 | vulkano-taskgraph/src/command_buffer/commands/clear.rs:123-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/command_buffer/commands/clear.rs:46` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `clear_info` to `&ClearColorImageInfo<'_>` in one and `&ClearDepthStencilImageInfo<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:428— vulkano-taskgraph/src/command_buffer/commands/copy.rs:428-438 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:600-610 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/command_buffer/commands/copy.rs:428` 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 × 2) vulkano-taskgraph/src/resource/state.rs:481— vulkano-taskgraph/src/resource/state.rs:481-491 | vulkano-taskgraph/src/resource/state.rs:780-790 — 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 `vulkano-taskgraph/src/resource/state.rs:780` 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 × 2) vulkano/src/buffer/mod.rs:829— vulkano/src/buffer/mod.rs:829-839 | vulkano/src/image/mod.rs:846-856 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:829` it does not close everything it opens, so those exact lines 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) vulkano/src/buffer/mod.rs:870— vulkano/src/buffer/mod.rs:870-880 | vulkano/src/image/mod.rs:898-908 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) vulkano/src/command_buffer/auto/builder.rs:1794— vulkano/src/command_buffer/auto/builder.rs:1794-1804 | vulkano/src/command_buffer/auto/builder.rs:1806-1816 — 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 `vulkano/src/command_buffer/auto/builder.rs:1794` 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) vulkano/src/command_buffer/auto/commands/render_pass.rs:817— vulkano/src/command_buffer/auto/commands/render_pass.rs:817-827 | vulkano/src/command_buffer/auto/commands/render_pass.rs:875-885 — 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 `vulkano/src/command_buffer/auto/commands/render_pass.rs:817` 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) vulkano/src/command_buffer/commands/sync.rs:863— vulkano/src/command_buffer/commands/sync.rs:863-873 | vulkano/src/command_buffer/mod.rs:1455-1466 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:863` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) vulkano/src/command_buffer/commands/sync.rs:950— vulkano/src/command_buffer/commands/sync.rs:950-960 | vulkano/src/command_buffer/commands/sync.rs:2933-2943 — 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 `vulkano/src/command_buffer/commands/sync.rs:950` 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) vulkano/src/command_buffer/mod.rs:723— vulkano/src/command_buffer/mod.rs:723-733 | vulkano/src/pipeline/graphics/subpass.rs:149-159 — before extracting anything, compare `vulkano/src/command_buffer/mod.rs` and `vulkano/src/pipeline/graphics/subpass.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 `vulkano/src/command_buffer/mod.rs:723` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) vulkano/src/device/physical.rs:602— vulkano/src/device/physical.rs:602-612 | vulkano/src/device/physical.rs:752-762 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) vulkano/src/device/queue.rs:574— vulkano/src/device/queue.rs:574-584 | vulkano/src/swapchain/mod.rs:591-601 — 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 (11 lines × 2) vulkano/src/device/queue.rs:817— vulkano/src/device/queue.rs:817-827 | vulkano/src/device/queue.rs:864-874 — 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 `vulkano/src/device/queue.rs:817` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) vulkano/src/instance/mod.rs:687— vulkano/src/instance/mod.rs:687-697 | vulkano/src/instance/mod.rs:808-818 — 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 `vulkano/src/instance/mod.rs:687` 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 × 2) vulkano/src/memory/allocator/suballocator/free_list.rs:386— vulkano/src/memory/allocator/suballocator/free_list.rs:386-396 | vulkano/src/memory/allocator/suballocator/tlsf.rs:496-506 — before extracting anything, compare `vulkano/src/memory/allocator/suballocator/free_list.rs` and `vulkano/src/memory/allocator/suballocator/tlsf.rs` as WHOLE FILES: this scan already matched 3 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/memory/allocator/suballocator/free_list.rs:386` 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, `vulkano/src/memory/allocator/suballocator/tlsf.rs:494` calls `dangling` and `vulkano/src/memory/allocator/suballocator/free_list.rs:385` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) vulkano/src/sync/future/mod.rs:679— vulkano/src/sync/future/mod.rs:679-689 | vulkano/src/sync/future/mod.rs:837-847 — 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 `vulkano/src/sync/future/mod.rs:679` it does not close everything it opens, so those exact lines 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) vulkano/src/sync/semaphore.rs:1436— vulkano/src/sync/semaphore.rs:1436-1446 | vulkano/src/sync/semaphore.rs:2351-2361 — 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 `vulkano/src/sync/semaphore.rs:1436` 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) vulkano/src/render_pass/mod.rs:3069— vulkano/src/render_pass/mod.rs:3069-3079 | vulkano/src/render_pass/mod.rs:3163-3177 — 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) vulkano/src/device/physical.rs:2170— vulkano/src/device/physical.rs:2170-2180 | vulkano/src/swapchain/mod.rs:646-656 — before extracting anything, compare `vulkano/src/device/physical.rs` and `vulkano/src/swapchain/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/device/physical.rs:2170` 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 × 2) vulkano/src/command_buffer/commands/copy.rs:5191— vulkano/src/command_buffer/commands/copy.rs:5191-5201 | vulkano/src/command_buffer/commands/copy.rs:5404-5414 — 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) vulkano/src/command_buffer/commands/copy.rs:3782— vulkano/src/command_buffer/commands/copy.rs:3782-3792 | vulkano/src/command_buffer/commands/copy.rs:4500-4510 — 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) vulkano/src/command_buffer/commands/copy.rs:1607— vulkano/src/command_buffer/commands/copy.rs:1607-1617 | vulkano/src/command_buffer/commands/copy.rs:6104-6114 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) vulkano/src/command_buffer/commands/copy.rs:3287— vulkano/src/command_buffer/commands/copy.rs:3287-3297 | vulkano/src/command_buffer/commands/copy.rs:5045-5055 — 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) vulkano/src/pipeline/shader/validate_runtime.rs:2613— vulkano/src/pipeline/shader/validate_runtime.rs:2613-2623 | vulkano/src/pipeline/shader/validate_runtime.rs:2632-2642 — 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 `vulkano/src/pipeline/shader/validate_runtime.rs:2613` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) vulkano/src/swapchain/acquire_present.rs:886— vulkano/src/swapchain/acquire_present.rs:886-896 | vulkano/src/swapchain/acquire_present.rs:899-909 — 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 `vulkano/src/swapchain/acquire_present.rs:886` it does not close everything it opens, so those 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) autogen/src/extensions.rs:212— autogen/src/extensions.rs:212-219 | autogen/src/features.rs:229-236 — before extracting anything, compare `autogen/src/extensions.rs` and `autogen/src/features.rs` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/extensions.rs:212` 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) autogen/src/extensions.rs:943— autogen/src/extensions.rs:943-950 | autogen/src/spirv_reqs.rs:103-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/extensions.rs:943` it does not close everything it opens, so those exact lines 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) autogen/src/properties.rs:1100— autogen/src/properties.rs:1100-1107 | autogen/src/properties.rs:1127-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 `autogen/src/properties.rs:1100` it does not close everything it opens, so those exact lines 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) vulkano-taskgraph/src/command_buffer/commands/copy.rs:52— vulkano-taskgraph/src/command_buffer/commands/copy.rs:52-59 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:589-596 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/command_buffer/commands/copy.rs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:220— vulkano-taskgraph/src/command_buffer/commands/copy.rs:220-227 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:416-423 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:220` it does not close everything it opens, so those exact lines 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) vulkano-taskgraph/src/command_buffer/commands/sync.rs:116— vulkano-taskgraph/src/command_buffer/commands/sync.rs:116-123 | vulkano-taskgraph/src/command_buffer/commands/sync.rs:216-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/command_buffer/commands/sync.rs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) vulkano-taskgraph/src/graph/execute.rs:1068— vulkano-taskgraph/src/graph/execute.rs:1068-1075 | vulkano-taskgraph/src/graph/execute.rs:1110-1117 — 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 `vulkano-taskgraph/src/graph/execute.rs:1068` 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) vulkano/src/buffer/mod.rs:775— vulkano/src/buffer/mod.rs:775-782 | vulkano/src/image/mod.rs:788-795 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:775` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/auto/commands/copy.rs:188— vulkano/src/command_buffer/auto/commands/copy.rs:188-195 | vulkano/src/command_buffer/auto/commands/copy.rs:739-746 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/auto/commands/copy.rs:188` 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) vulkano/src/command_buffer/auto/commands/copy.rs:271— vulkano/src/command_buffer/auto/commands/copy.rs:271-278 | vulkano/src/command_buffer/auto/commands/copy.rs:825-832 — 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 `vulkano/src/command_buffer/auto/commands/copy.rs:271` 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) vulkano/src/command_buffer/commands/clear.rs:445— vulkano/src/command_buffer/commands/clear.rs:445-452 | vulkano/src/command_buffer/commands/clear.rs:678-685 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/commands/clear.rs:445` it does not close everything it opens, so those 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) vulkano/src/command_buffer/commands/copy.rs:1606— vulkano/src/command_buffer/commands/copy.rs:1606-1613 | vulkano/src/command_buffer/commands/copy.rs:3990-3997 — 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 `vulkano/src/command_buffer/commands/copy.rs:1606` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) vulkano/src/command_buffer/commands/sync.rs:3688— vulkano/src/command_buffer/commands/sync.rs:3688-3695 | vulkano/src/command_buffer/commands/sync.rs:3719-3726 — 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) vulkano/src/pipeline/graphics/viewport.rs:129— vulkano/src/pipeline/graphics/viewport.rs:129-136 | vulkano/src/pipeline/graphics/viewport.rs:143-150 — 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 `vulkano/src/pipeline/graphics/viewport.rs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) vulkano/src/render_pass/mod.rs:4451— vulkano/src/render_pass/mod.rs:4451-4458 | vulkano/src/render_pass/mod.rs:4463-4470 — 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 `vulkano/src/render_pass/mod.rs:4451` 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) vulkano/src/render_pass/mod.rs:4475— vulkano/src/render_pass/mod.rs:4475-4482 | vulkano/src/render_pass/mod.rs:4487-4494 — 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 `vulkano/src/render_pass/mod.rs:4475` 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) vulkano/src/sync/future/join.rs:172— vulkano/src/sync/future/join.rs:172-179 | vulkano/src/sync/future/join.rs:205-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/future/join.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 (8 lines × 2) vulkano/src/render_pass/mod.rs:718— vulkano/src/render_pass/mod.rs:718-725 | vulkano/src/render_pass/mod.rs:727-734 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) vulkano/src/buffer/mod.rs:819— vulkano/src/buffer/mod.rs:819-826 | vulkano/src/image/mod.rs:835-842 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) vulkano/src/sync/semaphore.rs:365— vulkano/src/sync/semaphore.rs:365-372 | vulkano/src/sync/semaphore.rs:449-458 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) vulkano/src/command_buffer/mod.rs:1035— vulkano/src/command_buffer/mod.rs:1035-1042 | vulkano/src/memory/sparse.rs:93-100 — 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 `vulkano/src/command_buffer/mod.rs:1035` 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) vulkano/src/command_buffer/commands/clear.rs:294— vulkano/src/command_buffer/commands/clear.rs:294-301 | vulkano/src/command_buffer/commands/copy.rs:3972-3979 — before extracting anything, compare `vulkano/src/command_buffer/commands/clear.rs` and `vulkano/src/command_buffer/commands/copy.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) vulkano/src/command_buffer/commands/render_pass.rs:959— vulkano/src/command_buffer/commands/render_pass.rs:959-966 | vulkano/src/command_buffer/commands/render_pass.rs:1389-1396 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) vulkano/src/swapchain/acquire_present.rs:106— vulkano/src/swapchain/acquire_present.rs:106-113 | vulkano/src/swapchain/acquire_present.rs:1053-1060 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) vulkano/src/command_buffer/commands/copy.rs:1232— vulkano/src/command_buffer/commands/copy.rs:1232-1239 | vulkano/src/command_buffer/commands/copy.rs:3254-3261 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) vulkano-taskgraph/src/graph/execute.rs:1477— vulkano-taskgraph/src/graph/execute.rs:1477-1489 | vulkano-taskgraph/src/graph/execute.rs:2112-2124 — 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 `vulkano-taskgraph/src/graph/execute.rs:1477` 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) vulkano-taskgraph/src/lib.rs:470— vulkano-taskgraph/src/lib.rs:470-482 | vulkano-taskgraph/src/lib.rs:612-624 — 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 `vulkano-taskgraph/src/lib.rs:470` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) vulkano/src/command_buffer/commands/sync.rs:2641— vulkano/src/command_buffer/commands/sync.rs:2641-2653 | vulkano/src/sync/pipeline.rs:1986-1998 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `image` to `&'a Image` in one and `Arc<Image>` 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 (13 lines × 2) vulkano/src/descriptor_set/update.rs:888— vulkano/src/descriptor_set/update.rs:888-900 | vulkano/src/descriptor_set/update.rs:1301-1313 — 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 `vulkano/src/descriptor_set/update.rs:888` it does not close everything it opens, so those exact lines 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) vulkano/src/device/physical.rs:964— vulkano/src/device/physical.rs:964-976 | vulkano/src/swapchain/surface.rs:2179-2191 — 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 `vulkano/src/device/physical.rs:964` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) vulkano/src/image/sys.rs:142— vulkano/src/image/sys.rs:142-154 | vulkano/src/image/view.rs:643-655 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/image/sys.rs:142` 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 `create_info` to `&ImageCreateInfo<'_>` in one and `&ImageViewCreateInfo<'_>` 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 (13 lines × 2) vulkano/src/pipeline/compute.rs:122— vulkano/src/pipeline/compute.rs:122-134 | vulkano/src/pipeline/ray_tracing.rs:173-186 — before extracting anything, compare `vulkano/src/pipeline/compute.rs` and `vulkano/src/pipeline/ray_tracing.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/pipeline/compute.rs:122` 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 `create_info` to `&ComputePipelineCreateInfo<'_>` in one and `&RayTracingPipelineCreateInfo<'_>` 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 (13 lines × 2) vulkano/src/shader/spirv/mod.rs:292— vulkano/src/shader/spirv/mod.rs:292-304 | vulkano/src/shader/spirv/mod.rs:331-343 — 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 `vulkano/src/shader/spirv/mod.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.
Duplicated block (13 lines × 2) vulkano/src/sync/future/fence_signal.rs:283— vulkano/src/sync/future/fence_signal.rs:283-295 | vulkano/src/sync/future/semaphore_signal.rs:119-131 — before extracting anything, compare `vulkano/src/sync/future/fence_signal.rs` and `vulkano/src/sync/future/semaphore_signal.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/future/fence_signal.rs:283` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) vulkano/src/device/mod.rs:1095— vulkano/src/device/mod.rs:1095-1107 | vulkano/src/device/mod.rs:1217-1229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `create_info` to `&BufferCreateInfo<'_>` in one and `&ImageCreateInfo<'_>` 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 (13 lines × 2) vulkano/src/device/mod.rs:2488— vulkano/src/device/mod.rs:2488-2500 | vulkano/src/device/queue.rs:293-305 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) vulkano/src/render_pass/mod.rs:3090— vulkano/src/render_pass/mod.rs:3090-3102 | vulkano/src/render_pass/mod.rs:3188-3204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) autogen/src/spirv_parse.rs:718— autogen/src/spirv_parse.rs:718-730 | autogen/src/spirv_parse.rs:884-896 — 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 `autogen/src/spirv_parse.rs:718` it does not close everything it opens, so those exact lines 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) vulkano/src/render_pass/mod.rs:2342— vulkano/src/render_pass/mod.rs:2342-2354 | vulkano/src/render_pass/mod.rs:2361-2373 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) vulkano/src/sync/fence.rs:595— vulkano/src/sync/fence.rs:595-607 | vulkano/src/sync/fence.rs:1295-1307 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/fence.rs:595` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) vulkano/src/sync/semaphore.rs:679— vulkano/src/sync/semaphore.rs:679-691 | vulkano/src/sync/semaphore.rs:2001-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. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/semaphore.rs:679` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) vulkano/src/image/sampler/ycbcr.rs:769— vulkano/src/image/sampler/ycbcr.rs:769-781 | vulkano/src/image/sampler/ycbcr.rs:791-803 — 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 `vulkano/src/image/sampler/ycbcr.rs:769` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) vulkano/src/command_buffer/commands/sync.rs:2399— vulkano/src/command_buffer/commands/sync.rs:2399-2411 | vulkano/src/command_buffer/commands/sync.rs:3295-3307 — 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 `vulkano/src/command_buffer/commands/sync.rs:2399` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) vulkano/src/pipeline/shader/validate_runtime.rs:2394— vulkano/src/pipeline/shader/validate_runtime.rs:2394-2406 | vulkano/src/pipeline/shader/validate_runtime.rs:2408-2420 — 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 `vulkano/src/pipeline/shader/validate_runtime.rs:2394` 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) vulkano/src/command_buffer/commands/sync.rs:293— vulkano/src/command_buffer/commands/sync.rs:293-305 | vulkano/src/command_buffer/commands/sync.rs:533-545 — 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 `vulkano/src/command_buffer/commands/sync.rs:293` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano/src/command_buffer/commands/sync.rs:547` calls `iter`, `enumerate` and `vulkano/src/command_buffer/commands/sync.rs:308` 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 (13 lines × 2) vulkano/src/render_pass/mod.rs:3296— vulkano/src/render_pass/mod.rs:3296-3308 | vulkano/src/render_pass/mod.rs:3382-3394 — 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 `vulkano/src/render_pass/mod.rs:3296` 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) vulkano/src/pipeline/graphics/subpass.rs:223— vulkano/src/pipeline/graphics/subpass.rs:223-235 | vulkano/src/pipeline/graphics/subpass.rs:264-276 — 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 `vulkano/src/pipeline/graphics/subpass.rs:223` 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) vulkano/src/sync/fence.rs:725— vulkano/src/sync/fence.rs:725-737 | vulkano/src/sync/fence.rs:1399-1411 — 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 `vulkano/src/sync/fence.rs:725` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) vulkano/src/pipeline/shader/validate_runtime.rs:1607— vulkano/src/pipeline/shader/validate_runtime.rs:1607-1619 | vulkano/src/pipeline/shader/validate_runtime.rs:1633-1645 — 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 `vulkano/src/pipeline/shader/validate_runtime.rs:1607` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) vulkano/src/image/sampler/ycbcr.rs:720— vulkano/src/image/sampler/ycbcr.rs:720-732 | vulkano/src/image/sampler/ycbcr.rs:742-754 — 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 `vulkano/src/image/sampler/ycbcr.rs:720` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) vulkano-shaders/src/lib.rs:1154— vulkano-shaders/src/lib.rs:1154-1163 | vulkano-shaders/src/lib.rs:1532-1541 — 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 `vulkano-shaders/src/lib.rs:1154` it does not close everything it opens, so those exact lines 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) vulkano-taskgraph/src/command_buffer/commands/copy.rs:251— vulkano-taskgraph/src/command_buffer/commands/copy.rs:251-260 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1022-1031 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:251` 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) vulkano-taskgraph/src/graph/execute.rs:1193— vulkano-taskgraph/src/graph/execute.rs:1193-1202 | vulkano-taskgraph/src/graph/execute.rs:1813-1822 — 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 `vulkano-taskgraph/src/graph/execute.rs:1193` it does not close everything it opens, so those exact lines 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) vulkano/src/buffer/mod.rs:763— vulkano/src/buffer/mod.rs:763-772 | vulkano/src/image/mod.rs:775-784 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) vulkano/src/command_buffer/commands/clear.rs:597— vulkano/src/command_buffer/commands/clear.rs:597-606 | vulkano/src/command_buffer/commands/clear.rs:866-875 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) vulkano/src/command_buffer/commands/copy.rs:3130— vulkano/src/command_buffer/commands/copy.rs:3130-3139 | vulkano/src/command_buffer/commands/copy.rs:6873-6882 — 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 (10 lines × 2) vulkano/src/command_buffer/commands/sync.rs:1608— vulkano/src/command_buffer/commands/sync.rs:1608-1617 | vulkano/src/command_buffer/commands/sync.rs:1622-1631 — 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 `vulkano/src/command_buffer/commands/sync.rs:1608` 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, `vulkano/src/command_buffer/commands/sync.rs:1634` calls `enabled_features` and `vulkano/src/command_buffer/commands/sync.rs:1619` 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) vulkano/src/command_buffer/commands/sync.rs:2166— vulkano/src/command_buffer/commands/sync.rs:2166-2175 | vulkano/src/command_buffer/commands/sync.rs:2180-2189 — 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 `vulkano/src/command_buffer/commands/sync.rs:2166` 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, `vulkano/src/command_buffer/commands/sync.rs:2192` calls `enabled_features` and `vulkano/src/command_buffer/commands/sync.rs:2177` 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) vulkano/src/command_buffer/traits.rs:398— vulkano/src/command_buffer/traits.rs:398-407 | vulkano/src/command_buffer/traits.rs:445-454 — 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 `vulkano/src/command_buffer/traits.rs:398` 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 × 2) vulkano/src/memory/allocator/suballocator/free_list.rs:414— vulkano/src/memory/allocator/suballocator/free_list.rs:414-423 | vulkano/src/memory/allocator/suballocator/tlsf.rs:526-535 — before extracting anything, compare `vulkano/src/memory/allocator/suballocator/free_list.rs` and `vulkano/src/memory/allocator/suballocator/tlsf.rs` as WHOLE FILES: this scan already matched 3 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/memory/allocator/suballocator/free_list.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vulkano/src/memory/allocator/suballocator/tlsf.rs:524` calls `dangling` and `vulkano/src/memory/allocator/suballocator/free_list.rs:413` 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) vulkano/src/memory/device_memory.rs:2494— vulkano/src/memory/device_memory.rs:2494-2503 | vulkano/src/memory/device_memory.rs:2550-2559 — 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 (10 lines × 2) vulkano/src/pipeline/graphics/mod.rs:1433— vulkano/src/pipeline/graphics/mod.rs:1433-1442 | vulkano/src/pipeline/graphics/mod.rs:1444-1453 — 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 (10 lines × 2) vulkano/src/pipeline/graphics/mod.rs:2153— vulkano/src/pipeline/graphics/mod.rs:2153-2162 | vulkano/src/pipeline/graphics/mod.rs:2220-2229 — 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 `vulkano/src/pipeline/graphics/mod.rs:2153` it does not close everything it opens, so those exact lines 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) vulkano/src/shader/reflect.rs:993— vulkano/src/shader/reflect.rs:993-1002 | vulkano/src/shader/spirv/specialization.rs:166-175 — 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 `vulkano/src/shader/reflect.rs:993` it does not close everything it opens, so those exact lines 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) vulkano-taskgraph/src/command_buffer/commands/clear.rs:256— vulkano-taskgraph/src/command_buffer/commands/clear.rs:256-265 | vulkano/src/command_buffer/commands/clear.rs:339-348 — 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 `vulkano-taskgraph/src/command_buffer/commands/clear.rs:256` 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) vulkano/src/command_buffer/auto/commands/pipeline.rs:2867— vulkano/src/command_buffer/auto/commands/pipeline.rs:2867-2879 | vulkano/src/pipeline/graphics/input_assembly.rs:137-146 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:2867` it does not close everything it opens, so those 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 (10 lines × 2) vulkano/src/descriptor_set/pool.rs:734— vulkano/src/descriptor_set/pool.rs:734-744 | vulkano/src/device/mod.rs:2225-2234 — 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 `vulkano/src/descriptor_set/pool.rs:734` 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) vulkano/src/command_buffer/commands/copy.rs:4963— vulkano/src/command_buffer/commands/copy.rs:4963-4972 | vulkano/src/command_buffer/commands/copy.rs:6096-6105 — 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 (10 lines × 2) vulkano/src/command_buffer/commands/render_pass.rs:1659— vulkano/src/command_buffer/commands/render_pass.rs:1659-1668 | vulkano/src/command_buffer/commands/render_pass.rs:1783-1792 — 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 `vulkano/src/command_buffer/commands/render_pass.rs:1659` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) vulkano/src/acceleration_structure.rs:1682— vulkano/src/acceleration_structure.rs:1682-1691 | vulkano/src/acceleration_structure.rs:1767-1776 — 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 `vulkano/src/acceleration_structure.rs:1682` 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 × 2) vulkano/src/command_buffer/auto/commands/render_pass.rs:202— vulkano/src/command_buffer/auto/commands/render_pass.rs:202-211 | vulkano/src/command_buffer/auto/commands/render_pass.rs:311-320 — 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 `vulkano/src/command_buffer/auto/commands/render_pass.rs:202` 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 × 2) vulkano/src/command_buffer/commands/copy.rs:5015— vulkano/src/command_buffer/commands/copy.rs:5015-5024 | vulkano/src/command_buffer/commands/copy.rs:6139-6148 — 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 (10 lines × 2) vulkano/src/command_buffer/mod.rs:804— vulkano/src/command_buffer/mod.rs:804-813 | vulkano/src/command_buffer/mod.rs:846-855 — 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 `vulkano/src/command_buffer/mod.rs:804` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:485— vulkano-taskgraph/src/command_buffer/commands/copy.rs:485-499 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:657-671 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:485` it does not close everything it opens, so those exact lines 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) vulkano-taskgraph/src/graph/execute.rs:1840— vulkano-taskgraph/src/graph/execute.rs:1840-1854 | vulkano-taskgraph/src/graph/execute.rs:1860-1874 — 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 `vulkano-taskgraph/src/graph/execute.rs:1840` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) vulkano/src/buffer/mod.rs:897— vulkano/src/buffer/mod.rs:897-911 | vulkano/src/image/mod.rs:945-959 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:897` it does not close everything it opens, so those 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 `self` to `crate) unsafe fn gpu_write_lock(&mut` in one and `crate) unsafe fn gpu_write_lock( &mut` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) vulkano/src/buffer/mod.rs:918— vulkano/src/buffer/mod.rs:918-932 | vulkano/src/image/mod.rs:968-982 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:918` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/allocator.rs:650— vulkano/src/command_buffer/allocator.rs:650-664 | vulkano/src/command_buffer/allocator.rs:689-703 — 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 `vulkano/src/command_buffer/allocator.rs:650` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/auto/commands/render_pass.rs:517— vulkano/src/command_buffer/auto/commands/render_pass.rs:517-531 | vulkano/src/command_buffer/auto/commands/render_pass.rs:569-583 — 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 `vulkano/src/command_buffer/auto/commands/render_pass.rs:517` 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) vulkano/src/device/physical.rs:195— vulkano/src/device/physical.rs:195-209 | vulkano/src/library.rs:211-225 — 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 `vulkano/src/device/physical.rs:195` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) vulkano/src/device/physical.rs:840— vulkano/src/device/physical.rs:840-854 | vulkano/src/device/physical.rs:881-895 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/device/physical.rs:840` 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) vulkano/src/memory/device_memory.rs:223— vulkano/src/memory/device_memory.rs:223-237 | vulkano/src/memory/device_memory.rs:269-283 — 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) vulkano/src/render_pass/mod.rs:3045— vulkano/src/render_pass/mod.rs:3045-3059 | vulkano/src/render_pass/mod.rs:3138-3152 — 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) vulkano/src/render_pass/mod.rs:1167— vulkano/src/render_pass/mod.rs:1167-1181 | vulkano/src/render_pass/mod.rs:1394-1409 — 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 `vulkano/src/render_pass/mod.rs:1167` it does not close everything it opens, so those 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 (15 lines × 2) vulkano/src/render_pass/mod.rs:2419— vulkano/src/render_pass/mod.rs:2419-2433 | vulkano/src/render_pass/mod.rs:2460-2474 — 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) vulkano/src/memory/sparse.rs:1267— vulkano/src/memory/sparse.rs:1267-1281 | vulkano/src/memory/sparse.rs:1283-1297 — 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 `vulkano/src/memory/sparse.rs:1267` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) vulkano/src/sync/semaphore.rs:828— vulkano/src/sync/semaphore.rs:828-842 | vulkano/src/sync/semaphore.rs:2111-2125 — 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 `vulkano/src/sync/semaphore.rs:828` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) vulkano/src/command_buffer/commands/copy.rs:5891— vulkano/src/command_buffer/commands/copy.rs:5891-5905 | vulkano/src/command_buffer/commands/copy.rs:6824-6838 — 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) vulkano/src/pipeline/graphics/mod.rs:1144— vulkano/src/pipeline/graphics/mod.rs:1144-1158 | vulkano/src/pipeline/graphics/mod.rs:1185-1199 — 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 `vulkano/src/pipeline/graphics/mod.rs:1144` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) vulkano/src/memory/sparse.rs:315— vulkano/src/memory/sparse.rs:315-329 | vulkano/src/memory/sparse.rs:769-783 — 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 `vulkano/src/memory/sparse.rs:315` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) vulkano/src/render_pass/mod.rs:2551— vulkano/src/render_pass/mod.rs:2551-2565 | vulkano/src/render_pass/mod.rs:2617-2631 — 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) vulkano/src/command_buffer/commands/sync.rs:1905— vulkano/src/command_buffer/commands/sync.rs:1905-1919 | vulkano/src/command_buffer/commands/sync.rs:2658-2672 — 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 `vulkano/src/command_buffer/commands/sync.rs:1905` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) vulkano/src/command_buffer/commands/render_pass.rs:1362— vulkano/src/command_buffer/commands/render_pass.rs:1362-1376 | vulkano/src/image/sampler/mod.rs:779-793 — 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 `vulkano/src/command_buffer/commands/render_pass.rs:1362` 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) autogen/src/formats.rs:311— autogen/src/formats.rs:311-319 | autogen/src/spirv_reqs.rs:108-116 — before extracting anything, compare `autogen/src/formats.rs` and `autogen/src/spirv_reqs.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/formats.rs:311` 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) vulkano-taskgraph/src/command_buffer/commands/copy.rs:290— vulkano-taskgraph/src/command_buffer/commands/copy.rs:290-298 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1061-1069 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.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.
Duplicated block (9 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:307— vulkano-taskgraph/src/command_buffer/commands/copy.rs:307-315 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1078-1086 — 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) vulkano-taskgraph/src/graph/execute.rs:1464— vulkano-taskgraph/src/graph/execute.rs:1464-1472 | vulkano-taskgraph/src/graph/execute.rs:2098-2106 — 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 `vulkano-taskgraph/src/graph/execute.rs:1464` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/auto/commands/copy.rs:316— vulkano/src/command_buffer/auto/commands/copy.rs:316-324 | vulkano/src/command_buffer/auto/commands/copy.rs:451-459 — 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 `vulkano/src/command_buffer/auto/commands/copy.rs:316` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano/src/command_buffer/auto/commands/copy.rs:326` calls `buffer` and `vulkano/src/command_buffer/auto/commands/copy.rs:461` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) vulkano/src/command_buffer/auto/commands/copy.rs:406— vulkano/src/command_buffer/auto/commands/copy.rs:406-414 | vulkano/src/command_buffer/auto/commands/copy.rs:541-549 — 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 `vulkano/src/command_buffer/auto/commands/copy.rs:406` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano/src/command_buffer/auto/commands/copy.rs:416` calls `buffer` and `vulkano/src/command_buffer/auto/commands/copy.rs:551` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) vulkano/src/command_buffer/commands/sync.rs:837— vulkano/src/command_buffer/commands/sync.rs:837-845 | vulkano/src/command_buffer/mod.rs:1430-1438 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:837` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) vulkano/src/swapchain/acquire_present.rs:84— vulkano/src/swapchain/acquire_present.rs:84-92 | vulkano/src/sync/semaphore.rs:551-559 — 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 (9 lines × 2) vulkano/src/swapchain/acquire_present.rs:84— vulkano/src/swapchain/acquire_present.rs:84-92 | vulkano/src/sync/semaphore.rs:462-470 — 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 (9 lines × 2) vulkano/src/swapchain/mod.rs:848— vulkano/src/swapchain/mod.rs:848-856 | vulkano/src/swapchain/mod.rs:946-955 — 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 `vulkano/src/swapchain/mod.rs:848` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) vulkano/src/swapchain/mod.rs:2716— vulkano/src/swapchain/mod.rs:2716-2724 | vulkano/src/swapchain/surface.rs:2868-2876 — before extracting anything, compare `vulkano/src/swapchain/mod.rs` and `vulkano/src/swapchain/surface.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) autogen/src/features.rs:748— autogen/src/features.rs:748-756 | autogen/src/properties.rs:581-589 — before extracting anything, compare `autogen/src/features.rs` and `autogen/src/properties.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/features.rs:748` 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) vulkano-taskgraph/src/command_buffer/commands/sync.rs:307— vulkano-taskgraph/src/command_buffer/commands/sync.rs:307-315 | vulkano/src/command_buffer/commands/sync.rs:1095-1103 — 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 (9 lines × 2) vulkano/src/command_buffer/auto/commands/pipeline.rs:186— vulkano/src/command_buffer/auto/commands/pipeline.rs:186-194 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1433-1441 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `indirect_buffer` to `Subbuffer<[DispatchIndirectCommand]>` in one and `Subbuffer<[DrawMeshTasksIndirectCommand]>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) vulkano/src/pipeline/graphics/depth_stencil.rs:134— vulkano/src/pipeline/graphics/depth_stencil.rs:134-142 | vulkano/src/pipeline/graphics/depth_stencil.rs:145-153 — 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 `vulkano/src/pipeline/graphics/depth_stencil.rs:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vulkano/src/pipeline/graphics/depth_stencil.rs:132` calls `enabled_extensions` and `vulkano/src/pipeline/graphics/depth_stencil.rs:142` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) vulkano/src/command_buffer/mod.rs:790— vulkano/src/command_buffer/mod.rs:790-798 | vulkano/src/command_buffer/mod.rs:832-840 — 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 `vulkano/src/command_buffer/mod.rs:790` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) vulkano/src/render_pass/mod.rs:3081— vulkano/src/render_pass/mod.rs:3081-3089 | vulkano/src/render_pass/mod.rs:3564-3572 — 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 `vulkano/src/render_pass/mod.rs:3564` it does not close everything it opens, so those exact lines 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) autogen/src/features.rs:778— autogen/src/features.rs:778-789 | autogen/src/properties.rs:770-781 — before extracting anything, compare `autogen/src/features.rs` and `autogen/src/properties.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:700— vulkano-taskgraph/src/command_buffer/commands/copy.rs:700-711 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1126-1137 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:700` 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, `vulkano-taskgraph/src/command_buffer/commands/copy.rs:1138` calls `into` and `vulkano-taskgraph/src/command_buffer/commands/copy.rs:712` 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) vulkano-taskgraph/src/command_buffer/commands/copy.rs:933— vulkano-taskgraph/src/command_buffer/commands/copy.rs:933-944 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1129-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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:933` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano-taskgraph/src/command_buffer/commands/copy.rs:945` calls `into` and `vulkano-taskgraph/src/command_buffer/commands/copy.rs:1141` 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) vulkano-taskgraph/src/slotmap.rs:412— vulkano-taskgraph/src/slotmap.rs:412-423 | vulkano-taskgraph/src/slotmap.rs:432-443 — 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 `vulkano-taskgraph/src/slotmap.rs:412` 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) vulkano-taskgraph/src/slotmap.rs:461— vulkano-taskgraph/src/slotmap.rs:461-472 | vulkano-taskgraph/src/slotmap.rs:481-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 `vulkano-taskgraph/src/slotmap.rs:461` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) vulkano/src/buffer/sys.rs:230— vulkano/src/buffer/sys.rs:230-241 | vulkano/src/image/sys.rs:347-358 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) vulkano/src/command_buffer/auto/commands/copy.rs:1353— vulkano/src/command_buffer/auto/commands/copy.rs:1353-1364 | vulkano/src/command_buffer/commands/copy.rs:4700-4711 — before extracting anything, compare `vulkano/src/command_buffer/auto/commands/copy.rs` and `vulkano/src/command_buffer/commands/copy.rs` as WHOLE FILES: this scan already matched 5 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 `vulkano/src/command_buffer/auto/commands/copy.rs:1353` it does not close everything it opens, so those exact lines 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) vulkano/src/swapchain/mod.rs:1775— vulkano/src/swapchain/mod.rs:1775-1786 | vulkano/src/sync/semaphore.rs:462-473 — 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 `vulkano/src/swapchain/mod.rs:1775` 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, `vulkano/src/sync/semaphore.rs:459` calls `validate`, `map_err`, `add_context` and `vulkano/src/swapchain/mod.rs:1773` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) vulkano/src/render_pass/mod.rs:3455— vulkano/src/render_pass/mod.rs:3455-3466 | vulkano/src/render_pass/mod.rs:3484-3495 — 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 `vulkano/src/render_pass/mod.rs:3455` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/mod.rs:742— vulkano/src/command_buffer/mod.rs:742-753 | vulkano/src/pipeline/graphics/subpass.rs:168-179 — before extracting anything, compare `vulkano/src/command_buffer/mod.rs` and `vulkano/src/pipeline/graphics/subpass.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 `vulkano/src/command_buffer/mod.rs:742` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) vulkano/src/command_buffer/commands/copy.rs:6233— vulkano/src/command_buffer/commands/copy.rs:6233-6244 | vulkano/src/command_buffer/commands/copy.rs:6436-6447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) vulkano/src/command_buffer/auto/commands/render_pass.rs:1433— vulkano/src/command_buffer/auto/commands/render_pass.rs:1433-1444 | vulkano/src/format.rs:452-463 — 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 `vulkano/src/command_buffer/auto/commands/render_pass.rs:1433` 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) vulkano/src/command_buffer/commands/copy.rs:3068— vulkano/src/command_buffer/commands/copy.rs:3068-3079 | vulkano/src/memory/sparse.rs:1572-1583 — before extracting anything, compare `vulkano/src/command_buffer/commands/copy.rs` and `vulkano/src/memory/sparse.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/memory/sparse.rs:1572` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) vulkano/src/command_buffer/commands/copy.rs:1619— vulkano/src/command_buffer/commands/copy.rs:1619-1630 | vulkano/src/command_buffer/commands/copy.rs:3273-3284 — 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 `vulkano/src/command_buffer/commands/copy.rs:1619` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) vulkano/src/sync/fence.rs:1387— vulkano/src/sync/fence.rs:1387-1398 | vulkano/src/sync/semaphore.rs:2098-2109 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/fence.rs:1387` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) vulkano/src/sync/fence.rs:1283— vulkano/src/sync/fence.rs:1283-1294 | vulkano/src/sync/semaphore.rs:1989-2000 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/fence.rs:1283` 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.
TooManyMethods: RecordingCommandBuffer vulkano/src/command_buffer/sys.rs:24— TooManyMethods — 364 methods, declared across 13 files: commands/dynamic_state.rs (126), commands/pipeline.rs (52), commands/bind_push.rs (29), commands/acceleration_structure.rs (24), +9 more file(s). The bar is 30 methods; this is 334 over it, 12.13× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AutoCommandBufferBuilder vulkano/src/command_buffer/auto/builder.rs:65— TooManyMethods — 265 methods, declared across 11 files: commands/dynamic_state.rs (97), commands/pipeline.rs (48), commands/bind_push.rs (23), commands/copy.rs (18), +7 more file(s). The bar is 30 methods; this is 235 over it, 8.83× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RecordingCommandBuffer vulkano-taskgraph/src/command_buffer/mod.rs:32— TooManyMethods — 193 methods, declared across 8 files: commands/dynamic_state.rs (96), commands/pipeline.rs (39), commands/copy.rs (18), commands/bind_push.rs (16), +4 more file(s). The bar is 30 methods; this is 163 over it, 6.43× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PhysicalDevice vulkano/src/device/physical.rs:61— TooManyMethods — 109 methods. The bar is 30 methods; this is 79 over it, 3.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Surface vulkano/src/swapchain/surface.rs:38— TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Device vulkano/src/device/mod.rs:171— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Swapchain vulkano/src/swapchain/mod.rs:378— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Resources vulkano-taskgraph/src/resource/mod.rs:46— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Semaphore vulkano/src/sync/semaphore.rs:85— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Fence vulkano/src/sync/fence.rs:52— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DeviceMemory vulkano/src/memory/device_memory.rs:47— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RawImage vulkano/src/image/sys.rs:50— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Image vulkano/src/image/mod.rs:104— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Subbuffer vulkano/src/buffer/subbuffer.rs:56— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GlobalDescriptorSet vulkano-taskgraph/src/descriptor_set.rs:252— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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) vulkano-taskgraph/src/command_buffer/commands/copy.rs:281— vulkano-taskgraph/src/command_buffer/commands/copy.rs:281-287 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1052-1058 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:281` 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) vulkano-taskgraph/src/graph/execute.rs:1029— vulkano-taskgraph/src/graph/execute.rs:1029-1035 | vulkano-taskgraph/src/graph/execute.rs:1210-1216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/graph/execute.rs:1029` 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) vulkano/src/buffer/mod.rs:857— vulkano/src/buffer/mod.rs:857-863 | vulkano/src/image/mod.rs:885-891 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:857` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/auto/commands/copy.rs:263— vulkano/src/command_buffer/auto/commands/copy.rs:263-269 | vulkano/src/command_buffer/auto/commands/copy.rs:817-823 — 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 `vulkano/src/command_buffer/auto/commands/copy.rs:263` 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) vulkano/src/command_buffer/auto/commands/pipeline.rs:458— vulkano/src/command_buffer/auto/commands/pipeline.rs:458-464 | vulkano/src/command_buffer/auto/commands/pipeline.rs:589-595 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:458` 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) vulkano/src/instance/mod.rs:1152— vulkano/src/instance/mod.rs:1152-1158 | vulkano/src/instance/mod.rs:1204-1210 — 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 `vulkano/src/instance/mod.rs:1152` 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) vulkano/src/memory/allocator/suballocator/buddy.rs:566— vulkano/src/memory/allocator/suballocator/buddy.rs:566-572 | vulkano/src/memory/allocator/suballocator/buddy.rs:631-637 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:1728— vulkano-taskgraph/src/command_buffer/commands/copy.rs:1728-1734 | vulkano/src/command_buffer/commands/copy.rs:6925-6931 — before extracting anything, compare `vulkano-taskgraph/src/command_buffer/commands/copy.rs` and `vulkano/src/command_buffer/commands/copy.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire 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) vulkano/src/buffer/mod.rs:714— vulkano/src/buffer/mod.rs:714-720 | vulkano/src/image/mod.rs:724-730 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) vulkano/src/buffer/sys.rs:884— vulkano/src/buffer/sys.rs:884-890 | vulkano/src/image/sys.rs:2517-2523 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:884` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) vulkano/src/swapchain/mod.rs:2519— vulkano/src/swapchain/mod.rs:2519-2525 | vulkano/src/swapchain/mod.rs:2541-2547 — 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 `vulkano/src/swapchain/mod.rs:2519` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) vulkano/src/command_buffer/mod.rs:1046— vulkano/src/command_buffer/mod.rs:1046-1052 | vulkano/src/command_buffer/mod.rs:1057-1063 — 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 `vulkano/src/command_buffer/mod.rs:1046` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) vulkano/src/buffer/sys.rs:833— vulkano/src/buffer/sys.rs:833-839 | vulkano/src/image/sys.rs:1899-1905 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:833` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) vulkano/src/descriptor_set/layout.rs:832— vulkano/src/descriptor_set/layout.rs:832-838 | vulkano/src/image/sys.rs:2373-2379 — 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 `vulkano/src/descriptor_set/layout.rs:832` 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) vulkano-shaders/src/shaders.rs:427— vulkano-shaders/src/shaders.rs:427-433 | vulkano-shaders/src/shaders.rs:444-450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-shaders/src/shaders.rs:427` 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.
RecordingCommandBuffer::validate_copy_image (cognitive 94) vulkano/src/command_buffer/commands/copy.rs:118— RecordingCommandBuffer::validate_copy_image has cognitive complexity 94 (threshold 15). Drivers by points: if/else 19 (70 pts), loops 5 (22 pts), boolean chains 2 (nesting depth added 68). 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.
RecordingCommandBuffer::validate_build_acceleration_structure (cognitive 70) vulkano/src/command_buffer/commands/acceleration_structure.rs:41— RecordingCommandBuffer::validate_build_acceleration_structure has cognitive complexity 70 (threshold 15). Drivers by points: if/else 25 (66 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 42). 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.
RecordingCommandBuffer::validate_copy_buffer_to_image (cognitive 66) vulkano/src/command_buffer/commands/copy.rs:476— RecordingCommandBuffer::validate_copy_buffer_to_image has cognitive complexity 66 (threshold 15). Drivers by points: if/else 15 (51 pts), loops 3 (12 pts), boolean chains 3 (nesting depth added 45). 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.
RecordingCommandBuffer::validate_copy_image_to_buffer (cognitive 58) vulkano/src/command_buffer/commands/copy.rs:761— RecordingCommandBuffer::validate_copy_image_to_buffer has cognitive complexity 58 (threshold 15). Drivers by points: if/else 13 (43 pts), loops 3 (12 pts), boolean chains 3 (nesting depth added 39). 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.
RecordingCommandBuffer::validate_begin_render_pass (cognitive 54) vulkano/src/command_buffer/commands/render_pass.rs:38— RecordingCommandBuffer::validate_begin_render_pass has cognitive complexity 54 (threshold 15). Drivers by points: if/else 12 (42 pts), loops 4 (6 pts), match/switch 2 (6 pts) (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.
RecordingCommandBuffer::validate_build_acceleration_structure_indirect (cognitive 46) vulkano/src/command_buffer/commands/acceleration_structure.rs:510— RecordingCommandBuffer::validate_build_acceleration_structure_indirect has cognitive complexity 46 (threshold 15). Drivers by points: if/else 20 (42 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (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.
RecordingCommandBuffer::validate_reset_event (cognitive 40) vulkano/src/command_buffer/commands/sync.rs:805— RecordingCommandBuffer::validate_reset_event has cognitive complexity 40 (threshold 15). Drivers by points: if/else 26 (38 pts), boolean chains 2 (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.
RecordingCommandBuffer::validate_write_timestamp (cognitive 29) vulkano/src/command_buffer/commands/query.rs:287— RecordingCommandBuffer::validate_write_timestamp has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 2, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RecordingCommandBuffer::validate_bind_descriptor_sets (cognitive 26) vulkano/src/command_buffer/commands/bind_push.rs:69— RecordingCommandBuffer::validate_bind_descriptor_sets has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (7 pts), match/switch 2 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RecordingCommandBuffer::validate_wait_events (cognitive 26) vulkano/src/command_buffer/commands/sync.rs:526— RecordingCommandBuffer::validate_wait_events has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 4 (7 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RecordingCommandBuffer::validate_bind_vertex_buffers (cognitive 20) vulkano/src/command_buffer/commands/bind_push.rs:614— RecordingCommandBuffer::validate_bind_vertex_buffers has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RecordingCommandBuffer::validate_begin_query (cognitive 18) vulkano/src/command_buffer/commands/query.rs:36— RecordingCommandBuffer::validate_begin_query has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, match/switch 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.
RecordingCommandBuffer::validate_set_event (cognitive 17) vulkano/src/command_buffer/commands/sync.rs:285— RecordingCommandBuffer::validate_set_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (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.
RecordingCommandBuffer::validate_pipeline_barrier (cognitive 16) vulkano/src/command_buffer/commands/sync.rs:33— RecordingCommandBuffer::validate_pipeline_barrier has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (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.
FunctionTooLong: autogen::formats::formats_output autogen/src/formats.rs:57— FunctionTooLong — autogen::formats::formats_output runs 331 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 231 over it, 3.31× 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: vulkano::shader::reflect::inspect_entry_point vulkano/src/shader/reflect.rs:110— FunctionTooLong — vulkano::shader::reflect::inspect_entry_point runs 305 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 205 over it, 3.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: autogen::formats::formats_members autogen/src/formats.rs:632— FunctionTooLong — autogen::formats::formats_members runs 257 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 157 over it, 2.57× 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: autogen::spirv_parse::instruction_output autogen/src/spirv_parse.rs:115— FunctionTooLong — autogen::spirv_parse::instruction_output runs 245 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 145 over it, 2.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: vulkano::sync::future::queue_submit vulkano/src/sync/future/mod.rs:631— FunctionTooLong — vulkano::sync::future::queue_submit 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.
FunctionTooLong: vulkano::shader::spirv::specialization::replace_specialization_instructions vulkano/src/shader/spirv/specialization.rs:11— FunctionTooLong — vulkano::shader::spirv::specialization::replace_specialization_instructions runs 173 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 73 over it, 1.73× 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: vulkano::shader::reflect::descriptor_binding_requirements_of vulkano/src/shader/reflect.rs:592— FunctionTooLong — vulkano::shader::reflect::descriptor_binding_requirements_of runs 166 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 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: vulkano::shader::spirv::specialization::evaluate_spec_constant_op vulkano/src/shader/spirv/specialization.rs:300— FunctionTooLong — vulkano::shader::spirv::specialization::evaluate_spec_constant_op runs 161 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 61 over it, 1.61× 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: vulkano_taskgraph::graph::compile::create_render_pass vulkano-taskgraph/src/graph/compile.rs:1220— FunctionTooLong — vulkano_taskgraph::graph::compile::create_render_pass 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.
FunctionTooLong: vulkano::shader::spirv::specialization::evaluate_spec_constant_calculation_op vulkano/src/shader/spirv/specialization.rs:531— FunctionTooLong — vulkano::shader::spirv::specialization::evaluate_spec_constant_calculation_op runs 138 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 38 over it, 1.38× 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: vulkano::pipeline::shader::inout_interface::validate_interfaces_compatible vulkano/src/pipeline/shader/inout_interface.rs:13— FunctionTooLong — vulkano::pipeline::shader::inout_interface::validate_interfaces_compatible runs 126 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 26 over it, 1.26× 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: autogen::spirv_reqs::spirv_reqs_output autogen/src/spirv_reqs.rs:65— FunctionTooLong — autogen::spirv_reqs::spirv_reqs_output runs 123 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 23 over it, 1.23× 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: vulkano::pipeline::shader::inout_interface::are_interface_types_compatible vulkano/src/pipeline/shader/inout_interface.rs:254— FunctionTooLong — vulkano::pipeline::shader::inout_interface::are_interface_types_compatible runs 121 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 21 over it, 1.21× 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: vulkano_macros::derive_buffer_contents::derive_buffer_contents vulkano-macros/src/derive_buffer_contents.rs:9— FunctionTooLong — vulkano_macros::derive_buffer_contents::derive_buffer_contents 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.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×13
Edited copy of a member (1 corresponding lines) vulkano/src/pipeline/mod.rs:996— vulkano/src/pipeline/mod.rs:996-996 | vulkano/src/sync/pipeline.rs:15-15 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/format.rs:1144— vulkano/src/format.rs:1144-1144 | vulkano/src/sync/pipeline.rs:15-15 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/image/aspect.rs:3— vulkano/src/image/aspect.rs:3-3 | vulkano/src/image/mod.rs:1134-1134 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/memory/device_memory.rs:1605— vulkano/src/memory/device_memory.rs:1605-1605 | vulkano/src/query.rs:632-632 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/device/queue.rs:1274— vulkano/src/device/queue.rs:1274-1274 | vulkano/src/memory/mod.rs:661-661 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/sync/fence.rs:1180— vulkano/src/sync/fence.rs:1180-1180 | vulkano/src/sync/semaphore.rs:1588-1588 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/display.rs:829— vulkano/src/display.rs:829-829 | vulkano/src/swapchain/surface.rs:2485-2485 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/descriptor_set/pool.rs:810— vulkano/src/descriptor_set/pool.rs:810-810 | vulkano/src/image/sampler/mod.rs:1422-1422 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/buffer/mod.rs:945— vulkano/src/buffer/mod.rs:945-945 | vulkano/src/command_buffer/pool.rs:550-550 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/render_pass/mod.rs:4780— vulkano/src/render_pass/mod.rs:4780-4780 | vulkano/src/swapchain/mod.rs:2865-2865 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/image/sampler/mod.rs:1379— vulkano/src/image/sampler/mod.rs:1379-1379 | vulkano/src/pipeline/mod.rs:741-741 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/descriptor_set/layout.rs:32— vulkano/src/descriptor_set/layout.rs:32-32 | vulkano/src/render_pass/mod.rs:121-121 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) vulkano/src/sync/fence.rs:1225— vulkano/src/sync/fence.rs:1225-1225 | vulkano/src/sync/semaphore.rs:1931-1931 — These two members are one piece of code written twice and then edited apart: 1 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) autogen/src/formats.rs:325— autogen/src/formats.rs:325-340 | autogen/src/spirv_reqs.rs:121-136 — before extracting anything, compare `autogen/src/formats.rs` and `autogen/src/spirv_reqs.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/formats.rs:325` 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) vulkano-taskgraph/src/command_buffer/commands/copy.rs:260— vulkano-taskgraph/src/command_buffer/commands/copy.rs:260-275 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:331-346 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:260` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) vulkano/src/buffer/sys.rs:333— vulkano/src/buffer/sys.rs:333-348 | vulkano/src/image/sys.rs:674-689 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:333` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) vulkano/src/command_buffer/auto/commands/pipeline.rs:272— vulkano/src/command_buffer/auto/commands/pipeline.rs:272-287 | vulkano/src/command_buffer/auto/commands/pipeline.rs:767-782 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:272` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/commands/copy.rs:5909— vulkano/src/command_buffer/commands/copy.rs:5909-5924 | vulkano/src/command_buffer/commands/copy.rs:5956-5971 — 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 (16 lines × 2) vulkano/src/image/mod.rs:1606— vulkano/src/image/mod.rs:1606-1621 | vulkano/src/image/mod.rs:1786-1801 — 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 (16 lines × 2) vulkano/src/sync/future/fence_signal.rs:298— vulkano/src/sync/future/fence_signal.rs:298-313 | vulkano/src/sync/future/semaphore_signal.rs:134-149 — before extracting anything, compare `vulkano/src/sync/future/fence_signal.rs` and `vulkano/src/sync/future/semaphore_signal.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/future/fence_signal.rs:298` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) vulkano/src/sync/future/mod.rs:694— vulkano/src/sync/future/mod.rs:694-709 | vulkano/src/sync/future/mod.rs:742-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. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/future/mod.rs:694` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) vulkano/src/command_buffer/auto/commands/pipeline.rs:3085— vulkano/src/command_buffer/auto/commands/pipeline.rs:3085-3100 | vulkano/src/command_buffer/auto/commands/pipeline.rs:3303-3319 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:3085` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) vulkano/src/memory/sparse.rs:695— vulkano/src/memory/sparse.rs:695-710 | vulkano/src/memory/sparse.rs:727-742 — 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 `vulkano/src/memory/sparse.rs:695` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) vulkano/src/command_buffer/commands/render_pass.rs:1618— vulkano/src/command_buffer/commands/render_pass.rs:1618-1633 | vulkano/src/command_buffer/commands/render_pass.rs:1742-1757 — 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 (16 lines × 2) vulkano/src/descriptor_set/update.rs:2007— vulkano/src/descriptor_set/update.rs:2007-2022 | vulkano/src/descriptor_set/update.rs:2035-2050 — 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 `vulkano/src/descriptor_set/update.rs:2007` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) vulkano/src/render_pass/mod.rs:2507— vulkano/src/render_pass/mod.rs:2507-2522 | vulkano/src/render_pass/mod.rs:2531-2546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) vulkano-taskgraph/src/command_buffer/commands/sync.rs:61— vulkano-taskgraph/src/command_buffer/commands/sync.rs:61-77 | vulkano-taskgraph/src/command_buffer/commands/sync.rs:159-175 — 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 `vulkano-taskgraph/src/command_buffer/commands/sync.rs:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano-taskgraph/src/command_buffer/commands/sync.rs:177` calls `into` and `vulkano-taskgraph/src/command_buffer/commands/sync.rs:79` 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) vulkano/src/command_buffer/auto/commands/clear.rs:66— vulkano/src/command_buffer/auto/commands/clear.rs:66-82 | vulkano/src/command_buffer/auto/commands/clear.rs:147-163 — 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 `vulkano/src/command_buffer/auto/commands/clear.rs:66` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/auto/commands/copy.rs:1333— vulkano/src/command_buffer/auto/commands/copy.rs:1333-1349 | vulkano/src/command_buffer/commands/copy.rs:4680-4696 — before extracting anything, compare `vulkano/src/command_buffer/auto/commands/copy.rs` and `vulkano/src/command_buffer/commands/copy.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) vulkano/src/command_buffer/auto/commands/render_pass.rs:1335— vulkano/src/command_buffer/auto/commands/render_pass.rs:1335-1351 | vulkano/src/command_buffer/commands/render_pass.rs:2092-2108 — before extracting anything, compare `vulkano/src/command_buffer/auto/commands/render_pass.rs` and `vulkano/src/command_buffer/commands/render_pass.rs` as WHOLE FILES: this scan already matched 5 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `image_view` to `Arc<ImageView>` in one and `&'a ImageView` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) vulkano/src/descriptor_set/update.rs:402— vulkano/src/descriptor_set/update.rs:402-418 | vulkano/src/descriptor_set/update.rs:549-565 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) vulkano/src/device/physical.rs:1893— vulkano/src/device/physical.rs:1893-1909 | vulkano/src/device/physical.rs:2101-2117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) vulkano/src/memory/sparse.rs:556— vulkano/src/memory/sparse.rs:556-572 | vulkano/src/memory/sparse.rs:1027-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 `vulkano/src/memory/sparse.rs:556` 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) vulkano/src/memory/sparse.rs:609— vulkano/src/memory/sparse.rs:609-625 | vulkano/src/memory/sparse.rs:1085-1101 — 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 (17 lines × 2) vulkano/src/pipeline/graphics/mod.rs:817— vulkano/src/pipeline/graphics/mod.rs:817-836 | vulkano/src/render_pass/mod.rs:2280-2296 — 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 `vulkano/src/pipeline/graphics/mod.rs:817` 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) vulkano/src/swapchain/mod.rs:670— vulkano/src/swapchain/mod.rs:670-686 | vulkano/src/swapchain/mod.rs:692-708 — 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 `vulkano/src/swapchain/mod.rs:670` 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) vulkano/src/command_buffer/commands/sync.rs:183— vulkano/src/command_buffer/commands/sync.rs:183-199 | vulkano/src/command_buffer/commands/sync.rs:447-463 — 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 `vulkano/src/command_buffer/commands/sync.rs:183` 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) vulkano/src/render_pass/mod.rs:3029— vulkano/src/render_pass/mod.rs:3029-3045 | vulkano/src/render_pass/mod.rs:3525-3541 — 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 `vulkano/src/render_pass/mod.rs:3525` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) vulkano/src/command_buffer/commands/copy.rs:2903— vulkano/src/command_buffer/commands/copy.rs:2903-2916 | vulkano/src/command_buffer/commands/copy.rs:6668-6681 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) vulkano/src/command_buffer/commands/copy.rs:3161— vulkano/src/command_buffer/commands/copy.rs:3161-3174 | vulkano/src/command_buffer/commands/copy.rs:6904-6917 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) vulkano/src/command_buffer/commands/sync.rs:2422— vulkano/src/command_buffer/commands/sync.rs:2422-2435 | vulkano/src/command_buffer/commands/sync.rs:3318-3331 — 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 `vulkano/src/command_buffer/commands/sync.rs:2422` it does not close everything it opens, so those exact lines 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) vulkano/src/descriptor_set/allocator.rs:442— vulkano/src/descriptor_set/allocator.rs:442-455 | vulkano/src/descriptor_set/allocator.rs:682-695 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) vulkano/src/memory/allocator/mod.rs:1395— vulkano/src/memory/allocator/mod.rs:1395-1408 | vulkano/src/memory/allocator/mod.rs:1528-1541 — 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 `vulkano/src/memory/allocator/mod.rs:1395` 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) vulkano-taskgraph/src/graph/execute.rs:1219— vulkano-taskgraph/src/graph/execute.rs:1219-1232 | vulkano-taskgraph/src/graph/execute.rs:1238-1251 — 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 `vulkano-taskgraph/src/graph/execute.rs:1219` 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) vulkano/src/command_buffer/auto/commands/render_pass.rs:1384— vulkano/src/command_buffer/auto/commands/render_pass.rs:1384-1397 | vulkano/src/command_buffer/commands/render_pass.rs:2284-2297 — before extracting anything, compare `vulkano/src/command_buffer/auto/commands/render_pass.rs` and `vulkano/src/command_buffer/commands/render_pass.rs` as WHOLE FILES: this scan already matched 5 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `image_view` to `Arc<ImageView>` in one and `&'a ImageView` 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 (14 lines × 2) vulkano/src/pipeline/graphics/mod.rs:820— vulkano/src/pipeline/graphics/mod.rs:820-836 | vulkano/src/pipeline/ray_tracing.rs:505-518 — before extracting anything, compare `vulkano/src/pipeline/graphics/mod.rs` and `vulkano/src/pipeline/ray_tracing.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/pipeline/graphics/mod.rs:820` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `device` to `&Device` in one and `&Arc<Device>` 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 (14 lines × 2) vulkano/src/descriptor_set/update.rs:355— vulkano/src/descriptor_set/update.rs:355-369 | vulkano/src/descriptor_set/update.rs:1327-1340 — 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 `vulkano/src/descriptor_set/update.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) vulkano/src/command_buffer/auto/commands/pipeline.rs:84— vulkano/src/command_buffer/auto/commands/pipeline.rs:84-97 | vulkano/src/command_buffer/auto/commands/pipeline.rs:157-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/auto/commands/pipeline.rs:84` 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) vulkano/src/pipeline/graphics/mod.rs:1016— vulkano/src/pipeline/graphics/mod.rs:1016-1029 | vulkano/src/pipeline/graphics/mod.rs:1106-1119 — 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 `vulkano/src/pipeline/graphics/mod.rs:1016` 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 × 2) vulkano/src/pipeline/compute.rs:309— vulkano/src/pipeline/compute.rs:309-322 | vulkano/src/pipeline/graphics/mod.rs:840-853 — before extracting anything, compare `vulkano/src/pipeline/compute.rs` and `vulkano/src/pipeline/graphics/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/pipeline/compute.rs:309` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/auto/commands/pipeline.rs:734— vulkano/src/command_buffer/auto/commands/pipeline.rs:734-740 | vulkano/src/command_buffer/auto/commands/pipeline.rs:950-956 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1096-1102 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:734` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/commands/sync.rs:1436— vulkano/src/command_buffer/commands/sync.rs:1436-1442 | vulkano/src/command_buffer/commands/sync.rs:1994-2000 | vulkano/src/command_buffer/commands/sync.rs:2747-2753 — 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 `vulkano/src/command_buffer/commands/sync.rs:1436` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1494— vulkano/src/command_buffer/commands/sync.rs:1494-1500 | vulkano/src/command_buffer/commands/sync.rs:2052-2058 | vulkano/src/command_buffer/commands/sync.rs:2805-2811 — 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 `vulkano/src/command_buffer/commands/sync.rs:1494` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1518— vulkano/src/command_buffer/commands/sync.rs:1518-1524 | vulkano/src/command_buffer/commands/sync.rs:2076-2082 | vulkano/src/command_buffer/commands/sync.rs:2829-2835 — 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 `vulkano/src/command_buffer/commands/sync.rs:1518` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1542— vulkano/src/command_buffer/commands/sync.rs:1542-1548 | vulkano/src/command_buffer/commands/sync.rs:2100-2106 | vulkano/src/command_buffer/commands/sync.rs:2853-2859 — 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 `vulkano/src/command_buffer/commands/sync.rs:1542` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1566— vulkano/src/command_buffer/commands/sync.rs:1566-1572 | vulkano/src/command_buffer/commands/sync.rs:2124-2130 | vulkano/src/command_buffer/commands/sync.rs:2877-2883 — 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 `vulkano/src/command_buffer/commands/sync.rs:1566` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1590— vulkano/src/command_buffer/commands/sync.rs:1590-1596 | vulkano/src/command_buffer/commands/sync.rs:2148-2154 | vulkano/src/command_buffer/commands/sync.rs:2901-2907 — 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 `vulkano/src/command_buffer/commands/sync.rs:1590` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1646— vulkano/src/command_buffer/commands/sync.rs:1646-1652 | vulkano/src/command_buffer/commands/sync.rs:2204-2210 | vulkano/src/command_buffer/commands/sync.rs:2957-2963 — 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 `vulkano/src/command_buffer/commands/sync.rs:1646` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1670— vulkano/src/command_buffer/commands/sync.rs:1670-1676 | vulkano/src/command_buffer/commands/sync.rs:2228-2234 | vulkano/src/command_buffer/commands/sync.rs:2981-2987 — 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 `vulkano/src/command_buffer/commands/sync.rs:1670` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1696— vulkano/src/command_buffer/commands/sync.rs:1696-1702 | vulkano/src/command_buffer/commands/sync.rs:2254-2260 | vulkano/src/command_buffer/commands/sync.rs:3007-3013 — 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 `vulkano/src/command_buffer/commands/sync.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/descriptor_set/update.rs:926— vulkano/src/descriptor_set/update.rs:926-932 | vulkano/src/descriptor_set/update.rs:979-985 | vulkano/src/descriptor_set/update.rs:1391-1397 — 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 `vulkano/src/descriptor_set/update.rs:926` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) vulkano/src/sync/future/join.rs:176— vulkano/src/sync/future/join.rs:176-182 | vulkano/src/sync/future/join.rs:209-215 | vulkano/src/sync/future/join.rs:237-243 — 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 `vulkano/src/sync/future/join.rs:176` it does not close everything it opens, so those exact lines 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) autogen/src/extensions.rs:953— autogen/src/extensions.rs:953-965 | autogen/src/formats.rs:321-333 | autogen/src/spirv_reqs.rs:117-129 — before extracting anything, compare `autogen/src/formats.rs` and `autogen/src/spirv_reqs.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/extensions.rs:953` it does not close everything it opens, so those exact lines 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) vulkano-taskgraph/src/graph/execute.rs:2681— vulkano-taskgraph/src/graph/execute.rs:2681-2693 | vulkano-taskgraph/src/graph/execute.rs:2758-2770 | vulkano-taskgraph/src/graph/execute.rs:2836-2848 — 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 `vulkano-taskgraph/src/graph/execute.rs:2681` 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 `virtual_id` to `Id<Buffer>` in one and `Id<Image>` 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 (13 lines × 3) vulkano/src/command_buffer/commands/copy.rs:157— vulkano/src/command_buffer/commands/copy.rs:157-169 | vulkano/src/command_buffer/commands/copy.rs:507-519 | vulkano/src/command_buffer/commands/copy.rs:792-804 — 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 `vulkano/src/command_buffer/commands/copy.rs:157` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/commands/copy.rs:3167— vulkano/src/command_buffer/commands/copy.rs:3167-3179 | vulkano/src/command_buffer/commands/copy.rs:4848-4860 | vulkano/src/command_buffer/commands/copy.rs:6910-6922 — 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 (13 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1448— vulkano/src/command_buffer/commands/sync.rs:1448-1460 | vulkano/src/command_buffer/commands/sync.rs:2006-2018 | vulkano/src/command_buffer/commands/sync.rs:2759-2771 — 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 `vulkano/src/command_buffer/commands/sync.rs:1448` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 3) vulkano/src/swapchain/acquire_present.rs:1227— vulkano/src/swapchain/acquire_present.rs:1227-1239 | vulkano/src/sync/future/fence_signal.rs:300-312 | vulkano/src/sync/future/semaphore_signal.rs:136-148 — before extracting anything, compare `vulkano/src/sync/future/fence_signal.rs` and `vulkano/src/sync/future/semaphore_signal.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/swapchain/acquire_present.rs:1227` 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) vulkano/src/render_pass/mod.rs:3090— vulkano/src/render_pass/mod.rs:3090-3102 | vulkano/src/render_pass/mod.rs:3188-3204 | vulkano/src/render_pass/mod.rs:3573-3585 — 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 `vulkano/src/render_pass/mod.rs:3573` 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) vulkano/src/render_pass/mod.rs:1086— vulkano/src/render_pass/mod.rs:1086-1098 | vulkano/src/render_pass/mod.rs:1172-1186 | vulkano/src/render_pass/mod.rs:1547-1559 — 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 `vulkano/src/render_pass/mod.rs:1086` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 3) vulkano/src/pipeline/graphics/color_blend.rs:845— vulkano/src/pipeline/graphics/color_blend.rs:845-857 | vulkano/src/pipeline/graphics/color_blend.rs:862-874 | vulkano/src/pipeline/graphics/color_blend.rs:879-891 — 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 `vulkano/src/pipeline/graphics/color_blend.rs:845` 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) vulkano/src/command_buffer/commands/sync.rs:590— vulkano/src/command_buffer/commands/sync.rs:590-602 | vulkano/src/command_buffer/commands/sync.rs:635-647 | vulkano/src/command_buffer/commands/sync.rs:680-692 — 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 `vulkano/src/command_buffer/commands/sync.rs:590` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 3) vulkano/src/pipeline/shader/validate_runtime.rs:2393— vulkano/src/pipeline/shader/validate_runtime.rs:2393-2405 | vulkano/src/pipeline/shader/validate_runtime.rs:2407-2419 | vulkano/src/pipeline/shader/validate_runtime.rs:2421-2433 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1482— vulkano/src/command_buffer/commands/sync.rs:1482-1489 | vulkano/src/command_buffer/commands/sync.rs:2040-2047 | vulkano/src/command_buffer/commands/sync.rs:2793-2800 — 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 `vulkano/src/command_buffer/commands/sync.rs:1482` it does not close everything it opens, so those 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 × 3) vulkano/src/command_buffer/commands/sync.rs:1506— vulkano/src/command_buffer/commands/sync.rs:1506-1513 | vulkano/src/command_buffer/commands/sync.rs:2064-2071 | vulkano/src/command_buffer/commands/sync.rs:2817-2824 — 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 `vulkano/src/command_buffer/commands/sync.rs:1506` it does not close everything it opens, so those 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 × 3) vulkano/src/command_buffer/commands/sync.rs:1530— vulkano/src/command_buffer/commands/sync.rs:1530-1537 | vulkano/src/command_buffer/commands/sync.rs:2088-2095 | vulkano/src/command_buffer/commands/sync.rs:2841-2848 — 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 `vulkano/src/command_buffer/commands/sync.rs:1530` it does not close everything it opens, so those 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 × 3) vulkano/src/command_buffer/commands/sync.rs:1554— vulkano/src/command_buffer/commands/sync.rs:1554-1561 | vulkano/src/command_buffer/commands/sync.rs:2112-2119 | vulkano/src/command_buffer/commands/sync.rs:2865-2872 — 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 `vulkano/src/command_buffer/commands/sync.rs:1554` it does not close everything it opens, so those 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 × 3) vulkano/src/command_buffer/commands/sync.rs:1578— vulkano/src/command_buffer/commands/sync.rs:1578-1585 | vulkano/src/command_buffer/commands/sync.rs:2136-2143 | vulkano/src/command_buffer/commands/sync.rs:2889-2896 — 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 `vulkano/src/command_buffer/commands/sync.rs:1578` it does not close everything it opens, so those 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 × 3) vulkano/src/command_buffer/commands/sync.rs:1634— vulkano/src/command_buffer/commands/sync.rs:1634-1641 | vulkano/src/command_buffer/commands/sync.rs:2192-2199 | vulkano/src/command_buffer/commands/sync.rs:2945-2952 — 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 `vulkano/src/command_buffer/commands/sync.rs:1634` it does not close everything it opens, so those 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 × 3) vulkano/src/command_buffer/commands/sync.rs:1658— vulkano/src/command_buffer/commands/sync.rs:1658-1665 | vulkano/src/command_buffer/commands/sync.rs:2216-2223 | vulkano/src/command_buffer/commands/sync.rs:2969-2976 — 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 `vulkano/src/command_buffer/commands/sync.rs:1658` it does not close everything it opens, so those 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 × 3) vulkano/src/image/mod.rs:2121— vulkano/src/image/mod.rs:2121-2128 | vulkano/src/image/sys.rs:1932-1939 | vulkano/src/swapchain/mod.rs:2446-2453 — before extracting anything, compare `vulkano/src/image/mod.rs` and `vulkano/src/image/sys.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/image/mod.rs:2121` 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 × 3) vulkano-shaders/src/lib.rs:1368— vulkano-shaders/src/lib.rs:1368-1375 | vulkano-shaders/src/lib.rs:1392-1399 | vulkano-shaders/src/lib.rs:1416-1423 — 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 `vulkano-shaders/src/lib.rs:1368` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) vulkano/src/command_buffer/commands/copy.rs:3072— vulkano/src/command_buffer/commands/copy.rs:3072-3079 | vulkano/src/image/sys.rs:2078-2085 | vulkano/src/memory/sparse.rs:1576-1583 — before extracting anything, compare `vulkano/src/command_buffer/commands/copy.rs` and `vulkano/src/memory/sparse.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 3) vulkano/src/command_buffer/commands/copy.rs:3263— vulkano/src/command_buffer/commands/copy.rs:3263-3270 | vulkano/src/command_buffer/commands/copy.rs:5014-5021 | vulkano/src/command_buffer/commands/copy.rs:6138-6145 — 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.
AutoCommandBufferBuilder::validate_pipeline_graphics_dynamic_state (cognitive 208) vulkano/src/command_buffer/auto/commands/pipeline.rs:2516— AutoCommandBufferBuilder::validate_pipeline_graphics_dynamic_state has cognitive complexity 208 (threshold 15). Drivers by points: if/else 62 (188 pts), loops 4 (10 pts), match/switch 2 (6 pts), boolean chains 4 (nesting depth added 136). 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.
AutoCommandBufferBuilder::validate_pipeline_descriptor_sets (cognitive 117) vulkano/src/command_buffer/auto/commands/pipeline.rs:1724— AutoCommandBufferBuilder::validate_pipeline_descriptor_sets has cognitive complexity 117 (threshold 15). Drivers by points: if/else 36 (88 pts), loops 7 (13 pts), boolean chains 11, match/switch 2 (5 pts) (nesting depth added 61). Of this number, 112 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AutoCommandBufferBuilder::validate_execute_commands (cognitive 95) vulkano/src/command_buffer/auto/commands/secondary.rs:56— AutoCommandBufferBuilder::validate_execute_commands has cognitive complexity 95 (threshold 15). Drivers by points: if/else 22 (81 pts), loops 3 (7 pts), match/switch 2 (6 pts), boolean chains 1 (nesting depth added 67). 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.
AutoCommandBufferBuilder::add_descriptor_sets_resources (cognitive 55) vulkano/src/command_buffer/auto/commands/pipeline.rs:3558— AutoCommandBufferBuilder::add_descriptor_sets_resources has cognitive complexity 55 (threshold 15). Drivers by points: if/else 10 (34 pts), loops 6 (18 pts), match/switch 2 (3 pts) (nesting depth added 37). 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.
AutoCommandBufferBuilder::validate_bind_descriptor_sets (cognitive 49) vulkano/src/command_buffer/auto/commands/bind_push.rs:55— AutoCommandBufferBuilder::validate_bind_descriptor_sets has cognitive complexity 49 (threshold 15). Drivers by points: if/else 9 (34 pts), match/switch 3 (8 pts), loops 3 (7 pts) (nesting depth added 34). 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.
AutoCommandBufferBuilder::validate_clear_attachments (cognitive 39) vulkano/src/command_buffer/auto/commands/render_pass.rs:743— AutoCommandBufferBuilder::validate_clear_attachments has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 3 (4 pts), boolean chains 3, match/switch 1 (2 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.
AutoCommandBufferBuilder::validate_pipeline_graphics_render_pass (cognitive 25) vulkano/src/command_buffer/auto/commands/pipeline.rs:3375— AutoCommandBufferBuilder::validate_pipeline_graphics_render_pass has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 1 (2 pts), match/switch 1 (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.
AutoCommandBufferBuilder::validate_draw (cognitive 19) vulkano/src/command_buffer/auto/commands/pipeline.rs:235— AutoCommandBufferBuilder::validate_draw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (3 pts), loops 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.
AutoCommandBufferBuilder::validate_draw_indexed (cognitive 19) vulkano/src/command_buffer/auto/commands/pipeline.rs:695— AutoCommandBufferBuilder::validate_draw_indexed has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 2 (3 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vulkano::shader::reflect::inspect_entry_point (cognitive 120) vulkano/src/shader/reflect.rs:110— vulkano::shader::reflect::inspect_entry_point has cognitive complexity 120 (threshold 15). Drivers by points: if/else 30 (97 pts), loops 4 (8 pts), match/switch 5 (8 pts), boolean chains 7 (nesting depth added 74). Of this number, 117 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vulkano::sync::future::queue_submit (cognitive 93) vulkano/src/sync/future/mod.rs:631— vulkano::sync::future::queue_submit has cognitive complexity 93 (threshold 15). Drivers by points: if/else 12 (46 pts), loops 12 (34 pts), match/switch 3 (13 pts) (nesting depth added 66). 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.
vulkano::shader::reflect::descriptor_binding_requirements_of (cognitive 48) vulkano/src/shader/reflect.rs:592— vulkano::shader::reflect::descriptor_binding_requirements_of has cognitive complexity 48 (threshold 15). Drivers by points: match/switch 10 (23 pts), if/else 8 (22 pts), boolean chains 2, loops 1 (nesting depth added 27). 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.
vulkano::shader::spirv::specialization::replace_specialization_instructions (cognitive 32) vulkano/src/shader/spirv/specialization.rs:11— vulkano::shader::spirv::specialization::replace_specialization_instructions has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 6 (15 pts), loops 1 (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.
vulkano::pipeline::shader::inout_interface::input_output_map (cognitive 27) vulkano/src/pipeline/shader/inout_interface.rs:875— vulkano::pipeline::shader::inout_interface::input_output_map has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 5 (8 pts), loops 3 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vulkano::shader::spirv::specialization::evaluate_spec_constant_op (cognitive 26) vulkano/src/shader/spirv/specialization.rs:300— vulkano::shader::spirv::specialization::evaluate_spec_constant_op has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 5 (8 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.
vulkano::shader::reflect::specialization_constants (cognitive 18) vulkano/src/shader/reflect.rs:961— vulkano::shader::reflect::specialization_constants has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 4 (8 pts) (nesting depth added 9). 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.
vulkano::pipeline::shader::inout_interface::shader_interface_analyze_type (cognitive 16) vulkano/src/pipeline/shader/inout_interface.rs:748— vulkano::pipeline::shader::inout_interface::shader_interface_analyze_type has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 4 (7 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.
vulkano::shader::reflect::push_constant_requirements::find_variables_used (cognitive 16) vulkano/src/shader/reflect.rs:874— vulkano::shader::reflect::push_constant_requirements::find_variables_used has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (4 pts), match/switch 1 (2 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 (4 members, 50+ identical tokens) · ×9
Members sharing a duplicated core (4 members, 50+ identical tokens) vulkano-taskgraph/src/resource/mod.rs:973— vulkano-taskgraph/src/resource/mod.rs:973-989 | vulkano-taskgraph/src/resource/mod.rs:1015-1027 | vulkano-taskgraph/src/resource/mod.rs:1053-1065 | vulkano-taskgraph/src/resource/mod.rs:1091-1103 — 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) vulkano/src/buffer/mod.rs:869— vulkano/src/buffer/mod.rs:869-880 | vulkano/src/buffer/mod.rs:896-915 | vulkano/src/image/mod.rs:897-908 | vulkano/src/image/mod.rs:939-965 — 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) vulkano/src/buffer/sys.rs:750— vulkano/src/buffer/sys.rs:750-958 | vulkano/src/image/mod.rs:2458-2511 | vulkano/src/image/sys.rs:1788-3096 | vulkano/src/swapchain/mod.rs:2254-2600 — 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) vulkano/src/command_buffer/commands/copy.rs:2886— vulkano/src/command_buffer/commands/copy.rs:2886-2916 | vulkano/src/command_buffer/commands/copy.rs:2936-2967 | vulkano/src/command_buffer/commands/copy.rs:6651-6681 | vulkano/src/command_buffer/commands/copy.rs:6701-6732 — 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) vulkano/src/command_buffer/commands/copy.rs:3102— vulkano/src/command_buffer/commands/copy.rs:3102-3139 | vulkano/src/command_buffer/commands/copy.rs:3141-3179 | vulkano/src/command_buffer/commands/copy.rs:6845-6882 | vulkano/src/command_buffer/commands/copy.rs:6884-6922 — 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) vulkano/src/command_buffer/commands/copy.rs:3141— vulkano/src/command_buffer/commands/copy.rs:3141-3179 | vulkano/src/command_buffer/commands/copy.rs:4831-4860 | vulkano/src/command_buffer/commands/copy.rs:6884-6922 | vulkano/src/memory/sparse.rs:1611-1648 — 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) vulkano/src/command_buffer/commands/render_pass.rs:1360— vulkano/src/command_buffer/commands/render_pass.rs:1360-1962 | vulkano/src/command_buffer/mod.rs:716-896 | vulkano/src/pipeline/graphics/subpass.rs:142-312 | vulkano/src/render_pass/mod.rs:2969-3639 — 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) vulkano/src/descriptor_set/allocator.rs:415— vulkano/src/descriptor_set/allocator.rs:415-467 | vulkano/src/descriptor_set/allocator.rs:472-514 | vulkano/src/descriptor_set/allocator.rs:571-598 | vulkano/src/descriptor_set/allocator.rs:604-634 — 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) vulkano/src/swapchain/acquire_present.rs:76— vulkano/src/swapchain/acquire_present.rs:76-122 | vulkano/src/swapchain/mod.rs:1756-1786 | vulkano/src/sync/semaphore.rs:448-473 | vulkano/src/sync/semaphore.rs:550-571 — 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 (20 lines × 2) vulkano/src/command_buffer/auto/commands/pipeline.rs:289— vulkano/src/command_buffer/auto/commands/pipeline.rs:289-308 | vulkano/src/command_buffer/auto/commands/pipeline.rs:784-803 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:289` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) vulkano/src/command_buffer/commands/sync.rs:157— vulkano/src/command_buffer/commands/sync.rs:157-176 | vulkano/src/command_buffer/commands/sync.rs:421-440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/commands/sync.rs:157` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) vulkano/src/display.rs:164— vulkano/src/display.rs:164-183 | vulkano/src/display.rs:214-233 — 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 `vulkano/src/display.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 (20 lines × 2) vulkano/src/pipeline/shader/inout_interface.rs:906— vulkano/src/pipeline/shader/inout_interface.rs:906-925 | vulkano/src/pipeline/shader/inout_interface.rs:960-979 — 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 `vulkano/src/pipeline/shader/inout_interface.rs:906` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) autogen/src/features.rs:1065— autogen/src/features.rs:1065-1084 | autogen/src/properties.rs:1078-1097 — before extracting anything, compare `autogen/src/features.rs` and `autogen/src/properties.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/features.rs:1065` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) vulkano/src/command_buffer/commands/render_pass.rs:1543— vulkano/src/command_buffer/commands/render_pass.rs:1543-1562 | vulkano/src/command_buffer/commands/render_pass.rs:1582-1604 — 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 `vulkano/src/command_buffer/commands/render_pass.rs:1543` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) vulkano/src/render_pass/mod.rs:1343— vulkano/src/render_pass/mod.rs:1343-1362 | vulkano/src/render_pass/mod.rs:1468-1487 — 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 (20 lines × 2) vulkano/src/command_buffer/commands/copy.rs:5172— vulkano/src/command_buffer/commands/copy.rs:5172-5191 | vulkano/src/command_buffer/commands/copy.rs:6214-6233 — 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 (20 lines × 2) vulkano/src/command_buffer/commands/copy.rs:2652— vulkano/src/command_buffer/commands/copy.rs:2652-2671 | vulkano/src/command_buffer/commands/copy.rs:2673-2692 — 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 before the matched lines, `vulkano/src/command_buffer/commands/copy.rs:2662` calls `array_layers` and `vulkano/src/command_buffer/commands/copy.rs:2641` 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.
vulkano::shader::reflect::inspect_entry_point (cyclomatic 66) vulkano/src/shader/reflect.rs:110— vulkano::shader::reflect::inspect_entry_point has cyclomatic complexity 66 (threshold 15). Of this number, 63 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vulkano::shader::reflect::descriptor_binding_requirements_of (cyclomatic 36) vulkano/src/shader/reflect.rs:592— vulkano::shader::reflect::descriptor_binding_requirements_of has cyclomatic complexity 36 (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.
vulkano::shader::spirv::specialization::replace_specialization_instructions (cyclomatic 28) vulkano/src/shader/spirv/specialization.rs:11— vulkano::shader::spirv::specialization::replace_specialization_instructions has cyclomatic complexity 28 (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. This is NOT this file's highest cyclomatic complexity: vulkano::shader::spirv::specialization::evaluate_spec_constant_calculation_op (cyclomatic 38) 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.
vulkano::sync::future::queue_submit (cyclomatic 27) vulkano/src/sync/future/mod.rs:631— vulkano::sync::future::queue_submit 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.
vulkano::pipeline::shader::inout_interface::input_output_map (cyclomatic 21) vulkano/src/pipeline/shader/inout_interface.rs:875— vulkano::pipeline::shader::inout_interface::input_output_map has cyclomatic complexity 21 (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.
vulkano::shader::reflect::specialization_constants (cyclomatic 20) vulkano/src/shader/reflect.rs:961— vulkano::shader::reflect::specialization_constants has cyclomatic complexity 20 (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.
vulkano::pipeline::shader::inout_interface::are_interface_types_compatible (cyclomatic 17) vulkano/src/pipeline/shader/inout_interface.rs:254— vulkano::pipeline::shader::inout_interface::are_interface_types_compatible 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.
vulkano::shader::spirv::specialization::evaluate_spec_constant_op (cyclomatic 17) vulkano/src/shader/spirv/specialization.rs:300— vulkano::shader::spirv::specialization::evaluate_spec_constant_op 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. This is NOT this file's highest cyclomatic complexity: vulkano::shader::spirv::specialization::evaluate_spec_constant_calculation_op (cyclomatic 38) 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.
RecordingCommandBuffer::validate_write_timestamp (cyclomatic 29) vulkano/src/command_buffer/commands/query.rs:287— RecordingCommandBuffer::validate_write_timestamp 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.
RecordingCommandBuffer::validate_reset_event (cyclomatic 29) vulkano/src/command_buffer/commands/sync.rs:805— RecordingCommandBuffer::validate_reset_event 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.
RecordingCommandBuffer::validate_build_acceleration_structure (cyclomatic 28) vulkano/src/command_buffer/commands/acceleration_structure.rs:41— RecordingCommandBuffer::validate_build_acceleration_structure has cyclomatic complexity 28 (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.
RecordingCommandBuffer::validate_begin_render_pass (cyclomatic 27) vulkano/src/command_buffer/commands/render_pass.rs:38— RecordingCommandBuffer::validate_begin_render_pass 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.
RecordingCommandBuffer::validate_copy_image (cyclomatic 24) vulkano/src/command_buffer/commands/copy.rs:118— RecordingCommandBuffer::validate_copy_image has cyclomatic complexity 24 (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.
RecordingCommandBuffer::validate_build_acceleration_structure_indirect (cyclomatic 23) vulkano/src/command_buffer/commands/acceleration_structure.rs:510— RecordingCommandBuffer::validate_build_acceleration_structure_indirect 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.
RecordingCommandBuffer::validate_copy_buffer_to_image (cyclomatic 20) vulkano/src/command_buffer/commands/copy.rs:476— RecordingCommandBuffer::validate_copy_buffer_to_image has cyclomatic complexity 20 (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.
RecordingCommandBuffer::validate_copy_image_to_buffer (cyclomatic 18) vulkano/src/command_buffer/commands/copy.rs:761— RecordingCommandBuffer::validate_copy_image_to_buffer 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.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×8
Edited copy of a member (20 corresponding lines) vulkano-shaders/src/lib.rs:1153— vulkano-shaders/src/lib.rs:1153-1173 | vulkano-shaders/src/lib.rs:1531-1550 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) vulkano/src/command_buffer/auto/commands/render_pass.rs:1428— vulkano/src/command_buffer/auto/commands/render_pass.rs:1428-1447 | vulkano/src/format.rs:447-466 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) vulkano/src/buffer/mod.rs:917— vulkano/src/buffer/mod.rs:917-936 | vulkano/src/image/mod.rs:967-986 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) vulkano/src/command_buffer/auto/commands/clear.rs:30— vulkano/src/command_buffer/auto/commands/clear.rs:30-49 | vulkano/src/command_buffer/auto/commands/clear.rs:110-130 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) vulkano/src/buffer/allocator.rs:94— vulkano/src/buffer/allocator.rs:94-113 | vulkano/src/buffer/allocator.rs:698-717 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) vulkano/src/memory/allocator/suballocator/buddy.rs:862— vulkano/src/memory/allocator/suballocator/buddy.rs:862-881 | vulkano/src/memory/allocator/suballocator/buddy.rs:901-920 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) vulkano/src/image/sampler/mod.rs:1167— vulkano/src/image/sampler/mod.rs:1167-1191 | vulkano/src/image/view.rs:1181-1200 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) autogen/src/features.rs:981— autogen/src/features.rs:981-1001 | autogen/src/features.rs:1271-1290 — These two members are one piece of code written twice and then edited apart: 20 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 (19 lines × 2) vulkano-taskgraph/src/graph/mod.rs:1009— vulkano-taskgraph/src/graph/mod.rs:1009-1027 | vulkano-taskgraph/src/graph/mod.rs:1083-1101 — 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 `vulkano-taskgraph/src/graph/mod.rs:1009` 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) vulkano/src/command_buffer/auto/commands/pipeline.rs:329— vulkano/src/command_buffer/auto/commands/pipeline.rs:329-347 | vulkano/src/command_buffer/auto/commands/pipeline.rs:805-823 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:329` it does not close everything it opens, so those exact lines 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) vulkano/src/command_buffer/auto/commands/pipeline.rs:2043— vulkano/src/command_buffer/auto/commands/pipeline.rs:2043-2061 | vulkano/src/image/sampler/mod.rs:354-372 — 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 (19 lines × 2) vulkano/src/command_buffer/commands/copy.rs:2810— vulkano/src/command_buffer/commands/copy.rs:2810-2828 | vulkano/src/command_buffer/commands/copy.rs:5659-5677 — 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 (19 lines × 2) vulkano/src/command_buffer/commands/copy.rs:2949— vulkano/src/command_buffer/commands/copy.rs:2949-2967 | vulkano/src/command_buffer/commands/copy.rs:6714-6732 — 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 (19 lines × 2) vulkano/src/render_pass/mod.rs:3665— vulkano/src/render_pass/mod.rs:3665-3683 | vulkano/src/render_pass/mod.rs:3891-3909 — 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 (19 lines × 2) vulkano/src/sync/semaphore.rs:2128— vulkano/src/sync/semaphore.rs:2128-2146 | vulkano/src/sync/semaphore.rs:2232-2251 — 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 `vulkano/src/sync/semaphore.rs:2128` 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) vulkano/src/command_buffer/commands/sync.rs:3504— vulkano/src/command_buffer/commands/sync.rs:3504-3522 | vulkano/src/command_buffer/commands/sync.rs:3619-3637 — 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 (18 lines × 2) vulkano-taskgraph/src/graph/execute.rs:1491— vulkano-taskgraph/src/graph/execute.rs:1491-1508 | vulkano-taskgraph/src/graph/execute.rs:2126-2143 — 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 `vulkano-taskgraph/src/graph/execute.rs:1491` 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) vulkano/src/command_buffer/auto/commands/render_pass.rs:1235— vulkano/src/command_buffer/auto/commands/render_pass.rs:1235-1252 | vulkano/src/command_buffer/commands/render_pass.rs:1306-1323 — before extracting anything, compare `vulkano/src/command_buffer/auto/commands/render_pass.rs` and `vulkano/src/command_buffer/commands/render_pass.rs` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (18 lines × 2) vulkano/src/command_buffer/commands/sync.rs:70— vulkano/src/command_buffer/commands/sync.rs:70-87 | vulkano/src/command_buffer/commands/sync.rs:334-351 — 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 `vulkano/src/command_buffer/commands/sync.rs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) vulkano/src/memory/allocator/mod.rs:1336— vulkano/src/memory/allocator/mod.rs:1336-1353 | vulkano/src/memory/allocator/mod.rs:1471-1488 — 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 `vulkano/src/memory/allocator/mod.rs:1336` it does not close everything it opens, so those exact lines 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) vulkano/src/memory/allocator/mod.rs:1627— vulkano/src/memory/allocator/mod.rs:1627-1644 | vulkano/src/memory/allocator/mod.rs:1831-1848 — 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 `vulkano/src/memory/allocator/mod.rs:1627` it does not close everything it opens, so those exact lines 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) vulkano/src/pipeline/shader/inout_interface.rs:593— vulkano/src/pipeline/shader/inout_interface.rs:593-610 | vulkano/src/pipeline/shader/inout_interface.rs:617-634 — 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 `vulkano/src/pipeline/shader/inout_interface.rs:593` it does not close everything it opens, so those exact lines 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) vulkano/src/buffer/sys.rs:496— vulkano/src/buffer/sys.rs:496-513 | vulkano/src/image/sys.rs:894-911 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:496` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) vulkano/src/command_buffer/commands/copy.rs:2561— vulkano/src/command_buffer/commands/copy.rs:2561-2578 | vulkano/src/command_buffer/commands/copy.rs:2593-2610 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 3) vulkano/src/command_buffer/commands/copy.rs:1582— vulkano/src/command_buffer/commands/copy.rs:1582-1593 | vulkano/src/command_buffer/commands/copy.rs:3239-3250 | vulkano/src/command_buffer/commands/copy.rs:3957-3968 — 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 `vulkano/src/command_buffer/commands/copy.rs:1582` 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) vulkano/src/command_buffer/commands/sync.rs:1465— vulkano/src/command_buffer/commands/sync.rs:1465-1476 | vulkano/src/command_buffer/commands/sync.rs:2023-2034 | vulkano/src/command_buffer/commands/sync.rs:2776-2787 — 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 `vulkano/src/command_buffer/commands/sync.rs:1465` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1602— vulkano/src/command_buffer/commands/sync.rs:1602-1613 | vulkano/src/command_buffer/commands/sync.rs:2160-2171 | vulkano/src/command_buffer/commands/sync.rs:2913-2924 — 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 `vulkano/src/command_buffer/commands/sync.rs:1602` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 3) vulkano/src/render_pass/mod.rs:3755— vulkano/src/render_pass/mod.rs:3755-3766 | vulkano/src/render_pass/mod.rs:3768-3779 | vulkano/src/render_pass/mod.rs:3780-3791 — 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 `vulkano/src/render_pass/mod.rs:3755` 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 (12 lines × 3) vulkano/src/command_buffer/commands/copy.rs:238— vulkano/src/command_buffer/commands/copy.rs:238-255 | vulkano/src/command_buffer/commands/copy.rs:607-618 | vulkano/src/command_buffer/commands/copy.rs:871-882 — 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 `vulkano/src/command_buffer/commands/copy.rs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 × 3) vulkano/src/buffer/mod.rs:1049— vulkano/src/buffer/mod.rs:1049-1060 | vulkano/src/image/mod.rs:2045-2056 | vulkano/src/image/mod.rs:2761-2772 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:1049` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 3) vulkano/src/device/physical.rs:1100— vulkano/src/device/physical.rs:1100-1111 | vulkano/src/device/physical.rs:1218-1229 | vulkano/src/device/physical.rs:1336-1347 — 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 `vulkano/src/device/physical.rs:1100` 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 `info` to `&ExternalBufferInfo<'_>` in one and `&ExternalFenceInfo<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 3) vulkano/src/memory/sparse.rs:1310— vulkano/src/memory/sparse.rs:1310-1321 | vulkano/src/memory/sparse.rs:1327-1338 | vulkano/src/memory/sparse.rs:1344-1355 — 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 `vulkano/src/memory/sparse.rs:1310` it does not close everything it opens, so those 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.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×7
Edited copy of a member (22 corresponding lines) vulkano/src/command_buffer/allocator.rs:293— vulkano/src/command_buffer/allocator.rs:293-314 | vulkano/src/command_buffer/allocator.rs:321-346 — 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) vulkano/src/acceleration_structure.rs:169— vulkano/src/acceleration_structure.rs:169-195 | vulkano/src/device/mod.rs:888-909 — 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) vulkano-shaders/src/lib.rs:1465— vulkano-shaders/src/lib.rs:1465-1487 | vulkano-shaders/src/lib.rs:1508-1529 — 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) vulkano/src/command_buffer/auto/commands/clear.rs:222— vulkano/src/command_buffer/auto/commands/clear.rs:222-248 | vulkano/src/command_buffer/auto/commands/clear.rs:296-317 — 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) vulkano/src/memory/sparse.rs:554— vulkano/src/memory/sparse.rs:554-575 | vulkano/src/memory/sparse.rs:1024-1050 — 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) vulkano/src/command_buffer/mod.rs:901— vulkano/src/command_buffer/mod.rs:901-924 | vulkano/src/pipeline/graphics/subpass.rs:317-338 — 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) vulkano/src/acceleration_structure.rs:234— vulkano/src/acceleration_structure.rs:234-255 | vulkano/src/image/sampler/ycbcr.rs:248-272 — 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 (11 corresponding lines) · ×7
Edited copy of a member (11 corresponding lines) vulkano/src/memory/mod.rs:304— vulkano/src/memory/mod.rs:304-316 | vulkano/src/memory/mod.rs:323-333 — 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.
Edited copy of a member (11 corresponding lines) vulkano/src/sync/future/fence_signal.rs:133— vulkano/src/sync/future/fence_signal.rs:133-143 | vulkano/src/sync/future/fence_signal.rs:359-370 — 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.
Edited copy of a member (11 corresponding lines) vulkano/src/device/physical.rs:159— vulkano/src/device/physical.rs:159-169 | vulkano/src/render_pass/mod.rs:464-478 — 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.
Edited copy of a member (11 corresponding lines) vulkano/src/pipeline/mod.rs:598— vulkano/src/pipeline/mod.rs:598-613 | vulkano/src/pipeline/mod.rs:633-643 — 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.
Edited copy of a member (11 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs:547— vulkano/src/memory/allocator/suballocator/free_list.rs:547-557 | vulkano/src/memory/allocator/suballocator/tlsf.rs:717-727 — 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.
Edited copy of a member (11 corresponding lines) vulkano/src/command_buffer/mod.rs:926— vulkano/src/command_buffer/mod.rs:926-940 | vulkano/src/pipeline/graphics/subpass.rs:340-350 — 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.
Edited copy of a member (11 corresponding lines) vulkano/src/memory/sparse.rs:438— vulkano/src/memory/sparse.rs:438-448 | vulkano/src/pipeline/graphics/discard_rectangle.rs:104-116 — 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.
Duplicated block (11 lines × 3) vulkano-taskgraph/src/command_buffer/commands/copy.rs:527— vulkano-taskgraph/src/command_buffer/commands/copy.rs:527-537 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:699-709 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1125-1135 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:527` 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, `vulkano-taskgraph/src/command_buffer/commands/copy.rs:1136` calls `into` and `vulkano-taskgraph/src/command_buffer/commands/copy.rs:538` 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 (11 lines × 3) vulkano/src/command_buffer/auto/commands/pipeline.rs:559— vulkano/src/command_buffer/auto/commands/pipeline.rs:559-569 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1065-1075 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1509-1519 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:559` 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) vulkano/src/command_buffer/auto/commands/pipeline.rs:1197— vulkano/src/command_buffer/auto/commands/pipeline.rs:1197-1207 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1399-1409 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1538-1548 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:1197` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1755— vulkano/src/command_buffer/commands/sync.rs:1755-1765 | vulkano/src/command_buffer/commands/sync.rs:2313-2323 | vulkano/src/command_buffer/commands/sync.rs:3066-3076 — 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 `vulkano/src/command_buffer/commands/sync.rs:1755` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) vulkano-taskgraph/src/command_buffer/commands/copy.rs:1491— vulkano-taskgraph/src/command_buffer/commands/copy.rs:1491-1501 | vulkano/src/command_buffer/auto/commands/copy.rs:1318-1328 | vulkano/src/command_buffer/commands/copy.rs:4665-4675 — before extracting anything, compare `vulkano-taskgraph/src/command_buffer/commands/copy.rs` and `vulkano/src/command_buffer/auto/commands/copy.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) vulkano/src/command_buffer/commands/copy.rs:1654— vulkano/src/command_buffer/commands/copy.rs:1654-1664 | vulkano/src/command_buffer/commands/copy.rs:5054-5064 | vulkano/src/command_buffer/commands/copy.rs:6182-6192 — 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 `vulkano/src/command_buffer/commands/copy.rs:1654` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vulkano/src/command_buffer/commands/copy.rs:6172` calls `tiling`, `format_features` and `vulkano/src/command_buffer/commands/copy.rs:5029` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) vulkano/src/pipeline/compute.rs:316— vulkano/src/pipeline/compute.rs:316-326 | vulkano/src/pipeline/graphics/mod.rs:847-857 | vulkano/src/pipeline/ray_tracing.rs:530-540 — before extracting anything, compare `vulkano/src/pipeline/compute.rs` and `vulkano/src/pipeline/graphics/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/pipeline/compute.rs:316` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) vulkano-taskgraph/src/command_buffer/commands/copy.rs:253— vulkano-taskgraph/src/command_buffer/commands/copy.rs:253-261 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:442-450 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1024-1032 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:253` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) vulkano/src/command_buffer/auto/commands/render_pass.rs:1264— vulkano/src/command_buffer/auto/commands/render_pass.rs:1264-1272 | vulkano/src/command_buffer/commands/render_pass.rs:1335-1343 | vulkano/src/render_pass/framebuffer.rs:506-514 — before extracting anything, compare `vulkano/src/command_buffer/auto/commands/render_pass.rs` and `vulkano/src/command_buffer/commands/render_pass.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/auto/commands/render_pass.rs:1264` 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 × 3) vulkano/src/command_buffer/commands/sync.rs:1619— vulkano/src/command_buffer/commands/sync.rs:1619-1627 | vulkano/src/command_buffer/commands/sync.rs:2177-2185 | vulkano/src/command_buffer/commands/sync.rs:2930-2938 — 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 `vulkano/src/command_buffer/commands/sync.rs:1619` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) vulkano/src/pipeline/shader/validate_runtime.rs:2744— vulkano/src/pipeline/shader/validate_runtime.rs:2744-2752 | vulkano/src/pipeline/shader/validate_runtime.rs:2764-2772 | vulkano/src/pipeline/shader/validate_runtime.rs:2784-2792 — 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 `vulkano/src/pipeline/shader/validate_runtime.rs:2744` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) vulkano-taskgraph/src/command_buffer/commands/copy.rs:1609— vulkano-taskgraph/src/command_buffer/commands/copy.rs:1609-1617 | vulkano/src/command_buffer/auto/commands/copy.rs:1506-1514 | vulkano/src/command_buffer/commands/copy.rs:5859-5867 — before extracting anything, compare `vulkano-taskgraph/src/command_buffer/commands/copy.rs` and `vulkano/src/command_buffer/auto/commands/copy.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) vulkano-taskgraph/src/command_buffer/commands/sync.rs:363— vulkano-taskgraph/src/command_buffer/commands/sync.rs:363-371 | vulkano/src/command_buffer/commands/sync.rs:1339-1347 | vulkano/src/sync/pipeline.rs:1854-1862 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 3) vulkano/src/render_pass/mod.rs:2405— vulkano/src/render_pass/mod.rs:2405-2415 | vulkano/src/render_pass/mod.rs:2446-2456 | vulkano/src/render_pass/mod.rs:4172-4180 — 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 `vulkano/src/render_pass/mod.rs:4172` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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.
AutoCommandBufferBuilder::validate_pipeline_graphics_dynamic_state (cyclomatic 93) vulkano/src/command_buffer/auto/commands/pipeline.rs:2516— AutoCommandBufferBuilder::validate_pipeline_graphics_dynamic_state has cyclomatic complexity 93 (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.
AutoCommandBufferBuilder::validate_pipeline_descriptor_sets (cyclomatic 58) vulkano/src/command_buffer/auto/commands/pipeline.rs:1724— AutoCommandBufferBuilder::validate_pipeline_descriptor_sets has cyclomatic complexity 58 (threshold 15). Of this number, 55 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AutoCommandBufferBuilder::validate_execute_commands (cyclomatic 31) vulkano/src/command_buffer/auto/commands/secondary.rs:56— AutoCommandBufferBuilder::validate_execute_commands has cyclomatic complexity 31 (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.
AutoCommandBufferBuilder::add_descriptor_sets_resources (cyclomatic 20) vulkano/src/command_buffer/auto/commands/pipeline.rs:3558— AutoCommandBufferBuilder::add_descriptor_sets_resources has cyclomatic complexity 20 (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.
AutoCommandBufferBuilder::validate_clear_attachments (cyclomatic 19) vulkano/src/command_buffer/auto/commands/render_pass.rs:743— AutoCommandBufferBuilder::validate_clear_attachments 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.
AutoCommandBufferBuilder::validate_bind_descriptor_sets (cyclomatic 17) vulkano/src/command_buffer/auto/commands/bind_push.rs:55— AutoCommandBufferBuilder::validate_bind_descriptor_sets has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HackComment vulkano-util/src/context.rs:125— // HACK: This should be replaced with `Surface::required_extensions`, but will need to — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment vulkano-taskgraph/src/resource/state.rs:125— // HACK: We need this in order to collect old swapchains. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment vulkano-taskgraph/src/resource/state.rs:910— // HACK: We need this in order to collect garbage. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment vulkano-shaders/src/shaders.rs:310— // HACK: The Makefile format doesn't support path quoting, and shaderc just outputs paths that — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment vulkano-macros/src/derive_buffer_contents.rs:168— // HACK: This works around Rust issue #48214, which makes it impossible to put these — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment vulkano-macros/src/derive_buffer_contents.rs:192— // HACK: This works around an inherent limitation of bytemuck, namely that an array where the — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D4 · Code Duplication· Edited copies of one member (3 members, 1+ corresponding lines) · ×6
Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/format.rs:1144— vulkano/src/format.rs:1144-1144 | vulkano/src/sync/pipeline.rs:15-15 | vulkano/src/sync/pipeline.rs:508-508 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 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.
Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/pipeline/mod.rs:996— vulkano/src/pipeline/mod.rs:996-996 | vulkano/src/sync/pipeline.rs:15-15 | vulkano/src/sync/pipeline.rs:508-508 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 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.
Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/image/aspect.rs:3— vulkano/src/image/aspect.rs:3-3 | vulkano/src/image/layout.rs:4-4 | vulkano/src/image/mod.rs:1134-1134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 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.
Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/image/aspect.rs:3— vulkano/src/image/aspect.rs:3-3 | vulkano/src/image/layout.rs:4-4 | vulkano/src/shader/mod.rs:1416-1416 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 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.
Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/device/queue.rs:1274— vulkano/src/device/queue.rs:1274-1274 | vulkano/src/image/mod.rs:1134-1134 | vulkano/src/memory/mod.rs:661-661 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 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.
Edited copies of one member (3 members, 1+ corresponding lines) vulkano/src/buffer/mod.rs:945— vulkano/src/buffer/mod.rs:945-945 | vulkano/src/command_buffer/pool.rs:550-550 | vulkano/src/device/mod.rs:2503-2503 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 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 (25 corresponding lines) · ×6
Edited copy of a member (25 corresponding lines) vulkano/src/descriptor_set/allocator.rs:263— vulkano/src/descriptor_set/allocator.rs:263-287 | vulkano/src/descriptor_set/allocator.rs:294-324 — These two members are one piece of code written twice and then edited apart: 25 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 (25 corresponding lines) vulkano/src/cache.rs:135— vulkano/src/cache.rs:135-159 | vulkano/src/cache.rs:168-192 — These two members are one piece of code written twice and then edited apart: 25 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 (25 corresponding lines) vulkano/src/lib.rs:567— vulkano/src/lib.rs:567-591 | vulkano/src/lib.rs:595-621 — These two members are one piece of code written twice and then edited apart: 25 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 (25 corresponding lines) vulkano/src/command_buffer/auto/commands/pipeline.rs:366— vulkano/src/command_buffer/auto/commands/pipeline.rs:366-390 | vulkano/src/command_buffer/auto/commands/pipeline.rs:843-874 — These two members are one piece of code written twice and then edited apart: 25 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 (25 corresponding lines) vulkano/src/display.rs:402— vulkano/src/display.rs:402-426 | vulkano/src/render_pass/framebuffer.rs:268-292 — These two members are one piece of code written twice and then edited apart: 25 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 (25 corresponding lines) vulkano/src/command_buffer/commands/sync.rs:1169— vulkano/src/command_buffer/commands/sync.rs:1169-1193 | vulkano/src/memory/sparse.rs:192-222 — These two members are one piece of code written twice and then edited apart: 25 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) · ×6
Edited copy of a member (17 corresponding lines) vulkano-util/src/window.rs:243— vulkano-util/src/window.rs:243-269 | vulkano-util/src/window.rs:271-287 — 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) vulkano/src/memory/mod.rs:1089— vulkano/src/memory/mod.rs:1089-1105 | vulkano/src/memory/mod.rs:1111-1129 — 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) vulkano/src/image/mod.rs:866— vulkano/src/image/mod.rs:866-882 | vulkano/src/image/mod.rs:914-933 — 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) vulkano/src/swapchain/acquire_present.rs:1047— vulkano/src/swapchain/acquire_present.rs:1047-1063 | vulkano/src/sync/semaphore.rs:1909-1928 — 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) vulkano/src/acceleration_structure.rs:481— vulkano/src/acceleration_structure.rs:481-498 | vulkano/src/image/mod.rs:2792-2808 — 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) vulkano/src/device/mod.rs:1498— vulkano/src/device/mod.rs:1498-1514 | vulkano/src/device/mod.rs:1608-1627 — 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 (13 corresponding lines) · ×6
Edited copy of a member (13 corresponding lines) vulkano/src/device/mod.rs:1094— vulkano/src/device/mod.rs:1094-1110 | vulkano/src/device/physical.rs:2698-2710 — 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) autogen/src/features.rs:10— autogen/src/features.rs:10-22 | autogen/src/properties.rs:15-27 — 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) vulkano/src/command_buffer/commands/sync.rs:1889— vulkano/src/command_buffer/commands/sync.rs:1889-1901 | vulkano/src/sync/pipeline.rs:1906-1918 — 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) vulkano/src/command_buffer/auto/commands/render_pass.rs:1200— vulkano/src/command_buffer/auto/commands/render_pass.rs:1200-1212 | vulkano/src/command_buffer/commands/render_pass.rs:1271-1283 — 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) vulkano/src/pipeline/cache.rs:433— vulkano/src/pipeline/cache.rs:433-446 | vulkano/src/pipeline/graphics/depth_stencil.rs:298-310 — 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) vulkano/src/pipeline/graphics/color_blend.rs:446— vulkano/src/pipeline/graphics/color_blend.rs:446-458 | vulkano/src/pipeline/graphics/vertex_input/mod.rs:485-498 — 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.
Duplicated block (24 lines × 2) vulkano-taskgraph/src/graph/execute.rs:1358— vulkano-taskgraph/src/graph/execute.rs:1358-1381 | vulkano-taskgraph/src/graph/execute.rs:1981-2004 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) vulkano/src/command_buffer/commands/copy.rs:595— vulkano/src/command_buffer/commands/copy.rs:595-618 | vulkano/src/command_buffer/commands/copy.rs:859-882 — 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 `vulkano/src/command_buffer/commands/copy.rs:595` it does not close everything it opens, so those 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 (24 lines × 2) vulkano/src/command_buffer/commands/copy.rs:2783— vulkano/src/command_buffer/commands/copy.rs:2783-2806 | vulkano/src/command_buffer/commands/copy.rs:5629-5652 — 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 (24 lines × 2) vulkano/src/descriptor_set/update.rs:1089— vulkano/src/descriptor_set/update.rs:1089-1112 | vulkano/src/descriptor_set/update.rs:1185-1208 — 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 `vulkano/src/descriptor_set/update.rs:1089` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) vulkano/src/pipeline/ray_tracing.rs:867— vulkano/src/pipeline/ray_tracing.rs:867-890 | vulkano/src/pipeline/ray_tracing.rs:895-918 — 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 `vulkano/src/pipeline/ray_tracing.rs:867` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) vulkano/src/buffer/subbuffer.rs:307— vulkano/src/buffer/subbuffer.rs:307-330 | vulkano/src/buffer/subbuffer.rs:401-424 — 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.
AccessFlags::from (cyclomatic 99) vulkano/src/sync/pipeline.rs:1280— AccessFlags::from has cyclomatic complexity 99 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (PipelineStages::from) 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.
AccessFlags::fmt (cyclomatic 84) vulkano/src/sync/pipeline.rs:508— AccessFlags::fmt has cyclomatic complexity 84 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: PipelineStages::from (cyclomatic 99) 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.
AccessFlags::validate_device_raw (cyclomatic 49) vulkano/src/sync/pipeline.rs:508— AccessFlags::validate_device_raw has cyclomatic complexity 49 (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. This shape REPEATS in the file: one other method here (AccessFlags::validate_instance_raw) 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. This is NOT this file's highest cyclomatic complexity: PipelineStages::from (cyclomatic 99) 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.
AccessFlags::validate_instance_raw (cyclomatic 49) vulkano/src/sync/pipeline.rs:508— AccessFlags::validate_instance_raw has cyclomatic complexity 49 (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. This shape REPEATS in the file: one other method here (AccessFlags::validate_device_raw) 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. This is NOT this file's highest cyclomatic complexity: PipelineStages::from (cyclomatic 99) 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.
AccessFlags::from (cyclomatic 24) vulkano/src/sync/pipeline.rs:951— AccessFlags::from has cyclomatic complexity 24 (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: PipelineStages::from (cyclomatic 99) 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.
AccessFlags::fmt (cognitive 124) vulkano/src/sync/pipeline.rs:508— AccessFlags::fmt has cognitive complexity 124 (threshold 15). Drivers by points: if/else 83 (124 pts) (nesting depth added 41). 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.
AccessFlags::from (cognitive 98) vulkano/src/sync/pipeline.rs:1280— AccessFlags::from has cognitive complexity 98 (threshold 15). Drivers by points: if/else 98. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (PipelineStages::from) 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.
AccessFlags::validate_device_raw (cognitive 48) vulkano/src/sync/pipeline.rs:508— AccessFlags::validate_device_raw has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 24, if/else 24. 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. This shape REPEATS in the file: one other method here (AccessFlags::validate_instance_raw) 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.
AccessFlags::validate_instance_raw (cognitive 48) vulkano/src/sync/pipeline.rs:508— AccessFlags::validate_instance_raw has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 24, if/else 24. 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. This shape REPEATS in the file: one other method here (AccessFlags::validate_device_raw) 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.
AccessFlags::from (cognitive 23) vulkano/src/sync/pipeline.rs:951— AccessFlags::from has cognitive complexity 23 (threshold 15). Drivers by points: if/else 23. 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.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×5
Edited copy of a member (18 corresponding lines) vulkano/src/shader/reflect.rs:1182— vulkano/src/shader/reflect.rs:1182-1199 | vulkano/src/shader/reflect.rs:1201-1218 — 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) vulkano/src/buffer/mod.rs:800— vulkano/src/buffer/mod.rs:800-817 | vulkano/src/image/mod.rs:815-832 — 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) vulkano/src/command_buffer/commands/clear.rs:59— vulkano/src/command_buffer/commands/clear.rs:59-76 | vulkano/src/command_buffer/commands/clear.rs:126-143 — 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) vulkano/src/pipeline/layout.rs:1089— vulkano/src/pipeline/layout.rs:1089-1106 | vulkano/src/pipeline/ray_tracing.rs:755-774 — 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) vulkano/src/sync/fence.rs:186— vulkano/src/sync/fence.rs:186-203 | vulkano/src/sync/semaphore.rs:210-228 — 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.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×5
Edited copies of one member (3 members, 17+ corresponding lines) vulkano-taskgraph/src/descriptor_set.rs:522— vulkano-taskgraph/src/descriptor_set.rs:522-538 | vulkano-taskgraph/src/descriptor_set.rs:579-601 | vulkano-taskgraph/src/descriptor_set.rs:608-631 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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.
Edited copies of one member (3 members, 17+ corresponding lines) vulkano/src/command_buffer/pool.rs:426— vulkano/src/command_buffer/pool.rs:426-446 | vulkano/src/device/private_data.rs:264-280 | vulkano/src/query.rs:443-466 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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.
Edited copies of one member (3 members, 17+ corresponding lines) vulkano-taskgraph/src/graph/mod.rs:370— vulkano-taskgraph/src/graph/mod.rs:370-386 | vulkano-taskgraph/src/graph/mod.rs:388-404 | vulkano-taskgraph/src/graph/mod.rs:406-422 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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.
Edited copies of one member (3 members, 17+ corresponding lines) vulkano/src/command_buffer/commands/copy.rs:2918— vulkano/src/command_buffer/commands/copy.rs:2918-2934 | vulkano/src/command_buffer/commands/copy.rs:5762-5780 | vulkano/src/command_buffer/commands/copy.rs:6683-6699 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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.
Edited copies of one member (3 members, 17+ corresponding lines) vulkano/src/memory/mod.rs:1016— vulkano/src/memory/mod.rs:1016-1033 | vulkano/src/sync/fence.rs:1541-1557 | vulkano/src/sync/semaphore.rs:2447-2463 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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 (12 corresponding lines) · ×5
Edited copy of a member (12 corresponding lines) vulkano/src/buffer/mod.rs:856— vulkano/src/buffer/mod.rs:856-867 | vulkano/src/image/mod.rs:884-895 — 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) vulkano-taskgraph/src/graph/execute.rs:1510— vulkano-taskgraph/src/graph/execute.rs:1510-1521 | vulkano-taskgraph/src/graph/execute.rs:2145-2156 — 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) vulkano/src/range_map.rs:373— vulkano/src/range_map.rs:373-384 | vulkano/src/range_map.rs:390-401 — 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) vulkano/src/buffer/sys.rs:991— vulkano/src/buffer/sys.rs:991-1003 | vulkano/src/sync/fence.rs:1152-1163 — 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) vulkano-taskgraph/src/command_buffer/commands/clear.rs:379— vulkano-taskgraph/src/command_buffer/commands/clear.rs:379-390 | vulkano/src/command_buffer/commands/clear.rs:648-659 — 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 (10 corresponding lines) · ×5
Edited copy of a member (10 corresponding lines) vulkano/src/command_buffer/traits.rs:487— vulkano/src/command_buffer/traits.rs:487-498 | vulkano/src/sync/future/semaphore_signal.rs:238-247 — 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) vulkano/src/pipeline/compute.rs:92— vulkano/src/pipeline/compute.rs:92-101 | vulkano/src/pipeline/ray_tracing.rs:139-149 — 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) vulkano/src/command_buffer/commands/render_pass.rs:1131— vulkano/src/command_buffer/commands/render_pass.rs:1131-1140 | vulkano/src/sync/event.rs:402-411 — 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) autogen/src/errors.rs:6— autogen/src/errors.rs:6-15 | autogen/src/formats.rs:11-24 — 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) vulkano/src/buffer/allocator.rs:227— vulkano/src/buffer/allocator.rs:227-238 | vulkano/src/memory/allocator/mod.rs:2235-2244 — 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.
Duplicated block (16 lines × 4) vulkano-taskgraph/src/command_buffer/commands/copy.rs:447— vulkano-taskgraph/src/command_buffer/commands/copy.rs:447-462 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:504-521 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:619-634 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:676-693 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:447` 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, `vulkano-taskgraph/src/command_buffer/commands/copy.rs:673` calls `handle` and `vulkano-taskgraph/src/command_buffer/commands/copy.rs:501` 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 × 4) vulkano/src/command_buffer/commands/copy.rs:1774— vulkano/src/command_buffer/commands/copy.rs:1774-1789 | vulkano/src/command_buffer/commands/copy.rs:2173-2188 | vulkano/src/command_buffer/commands/copy.rs:3383-3398 | vulkano/src/command_buffer/commands/copy.rs:4101-4116 — 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 `vulkano/src/command_buffer/commands/copy.rs:1774` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 4) vulkano/src/device/physical.rs:2237— vulkano/src/device/physical.rs:2237-2252 | vulkano/src/device/physical.rs:2289-2304 | vulkano/src/device/physical.rs:2479-2494 | vulkano/src/device/physical.rs:2522-2537 — 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 `vulkano/src/device/physical.rs:2237` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 4) vulkano/src/command_buffer/commands/copy.rs:261— vulkano/src/command_buffer/commands/copy.rs:261-276 | vulkano/src/command_buffer/commands/copy.rs:305-320 | vulkano/src/command_buffer/commands/copy.rs:624-640 | vulkano/src/command_buffer/commands/copy.rs:888-904 — 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 `vulkano/src/command_buffer/commands/copy.rs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 4) vulkano/src/descriptor_set/update.rs:616— vulkano/src/descriptor_set/update.rs:616-631 | vulkano/src/descriptor_set/update.rs:716-732 | vulkano/src/descriptor_set/update.rs:823-839 | vulkano/src/descriptor_set/update.rs:1229-1245 — 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 `vulkano/src/descriptor_set/update.rs:616` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano/src/descriptor_set/update.rs:634` calls `enabled_features` and `vulkano/src/descriptor_set/update.rs:1250` 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) vulkano/src/buffer/sys.rs:804— vulkano/src/buffer/sys.rs:804-813 | vulkano/src/image/mod.rs:2482-2491 | vulkano/src/swapchain/mod.rs:2369-2378 — `vulkano/src/image/mod.rs` and `vulkano/src/swapchain/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 90 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:804` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 3) vulkano/src/command_buffer/commands/sync.rs:950— vulkano/src/command_buffer/commands/sync.rs:950-959 | vulkano/src/command_buffer/commands/sync.rs:2919-2928 | vulkano/src/command_buffer/commands/sync.rs:2933-2942 — 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 `vulkano/src/command_buffer/commands/sync.rs:950` 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, `vulkano/src/command_buffer/commands/sync.rs:962` calls `enabled_features` and `vulkano/src/command_buffer/commands/sync.rs:2930` 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) vulkano/src/command_buffer/commands/sync.rs:1682— vulkano/src/command_buffer/commands/sync.rs:1682-1691 | vulkano/src/command_buffer/commands/sync.rs:2240-2249 | vulkano/src/command_buffer/commands/sync.rs:2993-3002 — 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 `vulkano/src/command_buffer/commands/sync.rs:1682` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1704— vulkano/src/command_buffer/commands/sync.rs:1704-1713 | vulkano/src/command_buffer/commands/sync.rs:2262-2271 | vulkano/src/command_buffer/commands/sync.rs:3015-3024 — 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 `vulkano/src/command_buffer/commands/sync.rs:1704` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 3) vulkano/src/command_buffer/auto/commands/pipeline.rs:430— vulkano/src/command_buffer/auto/commands/pipeline.rs:430-439 | vulkano/src/command_buffer/auto/commands/pipeline.rs:921-930 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1372-1381 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:430` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `indirect_buffer` to `Subbuffer<[DrawIndirectCommand]>` in one and `Subbuffer<[DrawIndexedIndirectCommand]>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 4) vulkano/src/command_buffer/commands/copy.rs:1588— vulkano/src/command_buffer/commands/copy.rs:1588-1595 | vulkano/src/command_buffer/commands/copy.rs:1597-1604 | vulkano/src/command_buffer/commands/copy.rs:3245-3252 | vulkano/src/command_buffer/commands/copy.rs:3963-3970 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 4) vulkano/src/command_buffer/commands/copy.rs:1582— vulkano/src/command_buffer/commands/copy.rs:1582-1589 | vulkano/src/command_buffer/commands/copy.rs:3239-3246 | vulkano/src/command_buffer/commands/copy.rs:3957-3964 | vulkano/src/command_buffer/commands/copy.rs:4950-4957 — 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 `vulkano/src/command_buffer/commands/copy.rs:1582` 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) vulkano/src/command_buffer/commands/copy.rs:1731— vulkano/src/command_buffer/commands/copy.rs:1731-1738 | vulkano/src/command_buffer/commands/copy.rs:2130-2137 | vulkano/src/command_buffer/commands/copy.rs:3340-3347 | vulkano/src/command_buffer/commands/copy.rs:4058-4065 — 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 `vulkano/src/command_buffer/commands/copy.rs:1731` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 4) vulkano/src/image/sampler/mod.rs:1265— vulkano/src/image/sampler/mod.rs:1265-1272 | vulkano/src/image/sampler/mod.rs:1274-1281 | vulkano/src/image/sampler/mod.rs:1283-1290 | vulkano/src/image/sampler/mod.rs:1292-1299 — 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 `vulkano/src/image/sampler/mod.rs:1265` 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) vulkano/src/command_buffer/commands/render_pass.rs:1431— vulkano/src/command_buffer/commands/render_pass.rs:1431-1438 | vulkano/src/command_buffer/mod.rs:731-738 | vulkano/src/pipeline/graphics/subpass.rs:157-164 | vulkano/src/render_pass/mod.rs:3618-3625 — before extracting anything, compare `vulkano/src/command_buffer/mod.rs` and `vulkano/src/pipeline/graphics/subpass.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 `vulkano/src/command_buffer/commands/render_pass.rs:1431` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 4) vulkano-taskgraph/src/graph/execute.rs:994— vulkano-taskgraph/src/graph/execute.rs:994-999 | vulkano-taskgraph/src/graph/execute.rs:1195-1200 | vulkano-taskgraph/src/graph/execute.rs:1609-1614 | vulkano-taskgraph/src/graph/execute.rs:1815-1820 — 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 `vulkano-taskgraph/src/graph/execute.rs:994` it does not close everything it opens, so those exact lines 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) vulkano-taskgraph/src/graph/execute.rs:1226— vulkano-taskgraph/src/graph/execute.rs:1226-1231 | vulkano-taskgraph/src/graph/execute.rs:1245-1250 | vulkano-taskgraph/src/graph/execute.rs:1845-1850 | vulkano-taskgraph/src/graph/execute.rs:1865-1870 — 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 `vulkano-taskgraph/src/graph/execute.rs:1226` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano-taskgraph/src/graph/execute.rs:1852` calls `convert_stage_mask` and `vulkano-taskgraph/src/graph/execute.rs:1232` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) vulkano-taskgraph/src/resource/mod.rs:984— vulkano-taskgraph/src/resource/mod.rs:984-989 | vulkano-taskgraph/src/resource/mod.rs:1022-1027 | vulkano-taskgraph/src/resource/mod.rs:1060-1065 | vulkano-taskgraph/src/resource/mod.rs:1098-1103 — 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 `vulkano-taskgraph/src/resource/mod.rs:984` 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 `id` to `Id<Buffer>` in one and `Id<Image>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 4) vulkano/src/pipeline/compute.rs:69— vulkano/src/pipeline/compute.rs:69-74 | vulkano/src/pipeline/graphics/mod.rs:196-201 | vulkano/src/pipeline/ray_tracing.rs:116-121 | vulkano/src/swapchain/mod.rs:448-453 — before extracting anything, compare `vulkano/src/pipeline/compute.rs` and `vulkano/src/pipeline/graphics/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/pipeline/compute.rs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `create_info` to `&ComputePipelineCreateInfo<'_>` in one and `&GraphicsPipelineCreateInfo<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 4) vulkano-taskgraph/src/descriptor_set.rs:453— vulkano-taskgraph/src/descriptor_set.rs:453-458 | vulkano-taskgraph/src/descriptor_set.rs:478-483 | vulkano-taskgraph/src/descriptor_set.rs:503-508 | vulkano-taskgraph/src/resource/mod.rs:239-244 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/descriptor_set.rs:453` 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.
PipelineStages::from (cyclomatic 99) vulkano/src/sync/pipeline.rs:1265— PipelineStages::from has cyclomatic complexity 99 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (AccessFlags::from) 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.
PipelineStages::fmt (cyclomatic 82) vulkano/src/sync/pipeline.rs:15— PipelineStages::fmt has cyclomatic complexity 82 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: PipelineStages::from (cyclomatic 99) 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.
PipelineStages::validate_device_raw (cyclomatic 47) vulkano/src/sync/pipeline.rs:15— PipelineStages::validate_device_raw has cyclomatic complexity 47 (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. This shape REPEATS in the file: one other method here (PipelineStages::validate_instance_raw) 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. This is NOT this file's highest cyclomatic complexity: PipelineStages::from (cyclomatic 99) 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.
PipelineStages::validate_instance_raw (cyclomatic 47) vulkano/src/sync/pipeline.rs:15— PipelineStages::validate_instance_raw has cyclomatic complexity 47 (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. This shape REPEATS in the file: one other method here (PipelineStages::validate_device_raw) 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. This is NOT this file's highest cyclomatic complexity: PipelineStages::from (cyclomatic 99) 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.
PipelineStages::fmt (cognitive 121) vulkano/src/sync/pipeline.rs:15— PipelineStages::fmt has cognitive complexity 121 (threshold 15). Drivers by points: if/else 81 (121 pts) (nesting depth added 40). 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.
PipelineStages::from (cognitive 98) vulkano/src/sync/pipeline.rs:1265— PipelineStages::from has cognitive complexity 98 (threshold 15). Drivers by points: if/else 98. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (AccessFlags::from) 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.
PipelineStages::validate_device_raw (cognitive 46) vulkano/src/sync/pipeline.rs:15— PipelineStages::validate_device_raw has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 23, if/else 23. 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. This shape REPEATS in the file: one other method here (PipelineStages::validate_instance_raw) 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.
PipelineStages::validate_instance_raw (cognitive 46) vulkano/src/sync/pipeline.rs:15— PipelineStages::validate_instance_raw has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 23, if/else 23. 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. This shape REPEATS in the file: one other method here (PipelineStages::validate_device_raw) 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.
autogen::formats::formats_members (cognitive 115) autogen/src/formats.rs:632— autogen::formats::formats_members has cognitive complexity 115 (threshold 15). Drivers by points: if/else 26 (68 pts), match/switch 8 (30 pts), loops 7 (15 pts), boolean chains 2 (nesting depth added 72). 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.
autogen::spirv_parse::instruction_output (cognitive 55) autogen/src/spirv_parse.rs:115— autogen::spirv_parse::instruction_output has cognitive complexity 55 (threshold 15). Drivers by points: if/else 40 (55 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
autogen::spirv_parse::instruction_members (cognitive 27) autogen/src/spirv_parse.rs:491— autogen::spirv_parse::instruction_members has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 5, loops 2 (3 pts), match/switch 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
autogen::properties::c_type_to_vulkano_type (cognitive 17) autogen/src/properties.rs:1119— autogen::properties::c_type_to_vulkano_type has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
Change coupling: traits.rs ↔ semaphore_signal.rs vulkano/src/command_buffer/traits.rs:1— `vulkano/src/command_buffer/traits.rs` and `vulkano/src/sync/future/semaphore_signal.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f7121111` Use references as params in `Queue::submit` and `Queue::bind_sparse` …; `def21843` Partial validation of queue commands (#2373); `765bc6ac` Fix potential panics during panics (#2162) — run `git show` on any of them.
Change coupling: fence_signal.rs ↔ semaphore_signal.rs vulkano/src/sync/future/fence_signal.rs:1— `vulkano/src/sync/future/fence_signal.rs` and `vulkano/src/sync/future/semaphore_signal.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f7121111` Use references as params in `Queue::submit` and `Queue::bind_sparse` …; `def21843` Partial validation of queue commands (#2373); `765bc6ac` Fix potential panics during panics (#2162) — run `git show` on any of them.
Change coupling: compute.rs ↔ mod.rs vulkano/src/pipeline/compute.rs:1— `vulkano/src/pipeline/compute.rs` and `vulkano/src/pipeline/graphics/mod.rs` change together 51% of the time (32 of the 63 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 32 shared commits counted here, the most recent 3 are `ac248146` Correct various grammar throughout the codebase (#2718); `909096db` Enable and fix `rust_2024_incompatible_pat` lint (#2631); `130f9e5d` Ray Tracing Pipeline (KHR) (#2564) — run `git show` on any of them.
Change coupling: copy.rs ↔ view.rs vulkano/src/command_buffer/commands/copy.rs:1— `vulkano/src/command_buffer/commands/copy.rs` and `vulkano/src/image/view.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `9e375203` #2752 fixes (#2754); `872f0187` Implement `Default` for `ImageSubresource*`, deprecations and mainten…; `6087ae1b` Make stencil_usage an Option (#2276) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×4
Edited copy of a member (38 corresponding lines) vulkano-taskgraph/src/graph/execute.rs:1147— vulkano-taskgraph/src/graph/execute.rs:1147-1184 | vulkano-taskgraph/src/graph/execute.rs:1767-1804 — 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.
Edited copy of a member (38 corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs:307— vulkano/src/command_buffer/auto/commands/copy.rs:307-344 | vulkano/src/command_buffer/auto/commands/copy.rs:442-479 — 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.
Edited copy of a member (38 corresponding lines) vulkano/src/command_buffer/commands/copy.rs:5869— vulkano/src/command_buffer/commands/copy.rs:5869-5906 | vulkano/src/command_buffer/commands/copy.rs:6794-6839 — 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.
Edited copy of a member (38 corresponding lines) vulkano/src/device/mod.rs:1012— vulkano/src/device/mod.rs:1012-1049 | vulkano/src/device/mod.rs:1116-1159 — 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 (23 corresponding lines) · ×4
Edited copy of a member (23 corresponding lines) vulkano/src/command_buffer/commands/sync.rs:470— vulkano/src/command_buffer/commands/sync.rs:470-508 | vulkano/src/command_buffer/commands/sync.rs:1020-1042 — These two members are one piece of code written twice and then edited apart: 23 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 (23 corresponding lines) vulkano/src/pipeline/shader/inout_interface.rs:592— vulkano/src/pipeline/shader/inout_interface.rs:592-614 | vulkano/src/pipeline/shader/inout_interface.rs:616-639 — These two members are one piece of code written twice and then edited apart: 23 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 (23 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs:107— vulkano/src/memory/allocator/suballocator/free_list.rs:107-132 | vulkano/src/memory/allocator/suballocator/tlsf.rs:138-160 — These two members are one piece of code written twice and then edited apart: 23 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 (23 corresponding lines) vulkano-shaders/src/lib.rs:1367— vulkano-shaders/src/lib.rs:1367-1389 | vulkano-shaders/src/lib.rs:1391-1413 — These two members are one piece of code written twice and then edited apart: 23 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) · ×4
Edited copy of a member (27 corresponding lines) vulkano/src/pipeline/mod.rs:266— vulkano/src/pipeline/mod.rs:266-292 | vulkano/src/pipeline/mod.rs:407-437 — 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.
Edited copy of a member (27 corresponding lines) vulkano/src/device/private_data.rs:201— vulkano/src/device/private_data.rs:201-227 | vulkano/src/device/private_data.rs:232-259 — 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.
Edited copy of a member (27 corresponding lines) vulkano-taskgraph/src/collector.rs:302— vulkano-taskgraph/src/collector.rs:302-328 | vulkano-taskgraph/src/collector.rs:352-378 — 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.
Edited copy of a member (27 corresponding lines) autogen/src/features.rs:658— autogen/src/features.rs:658-684 | autogen/src/properties.rs:606-632 — 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 (16 corresponding lines) · ×4
Edited copy of a member (16 corresponding lines) vulkano/src/buffer/mod.rs:828— vulkano/src/buffer/mod.rs:828-843 | vulkano/src/image/mod.rs:845-860 — 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.
Edited copy of a member (16 corresponding lines) vulkano/src/sync/fence.rs:837— vulkano/src/sync/fence.rs:837-852 | vulkano/src/sync/fence.rs:925-940 — 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.
Edited copy of a member (16 corresponding lines) vulkano/src/command_buffer/auto/commands/pipeline.rs:107— vulkano/src/command_buffer/auto/commands/pipeline.rs:107-122 | vulkano/src/command_buffer/auto/commands/pipeline.rs:183-204 — 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.
Edited copy of a member (16 corresponding lines) autogen/src/features.rs:1150— autogen/src/features.rs:1150-1165 | autogen/src/features.rs:1167-1182 — 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, 14+ corresponding lines) · ×4
Edited copies of one member (3 members, 14+ corresponding lines) vulkano/src/command_buffer/pool.rs:352— vulkano/src/command_buffer/pool.rs:352-365 | vulkano/src/descriptor_set/pool.rs:516-533 | vulkano/src/pipeline/cache.rs:348-365 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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.
Edited copies of one member (3 members, 14+ corresponding lines) vulkano/src/command_buffer/auto/commands/render_pass.rs:1511— vulkano/src/command_buffer/auto/commands/render_pass.rs:1511-1533 | vulkano/src/pipeline/graphics/viewport.rs:518-531 | vulkano/src/swapchain/acquire_present.rs:1005-1023 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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.
Edited copies of one member (3 members, 14+ corresponding lines) vulkano-taskgraph/src/resource/state.rs:290— vulkano-taskgraph/src/resource/state.rs:290-303 | vulkano-taskgraph/src/resource/state.rs:316-329 | vulkano-taskgraph/src/resource/state.rs:342-355 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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.
Edited copies of one member (3 members, 14+ corresponding lines) vulkano/src/buffer/view.rs:517— vulkano/src/buffer/view.rs:517-531 | vulkano/src/sync/fence.rs:1329-1342 | vulkano/src/sync/semaphore.rs:2040-2053 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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 (9 corresponding lines) · ×4
Edited copy of a member (9 corresponding lines) vulkano/src/memory/allocator/layout.rs:265— vulkano/src/memory/allocator/layout.rs:265-273 | vulkano/src/memory/allocator/layout.rs:280-290 — 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) vulkano/src/buffer/subbuffer.rs:509— vulkano/src/buffer/subbuffer.rs:509-517 | vulkano/src/buffer/subbuffer.rs:520-528 — 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) vulkano/src/memory/allocator/suballocator/free_list.rs:440— vulkano/src/memory/allocator/suballocator/free_list.rs:440-448 | vulkano/src/memory/allocator/suballocator/free_list.rs:524-538 — 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) vulkano/src/command_buffer/auto/commands/clear.rs:353— vulkano/src/command_buffer/auto/commands/clear.rs:353-363 | vulkano/src/command_buffer/commands/clear.rs:409-417 — 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 (22 lines × 2) vulkano/src/buffer/allocator.rs:60— vulkano/src/buffer/allocator.rs:60-81 | vulkano/src/buffer/allocator.rs:489-510 — 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 `vulkano/src/buffer/allocator.rs:60` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `create_info` to `&BufferAllocatorCreateInfo<'_>` in one and `SubbufferAllocatorCreateInfo` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (22 lines × 2) vulkano/src/command_buffer/commands/copy.rs:3308— vulkano/src/command_buffer/commands/copy.rs:3308-3329 | vulkano/src/command_buffer/commands/copy.rs:4026-4047 — 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 (22 lines × 2) vulkano/src/command_buffer/commands/copy.rs:3829— vulkano/src/command_buffer/commands/copy.rs:3829-3850 | vulkano/src/command_buffer/commands/copy.rs:4544-4565 — 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 (22 lines × 2) vulkano/src/command_buffer/commands/copy.rs:5326— vulkano/src/command_buffer/commands/copy.rs:5326-5347 | vulkano/src/command_buffer/commands/copy.rs:5539-5560 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) vulkano-taskgraph/src/lib.rs:485— vulkano-taskgraph/src/lib.rs:485-505 | vulkano-taskgraph/src/lib.rs:627-647 — 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 `vulkano-taskgraph/src/lib.rs:485` 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) vulkano/src/command_buffer/commands/sync.rs:111— vulkano/src/command_buffer/commands/sync.rs:111-131 | vulkano/src/command_buffer/commands/sync.rs:375-395 — 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 `vulkano/src/command_buffer/commands/sync.rs:111` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 2) vulkano/src/memory/allocator/mod.rs:1604— vulkano/src/memory/allocator/mod.rs:1604-1624 | vulkano/src/memory/allocator/mod.rs:1808-1828 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) vulkano/src/render_pass/mod.rs:624— vulkano/src/render_pass/mod.rs:624-644 | vulkano/src/render_pass/mod.rs:646-666 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 4) vulkano/src/command_buffer/commands/copy.rs:1748— vulkano/src/command_buffer/commands/copy.rs:1748-1759 | vulkano/src/command_buffer/commands/copy.rs:2147-2158 | vulkano/src/command_buffer/commands/copy.rs:3357-3368 | vulkano/src/command_buffer/commands/copy.rs:4075-4086 — 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 `vulkano/src/command_buffer/commands/copy.rs:1748` 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) vulkano/src/descriptor_set/update.rs:528— vulkano/src/descriptor_set/update.rs:528-539 | vulkano/src/descriptor_set/update.rs:669-680 | vulkano/src/descriptor_set/update.rs:770-781 | vulkano/src/descriptor_set/update.rs:1280-1291 — 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 `vulkano/src/descriptor_set/update.rs:528` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 4) vulkano/src/command_buffer/commands/copy.rs:1640— vulkano/src/command_buffer/commands/copy.rs:1640-1651 | vulkano/src/command_buffer/commands/copy.rs:4013-4024 | vulkano/src/command_buffer/commands/copy.rs:5001-5012 | vulkano/src/command_buffer/commands/copy.rs:6116-6127 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (12 lines × 4) vulkano/src/sync/fence.rs:610— vulkano/src/sync/fence.rs:610-621 | vulkano/src/sync/fence.rs:740-751 | vulkano/src/sync/semaphore.rs:845-856 | vulkano/src/sync/semaphore.rs:970-981 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/fence.rs:610` 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 `handle_type` to `ExternalFenceHandleType` in one and `ExternalSemaphoreHandleType` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:244— vulkano-taskgraph/src/command_buffer/commands/copy.rs:244-248 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1015-1019 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:244` 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) vulkano/src/image/mod.rs:2480— vulkano/src/image/mod.rs:2480-2484 | vulkano/src/image/sys.rs:2755-2759 — before extracting anything, compare `vulkano/src/image/mod.rs` and `vulkano/src/image/sys.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/image/mod.rs:2480` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) vulkano/src/pipeline/compute.rs:82— vulkano/src/pipeline/compute.rs:82-86 | vulkano/src/pipeline/graphics/mod.rs:209-213 — before extracting anything, compare `vulkano/src/pipeline/compute.rs` and `vulkano/src/pipeline/graphics/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/pipeline/compute.rs:82` 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 `create_info` to `&ComputePipelineCreateInfo<'_>` in one and `&GraphicsPipelineCreateInfo<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) vulkano/src/command_buffer/commands/render_pass.rs:1142— vulkano/src/command_buffer/commands/render_pass.rs:1142-1146 | vulkano/src/sync/event.rs:413-417 — 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.
RuntimeValidator::validate_global_variables (cyclomatic 124) vulkano/src/pipeline/shader/validate_runtime.rs:1046— RuntimeValidator::validate_global_variables has cyclomatic complexity 124 (threshold 15). Of this number, 118 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RuntimeValidator::validate_function (cyclomatic 110) vulkano/src/pipeline/shader/validate_runtime.rs:1946— RuntimeValidator::validate_function has cyclomatic complexity 110 (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.
RuntimeValidator::validate_execution_modes (cyclomatic 99) vulkano/src/pipeline/shader/validate_runtime.rs:160— RuntimeValidator::validate_execution_modes has cyclomatic complexity 99 (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.
FormatFeatures::fmt (cyclomatic 86) vulkano/src/format.rs:1144— FormatFeatures::fmt has cyclomatic complexity 86 (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.
FormatFeatures::validate_device_raw (cyclomatic 59) vulkano/src/format.rs:1144— FormatFeatures::validate_device_raw has cyclomatic complexity 59 (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. This shape REPEATS in the file: one other method here (FormatFeatures::validate_instance_raw) 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.
FormatFeatures::validate_instance_raw (cyclomatic 59) vulkano/src/format.rs:1144— FormatFeatures::validate_instance_raw has cyclomatic complexity 59 (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. This shape REPEATS in the file: one other method here (FormatFeatures::validate_device_raw) 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.
autogen::formats::formats_members (cyclomatic 56) autogen/src/formats.rs:632— autogen::formats::formats_members has cyclomatic complexity 56 (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.
autogen::spirv_parse::instruction_output (cyclomatic 21) autogen/src/spirv_parse.rs:115— autogen::spirv_parse::instruction_output has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
autogen::spirv_parse::instruction_members (cyclomatic 20) autogen/src/spirv_parse.rs:491— autogen::spirv_parse::instruction_members has cyclomatic complexity 20 (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.
ShaderStages::fmt (cyclomatic 32) vulkano/src/shader/mod.rs:1416— ShaderStages::fmt has cyclomatic complexity 32 (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.
ShaderStages::validate_device_raw (cyclomatic 19) vulkano/src/shader/mod.rs:1416— ShaderStages::validate_device_raw has cyclomatic complexity 19 (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. This shape REPEATS in the file: one other method here (ShaderStages::validate_instance_raw) 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.
ShaderStages::validate_instance_raw (cyclomatic 19) vulkano/src/shader/mod.rs:1416— ShaderStages::validate_instance_raw has cyclomatic complexity 19 (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. This shape REPEATS in the file: one other method here (ShaderStages::validate_device_raw) 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.
RuntimeValidator::validate_function (cognitive 317) vulkano/src/pipeline/shader/validate_runtime.rs:1946— RuntimeValidator::validate_function has cognitive complexity 317 (threshold 15). Drivers by points: if/else 64 (246 pts), match/switch 11 (42 pts), loops 5 (22 pts), boolean chains 7 (nesting depth added 230). 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.
RuntimeValidator::validate_global_variables (cognitive 246) vulkano/src/pipeline/shader/validate_runtime.rs:1046— RuntimeValidator::validate_global_variables has cognitive complexity 246 (threshold 15). Drivers by points: if/else 59 (163 pts), match/switch 16 (50 pts), loops 6 (18 pts), boolean chains 15 (nesting depth added 150). Of this number, 238 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RuntimeValidator::validate_execution_modes (cognitive 172) vulkano/src/pipeline/shader/validate_runtime.rs:160— RuntimeValidator::validate_execution_modes has cognitive complexity 172 (threshold 15). Drivers by points: if/else 45 (134 pts), match/switch 13 (33 pts), boolean chains 4, loops 1 (nesting depth added 109). 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.
FormatFeatures::fmt (cognitive 127) vulkano/src/format.rs:1144— FormatFeatures::fmt has cognitive complexity 127 (threshold 15). Drivers by points: if/else 85 (127 pts) (nesting depth added 42). 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.
FormatFeatures::validate_device_raw (cognitive 58) vulkano/src/format.rs:1144— FormatFeatures::validate_device_raw has cognitive complexity 58 (threshold 15). Drivers by points: boolean chains 29, if/else 29. 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. This shape REPEATS in the file: one other method here (FormatFeatures::validate_instance_raw) 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.
FormatFeatures::validate_instance_raw (cognitive 58) vulkano/src/format.rs:1144— FormatFeatures::validate_instance_raw has cognitive complexity 58 (threshold 15). Drivers by points: boolean chains 29, if/else 29. 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. This shape REPEATS in the file: one other method here (FormatFeatures::validate_device_raw) 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.
RenderingInfo::validate (cognitive 87) vulkano/src/command_buffer/commands/render_pass.rs:1360— RenderingInfo::validate has cognitive complexity 87 (threshold 15). Drivers by points: if/else 43 (75 pts), match/switch 3 (6 pts), boolean chains 5, loops 1 (nesting depth added 35). 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.
RenderingInfo::set_auto_extent_layers (cognitive 24) vulkano/src/command_buffer/auto/commands/render_pass.rs:1214— RenderingInfo::set_auto_extent_layers has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (5 pts), boolean chains 3 (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.
RenderingInfo::set_auto_extent_layers (cognitive 24) vulkano/src/command_buffer/commands/render_pass.rs:1285— RenderingInfo::set_auto_extent_layers has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (5 pts), boolean chains 3 (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.
ShaderStages::fmt (cognitive 46) vulkano/src/shader/mod.rs:1416— ShaderStages::fmt has cognitive complexity 46 (threshold 15). Drivers by points: if/else 31 (46 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShaderStages::validate_device_raw (cognitive 18) vulkano/src/shader/mod.rs:1416— ShaderStages::validate_device_raw has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 9. 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. This shape REPEATS in the file: one other method here (ShaderStages::validate_instance_raw) 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.
ShaderStages::validate_instance_raw (cognitive 18) vulkano/src/shader/mod.rs:1416— ShaderStages::validate_instance_raw has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 9. 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. This shape REPEATS in the file: one other method here (ShaderStages::validate_device_raw) 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.
GenericMemoryAllocator::try_allocate (cognitive 30) vulkano/src/memory/allocator/mod.rs:1597— GenericMemoryAllocator::try_allocate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (GenericMemoryAllocator::allocate_unchecked) 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.
GenericMemoryAllocator::allocate_unchecked (cognitive 30) vulkano/src/memory/allocator/mod.rs:1801— GenericMemoryAllocator::allocate_unchecked has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (GenericMemoryAllocator::try_allocate) 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.
GenericMemoryAllocator::new (cognitive 19) vulkano/src/memory/allocator/mod.rs:1059— GenericMemoryAllocator::new has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (58 corresponding lines) · ×3
Edited copy of a member (58 corresponding lines) vulkano/src/buffer/subbuffer.rs:306— vulkano/src/buffer/subbuffer.rs:306-369 | vulkano/src/buffer/subbuffer.rs:400-457 — These two members are one piece of code written twice and then edited apart: 58 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 (58 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs:457— vulkano/src/memory/allocator/suballocator/free_list.rs:457-515 | vulkano/src/memory/allocator/suballocator/tlsf.rs:612-669 — These two members are one piece of code written twice and then edited apart: 58 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 (58 corresponding lines) vulkano/src/command_buffer/allocator.rs:490— vulkano/src/command_buffer/allocator.rs:490-547 | vulkano/src/command_buffer/allocator.rs:554-612 — These two members are one piece of code written twice and then edited apart: 58 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 (41 corresponding lines) · ×3
Edited copy of a member (41 corresponding lines) vulkano-taskgraph/src/lib.rs:469— vulkano-taskgraph/src/lib.rs:469-509 | vulkano-taskgraph/src/lib.rs:611-651 — These two members are one piece of code written twice and then edited apart: 41 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 (41 corresponding lines) vulkano/src/command_buffer/auto/commands/clear.rs:55— vulkano/src/command_buffer/auto/commands/clear.rs:55-95 | vulkano/src/command_buffer/auto/commands/clear.rs:136-176 — These two members are one piece of code written twice and then edited apart: 41 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 (41 corresponding lines) vulkano/src/memory/sparse.rs:140— vulkano/src/memory/sparse.rs:140-190 | vulkano/src/render_pass/mod.rs:1817-1857 — These two members are one piece of code written twice and then edited apart: 41 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 (29 corresponding lines) · ×3
Edited copy of a member (29 corresponding lines) vulkano/src/command_buffer/auto/commands/pipeline.rs:76— vulkano/src/command_buffer/auto/commands/pipeline.rs:76-104 | vulkano/src/command_buffer/auto/commands/pipeline.rs:148-177 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) vulkano/src/sync/semaphore.rs:480— vulkano/src/sync/semaphore.rs:480-508 | vulkano/src/sync/semaphore.rs:577-611 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) vulkano/src/command_buffer/commands/render_pass.rs:449— vulkano/src/command_buffer/commands/render_pass.rs:449-481 | vulkano/src/command_buffer/commands/render_pass.rs:543-571 — These two members are one piece of code written twice and then edited apart: 29 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) · ×3
Edited copy of a member (24 corresponding lines) vulkano/src/command_buffer/commands/copy.rs:5737— vulkano/src/command_buffer/commands/copy.rs:5737-5760 | vulkano/src/command_buffer/commands/copy.rs:5782-5806 — 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.
Edited copy of a member (24 corresponding lines) vulkano/src/shader/reflect.rs:1251— vulkano/src/shader/reflect.rs:1251-1277 | vulkano/src/shader/reflect.rs:1282-1305 — 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.
Edited copy of a member (24 corresponding lines) autogen/src/extensions.rs:61— autogen/src/extensions.rs:61-84 | autogen/src/features.rs:110-134 — 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 copy of a member (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) vulkano/src/device/mod.rs:270— vulkano/src/device/mod.rs:270-302 | vulkano/src/instance/mod.rs:348-373 — 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.
Edited copy of a member (26 corresponding lines) vulkano/src/command_buffer/commands/render_pass.rs:1057— vulkano/src/command_buffer/commands/render_pass.rs:1057-1082 | vulkano/src/command_buffer/commands/render_pass.rs:1967-2002 — 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.
Edited copy of a member (26 corresponding lines) vulkano/src/memory/allocator/mod.rs:1199— vulkano/src/memory/allocator/mod.rs:1199-1224 | vulkano/src/memory/allocator/mod.rs:1233-1262 — 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 (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) vulkano/src/instance/debug.rs:120— vulkano/src/instance/debug.rs:120-144 | vulkano/src/shader/mod.rs:535-555 — 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) vulkano/src/command_buffer/commands/clear.rs:33— vulkano/src/command_buffer/commands/clear.rs:33-53 | vulkano/src/command_buffer/commands/copy.rs:36-56 — 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) vulkano-taskgraph/src/command_buffer/commands/clear.rs:196— vulkano-taskgraph/src/command_buffer/commands/clear.rs:196-220 | vulkano-taskgraph/src/command_buffer/commands/clear.rs:273-293 — 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 (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) vulkano/src/descriptor_set/allocator.rs:520— vulkano/src/descriptor_set/allocator.rs:520-534 | vulkano/src/descriptor_set/allocator.rs:540-555 — 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) vulkano-taskgraph/src/graph/compile.rs:883— vulkano-taskgraph/src/graph/compile.rs:883-901 | vulkano-taskgraph/src/graph/compile.rs:908-922 — 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) vulkano/src/command_buffer/commands/clear.rs:580— vulkano/src/command_buffer/commands/clear.rs:580-594 | vulkano/src/command_buffer/commands/copy.rs:4567-4581 — 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 copies of one member (3 members, 12+ corresponding lines) · ×3
Edited copies of one member (3 members, 12+ corresponding lines) vulkano-taskgraph/src/graph/mod.rs:427— vulkano-taskgraph/src/graph/mod.rs:427-439 | vulkano-taskgraph/src/graph/mod.rs:444-456 | vulkano-taskgraph/src/graph/mod.rs:461-472 — 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.
Edited copies of one member (3 members, 12+ corresponding lines) vulkano-taskgraph/src/graph/execute.rs:2889— vulkano-taskgraph/src/graph/execute.rs:2889-2900 | vulkano-taskgraph/src/graph/execute.rs:2909-2920 | vulkano-taskgraph/src/graph/execute.rs:2932-2943 — 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.
Edited copies of one member (3 members, 12+ corresponding lines) vulkano-taskgraph/src/lib.rs:276— vulkano-taskgraph/src/lib.rs:276-287 | vulkano-taskgraph/src/lib.rs:311-324 | vulkano-taskgraph/src/lib.rs:343-354 — 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.
Duplicated block (40 lines × 2) autogen/src/extensions.rs:151— autogen/src/extensions.rs:151-190 | autogen/src/features.rs:179-218 — before extracting anything, compare `autogen/src/extensions.rs` and `autogen/src/features.rs` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/extensions.rs:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (40 lines × 2) vulkano-taskgraph/src/collector.rs:768— vulkano-taskgraph/src/collector.rs:768-807 | vulkano-taskgraph/src/collector.rs:834-873 — 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, `vulkano-taskgraph/src/collector.rs:877` calls `get`, `collect_predicate`, `Continue` and `vulkano-taskgraph/src/collector.rs:809` 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 (40 lines × 2) vulkano/src/command_buffer/auto/commands/copy.rs:363— vulkano/src/command_buffer/auto/commands/copy.rs:363-402 | vulkano/src/command_buffer/auto/commands/copy.rs:498-537 — 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 `vulkano/src/command_buffer/auto/commands/copy.rs:363` 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 (30 lines × 2) vulkano-taskgraph/src/graph/execute.rs:282— vulkano-taskgraph/src/graph/execute.rs:282-311 | vulkano-taskgraph/src/graph/execute.rs:611-640 — 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 `vulkano-taskgraph/src/graph/execute.rs:282` 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 (30 lines × 2) vulkano-taskgraph/src/graph/execute.rs:991— vulkano-taskgraph/src/graph/execute.rs:991-1020 | vulkano-taskgraph/src/graph/execute.rs:1606-1635 — 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 `vulkano-taskgraph/src/graph/execute.rs:991` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) vulkano/src/command_buffer/auto/commands/copy.rs:1061— vulkano/src/command_buffer/auto/commands/copy.rs:1061-1090 | vulkano/src/command_buffer/auto/commands/copy.rs:1564-1593 — 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 `vulkano/src/command_buffer/auto/commands/copy.rs:1061` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) vulkano-taskgraph/src/command_buffer/commands/sync.rs:85— vulkano-taskgraph/src/command_buffer/commands/sync.rs:85-107 | vulkano-taskgraph/src/command_buffer/commands/sync.rs:184-206 — 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 `vulkano-taskgraph/src/command_buffer/commands/sync.rs:85` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano-taskgraph/src/command_buffer/commands/sync.rs:208` calls `into` and `vulkano-taskgraph/src/command_buffer/commands/sync.rs:109` 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 (23 lines × 2) vulkano/src/command_buffer/commands/copy.rs:3869— vulkano/src/command_buffer/commands/copy.rs:3869-3891 | vulkano/src/command_buffer/commands/copy.rs:4584-4606 — 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 (23 lines × 2) vulkano/src/command_buffer/commands/copy.rs:264— vulkano/src/command_buffer/commands/copy.rs:264-288 | vulkano/src/command_buffer/commands/copy.rs:349-371 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/commands/copy.rs:264` 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 × 2) autogen/src/extensions.rs:415— autogen/src/extensions.rs:415-423 | autogen/src/features.rs:462-471 — before extracting anything, compare `autogen/src/extensions.rs` and `autogen/src/features.rs` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/extensions.rs:415` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:833— vulkano-taskgraph/src/command_buffer/commands/copy.rs:833-841 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:871-880 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:871` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 2) vulkano/src/buffer/mod.rs:801— vulkano/src/buffer/mod.rs:801-809 | vulkano/src/image/mod.rs:816-825 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:801` it does not close everything it opens, so those 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–8 lines × 2) autogen/src/extensions.rs:433— autogen/src/extensions.rs:433-439 | autogen/src/features.rs:474-481 — before extracting anything, compare `autogen/src/extensions.rs` and `autogen/src/features.rs` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `autogen/src/extensions.rs:433` it does not close everything it opens, so those 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–8 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:440— vulkano-taskgraph/src/command_buffer/commands/copy.rs:440-446 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:474-481 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:474` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:612— vulkano-taskgraph/src/command_buffer/commands/copy.rs:612-618 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:646-653 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:646` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
DynamicState::validate_device_raw (cyclomatic 47) vulkano/src/pipeline/mod.rs:996— DynamicState::validate_device_raw has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DynamicState::validate_instance_raw) 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.
DynamicState::validate_instance_raw (cyclomatic 47) vulkano/src/pipeline/mod.rs:996— DynamicState::validate_instance_raw has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DynamicState::validate_device_raw) 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.
PipelineStage::validate_device_raw (cyclomatic 47) vulkano/src/sync/pipeline.rs:15— PipelineStage::validate_device_raw has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (PipelineStage::validate_instance_raw) 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. This is NOT this file's highest cyclomatic complexity: PipelineStages::from (cyclomatic 99) 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.
PipelineStage::validate_instance_raw (cyclomatic 47) vulkano/src/sync/pipeline.rs:15— PipelineStage::validate_instance_raw has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (PipelineStage::validate_device_raw) 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. This is NOT this file's highest cyclomatic complexity: PipelineStages::from (cyclomatic 99) 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.
ColorSpace::validate_device_raw (cyclomatic 31) vulkano/src/swapchain/surface.rs:2512— ColorSpace::validate_device_raw has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ColorSpace::validate_instance_raw) 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.
ColorSpace::validate_instance_raw (cyclomatic 31) vulkano/src/swapchain/surface.rs:2512— ColorSpace::validate_instance_raw has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ColorSpace::validate_device_raw) 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.
RawImage::validate_bind_memory (cyclomatic 30) vulkano/src/image/sys.rs:583— RawImage::validate_bind_memory 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.
RawImage::validate_subresource_layout (cyclomatic 27) vulkano/src/image/sys.rs:1317— RawImage::validate_subresource_layout 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.
ShaderStage::validate_device_raw (cyclomatic 19) vulkano/src/shader/mod.rs:1416— ShaderStage::validate_device_raw 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. This shape REPEATS in the file: one other method here (ShaderStage::validate_instance_raw) 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.
ShaderStage::validate_instance_raw (cyclomatic 19) vulkano/src/shader/mod.rs:1416— ShaderStage::validate_instance_raw 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. This shape REPEATS in the file: one other method here (ShaderStage::validate_device_raw) 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.
Hotspot: vulkano/src/pipeline/mod.rs vulkano/src/pipeline/mod.rs:996— vulkano/src/pipeline/mod.rs changed 2 times in last 90 days, max cyclomatic complexity 47 in DynamicState::validate_device_raw at line 996. 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-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 08:55:38 +00:00' --until='2026-11-04 08:55:38 +00:00' --full-history --no-merges -- vulkano/src/pipeline/mod.rs`: 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.
Hotspot: vulkano/src/device/queue.rs vulkano/src/device/queue.rs:1274— vulkano/src/device/queue.rs changed 2 times in last 90 days, max cyclomatic complexity 18 in QueueFlags::fmt at line 1274. 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-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 08:55:38 +00:00' --until='2026-11-04 08:55:38 +00:00' --full-history --no-merges -- vulkano/src/device/queue.rs`: 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.
RenderPassCreateInfo::validate (cognitive 136) vulkano/src/render_pass/mod.rs:984— RenderPassCreateInfo::validate has cognitive complexity 136 (threshold 15). Drivers by points: if/else 44 (112 pts), boolean chains 12, loops 6 (9 pts), match/switch 1 (3 pts) (nesting depth added 73). 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.
RenderPassCreateInfo::to_vk_fields1 (cognitive 19) vulkano/src/render_pass/mod.rs:2014— RenderPassCreateInfo::to_vk_fields1 has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskGraph::compile (cognitive 77) vulkano-taskgraph/src/graph/compile.rs:60— TaskGraph::compile has cognitive complexity 77 (threshold 15). Drivers by points: if/else 18 (47 pts), loops 11 (24 pts), match/switch 5, boolean chains 1 (nesting depth added 42). 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.
TaskGraph::lower (cognitive 24) vulkano-taskgraph/src/graph/compile.rs:505— TaskGraph::lower has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 4 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AutoSyncState::add_image (cognitive 70) vulkano/src/command_buffer/auto/builder.rs:1096— AutoSyncState::add_image has cognitive complexity 70 (threshold 15). Drivers by points: if/else 16 (52 pts), match/switch 3 (10 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 44). 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.
AutoSyncState::add_buffer (cognitive 16) vulkano/src/command_buffer/auto/builder.rs:971— AutoSyncState::add_buffer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 1 (3 pts), boolean chains 1, loops 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.
RawImage::validate_bind_memory (cognitive 64) vulkano/src/image/sys.rs:583— RawImage::validate_bind_memory has cognitive complexity 64 (threshold 15). Drivers by points: if/else 25 (52 pts), match/switch 3 (7 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 33). 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.
RawImage::validate_subresource_layout (cognitive 41) vulkano/src/image/sys.rs:1317— RawImage::validate_subresource_layout has cognitive complexity 41 (threshold 15). Drivers by points: if/else 21 (38 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 18). 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.
DynamicState::validate_device_raw (cognitive 47) vulkano/src/pipeline/mod.rs:996— DynamicState::validate_device_raw has cognitive complexity 47 (threshold 15). Drivers by points: if/else 23 (46 pts), match/switch 1 (nesting depth added 23). 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. This shape REPEATS in the file: one other method here (DynamicState::validate_instance_raw) 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.
DynamicState::validate_instance_raw (cognitive 47) vulkano/src/pipeline/mod.rs:996— DynamicState::validate_instance_raw has cognitive complexity 47 (threshold 15). Drivers by points: if/else 23 (46 pts), match/switch 1 (nesting depth added 23). 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. This shape REPEATS in the file: one other method here (DynamicState::validate_device_raw) 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.
PipelineStage::validate_device_raw (cognitive 47) vulkano/src/sync/pipeline.rs:15— PipelineStage::validate_device_raw has cognitive complexity 47 (threshold 15). Drivers by points: if/else 23 (46 pts), match/switch 1 (nesting depth added 23). 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. This shape REPEATS in the file: one other method here (PipelineStage::validate_instance_raw) 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.
PipelineStage::validate_instance_raw (cognitive 47) vulkano/src/sync/pipeline.rs:15— PipelineStage::validate_instance_raw has cognitive complexity 47 (threshold 15). Drivers by points: if/else 23 (46 pts), match/switch 1 (nesting depth added 23). 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. This shape REPEATS in the file: one other method here (PipelineStage::validate_device_raw) 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.
ColorSpace::validate_device_raw (cognitive 31) vulkano/src/swapchain/surface.rs:2512— ColorSpace::validate_device_raw has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (30 pts), match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (ColorSpace::validate_instance_raw) 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.
ColorSpace::validate_instance_raw (cognitive 31) vulkano/src/swapchain/surface.rs:2512— ColorSpace::validate_instance_raw has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (30 pts), match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (ColorSpace::validate_device_raw) 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.
SwapchainState::collect (cognitive 22) vulkano-taskgraph/src/resource/state.rs:407— SwapchainState::collect has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapchainState::handle_recreation (cognitive 21) vulkano-taskgraph/src/resource/state.rs:587— SwapchainState::handle_recreation has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 1 (2 pts), boolean chains 1 (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.
IntermediateRepresentationBuilder::resource_access (cognitive 20) vulkano-taskgraph/src/graph/compile.rs:758— IntermediateRepresentationBuilder::resource_access has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 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.
IntermediateRepresentationBuilder::subpass (cognitive 19) vulkano-taskgraph/src/graph/compile.rs:673— IntermediateRepresentationBuilder::subpass has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2, 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.
ShaderStage::validate_device_raw (cognitive 19) vulkano/src/shader/mod.rs:1416— ShaderStage::validate_device_raw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 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. This shape REPEATS in the file: one other method here (ShaderStage::validate_instance_raw) 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.
ShaderStage::validate_instance_raw (cognitive 19) vulkano/src/shader/mod.rs:1416— ShaderStage::validate_instance_raw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 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. This shape REPEATS in the file: one other method here (ShaderStage::validate_device_raw) 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.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (9 members, 50+ identical tokens) vulkano/src/command_buffer/auto/commands/pipeline.rs:241— vulkano/src/command_buffer/auto/commands/pipeline.rs:241-357 | vulkano/src/command_buffer/auto/commands/pipeline.rs:428-464 | vulkano/src/command_buffer/auto/commands/pipeline.rs:557-595 | vulkano/src/command_buffer/auto/commands/pipeline.rs:702-833 | vulkano/src/command_buffer/auto/commands/pipeline.rs:919-963 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1063-1109 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1173-1309 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1370-1416 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1507-1555 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
Members sharing a duplicated core (9 members, 50+ identical tokens) vulkano/src/format.rs:833— vulkano/src/format.rs:833-855 | vulkano/src/image/mod.rs:2243-2294 | vulkano/src/image/sys.rs:3101-3176 | vulkano/src/memory/device_memory.rs:1304-1345 | vulkano/src/pipeline/graphics/mod.rs:2387-2498 | vulkano/src/swapchain/acquire_present.rs:552-597 | vulkano/src/swapchain/mod.rs:2607-2684 | vulkano/src/swapchain/surface.rs:2836-2858 | vulkano/src/swapchain/surface.rs:3000-3027 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) vulkano-taskgraph/src/command_buffer/commands/copy.rs:43— vulkano-taskgraph/src/command_buffer/commands/copy.rs:43-153 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:208-376 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:406-548 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:578-720 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:797-952 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:979-1147 — 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) vulkano/src/command_buffer/commands/copy.rs:62— vulkano/src/command_buffer/commands/copy.rs:62-100 | vulkano/src/command_buffer/commands/copy.rs:417-456 | vulkano/src/command_buffer/commands/copy.rs:695-740 | vulkano/src/command_buffer/commands/copy.rs:959-1004 | vulkano/src/command_buffer/commands/copy.rs:1051-1092 | vulkano/src/command_buffer/commands/copy.rs:1139-1181 — 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 (47 corresponding lines) · ×2
Edited copy of a member (47 corresponding lines) vulkano-taskgraph/src/graph/execute.rs:278— vulkano-taskgraph/src/graph/execute.rs:278-324 | vulkano-taskgraph/src/graph/execute.rs:607-653 — These two members are one piece of code written twice and then edited apart: 47 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 (47 corresponding lines) vulkano/src/render_pass/mod.rs:3645— vulkano/src/render_pass/mod.rs:3645-3694 | vulkano/src/render_pass/mod.rs:3866-3912 — These two members are one piece of code written twice and then edited apart: 47 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 (48 corresponding lines) · ×2
Edited copy of a member (48 corresponding lines) vulkano/src/command_buffer/auto/commands/render_pass.rs:192— vulkano/src/command_buffer/auto/commands/render_pass.rs:192-244 | vulkano/src/command_buffer/auto/commands/render_pass.rs:306-353 — These two members are one piece of code written twice and then edited apart: 48 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 (48 corresponding lines) vulkano-taskgraph/src/command_buffer/commands/clear.rs:44— vulkano-taskgraph/src/command_buffer/commands/clear.rs:44-91 | vulkano-taskgraph/src/command_buffer/commands/clear.rs:121-168 — These two members are one piece of code written twice and then edited apart: 48 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 (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) vulkano/src/command_buffer/commands/sync.rs:1113— vulkano/src/command_buffer/commands/sync.rs:1113-1146 | vulkano/src/memory/sparse.rs:78-115 — These two members are one piece of code written twice and then edited apart: 34 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 (34 corresponding lines) vulkano/src/command_buffer/auto/builder.rs:823— vulkano/src/command_buffer/auto/builder.rs:823-856 | vulkano/src/command_buffer/auto/builder.rs:865-907 — These two members are one piece of code written twice and then edited apart: 34 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 (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) vulkano/src/command_buffer/allocator.rs:647— vulkano/src/command_buffer/allocator.rs:647-678 | vulkano/src/command_buffer/allocator.rs:685-717 — 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) vulkano-taskgraph/src/graph/execute.rs:948— vulkano-taskgraph/src/graph/execute.rs:948-984 | vulkano-taskgraph/src/graph/execute.rs:1568-1599 — 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 (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) vulkano/src/pipeline/graphics/mod.rs:232— vulkano/src/pipeline/graphics/mod.rs:232-276 | vulkano/src/pipeline/ray_tracing.rs:156-186 — These two members are one piece of code written twice and then edited apart: 31 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 (31 corresponding lines) vulkano/src/sync/event.rs:140— vulkano/src/sync/event.rs:140-170 | vulkano/src/sync/fence.rs:142-173 — These two members are one piece of code written twice and then edited apart: 31 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) · ×2
Edited copy of a member (28 corresponding lines) vulkano/src/command_buffer/traits.rs:385— vulkano/src/command_buffer/traits.rs:385-412 | vulkano/src/command_buffer/traits.rs:421-460 — 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.
Edited copy of a member (28 corresponding lines) vulkano/src/image/mod.rs:187— vulkano/src/image/mod.rs:187-214 | vulkano/src/image/mod.rs:231-258 — 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 copies of one member (4 members, 28+ corresponding lines) · ×2
Edited copies of one member (4 members, 28+ corresponding lines) vulkano/src/command_buffer/commands/sync.rs:2521— vulkano/src/command_buffer/commands/sync.rs:2521-2550 | vulkano/src/command_buffer/commands/sync.rs:2552-2579 | vulkano/src/command_buffer/commands/sync.rs:3664-3695 | vulkano/src/command_buffer/commands/sync.rs:3697-3726 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 28 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.
Edited copies of one member (4 members, 28+ corresponding lines) vulkano/src/acceleration_structure.rs:1678— vulkano/src/acceleration_structure.rs:1678-1709 | vulkano/src/acceleration_structure.rs:1763-1797 | vulkano/src/pipeline/graphics/discard_rectangle.rs:56-83 | vulkano/src/pipeline/graphics/rasterization.rs:708-736 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 28 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 copies of one member (4 members, 16+ corresponding lines) · ×2
Edited copies of one member (4 members, 16+ corresponding lines) vulkano/src/device/private_data.rs:73— vulkano/src/device/private_data.rs:73-89 | vulkano/src/image/sampler/ycbcr.rs:186-202 | vulkano/src/instance/debug.rs:99-114 | vulkano/src/sync/event.rs:88-105 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 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.
Edited copies of one member (4 members, 16+ corresponding lines) vulkano-taskgraph/src/slotmap.rs:408— vulkano-taskgraph/src/slotmap.rs:408-423 | vulkano-taskgraph/src/slotmap.rs:428-443 | vulkano-taskgraph/src/slotmap.rs:457-472 | vulkano-taskgraph/src/slotmap.rs:477-492 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 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 (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) vulkano/src/memory/device_memory.rs:2598— vulkano/src/memory/device_memory.rs:2598-2604 | vulkano/src/memory/device_memory.rs:2638-2649 — 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) vulkano/src/pipeline/graphics/mod.rs:2717— vulkano/src/pipeline/graphics/mod.rs:2717-2725 | vulkano/src/pipeline/ray_tracing.rs:776-782 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) vulkano/src/buffer/view.rs:433— vulkano/src/buffer/view.rs:433-438 | vulkano/src/render_pass/framebuffer.rs:380-383 — 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.
Edited copy of a member (4 corresponding lines) vulkano/src/command_buffer/sys.rs:247— vulkano/src/command_buffer/sys.rs:247-250 | vulkano/src/descriptor_set/sys.rs:288-291 — 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.
Duplicated block (42 lines × 2) vulkano/src/device/physical.rs:1918— vulkano/src/device/physical.rs:1918-1959 | vulkano/src/device/physical.rs:2126-2167 — 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 `vulkano/src/device/physical.rs:1918` 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 (42 lines × 2) vulkano/src/command_buffer/commands/sync.rs:2475— vulkano/src/command_buffer/commands/sync.rs:2475-2516 | vulkano/src/command_buffer/commands/sync.rs:3371-3412 — 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 `vulkano/src/command_buffer/commands/sync.rs:2475` 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 (25 lines × 2) vulkano-taskgraph/src/graph/execute.rs:1668— vulkano-taskgraph/src/graph/execute.rs:1668-1692 | vulkano-taskgraph/src/graph/execute.rs:1711-1735 — 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 `vulkano-taskgraph/src/graph/execute.rs:1668` 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 (25 lines × 2) vulkano/src/device/physical.rs:1961— vulkano/src/device/physical.rs:1961-1985 | vulkano/src/device/physical.rs:2413-2437 — 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 `vulkano/src/device/physical.rs:1961` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 3) vulkano/src/command_buffer/commands/copy.rs:1892— vulkano/src/command_buffer/commands/copy.rs:1892-1915 | vulkano/src/command_buffer/commands/copy.rs:5302-5325 | vulkano/src/command_buffer/commands/copy.rs:6331-6354 — 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 `vulkano/src/command_buffer/commands/copy.rs:1892` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (24 lines × 3) vulkano/src/command_buffer/commands/copy.rs:2291— vulkano/src/command_buffer/commands/copy.rs:2291-2314 | vulkano/src/command_buffer/commands/copy.rs:5515-5538 | vulkano/src/command_buffer/commands/copy.rs:6534-6557 — 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 (22 lines × 3) vulkano/src/descriptor_set/update.rs:633— vulkano/src/descriptor_set/update.rs:633-654 | vulkano/src/descriptor_set/update.rs:734-755 | vulkano/src/descriptor_set/update.rs:841-862 — 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 (22 lines × 3) vulkano/src/image/mod.rs:2266— vulkano/src/image/mod.rs:2266-2287 | vulkano/src/image/sys.rs:3148-3169 | vulkano/src/swapchain/mod.rs:2656-2677 — before extracting anything, compare `vulkano/src/image/mod.rs` and `vulkano/src/image/sys.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/image/mod.rs:2266` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `extensions_vk` to `&'a mut ImageFormatInfo2ExtensionsVk<'_>` in one and `&'a mut ImageCreateInfoExtensionsVk<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19 lines × 3) vulkano/src/format.rs:837— vulkano/src/format.rs:837-855 | vulkano/src/pipeline/graphics/mod.rs:2480-2498 | vulkano/src/swapchain/surface.rs:2840-2858 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/format.rs:837` 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 `extensions_vk` to `&'a mut GraphicsPipelineCreateInfoExtensionsVk<'_>` in one and `&'a mut SurfaceInfo2ExtensionsVk` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19 lines × 3) vulkano/src/command_buffer/commands/copy.rs:2110— vulkano/src/command_buffer/commands/copy.rs:2110-2128 | vulkano/src/command_buffer/commands/copy.rs:5384-5402 | vulkano/src/command_buffer/commands/copy.rs:6416-6434 — 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 (18–19 lines × 2) autogen/src/spirv_parse.rs:751— autogen/src/spirv_parse.rs:751-769 | autogen/src/spirv_parse.rs:906-923 — 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 `autogen/src/spirv_parse.rs:751` 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–19 lines × 2) vulkano/src/command_buffer/commands/sync.rs:59— vulkano/src/command_buffer/commands/sync.rs:59-76 | vulkano/src/command_buffer/commands/sync.rs:555-573 — 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 `vulkano/src/command_buffer/commands/sync.rs:59` it does not close everything it opens, so those exact lines 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 × 4) vulkano/src/command_buffer/commands/copy.rs:3103— vulkano/src/command_buffer/commands/copy.rs:3103-3119 | vulkano/src/command_buffer/commands/copy.rs:3142-3158 | vulkano/src/command_buffer/commands/copy.rs:6846-6862 | vulkano/src/command_buffer/commands/copy.rs:6885-6901 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 4) vulkano/src/descriptor_set/update.rs:453— vulkano/src/descriptor_set/update.rs:453-469 | vulkano/src/descriptor_set/update.rs:698-714 | vulkano/src/descriptor_set/update.rs:805-821 | vulkano/src/descriptor_set/update.rs:1211-1227 — 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 `vulkano/src/descriptor_set/update.rs:453` 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, `vulkano/src/descriptor_set/update.rs:451` calls `is_empty` and `vulkano/src/descriptor_set/update.rs:696` 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 (17 lines × 3) vulkano/src/command_buffer/commands/sync.rs:153— vulkano/src/command_buffer/commands/sync.rs:153-169 | vulkano/src/command_buffer/commands/sync.rs:417-433 | vulkano/src/command_buffer/commands/sync.rs:651-667 — 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 `vulkano/src/command_buffer/commands/sync.rs:153` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 3) vulkano/src/command_buffer/auto/commands/secondary.rs:220— vulkano/src/command_buffer/auto/commands/secondary.rs:220-236 | vulkano/src/command_buffer/auto/commands/secondary.rs:260-276 | vulkano/src/command_buffer/auto/commands/secondary.rs:300-316 — 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 `vulkano/src/command_buffer/auto/commands/secondary.rs:220` 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 × 4) vulkano/src/descriptor_set/allocator.rs:418— vulkano/src/descriptor_set/allocator.rs:418-431 | vulkano/src/descriptor_set/allocator.rs:477-490 | vulkano/src/descriptor_set/allocator.rs:574-587 | vulkano/src/descriptor_set/allocator.rs:609-622 — 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 `vulkano/src/descriptor_set/allocator.rs:418` it does not close everything it opens, so those 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 `layout` to `&Arc<DescriptorSetLayout>` in one and `&DescriptorSetLayout` 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 (14 lines × 4) vulkano/src/command_buffer/auto/commands/pipeline.rs:3107— vulkano/src/command_buffer/auto/commands/pipeline.rs:3107-3120 | vulkano/src/command_buffer/auto/commands/pipeline.rs:3125-3138 | vulkano/src/command_buffer/auto/commands/pipeline.rs:3143-3156 | vulkano/src/command_buffer/auto/commands/pipeline.rs:3177-3190 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:3107` 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 × 6) vulkano/src/image/mod.rs:2273— vulkano/src/image/mod.rs:2273-2285 | vulkano/src/image/sys.rs:3155-3167 | vulkano/src/memory/device_memory.rs:1325-1337 | vulkano/src/swapchain/acquire_present.rs:580-592 | vulkano/src/swapchain/mod.rs:2663-2675 | vulkano/src/swapchain/surface.rs:3010-3022 — before extracting anything, compare `vulkano/src/image/mod.rs` and `vulkano/src/image/sys.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/image/mod.rs:2273` it does not close everything it opens, so those exact lines 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 × 6) vulkano/src/device/physical.rs:2980— vulkano/src/device/physical.rs:2980-2995 | vulkano/src/device/physical.rs:3059-3071 | vulkano/src/device/physical.rs:3148-3163 | vulkano/src/device/physical.rs:3246-3261 | vulkano/src/device/physical.rs:3340-3355 | vulkano/src/device/physical.rs:3431-3446 — 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 `vulkano/src/device/physical.rs:2980` 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–13 lines × 2) vulkano/src/command_buffer/commands/clear.rs:501— vulkano/src/command_buffer/commands/clear.rs:501-512 | vulkano/src/command_buffer/commands/clear.rs:729-741 — 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 `vulkano/src/command_buffer/commands/clear.rs:501` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) vulkano/src/command_buffer/mod.rs:759— vulkano/src/command_buffer/mod.rs:759-771 | vulkano/src/pipeline/graphics/subpass.rs:187-198 — before extracting anything, compare `vulkano/src/command_buffer/mod.rs` and `vulkano/src/pipeline/graphics/subpass.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 `vulkano/src/command_buffer/mod.rs:759` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) vulkano/src/device/mod.rs:723— vulkano/src/device/mod.rs:723-733 | vulkano/src/device/mod.rs:889-900 — 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 `vulkano/src/device/mod.rs:723` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–12 lines × 2) vulkano/src/device/physical.rs:2273— vulkano/src/device/physical.rs:2273-2283 | vulkano/src/device/physical.rs:2505-2516 — 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 `vulkano/src/device/physical.rs:2273` 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 lines × 4) vulkano/src/command_buffer/commands/copy.rs:3168— vulkano/src/command_buffer/commands/copy.rs:3168-3177 | vulkano/src/command_buffer/commands/copy.rs:4849-4858 | vulkano/src/command_buffer/commands/copy.rs:6911-6920 | vulkano/src/memory/sparse.rs:1634-1643 — before extracting anything, compare `vulkano/src/command_buffer/commands/copy.rs` and `vulkano/src/memory/sparse.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) vulkano/src/pipeline/graphics/color_blend.rs:835— vulkano/src/pipeline/graphics/color_blend.rs:835-844 | vulkano/src/pipeline/graphics/color_blend.rs:852-861 | vulkano/src/pipeline/graphics/color_blend.rs:869-878 | vulkano/src/pipeline/graphics/color_blend.rs:886-895 — 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 `vulkano/src/pipeline/graphics/color_blend.rs:835` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 6) vulkano-taskgraph/src/command_buffer/commands/copy.rs:54— vulkano-taskgraph/src/command_buffer/commands/copy.rs:54-59 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:223-228 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:419-424 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:591-596 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:813-818 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:994-999 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vulkano-taskgraph/src/command_buffer/commands/copy.rs:589` calls `buffer_unchecked` and `vulkano-taskgraph/src/command_buffer/commands/copy.rs:221` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 6) vulkano/src/device/mod.rs:1433— vulkano/src/device/mod.rs:1433-1438 | vulkano/src/device/mod.rs:1540-1545 | vulkano/src/device/mod.rs:1654-1659 | vulkano/src/device/queue.rs:372-377 | vulkano/src/device/queue.rs:731-736 | vulkano/src/memory/device_memory.rs:430-435 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/device/mod.rs:1433` 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 × 3) vulkano/src/buffer/mod.rs:870— vulkano/src/buffer/mod.rs:870-874 | vulkano/src/buffer/mod.rs:897-901 | vulkano/src/image/mod.rs:898-902 — `vulkano/src/buffer/mod.rs` and `vulkano/src/image/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 138 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/mod.rs:870` it does not close everything it opens, so those 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 `self` to `crate) unsafe fn gpu_read_unlock(&mut` in one and `crate) unsafe fn gpu_write_lock(&mut` 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) vulkano/src/device/physical.rs:3124— vulkano/src/device/physical.rs:3124-3130 | vulkano/src/device/physical.rs:3222-3228 | vulkano/src/image/sys.rs:1311-1315 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/device/physical.rs:3124` 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) vulkano/src/sync/fence.rs:1433— vulkano/src/sync/fence.rs:1433-1447 | vulkano/src/sync/semaphore.rs:2151-2165 | vulkano/src/sync/semaphore.rs:2256-2269 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/semaphore.rs:2151` 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) vulkano/src/command_buffer/commands/copy.rs:124— vulkano/src/command_buffer/commands/copy.rs:124-137 | vulkano/src/command_buffer/commands/copy.rs:482-495 | vulkano/src/command_buffer/commands/copy.rs:767-780 — 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 (9 lines × 4) vulkano/src/pipeline/layout.rs:925— vulkano/src/pipeline/layout.rs:925-935 | vulkano/src/pipeline/layout.rs:957-965 | vulkano/src/pipeline/layout.rs:989-999 | vulkano/src/pipeline/layout.rs:1018-1026 — 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 `vulkano/src/pipeline/layout.rs:925` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vulkano/src/pipeline/layout.rs:922` calls `Some`, `into_iter`, `max_by_key` and `vulkano/src/pipeline/layout.rs:986` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 4) vulkano/src/pipeline/graphics/mod.rs:1482— vulkano/src/pipeline/graphics/mod.rs:1482-1490 | vulkano/src/pipeline/graphics/mod.rs:1494-1502 | vulkano/src/pipeline/graphics/mod.rs:1506-1514 | vulkano/src/pipeline/graphics/mod.rs:1518-1526 — 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 `vulkano/src/pipeline/graphics/mod.rs:1482` it does not close everything it opens, so those exact lines 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 × 5) vulkano/src/sync/fence.rs:839— vulkano/src/sync/fence.rs:839-848 | vulkano/src/sync/fence.rs:927-936 | vulkano/src/sync/semaphore.rs:1070-1079 | vulkano/src/sync/semaphore.rs:1184-1193 | vulkano/src/sync/semaphore.rs:1293-1302 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/fence.rs:839` 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 × 5) vulkano/src/sync/fence.rs:610— vulkano/src/sync/fence.rs:610-619 | vulkano/src/sync/fence.rs:740-749 | vulkano/src/sync/semaphore.rs:694-703 | vulkano/src/sync/semaphore.rs:845-854 | vulkano/src/sync/semaphore.rs:970-979 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/fence.rs:610` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `handle_type` to `ExternalFenceHandleType` in one and `ExternalSemaphoreHandleType` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1128— vulkano/src/command_buffer/commands/sync.rs:1128-1133 | vulkano/src/command_buffer/mod.rs:1035-1042 | vulkano/src/memory/sparse.rs:93-100 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:1128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 3) vulkano/src/command_buffer/mod.rs:1037— vulkano/src/command_buffer/mod.rs:1037-1042 | vulkano/src/memory/sparse.rs:95-100 | vulkano/src/memory/sparse.rs:101-106 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/mod.rs:1037` 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.
GraphicsPipelineCreateInfo::validate (cyclomatic 186) vulkano/src/pipeline/graphics/mod.rs:806— GraphicsPipelineCreateInfo::validate has cyclomatic complexity 186 (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.
ImageCreateInfo::validate (cyclomatic 149) vulkano/src/image/sys.rs:1788— ImageCreateInfo::validate has cyclomatic complexity 149 (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.
WriteDescriptorSet::validate (cyclomatic 125) vulkano/src/descriptor_set/update.rs:204— WriteDescriptorSet::validate has cyclomatic complexity 125 (threshold 15). Of this number, 121 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CopyImageInfo::validate (cyclomatic 124) vulkano/src/command_buffer/commands/copy.rs:1564— CopyImageInfo::validate has cyclomatic complexity 124 (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.
ImageMemoryBarrier::validate (cyclomatic 106) vulkano/src/command_buffer/commands/sync.rs:2655— ImageMemoryBarrier::validate has cyclomatic complexity 106 (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.
BlitImageInfo::validate (cyclomatic 68) vulkano/src/command_buffer/commands/copy.rs:4926— BlitImageInfo::validate has cyclomatic complexity 68 (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.
ImageView::validate_new (cyclomatic 67) vulkano/src/image/view.rs:83— ImageView::validate_new has cyclomatic complexity 67 (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.
RenderPassCreateInfo::validate (cyclomatic 63) vulkano/src/render_pass/mod.rs:984— RenderPassCreateInfo::validate 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.
BufferMemoryBarrier::validate (cyclomatic 62) vulkano/src/command_buffer/commands/sync.rs:1903— BufferMemoryBarrier::validate has cyclomatic complexity 62 (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.
SubpassDescription::validate (cyclomatic 58) vulkano/src/render_pass/mod.rs:2969— SubpassDescription::validate has cyclomatic complexity 58 (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.
RenderingInfo::validate (cyclomatic 54) vulkano/src/command_buffer/commands/render_pass.rs:1360— RenderingInfo::validate has cyclomatic complexity 54 (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.
PipelineShaderStageCreateInfo::validate (cyclomatic 53) vulkano/src/pipeline/shader/mod.rs:61— PipelineShaderStageCreateInfo::validate has cyclomatic complexity 53 (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.
CopyBufferToImageInfo::validate (cyclomatic 51) vulkano/src/command_buffer/commands/copy.rs:3227— CopyBufferToImageInfo::validate has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (CopyImageToBufferInfo::validate) 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.
CopyImageToBufferInfo::validate (cyclomatic 51) vulkano/src/command_buffer/commands/copy.rs:3945— CopyImageToBufferInfo::validate has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (CopyBufferToImageInfo::validate) 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.
ResolveImageInfo::validate (cyclomatic 47) vulkano/src/command_buffer/commands/copy.rs:6059— ResolveImageInfo::validate has cyclomatic complexity 47 (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.
MemoryBarrier::validate (cyclomatic 43) vulkano/src/command_buffer/commands/sync.rs:1349— MemoryBarrier::validate has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DescriptorSetLayoutBinding::validate (cyclomatic 42) vulkano/src/descriptor_set/layout.rs:814— DescriptorSetLayoutBinding::validate has cyclomatic complexity 42 (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.
SamplerYcbcrConversionCreateInfo::validate (cyclomatic 39) vulkano/src/image/sampler/ycbcr.rs:473— SamplerYcbcrConversionCreateInfo::validate has cyclomatic complexity 39 (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.
Swapchain::validate_new_inner (cyclomatic 39) vulkano/src/swapchain/mod.rs:586— Swapchain::validate_new_inner has cyclomatic complexity 39 (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.
Spirv::new (cyclomatic 37) vulkano/src/shader/spirv/mod.rs:47— Spirv::new has cyclomatic complexity 37 (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.
AttachmentDescription::validate (cyclomatic 36) vulkano/src/render_pass/mod.rs:2277— AttachmentDescription::validate has cyclomatic complexity 36 (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.
SamplerCreateInfo::validate (cyclomatic 35) vulkano/src/image/sampler/mod.rs:772— SamplerCreateInfo::validate has cyclomatic complexity 35 (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.
TaskGraph::compile (cyclomatic 35) vulkano-taskgraph/src/graph/compile.rs:60— TaskGraph::compile has cyclomatic complexity 35 (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.
SwapchainCreateInfo::validate (cyclomatic 33) vulkano/src/swapchain/mod.rs:2254— SwapchainCreateInfo::validate has cyclomatic complexity 33 (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.
SemaphoreSubmitInfo::validate (cyclomatic 29) vulkano/src/command_buffer/mod.rs:1399— SemaphoreSubmitInfo::validate has cyclomatic complexity 29 (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.
DeviceCreateInfo::validate (cyclomatic 29) vulkano/src/device/mod.rs:1971— DeviceCreateInfo::validate 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.
SparseImageMemoryBindInfo::validate (cyclomatic 29) vulkano/src/memory/sparse.rs:1084— SparseImageMemoryBindInfo::validate 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.
BufferUsage::fmt (cyclomatic 28) vulkano/src/buffer/usage.rs:3— BufferUsage::fmt has cyclomatic complexity 28 (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.
ExternalMemoryHandleTypes::fmt (cyclomatic 28) vulkano/src/memory/device_memory.rs:1605— ExternalMemoryHandleTypes::fmt has cyclomatic complexity 28 (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.
QueryPipelineStatisticFlags::fmt (cyclomatic 28) vulkano/src/query.rs:733— QueryPipelineStatisticFlags::fmt has cyclomatic complexity 28 (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.
ColorBlendState::validate_required_fragment_outputs (cyclomatic 27) vulkano/src/pipeline/graphics/color_blend.rs:167— ColorBlendState::validate_required_fragment_outputs has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RasterizationState::validate (cyclomatic 27) vulkano/src/pipeline/graphics/rasterization.rs:146— RasterizationState::validate 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.
Sampler::check_can_sample (cyclomatic 26) vulkano/src/image/sampler/mod.rs:240— Sampler::check_can_sample 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.
PipelineLayoutCreateInfo::validate (cyclomatic 25) vulkano/src/pipeline/layout.rs:600— PipelineLayoutCreateInfo::validate has cyclomatic complexity 25 (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.
BufferView::validate_new (cyclomatic 24) vulkano/src/buffer/view.rs:102— BufferView::validate_new has cyclomatic complexity 24 (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.
ImageAspects::fmt (cyclomatic 24) vulkano/src/image/aspect.rs:3— ImageAspects::fmt has cyclomatic complexity 24 (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.
MemoryAllocateInfo::validate (cyclomatic 24) vulkano/src/memory/device_memory.rs:1102— MemoryAllocateInfo::validate has cyclomatic complexity 24 (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.
RenderPass::is_compatible_with (cyclomatic 24) vulkano/src/render_pass/mod.rs:538— RenderPass::is_compatible_with has cyclomatic complexity 24 (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.
SubpassDependency::validate (cyclomatic 24) vulkano/src/render_pass/mod.rs:4419— SubpassDependency::validate has cyclomatic complexity 24 (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.
AutoSyncState::add_image (cyclomatic 23) vulkano/src/command_buffer/auto/builder.rs:1096— AutoSyncState::add_image 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. This is NOT this file's highest cyclomatic complexity: CommandBufferBuilderState::reset_dynamic_states (cyclomatic 33) 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.
ImageFormatInfo::validate (cyclomatic 23) vulkano/src/image/mod.rs:2001— ImageFormatInfo::validate 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.
RawBuffer::validate_bind_memory (cyclomatic 22) vulkano/src/buffer/sys.rs:315— RawBuffer::validate_bind_memory 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.
BufferCreateInfo::validate (cyclomatic 22) vulkano/src/buffer/sys.rs:750— BufferCreateInfo::validate 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.
ImageCreateFlags::fmt (cyclomatic 22) vulkano/src/image/mod.rs:1134— ImageCreateFlags::fmt 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.
MemoryMapInfo::validate (cyclomatic 22) vulkano/src/memory/device_memory.rs:1754— MemoryMapInfo::validate 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.
StateGuard::drop (cyclomatic 22) vulkano-taskgraph/src/graph/execute.rs:2339— StateGuard::drop 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.
ClearDepthStencilImageInfo::validate (cyclomatic 20) vulkano/src/command_buffer/commands/clear.rs:661— ClearDepthStencilImageInfo::validate has cyclomatic complexity 20 (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.
SubgroupFeatures::fmt (cyclomatic 20) vulkano/src/device/physical.rs:3818— SubgroupFeatures::fmt has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: DriverId::try_from (cyclomatic 24) 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.
MemoryPropertyFlags::fmt (cyclomatic 20) vulkano/src/memory/mod.rs:661— MemoryPropertyFlags::fmt has cyclomatic complexity 20 (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.
SparseImageOpaqueMemoryBindInfo::validate (cyclomatic 20) vulkano/src/memory/sparse.rs:608— SparseImageOpaqueMemoryBindInfo::validate has cyclomatic complexity 20 (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.
GraphicsPipeline::from_handle (cyclomatic 20) vulkano/src/pipeline/graphics/mod.rs:285— GraphicsPipeline::from_handle has cyclomatic complexity 20 (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.
SurfaceTransforms::fmt (cyclomatic 20) vulkano/src/swapchain/surface.rs:2439— SurfaceTransforms::fmt has cyclomatic complexity 20 (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.
TypeStruct::new (cyclomatic 20) vulkano-shaders/src/structs.rs:749— TypeStruct::new has cyclomatic complexity 20 (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.
Framebuffer::validate_new (cyclomatic 19) vulkano/src/render_pass/framebuffer.rs:84— Framebuffer::validate_new 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.
ExecuteState2::convert_initial_barriers (cyclomatic 19) vulkano-taskgraph/src/graph/execute.rs:990— ExecuteState2::convert_initial_barriers 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. This shape REPEATS in the file: one other method here (ExecuteState::convert_initial_barriers) 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.
ExecuteState::convert_initial_barriers (cyclomatic 19) vulkano-taskgraph/src/graph/execute.rs:1605— ExecuteState::convert_initial_barriers 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. This shape REPEATS in the file: one other method here (ExecuteState2::convert_initial_barriers) 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.
CopyDescriptorSet::validate (cyclomatic 18) vulkano/src/descriptor_set/update.rs:1920— CopyDescriptorSet::validate has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
QueueFlags::fmt (cyclomatic 18) vulkano/src/device/queue.rs:1274— QueueFlags::fmt 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.
ImageUsage::fmt (cyclomatic 18) vulkano/src/image/usage.rs:3— ImageUsage::fmt 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.
vulkano_taskgraph::graph::compile::create_render_pass (cyclomatic 18) vulkano-taskgraph/src/graph/compile.rs:1220— vulkano_taskgraph::graph::compile::create_render_pass 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.
ClearColorImageInfo::validate (cyclomatic 17) vulkano/src/command_buffer/commands/clear.rs:419— ClearColorImageInfo::validate 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.
CommandBufferInheritanceRenderingInfo::validate (cyclomatic 17) vulkano/src/command_buffer/mod.rs:716— CommandBufferInheritanceRenderingInfo::validate 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.
PipelineRenderingCreateInfo::validate (cyclomatic 17) vulkano/src/pipeline/graphics/subpass.rs:142— PipelineRenderingCreateInfo::validate 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.
vulkano_shaders::shaders::parse_deps_file (cyclomatic 17) vulkano-shaders/src/shaders.rs:243— vulkano_shaders::shaders::parse_deps_file has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolPurposes::fmt (cyclomatic 16) vulkano/src/device/physical.rs:3779— ToolPurposes::fmt has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: DriverId::try_from (cyclomatic 24) 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.
SampleCounts::fmt (cyclomatic 16) vulkano/src/image/mod.rs:1315— SampleCounts::fmt 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.
Viewport::validate (cyclomatic 16) vulkano/src/pipeline/graphics/viewport.rs:323— Viewport::validate has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TodoComment repeated across 21 files vulkano-taskgraph/src/lib.rs:830— The identical TodoComment appears in 21 files (56 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 56 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO:". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
TodoComment repeated across 26 files vulkano/src/acceleration_structure.rs:393— The identical TodoComment appears in 26 files (317 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 317 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO: document". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
WriteDescriptorSet::validate (cognitive 296) vulkano/src/descriptor_set/update.rs:204— WriteDescriptorSet::validate has cognitive complexity 296 (threshold 15). Drivers by points: if/else 109 (261 pts), loops 12 (28 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 170). Of this number, 295 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphicsPipelineCreateInfo::validate (cognitive 283) vulkano/src/pipeline/graphics/mod.rs:806— GraphicsPipelineCreateInfo::validate has cognitive complexity 283 (threshold 15). Drivers by points: if/else 96 (187 pts), match/switch 29 (52 pts), boolean chains 31, loops 7 (13 pts) (nesting depth added 120). 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.
ImageCreateInfo::validate (cognitive 225) vulkano/src/image/sys.rs:1788— ImageCreateInfo::validate has cognitive complexity 225 (threshold 15). Drivers by points: if/else 105 (182 pts), boolean chains 25, loops 5 (10 pts), match/switch 6 (8 pts) (nesting depth added 84). 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.
CopyImageInfo::validate (cognitive 201) vulkano/src/command_buffer/commands/copy.rs:1564— CopyImageInfo::validate has cognitive complexity 201 (threshold 15). Drivers by points: if/else 80 (156 pts), match/switch 9 (23 pts), boolean chains 18, loops 2 (4 pts) (nesting depth added 92). 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.
ImageMemoryBarrier::validate (cognitive 158) vulkano/src/command_buffer/commands/sync.rs:2655— ImageMemoryBarrier::validate has cognitive complexity 158 (threshold 15). Drivers by points: if/else 79 (145 pts), boolean chains 7, match/switch 3 (6 pts) (nesting depth added 69). 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.
SubpassDescription::validate (cognitive 122) vulkano/src/render_pass/mod.rs:2969— SubpassDescription::validate has cognitive complexity 122 (threshold 15). Drivers by points: if/else 44 (99 pts), match/switch 6 (17 pts), boolean chains 4, loops 2 (nesting depth added 66). 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.
BlitImageInfo::validate (cognitive 111) vulkano/src/command_buffer/commands/copy.rs:4926— BlitImageInfo::validate has cognitive complexity 111 (threshold 15). Drivers by points: if/else 54 (96 pts), boolean chains 6, match/switch 3 (5 pts), loops 2 (4 pts) (nesting depth added 46). 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.
ImageView::validate_new (cognitive 110) vulkano/src/image/view.rs:83— ImageView::validate_new has cognitive complexity 110 (threshold 15). Drivers by points: if/else 52 (92 pts), boolean chains 14, match/switch 2 (4 pts) (nesting depth added 42). 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.
BufferMemoryBarrier::validate (cognitive 94) vulkano/src/command_buffer/commands/sync.rs:1903— BufferMemoryBarrier::validate has cognitive complexity 94 (threshold 15). Drivers by points: if/else 54 (90 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 37). 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.
Swapchain::validate_new_inner (cognitive 82) vulkano/src/swapchain/mod.rs:586— Swapchain::validate_new_inner has cognitive complexity 82 (threshold 15). Drivers by points: if/else 32 (67 pts), loops 3 (10 pts), boolean chains 5 (nesting depth added 42). 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.
PipelineShaderStageCreateInfo::validate (cognitive 80) vulkano/src/pipeline/shader/mod.rs:61— PipelineShaderStageCreateInfo::validate has cognitive complexity 80 (threshold 15). Drivers by points: if/else 23 (54 pts), match/switch 11 (23 pts), loops 2, boolean chains 1 (nesting depth added 43). 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.
CopyBufferToImageInfo::validate (cognitive 77) vulkano/src/command_buffer/commands/copy.rs:3227— CopyBufferToImageInfo::validate has cognitive complexity 77 (threshold 15). Drivers by points: if/else 38 (63 pts), match/switch 3 (8 pts), boolean chains 5, loops 1 (nesting depth added 30). 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 (CopyImageToBufferInfo::validate) 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.
CopyImageToBufferInfo::validate (cognitive 77) vulkano/src/command_buffer/commands/copy.rs:3945— CopyImageToBufferInfo::validate has cognitive complexity 77 (threshold 15). Drivers by points: if/else 38 (63 pts), match/switch 3 (8 pts), boolean chains 5, loops 1 (nesting depth added 30). 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 (CopyBufferToImageInfo::validate) 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.
ResolveImageInfo::validate (cognitive 73) vulkano/src/command_buffer/commands/copy.rs:6059— ResolveImageInfo::validate has cognitive complexity 73 (threshold 15). Drivers by points: if/else 38 (65 pts), match/switch 2 (4 pts), boolean chains 3, loops 1 (nesting depth added 29). 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.
MemoryBarrier::validate (cognitive 65) vulkano/src/command_buffer/commands/sync.rs:1349— MemoryBarrier::validate has cognitive complexity 65 (threshold 15). Drivers by points: if/else 40 (63 pts), boolean chains 2 (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.
DescriptorSetLayoutBinding::validate (cognitive 63) vulkano/src/descriptor_set/layout.rs:814— DescriptorSetLayoutBinding::validate has cognitive complexity 63 (threshold 15). Drivers by points: if/else 27 (53 pts), boolean chains 6, loops 1 (2 pts), match/switch 1 (2 pts) (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.
PipelineLayoutCreateInfo::validate (cognitive 61) vulkano/src/pipeline/layout.rs:600— PipelineLayoutCreateInfo::validate has cognitive complexity 61 (threshold 15). Drivers by points: if/else 14 (41 pts), loops 8 (17 pts), match/switch 2 (3 pts) (nesting depth added 37). 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.
AttachmentDescription::validate (cognitive 59) vulkano/src/render_pass/mod.rs:2277— AttachmentDescription::validate has cognitive complexity 59 (threshold 15). Drivers by points: if/else 31 (55 pts), boolean chains 4 (nesting depth added 24). 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.
SparseImageOpaqueMemoryBindInfo::validate (cognitive 51) vulkano/src/memory/sparse.rs:608— SparseImageOpaqueMemoryBindInfo::validate has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (48 pts), boolean chains 2, loops 1 (nesting depth added 30). 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.
SwapchainCreateInfo::validate (cognitive 50) vulkano/src/swapchain/mod.rs:2254— SwapchainCreateInfo::validate has cognitive complexity 50 (threshold 15). Drivers by points: if/else 23 (37 pts), loops 4 (8 pts), boolean chains 4, match/switch 1 (nesting depth added 18). 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.
SamplerYcbcrConversionCreateInfo::validate (cognitive 49) vulkano/src/image/sampler/ycbcr.rs:473— SamplerYcbcrConversionCreateInfo::validate has cognitive complexity 49 (threshold 15). Drivers by points: if/else 23 (35 pts), boolean chains 8, match/switch 3 (5 pts), loops 1 (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.
BufferView::validate_new (cognitive 48) vulkano/src/buffer/view.rs:102— BufferView::validate_new has cognitive complexity 48 (threshold 15). Drivers by points: if/else 24 (45 pts), boolean chains 3 (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.
SparseImageMemoryBindInfo::validate (cognitive 46) vulkano/src/memory/sparse.rs:1084— SparseImageMemoryBindInfo::validate has cognitive complexity 46 (threshold 15). Drivers by points: if/else 23 (41 pts), boolean chains 4, loops 1 (nesting depth added 18). 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.
Sampler::check_can_sample (cognitive 44) vulkano/src/image/sampler/mod.rs:240— Sampler::check_can_sample has cognitive complexity 44 (threshold 15). Drivers by points: if/else 22 (38 pts), boolean chains 4, match/switch 1 (2 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.
ColorBlendState::validate_required_fragment_outputs (cognitive 44) vulkano/src/pipeline/graphics/color_blend.rs:167— ColorBlendState::validate_required_fragment_outputs has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (22 pts), loops 5 (10 pts), match/switch 3 (7 pts), boolean chains 5 (nesting depth added 16). Of this number, 43 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RasterizationState::validate (cognitive 43) vulkano/src/pipeline/graphics/rasterization.rs:146— RasterizationState::validate has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (36 pts), match/switch 2 (4 pts), boolean chains 3 (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.
Spirv::new (cognitive 43) vulkano/src/shader/spirv/mod.rs:47— Spirv::new has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (30 pts), match/switch 6 (12 pts), loops 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.
TypeStruct::new (cognitive 41) vulkano-shaders/src/structs.rs:749— TypeStruct::new has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (26 pts), match/switch 5 (11 pts), loops 2 (3 pts), boolean chains 1 (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.
BufferUsage::fmt (cognitive 40) vulkano/src/buffer/usage.rs:3— BufferUsage::fmt has cognitive complexity 40 (threshold 15). Drivers by points: if/else 27 (40 pts) (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.
SamplerCreateInfo::validate (cognitive 40) vulkano/src/image/sampler/mod.rs:772— SamplerCreateInfo::validate has cognitive complexity 40 (threshold 15). Drivers by points: if/else 28 (34 pts), boolean chains 5, loops 1 (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.
ExternalMemoryHandleTypes::fmt (cognitive 40) vulkano/src/memory/device_memory.rs:1605— ExternalMemoryHandleTypes::fmt has cognitive complexity 40 (threshold 15). Drivers by points: if/else 27 (40 pts) (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.
QueryPipelineStatisticFlags::fmt (cognitive 40) vulkano/src/query.rs:733— QueryPipelineStatisticFlags::fmt has cognitive complexity 40 (threshold 15). Drivers by points: if/else 27 (40 pts) (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.
DeviceCreateInfo::validate (cognitive 38) vulkano/src/device/mod.rs:1971— DeviceCreateInfo::validate has cognitive complexity 38 (threshold 15). Drivers by points: if/else 20 (29 pts), boolean chains 6, loops 2 (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.
MemoryMapInfo::validate (cognitive 38) vulkano/src/memory/device_memory.rs:1754— MemoryMapInfo::validate has cognitive complexity 38 (threshold 15). Drivers by points: if/else 20 (36 pts), boolean chains 2 (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.
vulkano_taskgraph::graph::compile::create_render_pass (cognitive 38) vulkano-taskgraph/src/graph/compile.rs:1220— vulkano_taskgraph::graph::compile::create_render_pass has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 5 (9 pts), boolean chains 2 (nesting depth added 18). 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.
MemoryAllocateInfo::validate (cognitive 37) vulkano/src/memory/device_memory.rs:1102— MemoryAllocateInfo::validate has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 7, match/switch 1 (2 pts) (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.
ImageAspects::fmt (cognitive 34) vulkano/src/image/aspect.rs:3— ImageAspects::fmt has cognitive complexity 34 (threshold 15). Drivers by points: if/else 23 (34 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SubpassDependency::validate (cognitive 34) vulkano/src/render_pass/mod.rs:4419— SubpassDependency::validate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (30 pts), boolean chains 4 (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.
StateGuard::drop (cognitive 34) vulkano-taskgraph/src/graph/execute.rs:2339— StateGuard::drop has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 4 (7 pts), match/switch 3 (7 pts), boolean chains 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.
BufferCreateInfo::validate (cognitive 33) vulkano/src/buffer/sys.rs:750— BufferCreateInfo::validate has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (29 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (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.
RawBuffer::validate_bind_memory (cognitive 32) vulkano/src/buffer/sys.rs:315— RawBuffer::validate_bind_memory has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImageFormatInfo::validate (cognitive 32) vulkano/src/image/mod.rs:2001— ImageFormatInfo::validate has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 5, loops 1 (2 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.
ExecuteState2::convert_initial_barriers (cognitive 32) vulkano-taskgraph/src/graph/execute.rs:990— ExecuteState2::convert_initial_barriers has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (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. This shape REPEATS in the file: one other method here (ExecuteState::convert_initial_barriers) 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.
ExecuteState::convert_initial_barriers (cognitive 32) vulkano-taskgraph/src/graph/execute.rs:1605— ExecuteState::convert_initial_barriers has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (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. This shape REPEATS in the file: one other method here (ExecuteState2::convert_initial_barriers) 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.
ImageCreateFlags::fmt (cognitive 31) vulkano/src/image/mod.rs:1134— ImageCreateFlags::fmt has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (31 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.
GraphicsPipeline::from_handle (cognitive 31) vulkano/src/pipeline/graphics/mod.rs:285— GraphicsPipeline::from_handle has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 3 (10 pts), loops 3 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SparseBufferMemoryBindInfo::validate (cognitive 30) vulkano/src/memory/sparse.rs:267— SparseBufferMemoryBindInfo::validate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 1, loops 1 (nesting depth added 16). 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.
SemaphoreSubmitInfo::validate (cognitive 29) vulkano/src/command_buffer/mod.rs:1399— SemaphoreSubmitInfo::validate has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 14, if/else 13 (14 pts), match/switch 1 (nesting depth added 1). 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.
vulkano_shaders::shaders::parse_deps_file (cognitive 29) vulkano-shaders/src/shaders.rs:243— vulkano_shaders::shaders::parse_deps_file has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 1, loops 1 (nesting depth added 12). Of this number, 25 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClearDepthStencilImageInfo::validate (cognitive 28) vulkano/src/command_buffer/commands/clear.rs:661— ClearDepthStencilImageInfo::validate has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SubgroupFeatures::fmt (cognitive 28) vulkano/src/device/physical.rs:3818— SubgroupFeatures::fmt has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (28 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MemoryPropertyFlags::fmt (cognitive 28) vulkano/src/memory/mod.rs:661— MemoryPropertyFlags::fmt has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (28 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SurfaceTransforms::fmt (cognitive 28) vulkano/src/swapchain/surface.rs:2439— SurfaceTransforms::fmt has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (28 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VkRegistryData::get_header_version (cognitive 27) autogen/src/main.rs:129— VkRegistryData::get_header_version has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (23 pts), loops 2 (4 pts) (nesting depth added 19). 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.
DescriptorSetLayoutCreateInfo::validate (cognitive 27) vulkano/src/descriptor_set/layout.rs:351— DescriptorSetLayoutCreateInfo::validate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 2 (3 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.
FreeListAllocator::allocate_inner (cognitive 27) vulkano/src/memory/allocator/suballocator/free_list.rs:152— FreeListAllocator::allocate_inner has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (22 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 15). Of this number, 24 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClearColorImageInfo::validate (cognitive 26) vulkano/src/command_buffer/commands/clear.rs:419— ClearColorImageInfo::validate has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommandBufferInheritanceRenderingInfo::validate (cognitive 25) vulkano/src/command_buffer/mod.rs:716— CommandBufferInheritanceRenderingInfo::validate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueueFlags::fmt (cognitive 25) vulkano/src/device/queue.rs:1274— QueueFlags::fmt has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (25 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImageUsage::fmt (cognitive 25) vulkano/src/image/usage.rs:3— ImageUsage::fmt has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (25 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PipelineRenderingCreateInfo::validate (cognitive 25) vulkano/src/pipeline/graphics/subpass.rs:142— PipelineRenderingCreateInfo::validate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RayTracingShaderGroupCreateInfo::validate (cognitive 25) vulkano/src/pipeline/ray_tracing.rs:830— RayTracingShaderGroupCreateInfo::validate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 2 (3 pts) (nesting depth added 14). 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.
VertexInputState::validate_required_vertex_inputs (cognitive 23) vulkano/src/pipeline/graphics/vertex_input/mod.rs:341— VertexInputState::validate_required_vertex_inputs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 1 (2 pts), loops 1 (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.
Framebuffer::validate_new (cognitive 23) vulkano/src/render_pass/framebuffer.rs:84— Framebuffer::validate_new has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 6, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RenderPass::is_compatible_with (cognitive 23) vulkano/src/render_pass/mod.rs:538— RenderPass::is_compatible_with has cognitive complexity 23 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 3, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ToolPurposes::fmt (cognitive 22) vulkano/src/device/physical.rs:3779— ToolPurposes::fmt has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (22 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SampleCounts::fmt (cognitive 22) vulkano/src/image/mod.rs:1315— SampleCounts::fmt has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (22 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstanceCreateInfo::validate (cognitive 22) vulkano/src/instance/mod.rs:1084— InstanceCreateInfo::validate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3 (6 pts), boolean chains 2 (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.
AccelerationStructureBuildGeometryInfo::validate (cognitive 21) vulkano/src/acceleration_structure.rs:617— AccelerationStructureBuildGeometryInfo::validate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommandBufferExecFuture::signal_finished (cognitive 21) vulkano/src/command_buffer/traits.rs:337— CommandBufferExecFuture::signal_finished has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (10 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FenceSignalFuture::flush_impl (cognitive 20) vulkano/src/sync/future/fence_signal.rs:199— FenceSignalFuture::flush_impl has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 3 (7 pts), loops 1 (3 pts) (nesting depth added 11). 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.
ExternalSemaphoreHandleTypes::fmt (cognitive 19) vulkano/src/sync/semaphore.rs:1588— ExternalSemaphoreHandleTypes::fmt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (19 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.
CopyBufferInfo::validate (cognitive 18) vulkano/src/command_buffer/commands/copy.rs:1220— CopyBufferInfo::validate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 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.
CopyDescriptorSet::validate (cognitive 18) vulkano/src/descriptor_set/update.rs:1920— CopyDescriptorSet::validate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (15 pts), match/switch 2, boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Device::validate_image_memory_requirements (cognitive 18) vulkano/src/device/mod.rs:1212— Device::validate_image_memory_requirements has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (2 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.
ImageViewCreateInfo::validate (cognitive 18) vulkano/src/image/view.rs:984— ImageViewCreateInfo::validate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 1, match/switch 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.
QueueGuard::validate_submit (cognitive 17) vulkano/src/device/queue.rs:788— QueueGuard::validate_submit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 4 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InputAssemblyState::validate (cognitive 17) vulkano/src/pipeline/graphics/input_assembly.rs:75— InputAssemblyState::validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (3 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.
Viewport::validate (cognitive 17) vulkano/src/pipeline/graphics/viewport.rs:323— Viewport::validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 2 (nesting depth added 2). 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.
PipelineLayout::from_handle (cognitive 17) vulkano/src/pipeline/layout.rs:323— PipelineLayout::from_handle has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 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.
FramebufferCreateInfo::validate (cognitive 17) vulkano/src/render_pass/framebuffer.rs:524— FramebufferCreateInfo::validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapchainPresentInfo::validate (cognitive 17) vulkano/src/swapchain/acquire_present.rs:835— SwapchainPresentInfo::validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, loops 1 (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.
SemaphoreCreateInfo::validate (cognitive 17) vulkano/src/sync/semaphore.rs:1409— SemaphoreCreateInfo::validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 1 (2 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.
VulkanoWindows::create_window (cognitive 17) vulkano-util/src/window.rs:43— VulkanoWindows::create_window has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeviceFeatures::new (cognitive 16) autogen/src/features.rs:32— DeviceFeatures::new has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (6 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.
Property::new (cognitive 16) autogen/src/properties.rs:764— Property::new has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), match/switch 6 (7 pts), boolean chains 1 (nesting depth added 2). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
BuildAccelerationStructureFlags::fmt (cognitive 16) vulkano/src/acceleration_structure.rs:809— BuildAccelerationStructureFlags::fmt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DescriptorBindingResources::write (cognitive 16) vulkano/src/descriptor_set/mod.rs:512— DescriptorBindingResources::write has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 6 (11 pts), if/else 2 (4 pts), boolean chains 1 (nesting depth added 7). 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.
PipelineCreateFlags::fmt (cognitive 16) vulkano/src/pipeline/mod.rs:774— PipelineCreateFlags::fmt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vulkano_macros::derive_vertex::derive_vertex (cognitive 16) vulkano-macros/src/derive_vertex.rs:10— vulkano_macros::derive_vertex::derive_vertex has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3 (5 pts), match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MacroInputParser::parse_shader_entries (cognitive 16) vulkano-shaders/src/lib.rs:1047— MacroInputParser::parse_shader_entries has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 2 (5 pts), loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExecutableTaskGraph::create_framebuffers (cognitive 16) vulkano-taskgraph/src/graph/execute.rs:326— ExecutableTaskGraph::create_framebuffers has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (7 pts), if/else 3 (6 pts), match/switch 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFields: CommandBufferBuilderState vulkano/src/command_buffer/auto/builder.rs:1394— TooManyFields — 42 stored fields beside 3 methods. 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×1
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×1
D4 · Code Duplication· Near-duplicate member family (5 members, 19 shared lines) · ×1
Near-duplicate member family (5 members, 19 shared lines) vulkano/src/sync/fence.rs:584— vulkano/src/sync/fence.rs:584-622 | vulkano/src/sync/fence.rs:714-752 | vulkano/src/sync/semaphore.rs:668-716 | vulkano/src/sync/semaphore.rs:812-857 | vulkano/src/sync/semaphore.rs:940-982 — These 5 members are variants of one another: a block of 19 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 (3 members, 252 shared lines) · ×1
Near-duplicate member family (3 members, 252 shared lines) vulkano/src/command_buffer/commands/sync.rs:1349— vulkano/src/command_buffer/commands/sync.rs:1349-1813 | vulkano/src/command_buffer/commands/sync.rs:1903-2519 | vulkano/src/command_buffer/commands/sync.rs:2655-3662 — These 3 members are variants of one another: a block of 252 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, 68 shared lines) · ×1
Near-duplicate member family (3 members, 68 shared lines) vulkano/src/command_buffer/commands/copy.rs:121— vulkano/src/command_buffer/commands/copy.rs:121-411 | vulkano/src/command_buffer/commands/copy.rs:479-689 | vulkano/src/command_buffer/commands/copy.rs:764-953 — These 3 members are variants of one another: a block of 68 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, 47 shared lines) · ×1
Near-duplicate member family (3 members, 47 shared lines) vulkano/src/command_buffer/commands/sync.rs:36— vulkano/src/command_buffer/commands/sync.rs:36-199 | vulkano/src/command_buffer/commands/sync.rs:289-463 | vulkano/src/command_buffer/commands/sync.rs:529-698 — These 3 members are variants of one another: a block of 47 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 (92 shared lines) vulkano-taskgraph/src/graph/execute.rs:990— vulkano-taskgraph/src/graph/execute.rs:990-1121 | vulkano-taskgraph/src/graph/execute.rs:1605-1739 — These two members are variants of one another: 92 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (74 shared lines) vulkano/src/command_buffer/commands/sync.rs:809— vulkano/src/command_buffer/commands/sync.rs:809-1013 | vulkano/src/command_buffer/mod.rs:1399-1590 — These two members are variants of one another: 74 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (51 shared lines) vulkano/src/command_buffer/commands/clear.rs:419— vulkano/src/command_buffer/commands/clear.rs:419-578 | vulkano/src/command_buffer/commands/clear.rs:661-847 — These two members are variants of one another: 51 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (40 shared lines) vulkano-taskgraph/src/graph/execute.rs:1463— vulkano-taskgraph/src/graph/execute.rs:1463-1508 | vulkano-taskgraph/src/graph/execute.rs:2097-2143 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (22 shared lines) vulkano-taskgraph/src/graph/execute.rs:1192— vulkano-taskgraph/src/graph/execute.rs:1192-1255 | vulkano-taskgraph/src/graph/execute.rs:1812-1878 — These two members are variants of one another: 22 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· Members sharing a duplicated core (15 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (15 members, 50+ identical tokens) vulkano/src/swapchain/surface.rs:398— vulkano/src/swapchain/surface.rs:398-426 | vulkano/src/swapchain/surface.rs:576-599 | vulkano/src/swapchain/surface.rs:669-698 | vulkano/src/swapchain/surface.rs:777-807 | vulkano/src/swapchain/surface.rs:881-911 | vulkano/src/swapchain/surface.rs:984-1014 | vulkano/src/swapchain/surface.rs:1089-1118 | vulkano/src/swapchain/surface.rs:1193-1222 | vulkano/src/swapchain/surface.rs:1302-1331 | vulkano/src/swapchain/surface.rs:1410-1442 | vulkano/src/swapchain/surface.rs:1512-1541 | vulkano/src/swapchain/surface.rs:1624-1654 | vulkano/src/swapchain/surface.rs:1737-1767 | vulkano/src/swapchain/surface.rs:1850-1880 | vulkano/src/swapchain/surface.rs:1963-1993 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication· Members sharing a duplicated core (14 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (14 members, 50+ identical tokens) vulkano/src/acceleration_structure.rs:201— vulkano/src/acceleration_structure.rs:201-222 | vulkano/src/buffer/sys.rs:110-131 | vulkano/src/buffer/view.rs:341-362 | vulkano/src/command_buffer/pool.rs:87-107 | vulkano/src/descriptor_set/layout.rs:125-149 | vulkano/src/descriptor_set/pool.rs:84-107 | vulkano/src/image/sampler/mod.rs:162-183 | vulkano/src/image/sampler/ycbcr.rs:208-235 | vulkano/src/pipeline/cache.rs:128-148 | vulkano/src/pipeline/layout.rs:139-160 | vulkano/src/query.rs:83-103 | vulkano/src/render_pass/mod.rs:185-250 | vulkano/src/sync/event.rs:111-131 | vulkano/src/sync/semaphore.rs:144-165 — These 14 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 14 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 14 times.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) vulkano/src/device/physical.rs:617— vulkano/src/device/physical.rs:617-718 | vulkano/src/device/physical.rs:812-905 | vulkano/src/device/physical.rs:989-1040 | vulkano/src/device/physical.rs:2200-2318 | vulkano/src/device/physical.rs:2444-2545 | vulkano/src/display.rs:137-247 | vulkano/src/instance/mod.rs:673-710 | vulkano/src/instance/mod.rs:789-853 | vulkano/src/library.rs:288-321 | vulkano/src/pipeline/mod.rs:168-213 | vulkano/src/pipeline/mod.rs:298-345 | vulkano/src/swapchain/mod.rs:1055-1115 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) vulkano/src/device/physical.rs:2603— vulkano/src/device/physical.rs:2603-2624 | vulkano/src/device/physical.rs:2969-2995 | vulkano/src/device/physical.rs:3048-3071 | vulkano/src/device/physical.rs:3137-3163 | vulkano/src/device/physical.rs:3235-3261 | vulkano/src/device/physical.rs:3329-3355 | vulkano/src/device/physical.rs:3420-3446 — 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 (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) vulkano/src/command_buffer/commands/copy.rs:1564— vulkano/src/command_buffer/commands/copy.rs:1564-2863 | vulkano/src/command_buffer/commands/copy.rs:3227-3807 | vulkano/src/command_buffer/commands/copy.rs:3945-4522 | vulkano/src/command_buffer/commands/copy.rs:4926-5712 | vulkano/src/command_buffer/commands/copy.rs:6059-6628 — 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 (81 corresponding lines) · ×1
Edited copy of a member (81 corresponding lines) autogen/src/extensions.rs:111— autogen/src/extensions.rs:111-219 | autogen/src/features.rs:156-236 — These two members are one piece of code written twice and then edited apart: 81 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 (125 corresponding lines) · ×1
Edited copy of a member (125 corresponding lines) vulkano/src/memory/allocator/mod.rs:1603— vulkano/src/memory/allocator/mod.rs:1603-1727 | vulkano/src/memory/allocator/mod.rs:1807-1953 — These two members are one piece of code written twice and then edited apart: 125 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 (79 corresponding lines) · ×1
Edited copy of a member (79 corresponding lines) vulkano/src/memory/allocator/mod.rs:1328— vulkano/src/memory/allocator/mod.rs:1328-1408 | vulkano/src/memory/allocator/mod.rs:1463-1541 — These two members are one piece of code written twice and then edited apart: 79 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 (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) vulkano/src/command_buffer/auto/commands/render_pass.rs:1214— vulkano/src/command_buffer/auto/commands/render_pass.rs:1214-1287 | vulkano/src/command_buffer/commands/render_pass.rs:1285-1358 — These two members are one piece of code written twice and then edited apart: 74 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 (91 corresponding lines) · ×1
Edited copy of a member (91 corresponding lines) vulkano/src/device/physical.rs:1726— vulkano/src/device/physical.rs:1726-1842 | vulkano/src/image/sys.rs:400-490 — These two members are one piece of code written twice and then edited apart: 91 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 (69 corresponding lines) · ×1
Edited copy of a member (69 corresponding lines) vulkano/src/command_buffer/commands/clear.rs:253— vulkano/src/command_buffer/commands/clear.rs:253-331 | vulkano/src/command_buffer/commands/clear.rs:929-997 — These two members are one piece of code written twice and then edited apart: 69 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 (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs:368— vulkano/src/memory/allocator/suballocator/free_list.rs:368-432 | vulkano/src/memory/allocator/suballocator/tlsf.rs:475-546 — These two members are one piece of code written twice and then edited apart: 65 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 (72 corresponding lines) · ×1
Edited copy of a member (72 corresponding lines) vulkano/src/command_buffer/commands/copy.rs:3029— vulkano/src/command_buffer/commands/copy.rs:3029-3100 | vulkano/src/command_buffer/commands/copy.rs:4727-4799 — These two members are one piece of code written twice and then edited apart: 72 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, 69+ corresponding lines) · ×1
Edited copies of one member (3 members, 69+ corresponding lines) vulkano/src/image/mod.rs:1562— vulkano/src/image/mod.rs:1562-1636 | vulkano/src/image/mod.rs:1731-1804 | vulkano/src/memory/sparse.rs:1541-1609 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 69 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 (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) autogen/src/features.rs:1042— autogen/src/features.rs:1042-1084 | autogen/src/properties.rs:1052-1097 — These two members are one piece of code written twice and then edited apart: 43 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 (55 corresponding lines) · ×1
Edited copy of a member (55 corresponding lines) vulkano/src/memory/sparse.rs:498— vulkano/src/memory/sparse.rs:498-552 | vulkano/src/memory/sparse.rs:967-1022 — These two members are one piece of code written twice and then edited apart: 55 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 (63 corresponding lines) · ×1
Edited copy of a member (63 corresponding lines) vulkano-taskgraph/src/graph/mod.rs:890— vulkano-taskgraph/src/graph/mod.rs:890-963 | vulkano-taskgraph/src/graph/mod.rs:986-1048 — These two members are one piece of code written twice and then edited apart: 63 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 (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) autogen/src/spirv_parse.rs:715— autogen/src/spirv_parse.rs:715-779 | autogen/src/spirv_parse.rs:881-933 — These two members are one piece of code written twice and then edited apart: 53 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs:317— vulkano/src/memory/allocator/suballocator/free_list.rs:317-353 | vulkano/src/memory/allocator/suballocator/tlsf.rs:288-332 — These two members are one piece of code written twice and then edited apart: 37 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 (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs:1332— vulkano/src/command_buffer/auto/commands/copy.rs:1332-1376 | vulkano/src/command_buffer/commands/copy.rs:4679-4725 — These two members are one piece of code written twice and then edited apart: 45 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 (5 members, 75+ corresponding lines) · ×1
Edited copies of one member (5 members, 75+ corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs:218— vulkano/src/command_buffer/auto/commands/copy.rs:218-292 | vulkano/src/command_buffer/auto/commands/copy.rs:350-427 | vulkano/src/command_buffer/auto/commands/copy.rs:485-562 | vulkano/src/command_buffer/auto/commands/copy.rs:641-715 | vulkano/src/command_buffer/auto/commands/copy.rs:772-846 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 75 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 copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) vulkano/src/buffer/mod.rs:445— vulkano/src/buffer/mod.rs:445-484 | vulkano/src/buffer/mod.rs:508-547 — These two members are one piece of code written twice and then edited apart: 40 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) · ×1
Edited copy of a member (33 corresponding lines) vulkano/src/device/mod.rs:352— vulkano/src/device/mod.rs:352-384 | vulkano/src/instance/mod.rs:423-455 — 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 copies of one member (4 members, 44+ corresponding lines) · ×1
Edited copies of one member (4 members, 44+ corresponding lines) vulkano/src/sync/fence.rs:1281— vulkano/src/sync/fence.rs:1281-1327 | vulkano/src/sync/fence.rs:1385-1431 | vulkano/src/sync/semaphore.rs:1987-2035 | vulkano/src/sync/semaphore.rs:2208-2251 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 44 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) vulkano/src/device/physical.rs:174— vulkano/src/device/physical.rs:174-209 | vulkano/src/library.rs:188-225 — 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 copies of one member (3 members, 33+ corresponding lines) · ×1
Edited copies of one member (3 members, 33+ corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs:183— vulkano/src/command_buffer/auto/commands/copy.rs:183-215 | vulkano/src/command_buffer/auto/commands/copy.rs:606-638 | vulkano/src/command_buffer/auto/commands/copy.rs:734-766 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 33 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, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) vulkano/src/sync/future/join.rs:165— vulkano/src/sync/future/join.rs:165-189 | vulkano/src/sync/future/join.rs:198-221 | vulkano/src/sync/future/join.rs:229-247 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 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, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) vulkano-taskgraph/src/graph/execute.rs:2629— vulkano-taskgraph/src/graph/execute.rs:2629-2660 | vulkano-taskgraph/src/graph/execute.rs:2708-2741 | vulkano-taskgraph/src/graph/execute.rs:2784-2815 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 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, 26+ corresponding lines) · ×1
Edited copies of one member (3 members, 26+ corresponding lines) vulkano/src/command_buffer/commands/render_pass.rs:380— vulkano/src/command_buffer/commands/render_pass.rs:380-422 | vulkano/src/command_buffer/commands/render_pass.rs:488-522 | vulkano/src/command_buffer/commands/render_pass.rs:577-602 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 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 (6 members, 30+ corresponding lines) · ×1
Edited copies of one member (6 members, 30+ corresponding lines) vulkano/src/command_buffer/auto/commands/pipeline.rs:472— vulkano/src/command_buffer/auto/commands/pipeline.rs:472-502 | vulkano/src/command_buffer/auto/commands/pipeline.rs:604-637 | vulkano/src/command_buffer/auto/commands/pipeline.rs:971-1002 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1118-1152 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1424-1453 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1564-1596 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 30 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 6 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) vulkano/src/buffer/allocator.rs:58— vulkano/src/buffer/allocator.rs:58-92 | vulkano/src/buffer/allocator.rs:487-524 — 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 copies of one member (3 members, 24+ corresponding lines) · ×1
Edited copies of one member (3 members, 24+ corresponding lines) vulkano/src/sync/semaphore.rs:1068— vulkano/src/sync/semaphore.rs:1068-1103 | vulkano/src/sync/semaphore.rs:1178-1217 | vulkano/src/sync/semaphore.rs:1291-1314 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 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, 40+ corresponding lines) · ×1
Edited copies of one member (3 members, 40+ corresponding lines) vulkano/src/device/physical.rs:1118— vulkano/src/device/physical.rs:1118-1157 | vulkano/src/device/physical.rs:1236-1275 | vulkano/src/device/physical.rs:1354-1394 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 40 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, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) vulkano/src/image/sys.rs:132— vulkano/src/image/sys.rs:132-154 | vulkano/src/pipeline/compute.rs:108-134 | vulkano/src/sync/fence.rs:111-133 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 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, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) vulkano/src/device/mod.rs:1771— vulkano/src/device/mod.rs:1771-1807 | vulkano/src/device/physical.rs:3469-3505 | vulkano/src/instance/mod.rs:927-957 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 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 (6 members, 22+ corresponding lines) · ×1
Edited copies of one member (6 members, 22+ corresponding lines) vulkano/src/memory/device_memory.rs:984— vulkano/src/memory/device_memory.rs:984-1006 | vulkano/src/sync/fence.rs:628-650 | vulkano/src/sync/fence.rs:758-779 | vulkano/src/sync/semaphore.rs:722-744 | vulkano/src/sync/semaphore.rs:863-885 | vulkano/src/sync/semaphore.rs:988-1010 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 22 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 15+ corresponding lines) · ×1
Edited copies of one member (6 members, 15+ corresponding lines) vulkano/src/command_buffer/pool.rs:409— vulkano/src/command_buffer/pool.rs:409-423 | vulkano/src/device/mod.rs:989-1006 | vulkano/src/device/physical.rs:1090-1111 | vulkano/src/device/physical.rs:1208-1229 | vulkano/src/device/physical.rs:1326-1347 | vulkano/src/instance/mod.rs:770-784 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) vulkano/src/command_buffer/commands/clear.rs:100— vulkano/src/command_buffer/commands/clear.rs:100-120 | vulkano/src/command_buffer/commands/copy.rs:1025-1045 | vulkano/src/command_buffer/commands/copy.rs:1113-1133 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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 (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) vulkano/src/command_buffer/commands/copy.rs:5908— vulkano/src/command_buffer/commands/copy.rs:5908-5953 | vulkano/src/command_buffer/commands/copy.rs:5955-6001 — These two members are one piece of code written twice and then edited apart: 46 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, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) vulkano/src/memory/device_memory.rs:723— vulkano/src/memory/device_memory.rs:723-738 | vulkano/src/memory/device_memory.rs:2493-2513 | vulkano/src/memory/device_memory.rs:2549-2569 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 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 (6 members, 1+ corresponding lines) · ×1
Edited copies of one member (6 members, 1+ corresponding lines) vulkano/src/image/mod.rs:2399— vulkano/src/image/mod.rs:2399-2399 | vulkano/src/image/mod.rs:2411-2411 | vulkano/src/pipeline/graphics/color_blend.rs:501-501 | vulkano/src/pipeline/graphics/discard_rectangle.rs:133-133 | vulkano/src/pipeline/graphics/subpass.rs:368-368 | vulkano/src/pipeline/graphics/viewport.rs:257-257 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 1 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) vulkano/src/command_buffer/commands/copy.rs:1356— vulkano/src/command_buffer/commands/copy.rs:1356-1374 | vulkano/src/command_buffer/commands/copy.rs:1390-1409 — 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 copies of one member (5 members, 17+ corresponding lines) · ×1
Edited copies of one member (5 members, 17+ corresponding lines) vulkano-taskgraph/src/collector.rs:108— vulkano-taskgraph/src/collector.rs:108-124 | vulkano-taskgraph/src/collector.rs:134-153 | vulkano-taskgraph/src/collector.rs:163-182 | vulkano-taskgraph/src/collector.rs:192-211 | vulkano-taskgraph/src/collector.rs:221-240 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 17 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, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) vulkano/src/sync/event.rs:345— vulkano/src/sync/event.rs:345-353 | vulkano/src/sync/fence.rs:986-994 | vulkano/src/sync/semaphore.rs:1337-1345 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) vulkano/src/buffer/mod.rs:774— vulkano/src/buffer/mod.rs:774-786 | vulkano/src/buffer/mod.rs:788-798 | vulkano/src/image/mod.rs:787-799 | vulkano/src/image/mod.rs:802-812 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 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 copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) vulkano-taskgraph/src/graph/execute.rs:2676— vulkano-taskgraph/src/graph/execute.rs:2676-2693 | vulkano-taskgraph/src/graph/execute.rs:2753-2770 | vulkano-taskgraph/src/graph/execute.rs:2831-2848 — 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 (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) vulkano/src/deferred.rs:110— vulkano/src/deferred.rs:110-125 | vulkano/src/deferred.rs:128-140 | vulkano/src/sync/event.rs:233-241 | vulkano/src/sync/fence.rs:249-257 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 13+ corresponding lines) · ×1
Edited copies of one member (5 members, 13+ corresponding lines) vulkano-taskgraph/src/descriptor_set.rs:745— vulkano-taskgraph/src/descriptor_set.rs:745-758 | vulkano-taskgraph/src/descriptor_set.rs:761-773 | vulkano-taskgraph/src/descriptor_set.rs:776-788 | vulkano-taskgraph/src/descriptor_set.rs:791-803 | vulkano-taskgraph/src/descriptor_set.rs:809-821 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 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 copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) vulkano/src/buffer/sys.rs:306— vulkano/src/buffer/sys.rs:306-313 | vulkano/src/image/sys.rs:574-581 — 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 copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) vulkano-taskgraph/src/graph/execute.rs:1123— vulkano-taskgraph/src/graph/execute.rs:1123-1137 | vulkano-taskgraph/src/graph/execute.rs:1395-1407 | vulkano-taskgraph/src/graph/execute.rs:1409-1418 | vulkano-taskgraph/src/graph/execute.rs:1424-1436 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 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 copies of one member (6 members, 10+ corresponding lines) · ×1
Edited copies of one member (6 members, 10+ corresponding lines) vulkano/src/swapchain/mod.rs:1686— vulkano/src/swapchain/mod.rs:1686-1699 | vulkano/src/sync/fence.rs:858-867 | vulkano/src/sync/fence.rs:946-960 | vulkano/src/sync/semaphore.rs:1109-1120 | vulkano/src/sync/semaphore.rs:1223-1235 | vulkano/src/sync/semaphore.rs:1320-1332 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 15+ corresponding lines) · ×1
Edited copies of one member (5 members, 15+ corresponding lines) vulkano/src/command_buffer/commands/copy.rs:2868— vulkano/src/command_buffer/commands/copy.rs:2868-2884 | vulkano/src/command_buffer/commands/copy.rs:3812-3826 | vulkano/src/command_buffer/commands/copy.rs:4527-4541 | vulkano/src/command_buffer/commands/copy.rs:5717-5735 | vulkano/src/command_buffer/commands/copy.rs:6633-6649 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) vulkano/src/memory/allocator/suballocator/free_list.rs:603— vulkano/src/memory/allocator/suballocator/free_list.rs:603-617 | vulkano/src/memory/allocator/suballocator/free_list.rs:632-646 | vulkano/src/memory/allocator/suballocator/tlsf.rs:1048-1062 | vulkano/src/memory/allocator/suballocator/tlsf.rs:1082-1096 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) vulkano/src/swapchain/mod.rs:2752— vulkano/src/swapchain/mod.rs:2752-2765 | vulkano/src/image/sys.rs:3220-3238 — 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· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) vulkano/src/command_buffer/auto/commands/copy.rs:876— vulkano/src/command_buffer/auto/commands/copy.rs:876-890 | vulkano/src/command_buffer/auto/commands/copy.rs:1187-1201 | vulkano/src/command_buffer/auto/commands/copy.rs:1245-1259 — 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 copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) vulkano/src/swapchain/mod.rs:1896— vulkano/src/swapchain/mod.rs:1896-1911 | vulkano/src/swapchain/mod.rs:1968-1983 | vulkano/src/sync/event.rs:277-283 | vulkano/src/sync/fence.rs:449-456 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 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 copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) vulkano/src/descriptor_set/mod.rs:205— vulkano/src/descriptor_set/mod.rs:205-223 | vulkano/src/descriptor_set/mod.rs:254-272 | vulkano/src/descriptor_set/sys.rs:194-203 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 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, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) vulkano/src/pipeline/compute.rs:237— vulkano/src/pipeline/compute.rs:237-240 | vulkano/src/pipeline/graphics/mod.rs:642-645 | vulkano/src/pipeline/ray_tracing.rs:432-437 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 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 (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) vulkano/src/query.rs:201— vulkano/src/query.rs:201-206 | vulkano/src/swapchain/surface.rs:151-156 — These two members are one piece of code written twice and then edited apart: 6 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 (92 lines × 2) vulkano-taskgraph/src/graph/execute.rs:411— vulkano-taskgraph/src/graph/execute.rs:411-502 | vulkano-taskgraph/src/graph/execute.rs:514-605 — 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 `vulkano-taskgraph/src/graph/execute.rs:411` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (64 lines × 2) vulkano/src/command_buffer/auto/builder.rs:331— vulkano/src/command_buffer/auto/builder.rs:331-394 | vulkano/src/command_buffer/auto/builder.rs:400-463 — 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 (58 lines × 2) vulkano/src/descriptor_set/update.rs:1018— vulkano/src/descriptor_set/update.rs:1018-1075 | vulkano/src/descriptor_set/update.rs:1114-1171 — 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 `vulkano/src/descriptor_set/update.rs:1018` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (56 lines × 2) vulkano-taskgraph/src/graph/execute.rs:1258— vulkano-taskgraph/src/graph/execute.rs:1258-1313 | vulkano-taskgraph/src/graph/execute.rs:1881-1936 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (55 lines × 2) vulkano/src/command_buffer/commands/copy.rs:503— vulkano/src/command_buffer/commands/copy.rs:503-557 | vulkano/src/command_buffer/commands/copy.rs:788-842 — 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 `vulkano/src/command_buffer/commands/copy.rs:503` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (53 lines × 2) vulkano/src/memory/allocator/suballocator/free_list.rs:463— vulkano/src/memory/allocator/suballocator/free_list.rs:463-515 | vulkano/src/memory/allocator/suballocator/tlsf.rs:617-669 — before extracting anything, compare `vulkano/src/memory/allocator/suballocator/free_list.rs` and `vulkano/src/memory/allocator/suballocator/tlsf.rs` as WHOLE FILES: this scan already matched 3 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/memory/allocator/suballocator/free_list.rs:463` 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, `vulkano/src/memory/allocator/suballocator/free_list.rs:461` calls `contains` and `vulkano/src/memory/allocator/suballocator/tlsf.rs:615` 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 (50 lines × 2) vulkano/src/memory/sparse.rs:503— vulkano/src/memory/sparse.rs:503-552 | vulkano/src/memory/sparse.rs:973-1022 — 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 `vulkano/src/memory/sparse.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 (56 lines × 3) vulkano/src/command_buffer/commands/sync.rs:1376— vulkano/src/command_buffer/commands/sync.rs:1376-1431 | vulkano/src/command_buffer/commands/sync.rs:1934-1989 | vulkano/src/command_buffer/commands/sync.rs:2687-2742 — 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 `vulkano/src/command_buffer/commands/sync.rs:1376` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (36 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:502— vulkano-taskgraph/src/command_buffer/commands/copy.rs:502-537 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:674-709 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:502` 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, `vulkano-taskgraph/src/command_buffer/commands/copy.rs:673` calls `handle` and `vulkano-taskgraph/src/command_buffer/commands/copy.rs:501` 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 (33 lines × 2) vulkano-taskgraph/src/command_buffer/commands/clear.rs:59— vulkano-taskgraph/src/command_buffer/commands/clear.rs:59-91 | vulkano-taskgraph/src/command_buffer/commands/clear.rs:136-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/command_buffer/commands/clear.rs:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27–31 lines × 2) autogen/src/spirv_parse.rs:134— autogen/src/spirv_parse.rs:134-164 | autogen/src/spirv_parse.rs:811-837 — 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 `autogen/src/spirv_parse.rs:134` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30–31 lines × 2) vulkano/src/image/mod.rs:2082— vulkano/src/image/mod.rs:2082-2112 | vulkano/src/image/sys.rs:2382-2411 — before extracting anything, compare `vulkano/src/image/mod.rs` and `vulkano/src/image/sys.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/image/mod.rs:2082` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (29 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:444— vulkano-taskgraph/src/command_buffer/commands/copy.rs:444-472 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:616-644 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:444` 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 (28–29 lines × 2) vulkano-taskgraph/src/graph/execute.rs:1148— vulkano-taskgraph/src/graph/execute.rs:1148-1175 | vulkano-taskgraph/src/graph/execute.rs:1768-1796 — 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 `vulkano-taskgraph/src/graph/execute.rs:1148` it does not close everything it opens, so those 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 (21–27 lines × 2) vulkano/src/buffer/subbuffer.rs:335— vulkano/src/buffer/subbuffer.rs:335-361 | vulkano/src/buffer/subbuffer.rs:429-449 — 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 (27 lines × 2) vulkano/src/command_buffer/auto/commands/render_pass.rs:1261— vulkano/src/command_buffer/auto/commands/render_pass.rs:1261-1287 | vulkano/src/command_buffer/commands/render_pass.rs:1332-1358 — before extracting anything, compare `vulkano/src/command_buffer/auto/commands/render_pass.rs` and `vulkano/src/command_buffer/commands/render_pass.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/auto/commands/render_pass.rs:1261` 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 (26 lines × 3) vulkano/src/descriptor_set/update.rs:511— vulkano/src/descriptor_set/update.rs:511-536 | vulkano/src/descriptor_set/update.rs:652-677 | vulkano/src/descriptor_set/update.rs:753-778 — 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 `vulkano/src/descriptor_set/update.rs:511` it does not close everything it opens, so those 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, `vulkano/src/descriptor_set/update.rs:510` calls `device` and `vulkano/src/descriptor_set/update.rs:650` 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 (26 lines × 2) vulkano-taskgraph/src/graph/execute.rs:1316— vulkano-taskgraph/src/graph/execute.rs:1316-1341 | vulkano-taskgraph/src/graph/execute.rs:1939-1964 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (25–26 lines × 2) vulkano/src/pipeline/shader/validate_runtime.rs:2477— vulkano/src/pipeline/shader/validate_runtime.rs:2477-2501 | vulkano/src/pipeline/shader/validate_runtime.rs:2507-2532 — 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 `vulkano/src/pipeline/shader/validate_runtime.rs:2507` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 3) vulkano-taskgraph/src/graph/execute.rs:2638— vulkano-taskgraph/src/graph/execute.rs:2638-2660 | vulkano-taskgraph/src/graph/execute.rs:2719-2741 | vulkano-taskgraph/src/graph/execute.rs:2793-2815 — 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 `vulkano-taskgraph/src/graph/execute.rs:2638` 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 `virtual_id` to `Id<Buffer>` in one and `Id<Image>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17–21 lines × 5) vulkano/src/image/mod.rs:2274— vulkano/src/image/mod.rs:2274-2294 | vulkano/src/image/sys.rs:3156-3176 | vulkano/src/swapchain/acquire_present.rs:581-597 | vulkano/src/swapchain/mod.rs:2664-2684 | vulkano/src/swapchain/surface.rs:3011-3027 — before extracting anything, compare `vulkano/src/image/mod.rs` and `vulkano/src/image/sys.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/image/mod.rs:2274` 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 (21 lines × 4) vulkano-taskgraph/src/graph/execute.rs:1041— vulkano-taskgraph/src/graph/execute.rs:1041-1061 | vulkano-taskgraph/src/graph/execute.rs:1083-1103 | vulkano-taskgraph/src/graph/execute.rs:1657-1677 | vulkano-taskgraph/src/graph/execute.rs:1700-1720 — 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 `vulkano-taskgraph/src/graph/execute.rs:1041` it does not close everything it opens, so those exact lines 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–21 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:842— vulkano-taskgraph/src/command_buffer/commands/copy.rs:842-860 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:904-924 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:842` 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 (38–39 lines × 2) vulkano/src/descriptor_set/update.rs:911— vulkano/src/descriptor_set/update.rs:911-948 | vulkano/src/descriptor_set/update.rs:964-1002 — 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 `vulkano/src/descriptor_set/update.rs:911` it does not close everything it opens, so those exact lines 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) vulkano/src/render_pass/mod.rs:1094— vulkano/src/render_pass/mod.rs:1094-1113 | vulkano/src/render_pass/mod.rs:1182-1202 — 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 `vulkano/src/render_pass/mod.rs:1094` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (20 lines × 4) vulkano/src/descriptor_set/update.rs:491— vulkano/src/descriptor_set/update.rs:491-510 | vulkano/src/descriptor_set/update.rs:633-652 | vulkano/src/descriptor_set/update.rs:734-753 | vulkano/src/descriptor_set/update.rs:841-860 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano/src/descriptor_set/update.rs:511` calls `device` and `vulkano/src/descriptor_set/update.rs:654` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17–20 lines × 3) vulkano/src/device/queue.rs:1032— vulkano/src/device/queue.rs:1032-1048 | vulkano/src/device/queue.rs:1107-1126 | vulkano/src/device/queue.rs:1174-1190 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18–20 lines × 2) vulkano-taskgraph/src/command_buffer/commands/copy.rs:1029— vulkano-taskgraph/src/command_buffer/commands/copy.rs:1029-1046 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1098-1117 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:1029` 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–18 lines × 2) vulkano-taskgraph/src/resource/state.rs:361— vulkano-taskgraph/src/resource/state.rs:361-378 | vulkano-taskgraph/src/resource/state.rs:500-512 — 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–18 lines × 2) vulkano/src/range_map.rs:299— vulkano/src/range_map.rs:299-313 | vulkano/src/range_map.rs:329-346 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–18 lines × 2) vulkano/src/sync/semaphore.rs:1418— vulkano/src/sync/semaphore.rs:1418-1434 | vulkano/src/sync/semaphore.rs:2332-2349 — 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 `vulkano/src/sync/semaphore.rs:1418` 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–17 lines × 3) vulkano/src/command_buffer/commands/sync.rs:109— vulkano/src/command_buffer/commands/sync.rs:109-124 | vulkano/src/command_buffer/commands/sync.rs:373-388 | vulkano/src/command_buffer/commands/sync.rs:606-622 — 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 `vulkano/src/command_buffer/commands/sync.rs:109` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (32 lines × 2) vulkano/src/command_buffer/commands/sync.rs:2437— vulkano/src/command_buffer/commands/sync.rs:2437-2468 | vulkano/src/command_buffer/commands/sync.rs:3333-3364 — 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 `vulkano/src/command_buffer/commands/sync.rs:2437` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–17 lines × 2) vulkano/src/sync/future/mod.rs:713— vulkano/src/sync/future/mod.rs:713-729 | vulkano/src/sync/future/mod.rs:761-776 — 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 `vulkano/src/sync/future/mod.rs:713` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–16 lines × 8) vulkano/src/format.rs:837— vulkano/src/format.rs:837-852 | vulkano/src/image/mod.rs:2268-2283 | vulkano/src/image/sys.rs:3150-3165 | vulkano/src/memory/device_memory.rs:1320-1335 | vulkano/src/pipeline/graphics/mod.rs:2480-2495 | vulkano/src/swapchain/mod.rs:2658-2673 | vulkano/src/swapchain/surface.rs:2840-2855 | vulkano/src/swapchain/surface.rs:3006-3020 — before extracting anything, compare `vulkano/src/image/mod.rs` and `vulkano/src/image/sys.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/format.rs:837` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `extensions_vk` to `&'a mut ImageFormatInfo2ExtensionsVk<'_>` in one and `&'a mut ImageCreateInfoExtensionsVk<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano/src/swapchain/surface.rs:3022` calls `Some`, `push_next` and `vulkano/src/format.rs:854` 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 × 5) vulkano/src/descriptor_set/update.rs:452— vulkano/src/descriptor_set/update.rs:452-467 | vulkano/src/descriptor_set/update.rs:592-606 | vulkano/src/descriptor_set/update.rs:697-712 | vulkano/src/descriptor_set/update.rs:804-819 | vulkano/src/descriptor_set/update.rs:1210-1225 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vulkano/src/descriptor_set/update.rs:451` calls `is_empty` and `vulkano/src/descriptor_set/update.rs:696` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–15 lines × 15) vulkano/src/swapchain/surface.rs:407— vulkano/src/swapchain/surface.rs:407-421 | vulkano/src/swapchain/surface.rs:585-596 | vulkano/src/swapchain/surface.rs:679-693 | vulkano/src/swapchain/surface.rs:788-802 | vulkano/src/swapchain/surface.rs:892-906 | vulkano/src/swapchain/surface.rs:995-1009 | vulkano/src/swapchain/surface.rs:1099-1113 | vulkano/src/swapchain/surface.rs:1203-1217 | vulkano/src/swapchain/surface.rs:1312-1326 | vulkano/src/swapchain/surface.rs:1423-1437 | vulkano/src/swapchain/surface.rs:1522-1536 | vulkano/src/swapchain/surface.rs:1635-1649 | vulkano/src/swapchain/surface.rs:1748-1762 | vulkano/src/swapchain/surface.rs:1861-1875 | vulkano/src/swapchain/surface.rs:1974-1988 — all 15 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/swapchain/surface.rs:407` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `instance` to `&Arc<Instance>` in one and `&Instance` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 6) vulkano-taskgraph/src/command_buffer/commands/copy.rs:264— vulkano-taskgraph/src/command_buffer/commands/copy.rs:264-278 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:335-349 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:847-861 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:911-925 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1035-1049 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1106-1120 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:264` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 4) vulkano/src/device/physical.rs:645— vulkano/src/device/physical.rs:645-659 | vulkano/src/device/physical.rs:691-705 | vulkano/src/pipeline/mod.rs:196-210 | vulkano/src/pipeline/mod.rs:328-342 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/device/physical.rs:645` 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–15 lines × 3) vulkano/src/command_buffer/commands/sync.rs:67— vulkano/src/command_buffer/commands/sync.rs:67-80 | vulkano/src/command_buffer/commands/sync.rs:331-344 | vulkano/src/command_buffer/commands/sync.rs:563-577 — 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 `vulkano/src/command_buffer/commands/sync.rs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 3) vulkano/src/render_pass/mod.rs:598— vulkano/src/render_pass/mod.rs:598-612 | vulkano/src/render_pass/mod.rs:629-643 | vulkano/src/render_pass/mod.rs:651-665 — 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 `vulkano/src/render_pass/mod.rs:598` 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–15 lines × 2) vulkano/src/instance/mod.rs:687— vulkano/src/instance/mod.rs:687-700 | vulkano/src/library.rs:302-316 — 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 `vulkano/src/instance/mod.rs:687` 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) vulkano/src/pipeline/graphics/mod.rs:370— vulkano/src/pipeline/graphics/mod.rs:370-382 | vulkano/src/pipeline/ray_tracing.rs:224-238 — before extracting anything, compare `vulkano/src/pipeline/graphics/mod.rs` and `vulkano/src/pipeline/ray_tracing.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/pipeline/graphics/mod.rs:370` 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 × 15) vulkano/src/device/physical.rs:643— vulkano/src/device/physical.rs:643-656 | vulkano/src/device/physical.rs:689-702 | vulkano/src/device/physical.rs:838-851 | vulkano/src/device/physical.rs:879-892 | vulkano/src/device/physical.rs:1010-1023 | vulkano/src/device/physical.rs:2235-2248 | vulkano/src/device/physical.rs:2287-2300 | vulkano/src/device/physical.rs:2477-2490 | vulkano/src/device/physical.rs:2520-2533 | vulkano/src/display.rs:166-179 | vulkano/src/display.rs:216-229 | vulkano/src/library.rs:300-313 | vulkano/src/pipeline/mod.rs:194-207 | vulkano/src/pipeline/mod.rs:326-339 | vulkano/src/swapchain/mod.rs:1099-1112 — before extracting anything, compare `vulkano/src/device/physical.rs` and `vulkano/src/swapchain/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/device/physical.rs:643` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vulkano/src/display.rs:164` calls `handle` and `vulkano/src/device/physical.rs:641` 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 (13–14 lines × 3) vulkano/src/render_pass/mod.rs:1102— vulkano/src/render_pass/mod.rs:1102-1114 | vulkano/src/render_pass/mod.rs:1190-1203 | vulkano/src/render_pass/mod.rs:1462-1475 — 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 `vulkano/src/render_pass/mod.rs:1102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–14 lines × 2) vulkano/src/image/mod.rs:2067— vulkano/src/image/mod.rs:2067-2080 | vulkano/src/image/sys.rs:2370-2379 — before extracting anything, compare `vulkano/src/image/mod.rs` and `vulkano/src/image/sys.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/image/mod.rs:2067` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 × 2) vulkano/src/pipeline/shader/inout_interface.rs:526— vulkano/src/pipeline/shader/inout_interface.rs:526-538 | vulkano/src/pipeline/shader/inout_interface.rs:550-563 — 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 `vulkano/src/pipeline/shader/inout_interface.rs:526` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 14) vulkano/src/acceleration_structure.rs:210— vulkano/src/acceleration_structure.rs:210-222 | vulkano/src/buffer/sys.rs:119-131 | vulkano/src/buffer/view.rs:350-362 | vulkano/src/command_buffer/pool.rs:95-107 | vulkano/src/descriptor_set/layout.rs:137-149 | vulkano/src/descriptor_set/pool.rs:95-107 | vulkano/src/image/sampler/mod.rs:171-183 | vulkano/src/image/sampler/ycbcr.rs:223-235 | vulkano/src/pipeline/cache.rs:136-148 | vulkano/src/pipeline/layout.rs:148-160 | vulkano/src/query.rs:91-103 | vulkano/src/render_pass/mod.rs:238-250 | vulkano/src/sync/event.rs:119-131 | vulkano/src/sync/semaphore.rs:153-165 — before extracting anything, compare `vulkano/src/buffer/sys.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/acceleration_structure.rs:210` 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 `create_info` to `&AccelerationStructureCreateInfo<'_>` in one and `&BufferCreateInfo<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vulkano/src/sync/event.rs:116` calls `fns` and `vulkano/src/query.rs:88` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–12 lines × 4) vulkano/src/command_buffer/commands/copy.rs:176— vulkano/src/command_buffer/commands/copy.rs:176-185 | vulkano/src/command_buffer/commands/copy.rs:189-198 | vulkano/src/command_buffer/commands/copy.rs:525-536 | vulkano/src/command_buffer/commands/copy.rs:810-821 — 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 `vulkano/src/command_buffer/commands/copy.rs:176` 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 (27 lines × 3) vulkano/src/device/physical.rs:1905— vulkano/src/device/physical.rs:1905-1931 | vulkano/src/device/physical.rs:2113-2139 | vulkano/src/device/physical.rs:2375-2401 — 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 `vulkano/src/device/physical.rs:1905` 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 × 6) vulkano-taskgraph/src/graph/execute.rs:1000— vulkano-taskgraph/src/graph/execute.rs:1000-1010 | vulkano-taskgraph/src/graph/execute.rs:1038-1048 | vulkano-taskgraph/src/graph/execute.rs:1080-1090 | vulkano-taskgraph/src/graph/execute.rs:1615-1625 | vulkano-taskgraph/src/graph/execute.rs:1654-1664 | vulkano-taskgraph/src/graph/execute.rs:1697-1707 — 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) vulkano/src/command_buffer/commands/copy.rs:2887— vulkano/src/command_buffer/commands/copy.rs:2887-2897 | vulkano/src/command_buffer/commands/copy.rs:2937-2947 | vulkano/src/command_buffer/commands/copy.rs:6652-6662 | vulkano/src/command_buffer/commands/copy.rs:6702-6712 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–11 lines × 3) vulkano/src/buffer/sys.rs:937— vulkano/src/buffer/sys.rs:937-947 | vulkano/src/image/sys.rs:2920-2930 | vulkano/src/memory/device_memory.rs:1239-1246 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:937` 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 (9–11 lines × 2) vulkano/src/swapchain/mod.rs:2573— vulkano/src/swapchain/mod.rs:2573-2581 | vulkano/src/swapchain/surface.rs:2809-2819 — before extracting anything, compare `vulkano/src/swapchain/mod.rs` and `vulkano/src/swapchain/surface.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/swapchain/mod.rs:2573` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 9) vulkano/src/command_buffer/auto/commands/pipeline.rs:367— vulkano/src/command_buffer/auto/commands/pipeline.rs:367-376 | vulkano/src/command_buffer/auto/commands/pipeline.rs:473-482 | vulkano/src/command_buffer/auto/commands/pipeline.rs:605-614 | vulkano/src/command_buffer/auto/commands/pipeline.rs:844-853 | vulkano/src/command_buffer/auto/commands/pipeline.rs:972-981 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1119-1128 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1313-1322 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1425-1434 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1565-1574 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano/src/command_buffer/auto/commands/pipeline.rs:484` calls `add_indirect_buffer_resources`, `as_bytes` and `vulkano/src/command_buffer/auto/commands/pipeline.rs:379` 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–10 lines × 6) vulkano/src/command_buffer/commands/copy.rs:63— vulkano/src/command_buffer/commands/copy.rs:63-71 | vulkano/src/command_buffer/commands/copy.rs:418-426 | vulkano/src/command_buffer/commands/copy.rs:696-705 | vulkano/src/command_buffer/commands/copy.rs:960-969 | vulkano/src/command_buffer/commands/copy.rs:1052-1060 | vulkano/src/command_buffer/commands/copy.rs:1140-1148 — 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 `vulkano/src/command_buffer/commands/copy.rs:63` it does not close everything it opens, so those 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, `vulkano/src/command_buffer/commands/copy.rs:71` calls `device`, `api_version`, `handle` and `vulkano/src/command_buffer/commands/copy.rs:705` 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–10 lines × 2) vulkano/src/command_buffer/allocator.rs:538— vulkano/src/command_buffer/allocator.rs:538-547 | vulkano/src/command_buffer/allocator.rs:605-612 — 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 `vulkano/src/command_buffer/allocator.rs:538` 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–9 lines × 2) vulkano/src/command_buffer/commands/render_pass.rs:385— vulkano/src/command_buffer/commands/render_pass.rs:385-393 | vulkano/src/command_buffer/commands/render_pass.rs:578-585 — 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 `vulkano/src/command_buffer/commands/render_pass.rs:385` it does not close everything it opens, so those 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–8 lines × 4) vulkano-taskgraph/src/command_buffer/commands/copy.rs:251— vulkano-taskgraph/src/command_buffer/commands/copy.rs:251-257 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:290-297 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1022-1028 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1061-1068 — 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 `vulkano-taskgraph/src/command_buffer/commands/copy.rs:251` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 4) vulkano-taskgraph/src/graph/execute.rs:1068— vulkano-taskgraph/src/graph/execute.rs:1068-1074 | vulkano-taskgraph/src/graph/execute.rs:1110-1116 | vulkano-taskgraph/src/graph/execute.rs:1682-1688 | vulkano-taskgraph/src/graph/execute.rs:1725-1731 — 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 `vulkano-taskgraph/src/graph/execute.rs:1068` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vulkano-taskgraph/src/graph/execute.rs:1690` calls `convert_stage_mask` and `vulkano-taskgraph/src/graph/execute.rs:1075` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 6) vulkano/src/command_buffer/auto/commands/pipeline.rs:266— vulkano/src/command_buffer/auto/commands/pipeline.rs:266-270 | vulkano/src/command_buffer/auto/commands/pipeline.rs:457-461 | vulkano/src/command_buffer/auto/commands/pipeline.rs:588-592 | vulkano/src/command_buffer/auto/commands/pipeline.rs:732-736 | vulkano/src/command_buffer/auto/commands/pipeline.rs:948-952 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1094-1098 — 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 (10 lines × 6) vulkano-taskgraph/src/command_buffer/commands/copy.rs:1333— vulkano-taskgraph/src/command_buffer/commands/copy.rs:1333-1342 | vulkano-taskgraph/src/command_buffer/commands/copy.rs:1716-1725 | vulkano/src/command_buffer/auto/commands/copy.rs:1140-1149 | vulkano/src/command_buffer/auto/commands/copy.rs:1643-1652 | vulkano/src/command_buffer/commands/copy.rs:3018-3027 | vulkano/src/command_buffer/commands/copy.rs:6783-6792 — before extracting anything, compare `vulkano-taskgraph/src/command_buffer/commands/copy.rs` and `vulkano/src/command_buffer/auto/commands/copy.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 23) vulkano-taskgraph/src/resource/mod.rs:106— vulkano-taskgraph/src/resource/mod.rs:106-111 | vulkano/src/buffer/sys.rs:64-69 | vulkano/src/buffer/view.rs:84-89 | vulkano/src/command_buffer/pool.rs:55-60 | vulkano/src/descriptor_set/layout.rs:65-70 | vulkano/src/descriptor_set/pool.rs:50-55 | vulkano/src/device/mod.rs:214-219 | vulkano/src/device/private_data.rs:50-55 | vulkano/src/display.rs:368-373 | vulkano/src/image/sampler/mod.rs:129-134 | vulkano/src/image/sampler/ycbcr.rs:161-166 | vulkano/src/image/sys.rs:93-98 | vulkano/src/image/view.rs:65-70 | vulkano/src/instance/debug.rs:78-83 | vulkano/src/instance/mod.rs:314-319 | vulkano/src/pipeline/cache.rs:95-100 | vulkano/src/pipeline/layout.rs:106-111 | vulkano/src/query.rs:50-55 | vulkano/src/render_pass/framebuffer.rs:65-70 | vulkano/src/render_pass/mod.rs:147-152 | vulkano/src/sync/event.rs:62-67 | vulkano/src/sync/fence.rs:78-83 | vulkano/src/sync/semaphore.rs:111-116 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/resource/mod.rs:106` 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 `create_info` to `&ResourcesCreateInfo<'_>` in one and `&BufferCreateInfo<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 11) vulkano-taskgraph/src/resource/mod.rs:290— vulkano-taskgraph/src/resource/mod.rs:290-295 | vulkano-taskgraph/src/resource/mod.rs:334-339 | vulkano-taskgraph/src/resource/mod.rs:545-550 | vulkano/src/device/physical.rs:1863-1868 | vulkano/src/device/physical.rs:2070-2075 | vulkano/src/device/physical.rs:2339-2344 | vulkano/src/device/physical.rs:2571-2576 | vulkano/src/device/private_data.rs:166-171 | vulkano/src/pipeline/ray_tracing.rs:315-320 | vulkano/src/swapchain/mod.rs:1724-1729 | vulkano/src/sync/semaphore.rs:424-429 — before extracting anything, compare `vulkano/src/device/physical.rs` and `vulkano/src/swapchain/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano-taskgraph/src/resource/mod.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. Note first that the copies are not typed on the same thing: the declarations holding them bind `create_info` to `&ImageCreateInfo<'_>` in one and `&SwapchainCreateInfo<'_>` 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 (72 lines × 2) vulkano/src/command_buffer/commands/sync.rs:3421— vulkano/src/command_buffer/commands/sync.rs:3421-3492 | vulkano/src/command_buffer/commands/sync.rs:3537-3608 — 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 (39 lines × 2) vulkano/src/command_buffer/auto/commands/pipeline.rs:1848— vulkano/src/command_buffer/auto/commands/pipeline.rs:1848-1886 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1921-1959 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:1848` 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) vulkano/src/command_buffer/commands/copy.rs:1315— vulkano/src/command_buffer/commands/copy.rs:1315-1330 | vulkano/src/command_buffer/commands/copy.rs:2820-2837 | vulkano/src/command_buffer/commands/copy.rs:5668-5686 — 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 `vulkano/src/command_buffer/commands/copy.rs:1315` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 8) vulkano/src/command_buffer/commands/copy.rs:1892— vulkano/src/command_buffer/commands/copy.rs:1892-1909 | vulkano/src/command_buffer/commands/copy.rs:2291-2308 | vulkano/src/command_buffer/commands/copy.rs:3511-3528 | vulkano/src/command_buffer/commands/copy.rs:4229-4246 | vulkano/src/command_buffer/commands/copy.rs:5302-5319 | vulkano/src/command_buffer/commands/copy.rs:5515-5532 | vulkano/src/command_buffer/commands/copy.rs:6331-6348 | vulkano/src/command_buffer/commands/copy.rs:6534-6551 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/commands/copy.rs:1892` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 4) vulkano/src/command_buffer/commands/render_pass.rs:48— vulkano/src/command_buffer/commands/render_pass.rs:48-65 | vulkano/src/command_buffer/commands/render_pass.rs:455-472 | vulkano/src/command_buffer/commands/render_pass.rs:549-566 | vulkano/src/command_buffer/commands/render_pass.rs:635-652 — 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 `vulkano/src/command_buffer/commands/render_pass.rs:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) vulkano/src/command_buffer/commands/clear.rs:515— vulkano/src/command_buffer/commands/clear.rs:515-545 | vulkano/src/command_buffer/commands/clear.rs:784-814 — 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 `vulkano/src/command_buffer/commands/clear.rs:515` 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 × 7) vulkano/src/command_buffer/commands/clear.rs:102— vulkano/src/command_buffer/commands/clear.rs:102-116 | vulkano/src/command_buffer/commands/copy.rs:1027-1041 | vulkano/src/command_buffer/commands/copy.rs:1115-1129 | vulkano/src/command_buffer/commands/render_pass.rs:52-66 | vulkano/src/command_buffer/commands/render_pass.rs:459-473 | vulkano/src/command_buffer/commands/render_pass.rs:553-567 | vulkano/src/command_buffer/commands/render_pass.rs:639-653 — before extracting anything, compare `vulkano/src/command_buffer/commands/clear.rs` and `vulkano/src/command_buffer/commands/copy.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/command_buffer/commands/clear.rs:102` 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 (28 lines × 2) vulkano/src/memory/sparse.rs:332— vulkano/src/memory/sparse.rs:332-359 | vulkano/src/memory/sparse.rs:787-814 — 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 `vulkano/src/memory/sparse.rs:332` 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 × 9) vulkano/src/command_buffer/auto/commands/pipeline.rs:250— vulkano/src/command_buffer/auto/commands/pipeline.rs:250-263 | vulkano/src/command_buffer/auto/commands/pipeline.rs:441-454 | vulkano/src/command_buffer/auto/commands/pipeline.rs:572-585 | vulkano/src/command_buffer/auto/commands/pipeline.rs:716-729 | vulkano/src/command_buffer/auto/commands/pipeline.rs:932-945 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1078-1091 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1181-1194 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1383-1396 | vulkano/src/command_buffer/auto/commands/pipeline.rs:1522-1535 — 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 `vulkano/src/command_buffer/auto/commands/pipeline.rs:250` 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 × 12) vulkano/src/command_buffer/commands/copy.rs:2024— vulkano/src/command_buffer/commands/copy.rs:2024-2036 | vulkano/src/command_buffer/commands/copy.rs:2042-2054 | vulkano/src/command_buffer/commands/copy.rs:2060-2072 | vulkano/src/command_buffer/commands/copy.rs:2423-2435 | vulkano/src/command_buffer/commands/copy.rs:2441-2453 | vulkano/src/command_buffer/commands/copy.rs:2459-2471 | vulkano/src/command_buffer/commands/copy.rs:3643-3656 | vulkano/src/command_buffer/commands/copy.rs:3662-3675 | vulkano/src/command_buffer/commands/copy.rs:3681-3694 | vulkano/src/command_buffer/commands/copy.rs:4361-4374 | vulkano/src/command_buffer/commands/copy.rs:4380-4393 | vulkano/src/command_buffer/commands/copy.rs:4399-4412 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 5) vulkano/src/buffer/sys.rs:937— vulkano/src/buffer/sys.rs:937-946 | vulkano/src/image/sys.rs:2920-2929 | vulkano/src/memory/device_memory.rs:1239-1246 | vulkano/src/sync/fence.rs:1073-1080 | vulkano/src/sync/semaphore.rs:1454-1461 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:937` 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 (9 lines × 5) vulkano/src/sync/fence.rs:586— vulkano/src/sync/fence.rs:586-594 | vulkano/src/sync/fence.rs:716-724 | vulkano/src/sync/semaphore.rs:670-678 | vulkano/src/sync/semaphore.rs:818-826 | vulkano/src/sync/semaphore.rs:942-950 — before extracting anything, compare `vulkano/src/sync/fence.rs` and `vulkano/src/sync/semaphore.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/sync/fence.rs:586` 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 `handle_type` to `ExternalFenceHandleType` in one and `ExternalSemaphoreHandleType` 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 × 7) vulkano/src/device/physical.rs:2606— vulkano/src/device/physical.rs:2606-2614 | vulkano/src/device/physical.rs:2972-2980 | vulkano/src/device/physical.rs:3051-3059 | vulkano/src/device/physical.rs:3140-3148 | vulkano/src/device/physical.rs:3238-3246 | vulkano/src/device/physical.rs:3332-3340 | vulkano/src/device/physical.rs:3423-3431 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/device/physical.rs:2606` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 6) vulkano/src/buffer/sys.rs:937— vulkano/src/buffer/sys.rs:937-944 | vulkano/src/image/sys.rs:2920-2927 | vulkano/src/memory/device_memory.rs:1239-1246 | vulkano/src/memory/device_memory.rs:1265-1272 | vulkano/src/sync/fence.rs:1073-1080 | vulkano/src/sync/semaphore.rs:1454-1461 — `vulkano/src/buffer/sys.rs` and `vulkano/src/image/sys.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vulkano/src/buffer/sys.rs:937` 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 × 5) vulkano/src/command_buffer/commands/sync.rs:1128— vulkano/src/command_buffer/commands/sync.rs:1128-1133 | vulkano/src/command_buffer/mod.rs:1035-1040 | vulkano/src/memory/sparse.rs:93-98 | vulkano/src/memory/sparse.rs:99-104 | vulkano/src/pipeline/graphics/viewport.rs:118-123 — before extracting anything, compare `vulkano/src/command_buffer/commands/sync.rs` and `vulkano/src/command_buffer/mod.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `vulkano/src/command_buffer/commands/sync.rs:1128` 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, `vulkano/src/pipeline/graphics/viewport.rs:115` calls `physical_device`, `properties` and `vulkano/src/command_buffer/mod.rs:1032` 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.
Off the main sequence: vulkano — vulkano: abstractness 0.03, instability 0.25, distance 0.72 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Orphaned file vulkano/src/pipeline/graphics/viewport.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/depth_stencil.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/subpass.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/tests.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano-util/src/window.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file autogen/src/spirv_reqs.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/image/layout.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/input_assembly.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/render_pass/macros.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/device/private_data.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/descriptor_set/sys.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/vertex_input/definition.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/sync/future/join.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/fragment_shading_rate.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/device/properties.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/sync/future/semaphore_signal.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/deferred.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/vertex_input/impl_vertex.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/multisample.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/command_buffer/commands/debug.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/tessellation.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file autogen/src/fns.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/buffer/usage.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/discard_rectangle.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file vulkano/src/pipeline/graphics/vertex_input/vertex.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate vulkano/src/command_buffer/traits.rs:488— `!*self.finished.get_mut() && !thread::panicking()` appears character-identically in 2 files — vulkano/src/command_buffer/traits.rs, vulkano/src/sync/future/semaphore_signal.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 vulkano/src/descriptor_set/mod.rs:206— `descriptor_writes.is_empty() && descriptor_copies.is_empty()` appears character-identically in 2 files — vulkano/src/descriptor_set/mod.rs, vulkano/src/descriptor_set/sys.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 vulkano/src/memory/device_memory.rs:1361— `device.api_version() >= Version::V1_1 || device.enabled_extensions().khr_dedicated_allocation` appears character-identically in 2 files — vulkano/src/memory/device_memory.rs, vulkano/src/memory/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 vulkano/src/buffer/sys.rs:932— `device.api_version() >= Version::V1_1 || device.enabled_extensions().khr_external_memory` appears character-identically in 3 files — vulkano/src/buffer/sys.rs, vulkano/src/image/sys.rs, vulkano/src/memory/device_memory.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 vulkano/src/buffer/sys.rs:237— `device.api_version() >= Version::V1_1 || device.enabled_extensions().khr_get_memory_requirements2` appears character-identically in 3 files — vulkano/src/buffer/sys.rs, vulkano/src/image/sys.rs, vulkano/src/memory/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 vulkano/src/command_buffer/commands/clear.rs:168— `device.api_version() >= Version::V1_1 || device.enabled_extensions().khr_maintenance1` appears character-identically in 2 files — vulkano/src/command_buffer/commands/clear.rs, vulkano/src/command_buffer/commands/copy.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 vulkano/src/image/sys.rs:1927— `device.api_version() >= Version::V1_2 || device.enabled_extensions().khr_image_format_list` appears character-identically in 2 files — vulkano/src/image/sys.rs, vulkano/src/swapchain/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 vulkano-taskgraph/src/command_buffer/commands/bind_push.rs:217— `device.api_version() >= Version::V1_3 || device.enabled_extensions().ext_extended_dynamic_state || device.enabled_extensions().ext_shader_ob…` appears character-identically in 2 files — vulkano-taskgraph/src/command_buffer/commands/bind_push.rs, vulkano/src/command_buffer/commands/bind_push.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 vulkano/src/command_buffer/commands/query.rs:432— `device.enabled_features().attachment_fragment_shading_rate || device.enabled_features().shading_rate_image` appears character-identically in 2 files — vulkano/src/command_buffer/commands/query.rs, vulkano/src/command_buffer/commands/sync.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 vulkano/src/image/mod.rs:2169— `flags.intersects(ImageCreateFlags::MUTABLE_FORMAT) && view_formats.is_empty()` appears character-identically in 2 files — vulkano/src/image/mod.rs, vulkano/src/image/sys.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 vulkano-taskgraph/src/graph/compile.rs:3518— `queue_flags.contains(QueueFlags::COMPUTE) && !queue_flags.contains(QueueFlags::GRAPHICS)` appears character-identically in 2 files — vulkano-taskgraph/src/graph/compile.rs, vulkano-taskgraph/src/resource/state.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 vulkano/src/command_buffer/auto/commands/render_pass.rs:1227— `render_area_extent[0] == 0 || render_area_extent[1] == 0` appears character-identically in 2 files — vulkano/src/command_buffer/auto/commands/render_pass.rs, vulkano/src/command_buffer/commands/render_pass.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 vulkano-taskgraph/src/command_buffer/commands/copy.rs:56— `self.device().api_version() >= Version::V1_3 || self.device().enabled_extensions().khr_copy_commands2` appears character-identically in 2 files — vulkano-taskgraph/src/command_buffer/commands/copy.rs, vulkano/src/command_buffer/commands/copy.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 vulkano/src/buffer/sys.rs:556— `self.device.api_version() >= Version::V1_1 || self.device.enabled_extensions().khr_bind_memory2` appears character-identically in 2 files — vulkano/src/buffer/sys.rs, vulkano/src/image/sys.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 vulkano-taskgraph/src/command_buffer/commands/sync.rs:320— `self.memory_barriers.is_empty() && self.buffer_memory_barriers.is_empty() && self.image_memory_barriers.is_empty()` appears character-identically in 3 files — vulkano-taskgraph/src/command_buffer/commands/sync.rs, vulkano/src/command_buffer/commands/sync.rs, vulkano/src/sync/pipeline.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 vulkano/src/device/physical.rs:2178— `surface.api() == SurfaceApi::Win32 && full_screen_exclusive == FullScreenExclusive::ApplicationControlled` appears character-identically in 2 files — vulkano/src/device/physical.rs, vulkano/src/swapchain/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 vulkano/src/command_buffer/commands/render_pass.rs:1427— `view_mask != 0 && !device.enabled_features().multiview` appears character-identically in 3 files — vulkano/src/command_buffer/commands/render_pass.rs, vulkano/src/command_buffer/mod.rs, vulkano/src/pipeline/graphics/subpass.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 16 significant file(s) lose their only recent owner: vulkano-taskgraph/src/graph/compile.rs, vulkano-taskgraph/src/resource/state.rs, vulkano/src/memory/allocator/mod.rs, vulkano-taskgraph/src/resource/mod.rs, vulkano-taskgraph/src/command_buffer/commands/copy.rs, vulkano-taskgraph/src/graph/mod.rs, vulkano-taskgraph/src/collector.rs, vulkano/src/memory/allocator/suballocator/tlsf.rs (+8 more). Pair on, review, or document these before any departure.
No ADRs found autogen/src/main.rs:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `autogen/src/main.rs` makes this repository a deployable product (line 1).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 6 project(s) overshoot their size bounds, lowering Project Cohesion to 6.7/10. The most over is `vulkano` (131151 LoC, 610 module-visible types across 24 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 30 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: vulkano/src/pipeline/graphics/viewport.rs, vulkano/src/pipeline/graphics/depth_stencil.rs, vulkano/src/pipeline/graphics/subpass.rs, vulkano/src/pipeline/graphics/tests.rs, vulkano-util/src/window.rs, autogen/src/spirv_reqs.rs, vulkano/src/image/layout.rs, vulkano/src/pipeline/graphics/input_assembly.rs (and 22 more) (58 orphaned of 158 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 158 of the 175 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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.9"` requirement declared in vulkano-taskgraph/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytemuck` and commit the updated REDACTED.
Outdated: crossbeam-queue — `crossbeam-queue` is locked at 0.3.13 but 0.3.14 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in vulkano/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-queue` and commit the updated REDACTED.
Outdated: indexmap — `indexmap` is locked at 2.14.0 but 2.14.2 is the current stable release on crates.io, and it already satisfies the `"2.0"` requirement declared in autogen/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: proc-macro2 — `proc-macro2` is locked at 1.0.106 but 1.0.107 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in autogen/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p proc-macro2` and commit the updated REDACTED.
Outdated: quote — `quote` is locked at 1.0.46 but 1.0.47 is the current stable release on crates.io, and it already satisfies the `"1.0.37"` requirement declared in autogen/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p quote` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in autogen/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.150 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in autogen/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: smallvec — `smallvec` is locked at 1.15.2 but 1.16.5 is the current stable release on crates.io, and it already satisfies the `"1.8"` requirement declared in vulkano-taskgraph/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: thread_local — `thread_local` is locked at 1.1.9 but 1.1.10 is the current stable release on crates.io, and it already satisfies the `"1.1"` requirement declared in vulkano-taskgraph/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p thread_local` 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 01a1db7a-aeb9-775a-a7b6-ddba3f650216 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 38 · Warnings: 1637 · Recommendations: 53 · Info: 9 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 19:13 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.