Public report of sisshiki1969/monoruby, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 05:09 UTC · Survey ID cd_f63ef733f1e04b82a66293e26d51b39d
sisshiki1969/monoruby
Measured 17 November 2026, 05:08 UTC, at code version dbd2df0
First survey, so nothing to compare with yet
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 487,106 lines of product code in 18 projects, tests not counted · Estimated rebuild effort: about 3.9 person-years · Weakest lens: Security and Compliance, 45.3
Findings by how serious they are
69 critical2441 serious44 minor
13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 05:08 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 ▸
58of 58 dimensions measured by tools.
2531of 2554 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
58dimensions across 8 lenses, read from 487,106 lines of product code in 18 projects.
sisshiki1969/monoruby falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 56.8 out of 100 and is rated Adequate, and 67 of its 69 critical findings are security problems.
Security and Compliance, at 45.3, is the weakest lens and counts most in the score. The best first step is replacing the weak hashes, worth about 5.5 points. Adding a diagnostic log comes next, worth about 5.2 points. Raising Security and Compliance to 70 would lift the score to about 64.2.
Fifty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Ten pipeline steps install packages that can change without warning, and two known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, pinning what the pipeline installs and updating the vulnerable packages would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first. The piece of product code that depends on test code needs its reference to the test project removed.
The product code is 487,106 lines, about €570,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 45.3 to 70, the lowest score rated Strong, the score would rise from 56.8 to about 64.2.
Code composition: what the lines of code are
Product code 88%Tests 12%
Rebuild cost: about €570,000 · Estimate
Cost to rebuild
€190,000 to €950,000, for 3,137 to 9,953 hours of work, about 3.9 person-years for 2 to 8 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.8 at a score of 57. 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: 487,106 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
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `ext/digest/src/lib.rs:60` (`Md5::digest`), `ext/digest/src/lib.rs:61` (`Sha1::digest`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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 5.2 points · Medium effort · Observability
3
Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 49 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €570,000 to build again, about 3.9 person-years of work. Its weakest lens is Security and Compliance, at 45.3 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. Of all the actions in this report, it raises the score most for the work it takes: about 5.5 points for medium effort. 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 5% to 10% on every change. The history of the code shows how much it changes: about 494,488 lines over the last 90 days, which is about 2,005,424 lines a year. At that pace, the extra work comes to an estimated 226.3 to 1358.1 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.
375 modules, with 1489 dependencies between them. 6 loops run through 97 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 335 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.
monoruby.value.rvalue.module uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.value.rvalue.module, while a change to monoruby.value.rvalue.module can't break monoruby.globals.store.class.
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→35 monoruby.value.rvalue.module uses monoruby.valuepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.module uses a type in monoruby.value.
monoruby.value.rvalue.module uses monoruby.value, so a change to monoruby.value can break monoruby.value.rvalue.module, while a change to monoruby.value.rvalue.module can't break monoruby.value.
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→36 monoruby.value.rvalue.module uses monoruby.allocpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.module uses a type in monoruby.alloc.
monoruby.value.rvalue.module uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.value.rvalue.module, while a change to monoruby.value.rvalue.module can't break monoruby.alloc.
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 monoruby.value.rvalue.proc uses monoruby.globals.store.functionpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.proc uses a type in monoruby.globals.store.function.
monoruby.value.rvalue.proc uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.value.rvalue.proc, while a change to monoruby.value.rvalue.proc can't break monoruby.globals.store.function.
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 monoruby.value.rvalue.proc uses monoruby.executor.framepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.proc uses a type in monoruby.executor.frame.
monoruby.value.rvalue.proc uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.value.rvalue.proc, while a change to monoruby.value.rvalue.proc can't break monoruby.executor.frame.
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→33 monoruby.value.rvalue.proc uses monoruby.bytecodepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.proc uses a type in monoruby.bytecode.
monoruby.value.rvalue.proc uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.value.rvalue.proc, while a change to monoruby.value.rvalue.proc can't break monoruby.bytecode.
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→35 monoruby.value.rvalue.proc uses monoruby.valuepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.proc uses a type in monoruby.value.
monoruby.value.rvalue.proc uses monoruby.value, so a change to monoruby.value can break monoruby.value.rvalue.proc, while a change to monoruby.value.rvalue.proc can't break monoruby.value.
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→36 monoruby.value.rvalue.proc uses monoruby.allocpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.proc uses a type in monoruby.alloc.
monoruby.value.rvalue.proc uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.value.rvalue.proc, while a change to monoruby.value.rvalue.proc can't break monoruby.alloc.
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 pairs of types, where a type in monoruby.globals.error uses a type in (global).
The types involved
monoruby.globals.error.MonorubyErr → String
monoruby.globals.error.error$module → String
Direction
monoruby.globals.error uses (global), so a change to (global) can break monoruby.globals.error, while a change to monoruby.globals.error can't break (global).
Position
Below the diagonal: monoruby.globals.error uses a module listed above it, which is the healthy direction.
monoruby.globals.error uses monoruby_ext, so a change to monoruby_ext can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby_ext.
Position
Below the diagonal: monoruby.globals.error uses a module listed above it, which is the healthy direction.
8→11 monoruby.globals.error uses monoruby.value.rvalue.stringpart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.error uses a type in monoruby.value.rvalue.string.
monoruby.globals.error uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.value.rvalue.string.
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→12 monoruby.globals.error uses monoruby.id_tablepart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.error uses a type in monoruby.id_table.
monoruby.globals.error uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.id_table.
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→17 monoruby.globals.error uses monoruby.globals.storepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.globals.error uses a type in monoruby.globals.store.
monoruby.globals.error uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.globals.store.
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 monoruby.globals.error uses monoruby.globals.store.functionpart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.error uses a type in monoruby.globals.store.function.
monoruby.globals.error uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.globals.store.function.
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 monoruby.globals.error uses monoruby.executor.framepart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.error uses a type in monoruby.executor.frame.
monoruby.globals.error uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.executor.frame.
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 monoruby.globals.error uses monoruby.executorpart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.error uses a type in monoruby.executor.
monoruby.globals.error uses monoruby.executor, so a change to monoruby.executor can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.executor.
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→32 monoruby.globals.error uses monoruby.globals.store.classpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.globals.error uses a type in monoruby.globals.store.class.
monoruby.globals.error uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.globals.store.class.
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→35 monoruby.globals.error uses monoruby.valuepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.globals.error uses a type in monoruby.value.
monoruby.globals.error uses monoruby.value, so a change to monoruby.value can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.value.
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→36 monoruby.globals.error uses monoruby.allocpart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.error uses a type in monoruby.alloc.
monoruby.globals.error uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.globals.error, while a change to monoruby.globals.error can't break monoruby.alloc.
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 pairs of types, where a type in monoruby.value.rvalue.array uses a type in (global).
The types involved
monoruby.value.rvalue.array.ArrayInner → Range
monoruby.value.rvalue.array.ArrayInner → String
Direction
monoruby.value.rvalue.array uses (global), so a change to (global) can break monoruby.value.rvalue.array, while a change to monoruby.value.rvalue.array can't break (global).
Position
Below the diagonal: monoruby.value.rvalue.array uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.array uses hashbrown.map, so a change to hashbrown.map can break monoruby.value.rvalue.array, while a change to monoruby.value.rvalue.array can't break hashbrown.map.
Position
Below the diagonal: monoruby.value.rvalue.array uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.array uses hashbrown.set, so a change to hashbrown.set can break monoruby.value.rvalue.array, while a change to monoruby.value.rvalue.array can't break hashbrown.set.
Position
Below the diagonal: monoruby.value.rvalue.array uses a module listed above it, which is the healthy direction.
9→17 monoruby.value.rvalue.array uses monoruby.globals.storepart of a loop✕
Connections
1 pair of types, where a type in monoruby.value.rvalue.array uses a type in monoruby.globals.store.
monoruby.value.rvalue.array uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.value.rvalue.array, while a change to monoruby.value.rvalue.array can't break monoruby.globals.store.
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→27 monoruby.value.rvalue.array uses monoruby.executorpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.array uses a type in monoruby.executor.
monoruby.value.rvalue.array uses monoruby.executor, so a change to monoruby.executor can break monoruby.value.rvalue.array, while a change to monoruby.value.rvalue.array can't break monoruby.executor.
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→31 monoruby.value.rvalue.array uses monoruby.globalspart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.array uses a type in monoruby.globals.
monoruby.value.rvalue.array uses monoruby.globals, so a change to monoruby.globals can break monoruby.value.rvalue.array, while a change to monoruby.value.rvalue.array can't break monoruby.globals.
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→35 monoruby.value.rvalue.array uses monoruby.valuepart of a loop✕
Connections
4 pairs of types, where a type in monoruby.value.rvalue.array uses a type in monoruby.value.
monoruby.value.rvalue.array uses monoruby.value, so a change to monoruby.value can break monoruby.value.rvalue.array, while a change to monoruby.value.rvalue.array can't break monoruby.value.
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 monoruby.value.rvalue.range uses a type in (global).
The types involved
monoruby.value.rvalue.range.RangeInner → String
Direction
monoruby.value.rvalue.range uses (global), so a change to (global) can break monoruby.value.rvalue.range, while a change to monoruby.value.rvalue.range can't break (global).
Position
Below the diagonal: monoruby.value.rvalue.range uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.range uses hashbrown.set, so a change to hashbrown.set can break monoruby.value.rvalue.range, while a change to monoruby.value.rvalue.range can't break hashbrown.set.
Position
Below the diagonal: monoruby.value.rvalue.range uses a module listed above it, which is the healthy direction.
10→17 monoruby.value.rvalue.range uses monoruby.globals.storepart of a loop✕
Connections
1 pair of types, where a type in monoruby.value.rvalue.range uses a type in monoruby.globals.store.
monoruby.value.rvalue.range uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.value.rvalue.range, while a change to monoruby.value.rvalue.range can't break monoruby.globals.store.
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 monoruby.value.rvalue.range uses monoruby.executorpart of a loop✕
Connections
1 pair of types, where a type in monoruby.value.rvalue.range uses a type in monoruby.executor.
monoruby.value.rvalue.range uses monoruby.executor, so a change to monoruby.executor can break monoruby.value.rvalue.range, while a change to monoruby.value.rvalue.range can't break monoruby.executor.
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→31 monoruby.value.rvalue.range uses monoruby.globalspart of a loop✕
Connections
1 pair of types, where a type in monoruby.value.rvalue.range uses a type in monoruby.globals.
monoruby.value.rvalue.range uses monoruby.globals, so a change to monoruby.globals can break monoruby.value.rvalue.range, while a change to monoruby.value.rvalue.range can't break monoruby.globals.
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→35 monoruby.value.rvalue.range uses monoruby.valuepart of a loop✕
Connections
1 pair of types, where a type in monoruby.value.rvalue.range uses a type in monoruby.value.
monoruby.value.rvalue.range uses monoruby.value, so a change to monoruby.value can break monoruby.value.rvalue.range, while a change to monoruby.value.rvalue.range can't break monoruby.value.
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→36 monoruby.value.rvalue.range uses monoruby.allocpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.range uses a type in monoruby.alloc.
monoruby.value.rvalue.range uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.value.rvalue.range, while a change to monoruby.value.rvalue.range can't break monoruby.alloc.
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.
monoruby.value.rvalue.string uses (global), so a change to (global) can break monoruby.value.rvalue.string, while a change to monoruby.value.rvalue.string can't break (global).
Position
Below the diagonal: monoruby.value.rvalue.string uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.string uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.value.rvalue.string, while a change to monoruby.value.rvalue.string can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.value.rvalue.string uses a module listed above it, which is the healthy direction.
11→17 monoruby.value.rvalue.string uses monoruby.globals.storepart of a loop✕
Connections
3 pairs of types, where a type in monoruby.value.rvalue.string uses a type in monoruby.globals.store.
monoruby.value.rvalue.string uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.value.rvalue.string, while a change to monoruby.value.rvalue.string can't break monoruby.globals.store.
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→35 monoruby.value.rvalue.string uses monoruby.valuepart of a loop✕
Connections
4 pairs of types, where a type in monoruby.value.rvalue.string uses a type in monoruby.value.
monoruby.value.rvalue.string uses monoruby.value, so a change to monoruby.value can break monoruby.value.rvalue.string, while a change to monoruby.value.rvalue.string can't break monoruby.value.
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.
monoruby.id_table uses hashbrown.map, so a change to hashbrown.map can break monoruby.id_table, while a change to monoruby.id_table can't break hashbrown.map.
Position
Below the diagonal: monoruby.id_table uses a module listed above it, which is the healthy direction.
monoruby.id_table uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.id_table, while a change to monoruby.id_table can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.id_table uses a module listed above it, which is the healthy direction.
monoruby.id_table uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.id_table, while a change to monoruby.id_table can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.id_table uses a module listed above it, which is the healthy direction.
12→28 monoruby.id_table uses monoruby.bytecodegenpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.id_table uses a type in monoruby.bytecodegen.
monoruby.id_table uses monoruby.bytecodegen, so a change to monoruby.bytecodegen can break monoruby.id_table, while a change to monoruby.id_table can't break monoruby.bytecodegen.
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 pairs of types, where a type in monoruby.value.rvalue.hash uses a type in (global).
The types involved
monoruby.value.rvalue.hash.HashRef → String
monoruby.value.rvalue.hash.Hashmap → String
Direction
monoruby.value.rvalue.hash uses (global), so a change to (global) can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break (global).
Position
Below the diagonal: monoruby.value.rvalue.hash uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.hash uses hashbrown.set, so a change to hashbrown.set can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break hashbrown.set.
Position
Below the diagonal: monoruby.value.rvalue.hash uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.hash uses monoruby.value.rvalue.proc, so a change to monoruby.value.rvalue.proc can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break monoruby.value.rvalue.proc.
Position
Below the diagonal: monoruby.value.rvalue.hash uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.hash uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.value.rvalue.hash uses a module listed above it, which is the healthy direction.
13→16 monoruby.value.rvalue.hash uses monoruby.value.rvaluepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.hash uses a type in monoruby.value.rvalue.
monoruby.value.rvalue.hash uses monoruby.value.rvalue, so a change to monoruby.value.rvalue can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break monoruby.value.rvalue.
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→17 monoruby.value.rvalue.hash uses monoruby.globals.storepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.hash uses a type in monoruby.globals.store.
monoruby.value.rvalue.hash uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break monoruby.globals.store.
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 monoruby.value.rvalue.hash uses monoruby.executorpart of a loop✕
Connections
5 pairs of types, where a type in monoruby.value.rvalue.hash uses a type in monoruby.executor.
monoruby.value.rvalue.hash uses monoruby.executor, so a change to monoruby.executor can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break monoruby.executor.
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→31 monoruby.value.rvalue.hash uses monoruby.globalspart of a loop✕
Connections
5 pairs of types, where a type in monoruby.value.rvalue.hash uses a type in monoruby.globals.
monoruby.value.rvalue.hash uses monoruby.globals, so a change to monoruby.globals can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break monoruby.globals.
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→35 monoruby.value.rvalue.hash uses monoruby.valuepart of a loop✕
Connections
6 pairs of types, where a type in monoruby.value.rvalue.hash uses a type in monoruby.value.
monoruby.value.rvalue.hash uses monoruby.value, so a change to monoruby.value can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break monoruby.value.
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→36 monoruby.value.rvalue.hash uses monoruby.allocpart of a loop✕
Connections
4 pairs of types, where a type in monoruby.value.rvalue.hash uses a type in monoruby.alloc.
monoruby.value.rvalue.hash uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.value.rvalue.hash, while a change to monoruby.value.rvalue.hash can't break monoruby.alloc.
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.
monoruby.value.rvalue.regexp uses (global), so a change to (global) can break monoruby.value.rvalue.regexp, while a change to monoruby.value.rvalue.regexp can't break (global).
Position
Below the diagonal: monoruby.value.rvalue.regexp uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.regexp uses hashbrown.map, so a change to hashbrown.map can break monoruby.value.rvalue.regexp, while a change to monoruby.value.rvalue.regexp can't break hashbrown.map.
Position
Below the diagonal: monoruby.value.rvalue.regexp uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.regexp uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.value.rvalue.regexp, while a change to monoruby.value.rvalue.regexp can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.value.rvalue.regexp uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue.regexp uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.value.rvalue.regexp, while a change to monoruby.value.rvalue.regexp can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.value.rvalue.regexp uses a module listed above it, which is the healthy direction.
14→17 monoruby.value.rvalue.regexp uses monoruby.globals.storepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.regexp uses a type in monoruby.globals.store.
monoruby.value.rvalue.regexp uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.value.rvalue.regexp, while a change to monoruby.value.rvalue.regexp can't break monoruby.globals.store.
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→27 monoruby.value.rvalue.regexp uses monoruby.executorpart of a loop✕
Connections
5 pairs of types, where a type in monoruby.value.rvalue.regexp uses a type in monoruby.executor.
monoruby.value.rvalue.regexp uses monoruby.executor, so a change to monoruby.executor can break monoruby.value.rvalue.regexp, while a change to monoruby.value.rvalue.regexp can't break monoruby.executor.
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→31 monoruby.value.rvalue.regexp uses monoruby.globalspart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue.regexp uses a type in monoruby.globals.
monoruby.value.rvalue.regexp uses monoruby.globals, so a change to monoruby.globals can break monoruby.value.rvalue.regexp, while a change to monoruby.value.rvalue.regexp can't break monoruby.globals.
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→35 monoruby.value.rvalue.regexp uses monoruby.valuepart of a loop✕
Connections
4 pairs of types, where a type in monoruby.value.rvalue.regexp uses a type in monoruby.value.
monoruby.value.rvalue.regexp uses monoruby.value, so a change to monoruby.value can break monoruby.value.rvalue.regexp, while a change to monoruby.value.rvalue.regexp can't break monoruby.value.
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 pairs of types, where a type in monoruby.globals.store.iseq uses a type in (global).
The types involved
monoruby.globals.store.iseq.ExceptionMapEntry → Range
monoruby.globals.store.iseq.ISeqInfo → Range
monoruby.globals.store.iseq.ISeqInfo → String
Direction
monoruby.globals.store.iseq uses (global), so a change to (global) can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break (global).
Position
Below the diagonal: monoruby.globals.store.iseq uses a module listed above it, which is the healthy direction.
monoruby.globals.store.iseq uses hashbrown.map, so a change to hashbrown.map can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break hashbrown.map.
Position
Below the diagonal: monoruby.globals.store.iseq uses a module listed above it, which is the healthy direction.
monoruby.globals.store.iseq uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break monoruby.id_table.
Position
Below the diagonal: monoruby.globals.store.iseq uses a module listed above it, which is the healthy direction.
15→17 monoruby.globals.store.iseq uses monoruby.globals.storepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.globals.store.iseq uses a type in monoruby.globals.store.
monoruby.globals.store.iseq uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break monoruby.globals.store.
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→24 monoruby.globals.store.iseq uses monoruby.globals.store.functionpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.globals.store.iseq uses a type in monoruby.globals.store.function.
monoruby.globals.store.iseq uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break monoruby.globals.store.function.
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 monoruby.globals.store.iseq uses monoruby.executorpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals.store.iseq uses a type in monoruby.executor.
monoruby.globals.store.iseq uses monoruby.executor, so a change to monoruby.executor can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break monoruby.executor.
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→32 monoruby.globals.store.iseq uses monoruby.globals.store.classpart of a loop✕
Connections
4 pairs of types, where a type in monoruby.globals.store.iseq uses a type in monoruby.globals.store.class.
monoruby.globals.store.iseq uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break monoruby.globals.store.class.
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→33 monoruby.globals.store.iseq uses monoruby.bytecodepart of a loop✕
Connections
5 pairs of types, where a type in monoruby.globals.store.iseq uses a type in monoruby.bytecode.
monoruby.globals.store.iseq uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break monoruby.bytecode.
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→36 monoruby.globals.store.iseq uses monoruby.allocpart of a loop✕
Connections
4 pairs of types, where a type in monoruby.globals.store.iseq uses a type in monoruby.alloc.
monoruby.globals.store.iseq uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.globals.store.iseq, while a change to monoruby.globals.store.iseq can't break monoruby.alloc.
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 pairs of types, where a type in monoruby.value.rvalue uses a type in (global).
The types involved
monoruby.value.rvalue.RValue → Complex
monoruby.value.rvalue.RValue → File
monoruby.value.rvalue.RValue → String
Direction
monoruby.value.rvalue uses (global), so a change to (global) can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break (global).
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses hashbrown.set, so a change to hashbrown.set can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break hashbrown.set.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.value.rvalue.proc, so a change to monoruby.value.rvalue.proc can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.value.rvalue.proc.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.value.rvalue.array, so a change to monoruby.value.rvalue.array can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.value.rvalue.array.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.value.rvalue.range, so a change to monoruby.value.rvalue.range can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.value.rvalue.range.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.id_table.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.value.rvalue.hash, so a change to monoruby.value.rvalue.hash can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.value.rvalue.hash.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
monoruby.value.rvalue uses monoruby.value.rvalue.regexp, so a change to monoruby.value.rvalue.regexp can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.value.rvalue.regexp.
Position
Below the diagonal: monoruby.value.rvalue uses a module listed above it, which is the healthy direction.
16→17 monoruby.value.rvalue uses monoruby.globals.storepart of a loop✕
Connections
1 pair of types, where a type in monoruby.value.rvalue uses a type in monoruby.globals.store.
monoruby.value.rvalue uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.globals.store.
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 monoruby.value.rvalue uses monoruby.globals.store.functionpart of a loop✕
Connections
1 pair of types, where a type in monoruby.value.rvalue uses a type in monoruby.globals.store.function.
monoruby.value.rvalue uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.globals.store.function.
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 monoruby.value.rvalue uses monoruby.executor.framepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue uses a type in monoruby.executor.frame.
monoruby.value.rvalue uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.executor.frame.
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→32 monoruby.value.rvalue uses monoruby.globals.store.classpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue uses a type in monoruby.globals.store.class.
monoruby.value.rvalue uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.globals.store.class.
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→33 monoruby.value.rvalue uses monoruby.bytecodepart of a loop✕
Connections
1 pair of types, where a type in monoruby.value.rvalue uses a type in monoruby.bytecode.
monoruby.value.rvalue uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.bytecode.
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→35 monoruby.value.rvalue uses monoruby.valuepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value.rvalue uses a type in monoruby.value.
monoruby.value.rvalue uses monoruby.value, so a change to monoruby.value can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.value.
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→36 monoruby.value.rvalue uses monoruby.allocpart of a loop✕
Connections
6 pairs of types, where a type in monoruby.value.rvalue uses a type in monoruby.alloc.
monoruby.value.rvalue uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.value.rvalue, while a change to monoruby.value.rvalue can't break monoruby.alloc.
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 pairs of types, where a type in monoruby.globals.store uses a type in (global).
The types involved
monoruby.globals.store.CallSiteInfo → String
monoruby.globals.store.ClassInfoTable → String
monoruby.globals.store.ConstSiteInfo → String
monoruby.globals.store.Store → String
Direction
monoruby.globals.store uses (global), so a change to (global) can break monoruby.globals.store, while a change to monoruby.globals.store can't break (global).
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses hashbrown.map, so a change to hashbrown.map can break monoruby.globals.store, while a change to monoruby.globals.store can't break hashbrown.map.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses hashbrown.set, so a change to hashbrown.set can break monoruby.globals.store, while a change to monoruby.globals.store can't break hashbrown.set.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses monoruby.value.rvalue.proc, so a change to monoruby.value.rvalue.proc can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.value.rvalue.proc.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.id_table.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
monoruby.globals.store uses monoruby.value.rvalue, so a change to monoruby.value.rvalue can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.value.rvalue.
Position
Below the diagonal: monoruby.globals.store uses a module listed above it, which is the healthy direction.
17→23 monoruby.globals.store uses monoruby.codegen.jitgen.spec_memopart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.store uses a type in monoruby.codegen.jitgen.spec_memo.
monoruby.globals.store uses monoruby.codegen.jitgen.spec_memo, so a change to monoruby.codegen.jitgen.spec_memo can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.codegen.jitgen.spec_memo.
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→24 monoruby.globals.store uses monoruby.globals.store.functionpart of a loop✕
Connections
9 pairs of types, where a type in monoruby.globals.store uses a type in monoruby.globals.store.function.
monoruby.globals.store uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.globals.store.function.
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→25 monoruby.globals.store uses monoruby.executor.framepart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals.store uses a type in monoruby.executor.frame.
monoruby.globals.store uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.executor.frame.
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→27 monoruby.globals.store uses monoruby.executorpart of a loop✕
Connections
7 pairs of types, where a type in monoruby.globals.store uses a type in monoruby.executor.
monoruby.globals.store uses monoruby.executor, so a change to monoruby.executor can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.executor.
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→28 monoruby.globals.store uses monoruby.bytecodegenpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals.store uses a type in monoruby.bytecodegen.
monoruby.globals.store uses monoruby.bytecodegen, so a change to monoruby.bytecodegen can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.bytecodegen.
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→31 monoruby.globals.store uses monoruby.globalspart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.store uses a type in monoruby.globals.
monoruby.globals.store uses monoruby.globals, so a change to monoruby.globals can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.globals.
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→32 monoruby.globals.store uses monoruby.globals.store.classpart of a loop✕
Connections
10 pairs of types, where a type in monoruby.globals.store uses a type in monoruby.globals.store.class.
monoruby.globals.store uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.globals.store.class.
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 monoruby.globals.store uses monoruby.bytecodepart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals.store uses a type in monoruby.bytecode.
monoruby.globals.store uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.bytecode.
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→35 monoruby.globals.store uses monoruby.valuepart of a loop✕
Connections
4 pairs of types, where a type in monoruby.globals.store uses a type in monoruby.value.
monoruby.globals.store uses monoruby.value, so a change to monoruby.value can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.value.
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→36 monoruby.globals.store uses monoruby.allocpart of a loop✕
Connections
6 pairs of types, where a type in monoruby.globals.store uses a type in monoruby.alloc.
monoruby.globals.store uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.globals.store, while a change to monoruby.globals.store can't break monoruby.alloc.
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 monoruby.codegen.jitgen.state.slot uses a type in (global).
The types involved
monoruby.codegen.jitgen.state.slot.SlotState → Range
Direction
monoruby.codegen.jitgen.state.slot uses (global), so a change to (global) can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break (global).
Position
Below the diagonal: monoruby.codegen.jitgen.state.slot uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.state.slot uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.codegen.jitgen.state.slot uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.state.slot uses monoruby.value.rvalue.range, so a change to monoruby.value.rvalue.range can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.value.rvalue.range.
Position
Below the diagonal: monoruby.codegen.jitgen.state.slot uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.state.slot uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.id_table.
Position
Below the diagonal: monoruby.codegen.jitgen.state.slot uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.state.slot uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.codegen.jitgen.state.slot uses a module listed above it, which is the healthy direction.
18→19 monoruby.codegen.jitgen.state.slot uses monoruby.codegen.jitgen.statepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.codegen.jitgen.state.
monoruby.codegen.jitgen.state.slot uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.codegen.jitgen.state.
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→20 monoruby.codegen.jitgen.state.slot uses monoruby.codegen.jitgen.contextpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.codegen.jitgen.context.
monoruby.codegen.jitgen.state.slot uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.codegen.jitgen.context.
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→21 monoruby.codegen.jitgen.state.slot uses monoruby.codegenpart of a loop✕
Connections
4 pairs of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.codegen.
monoruby.codegen.jitgen.state.slot uses monoruby.codegen, so a change to monoruby.codegen can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.codegen.
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→22 monoruby.codegen.jitgen.state.slot uses monoruby.codegen.jitgenpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.codegen.jitgen.
monoruby.codegen.jitgen.state.slot uses monoruby.codegen.jitgen, so a change to monoruby.codegen.jitgen can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.codegen.jitgen.
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 monoruby.codegen.jitgen.state.slot uses monoruby.globals.store.functionpart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.globals.store.function.
monoruby.codegen.jitgen.state.slot uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.globals.store.function.
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 monoruby.codegen.jitgen.state.slot uses monoruby.executorpart of a loop✕
Connections
4 pairs of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.executor.
monoruby.codegen.jitgen.state.slot uses monoruby.executor, so a change to monoruby.executor can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.executor.
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→30 monoruby.codegen.jitgen.state.slot uses monoruby.codegen.jitgen.asmirpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.codegen.jitgen.asmir.
monoruby.codegen.jitgen.state.slot uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.codegen.jitgen.asmir.
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 monoruby.codegen.jitgen.state.slot uses monoruby.globals.store.classpart of a loop✕
Connections
5 pairs of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.globals.store.class.
monoruby.codegen.jitgen.state.slot uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.globals.store.class.
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→35 monoruby.codegen.jitgen.state.slot uses monoruby.valuepart of a loop✕
Connections
5 pairs of types, where a type in monoruby.codegen.jitgen.state.slot uses a type in monoruby.value.
monoruby.codegen.jitgen.state.slot uses monoruby.value, so a change to monoruby.value can break monoruby.codegen.jitgen.state.slot, while a change to monoruby.codegen.jitgen.state.slot can't break monoruby.value.
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.
monoruby.codegen.jitgen.state uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.codegen.jitgen.state uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.state uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.id_table.
Position
Below the diagonal: monoruby.codegen.jitgen.state uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.state uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.codegen.jitgen.state uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.state uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.codegen.jitgen.state uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.state uses monoruby.codegen.jitgen.state.slot, so a change to monoruby.codegen.jitgen.state.slot can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.codegen.jitgen.state.slot.
Position
Below the diagonal: monoruby.codegen.jitgen.state uses a module listed above it, which is the healthy direction.
19→20 monoruby.codegen.jitgen.state uses monoruby.codegen.jitgen.contextpart of a loop✕
Connections
5 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.codegen.jitgen.context.
monoruby.codegen.jitgen.state uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.codegen.jitgen.context.
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→21 monoruby.codegen.jitgen.state uses monoruby.codegenpart of a loop✕
Connections
5 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.codegen.
monoruby.codegen.jitgen.state uses monoruby.codegen, so a change to monoruby.codegen can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.codegen.
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→22 monoruby.codegen.jitgen.state uses monoruby.codegen.jitgenpart of a loop✕
Connections
8 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.codegen.jitgen.
monoruby.codegen.jitgen.state uses monoruby.codegen.jitgen, so a change to monoruby.codegen.jitgen can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.codegen.jitgen.
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→24 monoruby.codegen.jitgen.state uses monoruby.globals.store.functionpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.globals.store.function.
monoruby.codegen.jitgen.state uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.globals.store.function.
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→25 monoruby.codegen.jitgen.state uses monoruby.executor.framepart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.executor.frame.
monoruby.codegen.jitgen.state uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.executor.frame.
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→27 monoruby.codegen.jitgen.state uses monoruby.executorpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.executor.
monoruby.codegen.jitgen.state uses monoruby.executor, so a change to monoruby.executor can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.executor.
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→28 monoruby.codegen.jitgen.state uses monoruby.bytecodegenpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.bytecodegen.
monoruby.codegen.jitgen.state uses monoruby.bytecodegen, so a change to monoruby.bytecodegen can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.bytecodegen.
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→30 monoruby.codegen.jitgen.state uses monoruby.codegen.jitgen.asmirpart of a loop✕
Connections
7 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.codegen.jitgen.asmir.
monoruby.codegen.jitgen.state uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.codegen.jitgen.asmir.
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 monoruby.codegen.jitgen.state uses monoruby.globals.store.classpart of a loop✕
Connections
4 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.globals.store.class.
monoruby.codegen.jitgen.state uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.globals.store.class.
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 monoruby.codegen.jitgen.state uses monoruby.bytecodepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.bytecode.
monoruby.codegen.jitgen.state uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.bytecode.
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→35 monoruby.codegen.jitgen.state uses monoruby.valuepart of a loop✕
Connections
3 pairs of types, where a type in monoruby.codegen.jitgen.state uses a type in monoruby.value.
monoruby.codegen.jitgen.state uses monoruby.value, so a change to monoruby.value can break monoruby.codegen.jitgen.state, while a change to monoruby.codegen.jitgen.state can't break monoruby.value.
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 monoruby.codegen.jitgen.context uses a type in (global).
The types involved
monoruby.codegen.jitgen.context.JitContext → Range
Direction
monoruby.codegen.jitgen.context uses (global), so a change to (global) can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break (global).
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses hashbrown.map, so a change to hashbrown.map can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break hashbrown.map.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses hashbrown.set, so a change to hashbrown.set can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break hashbrown.set.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.id_table.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses monoruby.value.rvalue, so a change to monoruby.value.rvalue can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.value.rvalue.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses monoruby.codegen.jitgen.state.slot, so a change to monoruby.codegen.jitgen.state.slot can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.codegen.jitgen.state.slot.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.context uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.codegen.jitgen.context uses a module listed above it, which is the healthy direction.
20→21 monoruby.codegen.jitgen.context uses monoruby.codegenpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.codegen.
monoruby.codegen.jitgen.context uses monoruby.codegen, so a change to monoruby.codegen can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.codegen.
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→22 monoruby.codegen.jitgen.context uses monoruby.codegen.jitgenpart of a loop✕
Connections
16 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.codegen.jitgen.
monoruby.codegen.jitgen.context uses monoruby.codegen.jitgen, so a change to monoruby.codegen.jitgen can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.codegen.jitgen.
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 monoruby.codegen.jitgen.context uses monoruby.codegen.jitgen.spec_memopart of a loop✕
Connections
8 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.codegen.jitgen.spec_memo.
monoruby.codegen.jitgen.context uses monoruby.codegen.jitgen.spec_memo, so a change to monoruby.codegen.jitgen.spec_memo can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.codegen.jitgen.spec_memo.
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 monoruby.codegen.jitgen.context uses monoruby.globals.store.functionpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.globals.store.function.
monoruby.codegen.jitgen.context uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.globals.store.function.
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 monoruby.codegen.jitgen.context uses monoruby.executor.framepart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.executor.frame.
monoruby.codegen.jitgen.context uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.executor.frame.
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 monoruby.codegen.jitgen.context uses monoruby.executorpart of a loop✕
Connections
8 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.executor.
monoruby.codegen.jitgen.context uses monoruby.executor, so a change to monoruby.executor can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.executor.
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→28 monoruby.codegen.jitgen.context uses monoruby.bytecodegenpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.bytecodegen.
monoruby.codegen.jitgen.context uses monoruby.bytecodegen, so a change to monoruby.bytecodegen can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.bytecodegen.
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→30 monoruby.codegen.jitgen.context uses monoruby.codegen.jitgen.asmirpart of a loop✕
Connections
10 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.codegen.jitgen.asmir.
monoruby.codegen.jitgen.context uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.codegen.jitgen.asmir.
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→32 monoruby.codegen.jitgen.context uses monoruby.globals.store.classpart of a loop✕
Connections
5 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.globals.store.class.
monoruby.codegen.jitgen.context uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.globals.store.class.
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→33 monoruby.codegen.jitgen.context uses monoruby.bytecodepart of a loop✕
Connections
3 pairs of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.bytecode.
monoruby.codegen.jitgen.context uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.bytecode.
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→35 monoruby.codegen.jitgen.context uses monoruby.valuepart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.jitgen.context uses a type in monoruby.value.
monoruby.codegen.jitgen.context uses monoruby.value, so a change to monoruby.value can break monoruby.codegen.jitgen.context, while a change to monoruby.codegen.jitgen.context can't break monoruby.value.
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.
monoruby.codegen uses hashbrown.map, so a change to hashbrown.map can break monoruby.codegen, while a change to monoruby.codegen can't break hashbrown.map.
Position
Below the diagonal: monoruby.codegen uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in monoruby.codegen uses a type in hashbrown.set.
The types involved
monoruby.codegen.Codegen → hashbrown.set.HashSet
Direction
monoruby.codegen uses hashbrown.set, so a change to hashbrown.set can break monoruby.codegen, while a change to monoruby.codegen can't break hashbrown.set.
Position
Below the diagonal: monoruby.codegen uses a module listed above it, which is the healthy direction.
monoruby.codegen uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.codegen uses a module listed above it, which is the healthy direction.
monoruby.codegen uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.id_table.
Position
Below the diagonal: monoruby.codegen uses a module listed above it, which is the healthy direction.
monoruby.codegen uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.codegen uses a module listed above it, which is the healthy direction.
monoruby.codegen uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.codegen uses a module listed above it, which is the healthy direction.
monoruby.codegen uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.codegen uses a module listed above it, which is the healthy direction.
21→22 monoruby.codegen uses monoruby.codegen.jitgenpart of a loop✕
Connections
16 pairs of types, where a type in monoruby.codegen uses a type in monoruby.codegen.jitgen.
monoruby.codegen uses monoruby.codegen.jitgen, so a change to monoruby.codegen.jitgen can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.codegen.jitgen.
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 monoruby.codegen uses monoruby.globals.store.functionpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.codegen uses a type in monoruby.globals.store.function.
monoruby.codegen uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.globals.store.function.
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 monoruby.codegen uses monoruby.executor.framepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen uses a type in monoruby.executor.frame.
monoruby.codegen uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.executor.frame.
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 monoruby.codegen uses monoruby.executorpart of a loop✕
Connections
4 pairs of types, where a type in monoruby.codegen uses a type in monoruby.executor.
monoruby.codegen uses monoruby.executor, so a change to monoruby.executor can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.executor.
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→28 monoruby.codegen uses monoruby.bytecodegenpart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen uses a type in monoruby.bytecodegen.
monoruby.codegen uses monoruby.bytecodegen, so a change to monoruby.bytecodegen can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.bytecodegen.
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→30 monoruby.codegen uses monoruby.codegen.jitgen.asmirpart of a loop✕
Connections
13 pairs of types, where a type in monoruby.codegen uses a type in monoruby.codegen.jitgen.asmir.
monoruby.codegen uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.codegen.jitgen.asmir.
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→31 monoruby.codegen uses monoruby.globalspart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen uses a type in monoruby.globals.
monoruby.codegen uses monoruby.globals, so a change to monoruby.globals can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.globals.
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→32 monoruby.codegen uses monoruby.globals.store.classpart of a loop✕
Connections
4 pairs of types, where a type in monoruby.codegen uses a type in monoruby.globals.store.class.
monoruby.codegen uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.globals.store.class.
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→33 monoruby.codegen uses monoruby.bytecodepart of a loop✕
Connections
4 pairs of types, where a type in monoruby.codegen uses a type in monoruby.bytecode.
monoruby.codegen uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.bytecode.
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→35 monoruby.codegen uses monoruby.valuepart of a loop✕
Connections
3 pairs of types, where a type in monoruby.codegen uses a type in monoruby.value.
monoruby.codegen uses monoruby.value, so a change to monoruby.value can break monoruby.codegen, while a change to monoruby.codegen can't break monoruby.value.
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.
monoruby.codegen.jitgen uses (global), so a change to (global) can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break (global).
Position
Below the diagonal: monoruby.codegen.jitgen uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.codegen.jitgen uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.codegen.jitgen uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.codegen.jitgen uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.codegen.jitgen uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen uses monoruby.codegen, so a change to monoruby.codegen can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.codegen.
Position
Below the diagonal: monoruby.codegen.jitgen uses a module listed above it, which is the healthy direction.
22→27 monoruby.codegen.jitgen uses monoruby.executorpart of a loop✕
Connections
6 pairs of types, where a type in monoruby.codegen.jitgen uses a type in monoruby.executor.
monoruby.codegen.jitgen uses monoruby.executor, so a change to monoruby.executor can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.executor.
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→30 monoruby.codegen.jitgen uses monoruby.codegen.jitgen.asmirpart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.jitgen uses a type in monoruby.codegen.jitgen.asmir.
monoruby.codegen.jitgen uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.codegen.jitgen.asmir.
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→32 monoruby.codegen.jitgen uses monoruby.globals.store.classpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen uses a type in monoruby.globals.store.class.
monoruby.codegen.jitgen uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.globals.store.class.
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→33 monoruby.codegen.jitgen uses monoruby.bytecodepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen uses a type in monoruby.bytecode.
monoruby.codegen.jitgen uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.codegen.jitgen, while a change to monoruby.codegen.jitgen can't break monoruby.bytecode.
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.
monoruby.codegen.jitgen.spec_memo uses hashbrown.map, so a change to hashbrown.map can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break hashbrown.map.
Position
Below the diagonal: monoruby.codegen.jitgen.spec_memo uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.spec_memo uses hashbrown.set, so a change to hashbrown.set can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break hashbrown.set.
Position
Below the diagonal: monoruby.codegen.jitgen.spec_memo uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.spec_memo uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.codegen.jitgen.spec_memo uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.spec_memo uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.codegen.jitgen.spec_memo uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.spec_memo uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.codegen.jitgen.spec_memo uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.spec_memo uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.codegen.jitgen.spec_memo uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.spec_memo uses monoruby.codegen.jitgen, so a change to monoruby.codegen.jitgen can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break monoruby.codegen.jitgen.
Position
Below the diagonal: monoruby.codegen.jitgen.spec_memo uses a module listed above it, which is the healthy direction.
23→27 monoruby.codegen.jitgen.spec_memo uses monoruby.executorpart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.jitgen.spec_memo uses a type in monoruby.executor.
monoruby.codegen.jitgen.spec_memo uses monoruby.executor, so a change to monoruby.executor can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break monoruby.executor.
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→32 monoruby.codegen.jitgen.spec_memo uses monoruby.globals.store.classpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.spec_memo uses a type in monoruby.globals.store.class.
monoruby.codegen.jitgen.spec_memo uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.codegen.jitgen.spec_memo, while a change to monoruby.codegen.jitgen.spec_memo can't break monoruby.globals.store.class.
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 pairs of types, where a type in monoruby.globals.store.function uses a type in (global).
The types involved
monoruby.globals.store.function.FuncInfo → String
monoruby.globals.store.function.Funcs → String
monoruby.globals.store.function.Meta → Range
Direction
monoruby.globals.store.function uses (global), so a change to (global) can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break (global).
Position
Below the diagonal: monoruby.globals.store.function uses a module listed above it, which is the healthy direction.
monoruby.globals.store.function uses monoruby.value.rvalue.proc, so a change to monoruby.value.rvalue.proc can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.value.rvalue.proc.
Position
Below the diagonal: monoruby.globals.store.function uses a module listed above it, which is the healthy direction.
monoruby.globals.store.function uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.id_table.
Position
Below the diagonal: monoruby.globals.store.function uses a module listed above it, which is the healthy direction.
monoruby.globals.store.function uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.globals.store.function uses a module listed above it, which is the healthy direction.
monoruby.globals.store.function uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.globals.store.function uses a module listed above it, which is the healthy direction.
monoruby.globals.store.function uses monoruby.codegen.jitgen.spec_memo, so a change to monoruby.codegen.jitgen.spec_memo can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.codegen.jitgen.spec_memo.
Position
Below the diagonal: monoruby.globals.store.function uses a module listed above it, which is the healthy direction.
24→25 monoruby.globals.store.function uses monoruby.executor.framepart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.store.function uses a type in monoruby.executor.frame.
monoruby.globals.store.function uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.executor.frame.
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.
24→27 monoruby.globals.store.function uses monoruby.executorpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals.store.function uses a type in monoruby.executor.
monoruby.globals.store.function uses monoruby.executor, so a change to monoruby.executor can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.executor.
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.
24→31 monoruby.globals.store.function uses monoruby.globalspart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.store.function uses a type in monoruby.globals.
monoruby.globals.store.function uses monoruby.globals, so a change to monoruby.globals can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.globals.
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.
24→32 monoruby.globals.store.function uses monoruby.globals.store.classpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals.store.function uses a type in monoruby.globals.store.class.
monoruby.globals.store.function uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.globals.store.class.
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.
24→33 monoruby.globals.store.function uses monoruby.bytecodepart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals.store.function uses a type in monoruby.bytecode.
monoruby.globals.store.function uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.bytecode.
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.
24→35 monoruby.globals.store.function uses monoruby.valuepart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals.store.function uses a type in monoruby.value.
monoruby.globals.store.function uses monoruby.value, so a change to monoruby.value can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.value.
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.
24→36 monoruby.globals.store.function uses monoruby.allocpart of a loop✕
Connections
6 pairs of types, where a type in monoruby.globals.store.function uses a type in monoruby.alloc.
monoruby.globals.store.function uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.globals.store.function, while a change to monoruby.globals.store.function can't break monoruby.alloc.
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.
monoruby.executor.frame uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.executor.frame, while a change to monoruby.executor.frame can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.executor.frame uses a module listed above it, which is the healthy direction.
25→27 monoruby.executor.frame uses monoruby.executorpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.executor.frame uses a type in monoruby.executor.
monoruby.executor.frame uses monoruby.executor, so a change to monoruby.executor can break monoruby.executor.frame, while a change to monoruby.executor.frame can't break monoruby.executor.
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→35 monoruby.executor.frame uses monoruby.valuepart of a loop✕
Connections
1 pair of types, where a type in monoruby.executor.frame uses a type in monoruby.value.
monoruby.executor.frame uses monoruby.value, so a change to monoruby.value can break monoruby.executor.frame, while a change to monoruby.executor.frame can't break monoruby.value.
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→36 monoruby.executor.frame uses monoruby.allocpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.executor.frame uses a type in monoruby.alloc.
monoruby.executor.frame uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.executor.frame, while a change to monoruby.executor.frame can't break monoruby.alloc.
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.
monoruby.codegen.runtime uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.codegen.runtime uses a module listed above it, which is the healthy direction.
monoruby.codegen.runtime uses monoruby.value.rvalue.proc, so a change to monoruby.value.rvalue.proc can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.value.rvalue.proc.
Position
Below the diagonal: monoruby.codegen.runtime uses a module listed above it, which is the healthy direction.
monoruby.codegen.runtime uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.codegen.runtime uses a module listed above it, which is the healthy direction.
monoruby.codegen.runtime uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.id_table.
Position
Below the diagonal: monoruby.codegen.runtime uses a module listed above it, which is the healthy direction.
monoruby.codegen.runtime uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.codegen.runtime uses a module listed above it, which is the healthy direction.
monoruby.codegen.runtime uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.codegen.runtime uses a module listed above it, which is the healthy direction.
monoruby.codegen.runtime uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.codegen.runtime uses a module listed above it, which is the healthy direction.
26→27 monoruby.codegen.runtime uses monoruby.executorpart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.runtime uses a type in monoruby.executor.
monoruby.codegen.runtime uses monoruby.executor, so a change to monoruby.executor can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.executor.
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→31 monoruby.codegen.runtime uses monoruby.globalspart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.runtime uses a type in monoruby.globals.
monoruby.codegen.runtime uses monoruby.globals, so a change to monoruby.globals can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.globals.
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→32 monoruby.codegen.runtime uses monoruby.globals.store.classpart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.runtime uses a type in monoruby.globals.store.class.
monoruby.codegen.runtime uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.globals.store.class.
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→33 monoruby.codegen.runtime uses monoruby.bytecodepart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.runtime uses a type in monoruby.bytecode.
monoruby.codegen.runtime uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.bytecode.
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→35 monoruby.codegen.runtime uses monoruby.valuepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.runtime uses a type in monoruby.value.
monoruby.codegen.runtime uses monoruby.value, so a change to monoruby.value can break monoruby.codegen.runtime, while a change to monoruby.codegen.runtime can't break monoruby.value.
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.
monoruby.executor uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.executor, while a change to monoruby.executor can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.value.rvalue.proc, so a change to monoruby.value.rvalue.proc can break monoruby.executor, while a change to monoruby.executor can't break monoruby.value.rvalue.proc.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.executor, while a change to monoruby.executor can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.executor, while a change to monoruby.executor can't break monoruby.id_table.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.value.rvalue.hash, so a change to monoruby.value.rvalue.hash can break monoruby.executor, while a change to monoruby.executor can't break monoruby.value.rvalue.hash.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.executor, while a change to monoruby.executor can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.executor, while a change to monoruby.executor can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.executor, while a change to monoruby.executor can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.executor, while a change to monoruby.executor can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
monoruby.executor uses monoruby.codegen.runtime, so a change to monoruby.codegen.runtime can break monoruby.executor, while a change to monoruby.executor can't break monoruby.codegen.runtime.
Position
Below the diagonal: monoruby.executor uses a module listed above it, which is the healthy direction.
27→31 monoruby.executor uses monoruby.globalspart of a loop✕
Connections
3 pairs of types, where a type in monoruby.executor uses a type in monoruby.globals.
monoruby.executor uses monoruby.globals, so a change to monoruby.globals can break monoruby.executor, while a change to monoruby.executor can't break monoruby.globals.
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→32 monoruby.executor uses monoruby.globals.store.classpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.executor uses a type in monoruby.globals.store.class.
monoruby.executor uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.executor, while a change to monoruby.executor can't break monoruby.globals.store.class.
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 monoruby.executor uses monoruby.bytecodepart of a loop✕
Connections
1 pair of types, where a type in monoruby.executor uses a type in monoruby.bytecode.
monoruby.executor uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.executor, while a change to monoruby.executor can't break monoruby.bytecode.
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→35 monoruby.executor uses monoruby.valuepart of a loop✕
Connections
5 pairs of types, where a type in monoruby.executor uses a type in monoruby.value.
monoruby.executor uses monoruby.value, so a change to monoruby.value can break monoruby.executor, while a change to monoruby.executor can't break monoruby.value.
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→36 monoruby.executor uses monoruby.allocpart of a loop✕
Connections
5 pairs of types, where a type in monoruby.executor uses a type in monoruby.alloc.
monoruby.executor uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.executor, while a change to monoruby.executor can't break monoruby.alloc.
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 pairs of types, where a type in monoruby.bytecodegen uses a type in (global).
The types involved
monoruby.bytecodegen.BytecodeGen → Range
monoruby.bytecodegen.BytecodeGen → String
monoruby.bytecodegen.ExceptionEntry → Range
monoruby.bytecodegen.ReplaySpan → Range
Direction
monoruby.bytecodegen uses (global), so a change to (global) can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break (global).
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses hashbrown.map, so a change to hashbrown.map can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break hashbrown.map.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.id_table.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
monoruby.bytecodegen uses monoruby.executor, so a change to monoruby.executor can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.executor.
Position
Below the diagonal: monoruby.bytecodegen uses a module listed above it, which is the healthy direction.
28→31 monoruby.bytecodegen uses monoruby.globalspart of a loop✕
Connections
2 pairs of types, where a type in monoruby.bytecodegen uses a type in monoruby.globals.
monoruby.bytecodegen uses monoruby.globals, so a change to monoruby.globals can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.globals.
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→33 monoruby.bytecodegen uses monoruby.bytecodepart of a loop✕
Connections
3 pairs of types, where a type in monoruby.bytecodegen uses a type in monoruby.bytecode.
monoruby.bytecodegen uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.bytecode.
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→35 monoruby.bytecodegen uses monoruby.valuepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.bytecodegen uses a type in monoruby.value.
monoruby.bytecodegen uses monoruby.value, so a change to monoruby.value can break monoruby.bytecodegen, while a change to monoruby.bytecodegen can't break monoruby.value.
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.
monoruby.ext uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.ext, while a change to monoruby.ext can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.ext uses a module listed above it, which is the healthy direction.
monoruby.ext uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.ext, while a change to monoruby.ext can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.ext uses a module listed above it, which is the healthy direction.
monoruby.ext uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.ext, while a change to monoruby.ext can't break monoruby.id_table.
Position
Below the diagonal: monoruby.ext uses a module listed above it, which is the healthy direction.
monoruby.ext uses monoruby.value.rvalue, so a change to monoruby.value.rvalue can break monoruby.ext, while a change to monoruby.ext can't break monoruby.value.rvalue.
Position
Below the diagonal: monoruby.ext uses a module listed above it, which is the healthy direction.
monoruby.ext uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.ext, while a change to monoruby.ext can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.ext uses a module listed above it, which is the healthy direction.
monoruby.ext uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.ext, while a change to monoruby.ext can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.ext uses a module listed above it, which is the healthy direction.
monoruby.ext uses monoruby.executor, so a change to monoruby.executor can break monoruby.ext, while a change to monoruby.ext can't break monoruby.executor.
Position
Below the diagonal: monoruby.ext uses a module listed above it, which is the healthy direction.
29→31 monoruby.ext uses monoruby.globalspart of a loop✕
Connections
1 pair of types, where a type in monoruby.ext uses a type in monoruby.globals.
monoruby.ext uses monoruby.globals, so a change to monoruby.globals can break monoruby.ext, while a change to monoruby.ext can't break monoruby.globals.
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.
29→32 monoruby.ext uses monoruby.globals.store.classpart of a loop✕
Connections
1 pair of types, where a type in monoruby.ext uses a type in monoruby.globals.store.class.
monoruby.ext uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.ext, while a change to monoruby.ext can't break monoruby.globals.store.class.
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.
29→33 monoruby.ext uses monoruby.bytecodepart of a loop✕
Connections
1 pair of types, where a type in monoruby.ext uses a type in monoruby.bytecode.
monoruby.ext uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.ext, while a change to monoruby.ext can't break monoruby.bytecode.
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.
29→35 monoruby.ext uses monoruby.valuepart of a loop✕
Connections
1 pair of types, where a type in monoruby.ext uses a type in monoruby.value.
The types involved
monoruby.ext.ext$module → monoruby.value.Value
Direction
monoruby.ext uses monoruby.value, so a change to monoruby.value can break monoruby.ext, while a change to monoruby.ext can't break monoruby.value.
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.
29→36 monoruby.ext uses monoruby.allocpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.ext uses a type in monoruby.alloc.
The types involved
monoruby.ext.ExtNative → monoruby.alloc.Allocator
monoruby.ext.ExtState → monoruby.alloc.Allocator
Direction
monoruby.ext uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.ext, while a change to monoruby.ext can't break monoruby.alloc.
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 monoruby.codegen.jitgen.asmir uses a type in (global).
The types involved
monoruby.codegen.jitgen.asmir.AsmInst → String
Direction
monoruby.codegen.jitgen.asmir uses (global), so a change to (global) can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break (global).
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses hashbrown.map, so a change to hashbrown.map can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break hashbrown.map.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.id_table.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.value.rvalue.hash, so a change to monoruby.value.rvalue.hash can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.value.rvalue.hash.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.codegen.jitgen.state.slot, so a change to monoruby.codegen.jitgen.state.slot can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.codegen.jitgen.state.slot.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.codegen, so a change to monoruby.codegen can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.codegen.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.codegen.jitgen, so a change to monoruby.codegen.jitgen can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.codegen.jitgen.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.executor, so a change to monoruby.executor can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.executor.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
monoruby.codegen.jitgen.asmir uses monoruby.bytecodegen, so a change to monoruby.bytecodegen can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.bytecodegen.
Position
Below the diagonal: monoruby.codegen.jitgen.asmir uses a module listed above it, which is the healthy direction.
30→33 monoruby.codegen.jitgen.asmir uses monoruby.bytecodepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.codegen.jitgen.asmir uses a type in monoruby.bytecode.
monoruby.codegen.jitgen.asmir uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.bytecode.
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→35 monoruby.codegen.jitgen.asmir uses monoruby.valuepart of a loop✕
Connections
1 pair of types, where a type in monoruby.codegen.jitgen.asmir uses a type in monoruby.value.
monoruby.codegen.jitgen.asmir uses monoruby.value, so a change to monoruby.value can break monoruby.codegen.jitgen.asmir, while a change to monoruby.codegen.jitgen.asmir can't break monoruby.value.
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 monoruby.globals uses a type in hashbrown.map.
The types involved
monoruby.globals.Globals → hashbrown.map.HashMap
Direction
monoruby.globals uses hashbrown.map, so a change to hashbrown.map can break monoruby.globals, while a change to monoruby.globals can't break hashbrown.map.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses hashbrown.set, so a change to hashbrown.set can break monoruby.globals, while a change to monoruby.globals can't break hashbrown.set.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.globals, while a change to monoruby.globals can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.value.rvalue.proc, so a change to monoruby.value.rvalue.proc can break monoruby.globals, while a change to monoruby.globals can't break monoruby.value.rvalue.proc.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.value.rvalue.array, so a change to monoruby.value.rvalue.array can break monoruby.globals, while a change to monoruby.globals can't break monoruby.value.rvalue.array.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.globals, while a change to monoruby.globals can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.globals, while a change to monoruby.globals can't break monoruby.id_table.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.globals, while a change to monoruby.globals can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.globals, while a change to monoruby.globals can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.globals, while a change to monoruby.globals can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.codegen.jitgen.spec_memo, so a change to monoruby.codegen.jitgen.spec_memo can break monoruby.globals, while a change to monoruby.globals can't break monoruby.codegen.jitgen.spec_memo.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.globals, while a change to monoruby.globals can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.globals, while a change to monoruby.globals can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.executor, so a change to monoruby.executor can break monoruby.globals, while a change to monoruby.globals can't break monoruby.executor.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in monoruby.globals uses a type in monoruby.ext.
The types involved
monoruby.globals.Globals → monoruby.ext.ExtState
Direction
monoruby.globals uses monoruby.ext, so a change to monoruby.ext can break monoruby.globals, while a change to monoruby.globals can't break monoruby.ext.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
monoruby.globals uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.globals, while a change to monoruby.globals can't break monoruby.codegen.jitgen.asmir.
Position
Below the diagonal: monoruby.globals uses a module listed above it, which is the healthy direction.
31→32 monoruby.globals uses monoruby.globals.store.classpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals uses a type in monoruby.globals.store.class.
monoruby.globals uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.globals, while a change to monoruby.globals can't break monoruby.globals.store.class.
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→33 monoruby.globals uses monoruby.bytecodepart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals uses a type in monoruby.bytecode.
monoruby.globals uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.globals, while a change to monoruby.globals can't break monoruby.bytecode.
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→35 monoruby.globals uses monoruby.valuepart of a loop✕
Connections
1 pair of types, where a type in monoruby.globals uses a type in monoruby.value.
The types involved
monoruby.globals.Globals → monoruby.value.Value
Direction
monoruby.globals uses monoruby.value, so a change to monoruby.value can break monoruby.globals, while a change to monoruby.globals can't break monoruby.value.
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→36 monoruby.globals uses monoruby.allocpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.globals uses a type in monoruby.alloc.
monoruby.globals uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.globals, while a change to monoruby.globals can't break monoruby.alloc.
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 pairs of types, where a type in monoruby.globals.store.class uses a type in (global).
The types involved
monoruby.globals.store.class.ClassId → String
monoruby.globals.store.class.ClassInfo → String
Direction
monoruby.globals.store.class uses (global), so a change to (global) can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break (global).
Position
Below the diagonal: monoruby.globals.store.class uses a module listed above it, which is the healthy direction.
monoruby.globals.store.class uses hashbrown.map, so a change to hashbrown.map can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break hashbrown.map.
Position
Below the diagonal: monoruby.globals.store.class uses a module listed above it, which is the healthy direction.
monoruby.globals.store.class uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.globals.store.class uses a module listed above it, which is the healthy direction.
monoruby.globals.store.class uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break monoruby.id_table.
Position
Below the diagonal: monoruby.globals.store.class uses a module listed above it, which is the healthy direction.
monoruby.globals.store.class uses monoruby.value.rvalue, so a change to monoruby.value.rvalue can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break monoruby.value.rvalue.
Position
Below the diagonal: monoruby.globals.store.class uses a module listed above it, which is the healthy direction.
monoruby.globals.store.class uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.globals.store.class uses a module listed above it, which is the healthy direction.
monoruby.globals.store.class uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.globals.store.class uses a module listed above it, which is the healthy direction.
monoruby.globals.store.class uses monoruby.globals, so a change to monoruby.globals can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break monoruby.globals.
Position
Below the diagonal: monoruby.globals.store.class uses a module listed above it, which is the healthy direction.
32→35 monoruby.globals.store.class uses monoruby.valuepart of a loop✕
Connections
2 pairs of types, where a type in monoruby.globals.store.class uses a type in monoruby.value.
monoruby.globals.store.class uses monoruby.value, so a change to monoruby.value can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break monoruby.value.
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.
32→36 monoruby.globals.store.class uses monoruby.allocpart of a loop✕
Connections
3 pairs of types, where a type in monoruby.globals.store.class uses a type in monoruby.alloc.
monoruby.globals.store.class uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.globals.store.class, while a change to monoruby.globals.store.class can't break monoruby.alloc.
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.
monoruby.bytecode uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.bytecode, while a change to monoruby.bytecode can't break monoruby.id_table.
Position
Below the diagonal: monoruby.bytecode uses a module listed above it, which is the healthy direction.
monoruby.bytecode uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.bytecode, while a change to monoruby.bytecode can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.bytecode uses a module listed above it, which is the healthy direction.
monoruby.bytecode uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.bytecode, while a change to monoruby.bytecode can't break monoruby.globals.store.class.
Position
Below the diagonal: monoruby.bytecode uses a module listed above it, which is the healthy direction.
33→35 monoruby.bytecode uses monoruby.valuepart of a loop✕
Connections
1 pair of types, where a type in monoruby.bytecode uses a type in monoruby.value.
The types involved
monoruby.bytecode.Bytecode → monoruby.value.Value
Direction
monoruby.bytecode uses monoruby.value, so a change to monoruby.value can break monoruby.bytecode, while a change to monoruby.bytecode can't break monoruby.value.
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.
monoruby.builtins.numeric.integer uses (global), so a change to (global) can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break (global).
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.value.rvalue.range, so a change to monoruby.value.rvalue.range can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.value.rvalue.range.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.codegen, so a change to monoruby.codegen can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.codegen.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.codegen.jitgen, so a change to monoruby.codegen.jitgen can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.codegen.jitgen.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.executor, so a change to monoruby.executor can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.executor.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.bytecodegen, so a change to monoruby.bytecodegen can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.bytecodegen.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.codegen.jitgen.asmir.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.globals, so a change to monoruby.globals can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.globals.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.globals.store.class.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.integer uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.builtins.numeric.integer, while a change to monoruby.builtins.numeric.integer can't break monoruby.bytecode.
Position
Below the diagonal: monoruby.builtins.numeric.integer uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.value, while a change to monoruby.value can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.value.rvalue.proc, so a change to monoruby.value.rvalue.proc can break monoruby.value, while a change to monoruby.value can't break monoruby.value.rvalue.proc.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.value, while a change to monoruby.value can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.value.rvalue.array, so a change to monoruby.value.rvalue.array can break monoruby.value, while a change to monoruby.value can't break monoruby.value.rvalue.array.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.value.rvalue.range, so a change to monoruby.value.rvalue.range can break monoruby.value, while a change to monoruby.value can't break monoruby.value.rvalue.range.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.value, while a change to monoruby.value can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.value, while a change to monoruby.value can't break monoruby.id_table.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.value.rvalue.hash, so a change to monoruby.value.rvalue.hash can break monoruby.value, while a change to monoruby.value can't break monoruby.value.rvalue.hash.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.value.rvalue.regexp, so a change to monoruby.value.rvalue.regexp can break monoruby.value, while a change to monoruby.value can't break monoruby.value.rvalue.regexp.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.value.rvalue, so a change to monoruby.value.rvalue can break monoruby.value, while a change to monoruby.value can't break monoruby.value.rvalue.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.value, while a change to monoruby.value can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.value, while a change to monoruby.value can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.value, while a change to monoruby.value can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.executor, so a change to monoruby.executor can break monoruby.value, while a change to monoruby.value can't break monoruby.executor.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.globals, so a change to monoruby.globals can break monoruby.value, while a change to monoruby.value can't break monoruby.globals.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.value, while a change to monoruby.value can't break monoruby.globals.store.class.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
monoruby.value uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.value, while a change to monoruby.value can't break monoruby.bytecode.
Position
Below the diagonal: monoruby.value uses a module listed above it, which is the healthy direction.
35→36 monoruby.value uses monoruby.allocpart of a loop✕
Connections
2 pairs of types, where a type in monoruby.value uses a type in monoruby.alloc.
The types involved
monoruby.value.Value → monoruby.alloc.Allocator
monoruby.value.Value → monoruby.alloc.GC
Direction
monoruby.value uses monoruby.alloc, so a change to monoruby.alloc can break monoruby.value, while a change to monoruby.value can't break monoruby.alloc.
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.
monoruby.alloc uses monoruby.value, so a change to monoruby.value can break monoruby.alloc, while a change to monoruby.alloc can't break monoruby.value.
Position
Below the diagonal: monoruby.alloc uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in monoruby.builtins.array uses a type in (global).
The types involved
monoruby.builtins.array.array$module → String
Direction
monoruby.builtins.array uses (global), so a change to (global) can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break (global).
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses hashbrown.set, so a change to hashbrown.set can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break hashbrown.set.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.value.rvalue.array, so a change to monoruby.value.rvalue.array can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.value.rvalue.array.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.value.rvalue.range, so a change to monoruby.value.rvalue.range can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.value.rvalue.range.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.id_table.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.codegen.runtime, so a change to monoruby.codegen.runtime can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.codegen.runtime.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.executor, so a change to monoruby.executor can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.executor.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.codegen.jitgen.asmir.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.globals, so a change to monoruby.globals can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.globals.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.globals.store.class.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.bytecode.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
monoruby.builtins.array uses monoruby.value, so a change to monoruby.value can break monoruby.builtins.array, while a change to monoruby.builtins.array can't break monoruby.value.
Position
Below the diagonal: monoruby.builtins.array uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in monoruby.builtins.kernel uses a type in (global).
The types involved
monoruby.builtins.kernel.kernel$module → String
Direction
monoruby.builtins.kernel uses (global), so a change to (global) can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break (global).
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.id_table, so a change to monoruby.id_table can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.id_table.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.value.rvalue.hash, so a change to monoruby.value.rvalue.hash can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.value.rvalue.hash.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.globals.store.iseq, so a change to monoruby.globals.store.iseq can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.globals.store.iseq.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.globals.store.function, so a change to monoruby.globals.store.function can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.globals.store.function.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.executor, so a change to monoruby.executor can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.executor.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.codegen.jitgen.asmir.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.globals, so a change to monoruby.globals can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.globals.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.globals.store.class.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.bytecode.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.kernel uses monoruby.value, so a change to monoruby.value can break monoruby.builtins.kernel, while a change to monoruby.builtins.kernel can't break monoruby.value.
Position
Below the diagonal: monoruby.builtins.kernel uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.ast.node, so a change to monoruby.ast.node can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.ast.node.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.value.rvalue.module, so a change to monoruby.value.rvalue.module can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.value.rvalue.module.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.codegen.jitgen, so a change to monoruby.codegen.jitgen can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.codegen.jitgen.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.executor, so a change to monoruby.executor can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.executor.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.bytecodegen, so a change to monoruby.bytecodegen can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.bytecodegen.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.codegen.jitgen.asmir.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.globals, so a change to monoruby.globals can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.globals.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.globals.store.class.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.bytecode.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
monoruby.builtins.numeric.float uses monoruby.value, so a change to monoruby.value can break monoruby.builtins.numeric.float, while a change to monoruby.builtins.numeric.float can't break monoruby.value.
Position
Below the diagonal: monoruby.builtins.numeric.float uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in monoruby.builtins.string uses a type in (global).
The types involved
monoruby.builtins.string.string$module → Range
monoruby.builtins.string.string$module → String
Direction
monoruby.builtins.string uses (global), so a change to (global) can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break (global).
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.globals.error, so a change to monoruby.globals.error can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.globals.error.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.value.rvalue.array, so a change to monoruby.value.rvalue.array can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.value.rvalue.array.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.value.rvalue.range, so a change to monoruby.value.rvalue.range can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.value.rvalue.range.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.value.rvalue.string, so a change to monoruby.value.rvalue.string can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.value.rvalue.string.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.value.rvalue.regexp, so a change to monoruby.value.rvalue.regexp can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.value.rvalue.regexp.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.globals.store, so a change to monoruby.globals.store can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.globals.store.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.codegen.jitgen.state, so a change to monoruby.codegen.jitgen.state can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.codegen.jitgen.state.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.codegen.jitgen.context, so a change to monoruby.codegen.jitgen.context can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.codegen.jitgen.context.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.executor.frame, so a change to monoruby.executor.frame can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.executor.frame.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.codegen.runtime, so a change to monoruby.codegen.runtime can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.codegen.runtime.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.executor, so a change to monoruby.executor can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.executor.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.codegen.jitgen.asmir, so a change to monoruby.codegen.jitgen.asmir can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.codegen.jitgen.asmir.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.globals, so a change to monoruby.globals can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.globals.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.globals.store.class, so a change to monoruby.globals.store.class can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.globals.store.class.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.bytecode, so a change to monoruby.bytecode can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.bytecode.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
monoruby.builtins.string uses monoruby.value, so a change to monoruby.value can break monoruby.builtins.string, while a change to monoruby.builtins.string can't break monoruby.value.
Position
Below the diagonal: monoruby.builtins.string uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 76.2 · Adequate · gated by D2 ·
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
79
High / Critical
A03:2025 — Software Supply Chain Failures
47
High / Critical
Roadmap
Top priorities: Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `ext/digest/src/lib.rs:60` (`Md5::digest`), `ext/digest/src/lib.rs:61` (`Sha1::digest`). Each is a separate decision — fixing only the line this row cites leaves the others in place; 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 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED (2).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `ext/digest/src/lib.rs:60` (`Md5::digest`), `ext/digest/src/lib.rs:61` (`Sha1::digest`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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 REDACTED finding(s) charged to Static Analysis (SAST) — the other 49 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
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 — 69
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 — 2441
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 — 44
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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 58 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 — 58 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, 2531 of 2554 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .rb) and this repository declares a Cargo test suite (repository root, 390 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 3665 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 2 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their 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 per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in REDACTED, whose lifetimes are not modelled 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.
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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 3 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
X17 Uncapped recursion over a caller-supplied document — 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. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X5 Nullable reference types — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 961 further occurrence(s) are not listed individually; the score already reflects all 1001.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
319 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Codegen::compile_asmir at 209. A further 42 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being monoruby::parser::prism_backend::node_kind_name at 145 — they are counted neither in the figure above nor in this dimension's score. 7 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: monoruby/src/value/rvalue.rs (RValue::mark_children at 35), monoruby/src/globals/error.rs (MonorubyErr::class_name at 29), monoruby/src/builtins/fiddle.rs (monoruby::builtins::fiddle::fiddle_read_inline at 23), monoruby/src/builtins/gc.rs (monoruby::builtins::gc::stat_value at 23), monoruby/src/builtins/string/byte_case.rs (monoruby::builtins::string::byte_case::byte_case_map at 19), and 2 more not listed here. 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.
+ 100 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with Codegen::compile_asmir (cyclomatic 209), monoruby::value::rvalue::string::transcode::stream_convert (cyclomatic 205), monoruby::value::rvalue::string::transcode_bytes_with_opts (cyclomatic 197). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 5.2 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.
+ 156 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 240 down to 240 or less in Cognitive Complexity — start with monoruby::value::rvalue::string::transcode::stream_convert (cognitive 469), Executor::format_by_args (cognitive 451), monoruby::value::rvalue::string::transcode_bytes_with_opts (cognitive 444). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 2.2 to about 3.4/10, projected with the scoring formula itself and assuming each lands exactly at 240; 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 Classes8.8 / 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 88 FileTooLong finding(s) in God Classes — start with lib.rs (4), string.rs (2), io.rs (2). — One of this dimension's main actionable groups (88 warning-level).
Resolve the 52 FunctionTooLong finding(s) in God Classes — start with io.rs (6), string.rs (5), lib.rs (5). — One of this dimension's main actionable groups (52 warning-level).
Resolve the 51 TooManyMethods finding(s) in God Classes — start with codegen.rs (2), store.rs (2), map.rs (2). — One of this dimension's main actionable groups (51 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
581 duplicated block group(s) detected. 4.8 % of the production lines (23,616 of 487,106) are in a reported copy. A further 438 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 226 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 51 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with string.rs (7), array.rs (3), hash.rs (3). — One of this dimension's main actionable groups (51 warning-level).
Resolve the 46 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with hash.rs (4), string.rs (4), io.rs (3). — One of this dimension's main actionable groups (46 warning-level).
Resolve the 44 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with string.rs (5), mod.rs (5), io.rs (3). — One of this dimension's main actionable groups (44 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.1 / 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.
17 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 13 of the 17 (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: host_ruby · ×4
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 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.
Low cohesion: Store (LCOM4 25) · ×11monoruby/src/globals/store.rs:110
What to do
Resolve the 11 Low cohesion finding(s) in Cohesion (LCOM4) — start with store.rs (2), class_dispatch.rs, executor.rs. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
8 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: cc · ×8
✓ 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 213 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 6 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.
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 72 Hotspot finding(s) in Churn × Complexity Hotspots — start with method_call.rs (2), string.rs (2), mod.rs (2). — One of this dimension's main actionable groups (72 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
43 deducted task-comment markers across 487106 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 25 TodoComment finding(s) in Explicit Debt — start with invoker.rs (3), jit_module.rs (2), node.rb (2). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 17 FixmeComment finding(s) in Explicit Debt — start with map.rs (4), iter.rs (3), table.rs (2). — One of this dimension's main actionable groups (17 warning-level).
Resolve the 1 XxxComment finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 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. 71 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 18 build units (Cargo) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionmonoruby/Cargo.toml:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml. — 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).
79 finding(s): 0 critical, 65 high, 14 medium, 0 low. 49 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 54 file(s) — `benchmark/protoboeuf/benchmark_pb.rb`, `bin/ruby-bench-diff` (lines 184–215), `monoruby/gem/prism/node.rb`, `monoruby/src/builtins/encoding.rs` (line 4010, lines 4039–4042), `monoruby/src/builtins/file.rs`, … (+49 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 49 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (50 issue-level, 1 of them charged here).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
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 15 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 9 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 413 of the 615 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with hash.rs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 5 Change coupling finding(s) in Change Coupling — start with method.rs, tests.rs, inline.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — .github/bench-pages/index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
Do you agree with this assessment?
AX8 · Test isolation7.5 / 10Strong✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
`monoruby` (production) references the test project `monoruby_test_support`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (ActiveRecord/Sequel/ROM) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Code Health — Unreviewed-generation residue in this repository's Rust: functions whose whole body is still `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Rust: functions whose body is `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, match arms and branches left as `todo!()`, functions that take inputs and return a constant (`Ok(())`, `None`, `Default::default()`, an empty `Vec`) or do nothing, and impls most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`io_close` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — ext/nokogiri/src/lib.rs:1095
`from` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — monoruby/src/ast/node.rs:447
`show_loc` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — monoruby/src/ast/source_info.rs:225
`to_f` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — REDACTED:301
`succ_walks_its_own_encoding` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — monoruby/src/builtins/string.rs:12535
`encode_linst` does real work, but one of its branches is `todo!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. (×2) — monoruby/src/codegen/arch/aarch64/compile/mod.rs:1821, monoruby/src/codegen/arch/x86_64/compile/mod.rs:623
`_dump_reg` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — REDACTED:3863
`func_id` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — monoruby/src/executor.rs:6132
`noinline_gen` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — monoruby/src/globals.rs:250
`ubf_handler` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — monoruby/src/scheduler/native.rs:64
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
`ext/bcrypt/Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — ext/bcrypt/Cargo.toml:13
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:80
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A Ruby benchmark-ips/Benchmark/rspec-benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmark/app_fib.yml
What to do
Measure allocations beside time — benchmark-memory's `Benchmark.memory { |x| x.report(…) }`, or memory_profiler — so allocation regressions are visible, not just time.
Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are read from a Rust server this repository starts itself, and its production Rust starts none. What serves its HTTP is outside the Rust source, and only what this card names about it was assessed.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — ext/digest/src/lib.rs:60, ext/digest/src/lib.rs:61
`https://cdn.jsdelivr.net/npm/chart.js@4` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 2 such include(s) across the repository's markup. — .github/bench-pages/index.html:7
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `ext/digest/src/lib.rs:60` (`Md5::digest`), `ext/digest/src/lib.rs:61` (`Sha1::digest`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
`let node = expand(ctx, this, args, reader) ?;` follows `{ return Ok(hash); }` (line 340) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — ext/nokogiri/src/reader.rs:343
`let node = expand(ctx, this, args, reader) ?;` follows `{ return Ok(hash); }` (line 365) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — ext/nokogiri/src/reader.rs:368
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document1.1 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`len` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 54 with a piece of the document (and at line 109, line 161) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/set/iter.rs:54
`clone` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 63 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `clone` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/set/iter.rs:63
`as_slice` is public and takes a `Drain` as its receiver from its caller, and it calls itself at line 145 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_slice` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/set/iter.rs:145
`as_slice` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 53 with a piece of the document (and at line 113, line 236, line 293) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_slice` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/map/iter.rs:53
`len` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 69 with a piece of the document (and at line 136, line 257, line 309) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/map/iter.rs:69
`clone` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 79 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `clone` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/map/iter.rs:79
`into_slice` is public and takes a `IterMut` as its receiver from its caller, and it calls itself at line 120 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `into_slice` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/map/iter.rs:120
`as_mut_slice` is public and takes a `IntoIter` as its receiver from its caller, and it calls itself at line 241 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_mut_slice` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/map/iter.rs:241
`index` is public and takes a `OccupiedEntry` as its receiver from its caller, and it recurses at line 172 through `get` and back with a piece of the document (and at line 191) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `index` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/map/core/entry.rs:172
`remove` is public and takes a `OccupiedEntry` as its receiver from its caller, and it recurses at line 229 through `swap_remove_entry`, `swap_remove` and back with a piece of the document (and at line 240, line 274) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `remove` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/map/core/entry.rs:229
`move_index` is public and takes a `OccupiedEntry` as its receiver from its caller, and it calls itself at line 305 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `move_index` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rubymap/src/map/core/entry.rs:305
`mark` is public and takes a `Executor` as its receiver from its caller, and it calls itself at line 598 with a piece of the document (and at line 601, line 613, line 621, line 625, line 628, line 633, line 636, line 641, line 644, line 650, line 656, line 658, line 665, line 666, line 669) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `mark` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/executor.rs:598
`method_func_id` is public and takes a `Executor` as its receiver from its caller, and it calls itself at line 831 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `method_func_id` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/executor.rs:831
`generate_proc_inner` is public and takes a `Executor` as its receiver from its caller, and it recurses at line 5436 through `materialize_escaped_block_handlers` and back with a piece of the document (and at line 5606) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `generate_proc_inner` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/executor.rs:5436
`next` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 1958 with a piece of the document (and at line 1959, line 1964) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `next` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/value/rvalue/hash.rs:1958
`prev` is public, takes a document from its caller (line 93) and hands it to `as_ptr`, which calls itself at line 87 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_ptr` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/executor/frame.rs:87
`format` is public, takes a document from its caller (line 742) and hands it to `format_inner`, which calls itself at line 759 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `format_inner` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/codegen/jitgen.rs:759
`jit_compile` is public, takes a document from its caller (line 765) and hands it to `unit_inst_len`, which calls itself at line 1030 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `unit_inst_len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/codegen/jitgen.rs:1030
`push` is public and takes a `AsmIr` as its receiver from its caller, and it calls itself at line 665 with a piece of the document (and at line 631) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `push` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/codegen/jitgen/asmir.rs:665
`is_empty` is public and takes a `AsmIr` as its receiver from its caller, and it calls itself at line 724 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `is_empty` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/codegen/jitgen/asmir.rs:724
`reads_frame_header` is public and takes a `AsmInfo` as its receiver from its caller, and it calls itself at line 319 with a piece of the document (and at line 323, line 327) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `reads_frame_header` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/codegen/jitgen/context.rs:319
`min` is public and takes `vm: &mut Executor` from its caller, and it calls itself at line 2860 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `min` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/builtins/array.rs:2860
`max` is public and takes `vm: &mut Executor` from its caller, and it calls itself at line 2964 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `max` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/src/builtins/array.rs:2964
`from_hash` is public and takes `object` — which it walks as a `Hash` — from its caller, and it calls itself at line 30 (`self.from_hash`) with a piece of `object` (and at line 34) — and nowhere in `from_hash` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `from_hash` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/gem/json/generic_object.rb:30
`make_shareable` is public, takes a document from its caller (line 115) and hands it to `__deep_freeze`, which walks `obj` as a `Hash` and calls itself at line 159 (`self.__deep_freeze`) with a piece of `obj` (and at line 161, line 163, line 165, line 166, line 170) — and nowhere in `__deep_freeze` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `__deep_freeze` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/builtins/ractor.rb:159
`make_shareable` is public, takes a document from its caller (line 115) and hands it to `__deep_copy`, which walks `obj` as a `Hash` and calls itself at line 183 (`self.__deep_copy`) with a piece of `obj` (and at line 188, line 197) — and nowhere in `__deep_copy` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `__deep_copy` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/builtins/ractor.rb:183
`shareable?` is public, takes a document from its caller (line 123) and hands it to `__shareable?`, which walks `obj` as a `Hash` and calls itself at line 211 (`self.__shareable?`) with a piece of `obj` (and at line 213, line 215, line 221) — and nowhere in `__shareable?` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `__shareable?` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — monoruby/builtins/ractor.rb:211
`clone` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 1659 with a piece of the document (and at line 1959) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `clone` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/map.rs:1659
`iter` is public and takes a `IntoIter` as its receiver from its caller, and it calls itself at line 1759 with a piece of the document (and at line 2055) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `iter` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/map.rs:1759
`next` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 2656 with a piece of the document (and at line 2759, line 2802, line 2921) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `next` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/map.rs:2656
`size_hint` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 2666 with a piece of the document (and at line 2763, line 2809, line 2925) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `size_hint` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/map.rs:2666
`fold` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 2674 with a piece of the document (and at line 2771, line 2817, line 2933) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `fold` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/map.rs:2674
`len` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 2683 with a piece of the document (and at line 2777, line 2823, line 2939) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/map.rs:2683
`remove_entry` is public and takes a `OccupiedEntry` as its receiver from its caller, and it recurses at line 3281 through `remove` and back with a piece of the document (and at line 3415) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `remove_entry` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/map.rs:3281
`insert` is public and takes a `VacantEntry` as its receiver from its caller, and it recurses at line 3557 through `insert_entry` and back with a piece of the document (and at line 3587) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `insert` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/map.rs:3557
`clone` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 1134 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `clone` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/set.rs:1134
`next` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 1151 with a piece of the document (and at line 1194, line 1233) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `next` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/set.rs:1151
`size_hint` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 1155 with a piece of the document (and at line 1201, line 1240) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `size_hint` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/set.rs:1155
`fold` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 1163 with a piece of the document (and at line 1209, line 1248) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `fold` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/set.rs:1163
`len` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 1169 with a piece of the document (and at line 1215, line 1254) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — hashbrown/src/set.rs:1169
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`f` (line 1687) is a `BufWriter` this function owns and never releases: no `flush()` (or `into_inner()`) on any path, and it is not handed on. Rust drops it at the end of the scope, and a buffered writer that is dropped flushes and throws the error away, so a failed write reports success. Release it where the work ends. — monoruby/src/prof.rs:1687
`StdFd.0` is a `ManuallyDrop<std::fs::File>` (line 43): wrapping it switched its `Drop` off, and no method of `StdFd` ever switches it back on — no `ManuallyDrop::drop`, `take` or `into_inner` of `self.0`, and `StdFd` has no `Drop` that does it. Every `StdFd` that goes away leaks what the field owns. Release it in `impl Drop for StdFd` (`unsafe { ManuallyDrop::drop(&mut self.0) }`), or hold the value plainly if nothing needs to control its drop order. — monoruby/src/value/rvalue/io/buf.rs:43
`mem::forget(guard)` (line 3083) takes `guard` out of Rust's ownership: its `Drop` never runs, so whatever it holds — a descriptor, a socket, a buffer, a lock — is never given back, and nothing can give it back later because the value is gone. Let it drop (or call its explicit close) where its work ends; if the handle must outlive this function, turn it into a raw handle with `into_raw`/`into_raw_fd` and reclaim it with the matching `from_raw` when the owner is done. — hashbrown/src/raw/mod.rs:3083
`group` (line 1804) is a `Group` this function owns and never releases: no `store_aligned()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Group` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends. — hashbrown/src/raw/mod.rs:1804
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
`CommandLineArgs.import` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — monoruby/src/bin/irm/main.rs:19
What to do
Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
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. Whether a walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone — Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether Rust's absent values are handled rather than forced — `Option` and `Result` make absence a value the caller must handle in every crate, and each `.unwrap()` or `.expect()` that no guard on its path proves present is a panic the first time the value is `None` or `Err`.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
`bytes[..8].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `read8` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/hasher.rs:34
`bytes[..4].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `read4` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/hasher.rs:39
`other.get(k1,&mut(),&mut())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `eq` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/map.rs:108
`self.get(key,&mut(),&mut())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/map.rs:125
`self.get(key,&mut(),&mut()).unwrap()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/map.rs:125
`table.find_mut(hash.get(),move|&i,_,_|Ok(i==old),e,g)?` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `update_index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/map/core.rs:153
`indices.find_entry(hash.get(),move|&i,_,_|Ok(i==index),e,g)?` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `from_index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/map/core/entry.rs:333
`self.map.swap_remove_index(self.index,e,g)?` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `swap_remove_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/map/core/entry.rs:483
`self.map.shift_remove_index(self.index,e,g)?` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `shift_remove_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — rubymap/src/map/core/entry.rs:494
`slot.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `thunk` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby_ext/src/lib.rs:697
`CString::new(s.as_bytes().iter().copied().take_while(|&b|b!=0).collect::<Vec<u8>>(),)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cstring` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby_ext/src/lib.rs:732
`dirs::home_dir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:43
`fs::create_dir_all(&lib_path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:134
`fs::remove_dir_all(&staging)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:138
`fs::create_dir_all(dir)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:141
`copy_dir_all(src,dst)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:203
`hash_tree(&staging,&mut hasher)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:221
`fs::write(&stamp,tree_stamp)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:271
`std::env::var_os("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_extensions` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:298
`std::env::var_os("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:399
`fs::create_dir_all(capi_dir)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:401
`fs::copy(&out,capi_dir.join("libmonoruby_capi.a"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:402
`fs::read_to_string(list)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_cruby_header_names` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:421
`path.parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_cruby_header_names` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:429
`fs::create_dir_all(path.parent().unwrap())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_cruby_header_names` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:429
`fs::write(&path,format!("/* CRuby's {name}: monoruby's C API is all in ruby/ruby.h (doc/c_api.md §3.17). */\n\
#include \"ruby/ruby.h\"\n"),)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_cruby_header_names` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:437
`std::env::var_os("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `capi_extensions_dir` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:444
`fs::create_dir_all(&dest)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_extensions` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:576
`std::env::var_os("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `report_compile_errors` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:668
`fs::read_to_string(list)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_stubs_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:814
`std::env::var_os("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_stubs_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:815
`fs::read_to_string(src)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_stubs_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:837
`fs::write(&stubs_c,src)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_stubs_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:864
`fs::create_dir_all(capi_dir)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_stubs_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:875
`fs::copy(out_dir.join("libmonoruby_capi_stubs.a"),capi_dir.join("libmonoruby_capi_stubs.a"),)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_stubs_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/build.rs:880
`std::ptr::NonNull::new(ptr as _)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/src/alloc.rs:1203
`std::ptr::NonNull::new(ptr)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new_page` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/src/alloc.rs:1269
`self.free_pages.pop_back()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `release_excess_free_pages` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/src/alloc.rs:2329
`std::fs::read_to_string("/proc/self/smaps")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `vm_flags` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/src/alloc.rs:2706
`loop_stack.pop()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — monoruby/src/basic_block.rs:227
What to do
Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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.
X10 Duplicated predicate — 20 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — 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
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — AX6 reached only 10% of this repository's production lines — rust (397,179 lines), c (858 lines), lua (8 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — 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 — ~66466 lines of test source are present (.rs, .rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rb, .rs source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Rust suite
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Ruby, Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
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: Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
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
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
X19 Unrestored process-global state — X19 reached only 10% of this repository's production lines — rust (397,179 lines), c (858 lines), lua (8 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X2 Cancellation propagation — no C# was loaded; this repository's Ruby and Rust were read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter; 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 10% of this repository's production lines — rust (397,179 lines), c (858 lines), lua (8 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X26 Unsynchronised callback handoff — 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 — X3 reached only 10% of this repository's production lines — rust (397,179 lines), c (858 lines), lua (8 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AX8 · Test isolation· Production project references a test project · ×1
Production project references a test project: monoruby → monoruby_test_support — `monoruby` (production) references the test project `monoruby_test_support`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Boundary-crossing change coupling: hash.rs ↔ core.rs monoruby/src/value/rvalue/hash.rs:1— `monoruby/src/value/rvalue/hash.rs` (context monoruby) and `rubymap/src/map/core.rs` (context rubymap) sit in DIFFERENT parts of the tree yet change together 64% of the time (9 of the 14 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `d09591c1` Hash: consult eql? only after a full stored-hash match (#1284); `adca54ed` Emit the Hash#[] probe as machine code for String keys and the indexe…; `2875cde7` Emit the Hash#[] probe as machine code for Symbol keys in a linear ma… — run `git show` on any of them.
monoruby::value::rvalue::string::transcode::stream_convert (cognitive 469) monoruby/src/value/rvalue/string/transcode.rs:6310— monoruby::value::rvalue::string::transcode::stream_convert has cognitive complexity 469 (threshold 15). Drivers by points: if/else 145 (339 pts), boolean chains 46, loops 14 (42 pts), match/switch 14 (42 pts) (nesting depth added 250). 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.
monoruby::value::rvalue::string::transcode_bytes_with_opts (cognitive 444) monoruby/src/value/rvalue/string.rs:5600— monoruby::value::rvalue::string::transcode_bytes_with_opts has cognitive complexity 444 (threshold 15). Drivers by points: if/else 121 (256 pts), match/switch 30 (98 pts), loops 16 (55 pts), boolean chains 35 (nesting depth added 242). 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.
monoruby::value::rvalue::string::pack::pack (cognitive 392) monoruby/src/value/rvalue/string/pack.rs:731— monoruby::value::rvalue::string::pack::pack has cognitive complexity 392 (threshold 15). Drivers by points: if/else 116 (296 pts), loops 20 (72 pts), match/switch 9 (21 pts), boolean chains 3 (nesting depth added 244). 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.
monoruby::value::rvalue::string::transcode::cell_decode (cognitive 358) monoruby/src/value/rvalue/string/transcode.rs:2930— monoruby::value::rvalue::string::transcode::cell_decode has cognitive complexity 358 (threshold 15). Drivers by points: if/else 60 (260 pts), match/switch 10 (55 pts), loops 7 (33 pts), boolean chains 10 (nesting depth added 271). 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.
monoruby::value::rvalue::string::pack::unpack (cognitive 342) monoruby/src/value/rvalue/string/pack.rs:163— monoruby::value::rvalue::string::pack::unpack has cognitive complexity 342 (threshold 15). Drivers by points: if/else 84 (228 pts), loops 25 (92 pts), match/switch 5 (16 pts), boolean chains 6 (nesting depth added 222). 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.
monoruby::builtins::string::split (cognitive 213) monoruby/src/builtins/string.rs:3331— monoruby::builtins::string::split has cognitive complexity 213 (threshold 15). Drivers by points: if/else 72 (153 pts), match/switch 14 (24 pts), loops 9 (22 pts), boolean chains 14 (nesting depth added 104). 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.
monoruby::builtins::marshal::marshal_dump_value (cognitive 178) monoruby/src/builtins/marshal.rs:2499— monoruby::builtins::marshal::marshal_dump_value has cognitive complexity 178 (threshold 15). Drivers by points: if/else 51 (132 pts), loops 10 (31 pts), match/switch 4 (10 pts), boolean chains 5 (nesting depth added 108). 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.
monoruby::prof::report (cognitive 174) monoruby/src/prof.rs:2031— monoruby::prof::report has cognitive complexity 174 (threshold 15). Drivers by points: if/else 53 (113 pts), loops 23 (55 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 95). 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.
monoruby::executor::op::integer_index1 (cognitive 122) monoruby/src/executor/op.rs:1852— monoruby::executor::op::integer_index1 has cognitive complexity 122 (threshold 15). Drivers by points: if/else 47 (104 pts), match/switch 6 (16 pts), boolean chains 2 (nesting depth added 67). Of this number, 106 points are the body's own statements and 16 belong to one function item inside it that branches. 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.
monoruby::builtins::io::io_select (cognitive 120) monoruby/src/builtins/io.rs:5457— monoruby::builtins::io::io_select has cognitive complexity 120 (threshold 15). Drivers by points: if/else 38 (75 pts), loops 20 (39 pts), boolean chains 6 (nesting depth added 56). 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.
monoruby::builtins::spawn::parse_exec_args (cognitive 118) monoruby/src/builtins/spawn.rs:134— monoruby::builtins::spawn::parse_exec_args has cognitive complexity 118 (threshold 15). Drivers by points: if/else 46 (89 pts), loops 6 (16 pts), boolean chains 8, match/switch 1 (5 pts) (nesting depth added 57). 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.
monoruby::main (cognitive 115) monoruby/src/main.rs:614— monoruby::main has cognitive complexity 115 (threshold 15). Drivers by points: if/else 53 (71 pts), match/switch 12 (28 pts), boolean chains 11, loops 4 (5 pts) (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.
monoruby::builtins::set::divide (cognitive 106) monoruby/src/builtins/set.rs:1346— monoruby::builtins::set::divide has cognitive complexity 106 (threshold 15). Drivers by points: if/else 19 (71 pts), loops 9 (29 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 75). 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.
monoruby::builtins::array::fill (cognitive 103) monoruby/src/builtins/array.rs:1792— monoruby::builtins::array::fill has cognitive complexity 103 (threshold 15). Drivers by points: if/else 34 (86 pts), loops 4 (16 pts), boolean chains 1 (nesting depth added 64). 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.
monoruby::builtins::string::slice_ (cognitive 91) monoruby/src/builtins/string.rs:3875— monoruby::builtins::string::slice_ has cognitive complexity 91 (threshold 15). Drivers by points: if/else 31 (54 pts), match/switch 12 (31 pts), boolean chains 6 (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.
monoruby::builtins::io::copy_stream_fds (cognitive 90) monoruby/src/builtins/io.rs:7168— monoruby::builtins::io::copy_stream_fds has cognitive complexity 90 (threshold 15). Drivers by points: if/else 21 (51 pts), match/switch 10 (24 pts), loops 4 (8 pts), boolean chains 7 (nesting depth added 48). Of this number, 87 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.
monoruby::builtins::range::range_include_impl (cognitive 90) monoruby/src/builtins/range.rs:441— monoruby::builtins::range::range_include_impl has cognitive complexity 90 (threshold 15). Drivers by points: if/else 31 (60 pts), boolean chains 18, match/switch 7 (12 pts) (nesting depth added 34). Of this number, 87 points are the body's own statements and 3 belong to 2 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.
monoruby::codegen::runtime::expand_array (cognitive 88) REDACTED:1696— monoruby::codegen::runtime::expand_array has cognitive complexity 88 (threshold 15). Drivers by points: loops 14 (55 pts), if/else 18 (30 pts), match/switch 2 (3 pts) (nesting depth added 54). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
monoruby::builtins::io::io_copy_stream (cognitive 82) monoruby/src/builtins/io.rs:6806— monoruby::builtins::io::io_copy_stream has cognitive complexity 82 (threshold 15). Drivers by points: if/else 31 (56 pts), match/switch 10 (14 pts), loops 4 (8 pts), boolean chains 4 (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.
monoruby::builtins::numeric::float::round (cognitive 79) monoruby/src/builtins/numeric/float.rs:960— monoruby::builtins::numeric::float::round has cognitive complexity 79 (threshold 15). Drivers by points: if/else 38 (71 pts), match/switch 2 (6 pts), boolean chains 2 (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.
monoruby::builtins::io::io_popen (cognitive 77) monoruby/src/builtins/io.rs:3275— monoruby::builtins::io::io_popen has cognitive complexity 77 (threshold 15). Drivers by points: if/else 32 (55 pts), boolean chains 10, loops 3 (6 pts), match/switch 4 (6 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.
monoruby::builtins::string::byteslice (cognitive 75) monoruby/src/builtins/string.rs:7863— monoruby::builtins::string::byteslice has cognitive complexity 75 (threshold 15). Drivers by points: if/else 38 (67 pts), match/switch 3 (8 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.
monoruby::codegen::runtime::args::set_callee_frame_arguments (cognitive 73) monoruby/src/codegen/runtime/args.rs:807— monoruby::codegen::runtime::args::set_callee_frame_arguments has cognitive complexity 73 (threshold 15). Drivers by points: if/else 30 (51 pts), boolean chains 11, loops 3 (8 pts), match/switch 1 (3 pts) (nesting depth added 28). Of this number, 72 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.
monoruby::value::rvalue::regexp::expand_unicode_braces (cognitive 73) monoruby/src/value/rvalue/regexp.rs:1255— monoruby::value::rvalue::regexp::expand_unicode_braces has cognitive complexity 73 (threshold 15). Drivers by points: if/else 16 (56 pts), loops 2 (6 pts), match/switch 1 (6 pts), boolean chains 5 (nesting depth added 49). 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.
monoruby::builtins::numeric::integer::index (cognitive 72) REDACTED:1276— monoruby::builtins::numeric::integer::index has cognitive complexity 72 (threshold 15). Drivers by points: if/else 28 (65 pts), match/switch 3 (7 pts) (nesting depth added 41). 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.
monoruby::value::rvalue::string::transcode::stream_convert (cyclomatic 205) monoruby/src/value/rvalue/string/transcode.rs:6310— monoruby::value::rvalue::string::transcode::stream_convert has cyclomatic complexity 205 (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.
monoruby::value::rvalue::string::transcode_bytes_with_opts (cyclomatic 197) monoruby/src/value/rvalue/string.rs:5600— monoruby::value::rvalue::string::transcode_bytes_with_opts has cyclomatic complexity 197 (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.
monoruby::value::rvalue::string::pack::pack (cyclomatic 129) monoruby/src/value/rvalue/string/pack.rs:731— monoruby::value::rvalue::string::pack::pack has cyclomatic complexity 129 (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.
monoruby::value::rvalue::string::pack::unpack (cyclomatic 114) monoruby/src/value/rvalue/string/pack.rs:163— monoruby::value::rvalue::string::pack::unpack has cyclomatic complexity 114 (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.
monoruby::builtins::string::split (cyclomatic 94) monoruby/src/builtins/string.rs:3331— monoruby::builtins::string::split has cyclomatic complexity 94 (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.
monoruby::builtins::marshal::marshal_dump_value (cyclomatic 85) monoruby/src/builtins/marshal.rs:2499— monoruby::builtins::marshal::marshal_dump_value has cyclomatic complexity 85 (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.
monoruby::main (cyclomatic 82) monoruby/src/main.rs:614— monoruby::main 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.
monoruby::value::rvalue::string::transcode::cell_decode (cyclomatic 76) monoruby/src/value/rvalue/string/transcode.rs:2930— monoruby::value::rvalue::string::transcode::cell_decode has cyclomatic complexity 76 (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.
monoruby::builtins::range::range_include_impl (cyclomatic 74) monoruby/src/builtins/range.rs:441— monoruby::builtins::range::range_include_impl has cyclomatic complexity 74 (threshold 15). Of this number, 70 points are the body's own statements and 4 belong to 2 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.
monoruby::prof::report (cyclomatic 74) monoruby/src/prof.rs:2031— monoruby::prof::report has cyclomatic complexity 74 (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.
monoruby::value::rvalue::string::pack::parse_template (cyclomatic 68) monoruby/src/value/rvalue/string/pack.rs:1375— monoruby::value::rvalue::string::pack::parse_template has cyclomatic complexity 68 (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.
monoruby::builtins::spawn::parse_exec_args (cyclomatic 59) monoruby/src/builtins/spawn.rs:134— monoruby::builtins::spawn::parse_exec_args has cyclomatic complexity 59 (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.
monoruby::builtins::io::io_select (cyclomatic 57) monoruby/src/builtins/io.rs:5457— monoruby::builtins::io::io_select has cyclomatic complexity 57 (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.
monoruby::builtins::io::io_copy_stream (cyclomatic 53) monoruby/src/builtins/io.rs:6806— monoruby::builtins::io::io_copy_stream 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.
monoruby::builtins::io::io_init_from_fd (cyclomatic 50) monoruby/src/builtins/io.rs:273— monoruby::builtins::io::io_init_from_fd has cyclomatic complexity 50 (threshold 15). Of this number, 49 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
monoruby::builtins::io::io_popen (cyclomatic 48) monoruby/src/builtins/io.rs:3275— monoruby::builtins::io::io_popen has cyclomatic complexity 48 (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.
monoruby::executor::op::integer_index1 (cyclomatic 47) monoruby/src/executor/op.rs:1852— monoruby::executor::op::integer_index1 has cyclomatic complexity 47 (threshold 15). Of this number, 41 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.
monoruby::builtins::io::copy_stream_fds (cyclomatic 44) monoruby/src/builtins/io.rs:7168— monoruby::builtins::io::copy_stream_fds has cyclomatic complexity 44 (threshold 15). Of this number, 40 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.
monoruby::builtins::time::directive_core (cyclomatic 44) monoruby/src/builtins/time.rs:3518— monoruby::builtins::time::directive_core has cyclomatic complexity 44 (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.
monoruby::builtins::encoding::converter_primitive_convert (cyclomatic 41) monoruby/src/builtins/encoding.rs:3264— monoruby::builtins::encoding::converter_primitive_convert has cyclomatic complexity 41 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: monoruby::builtins::encoding::enc_name_to_const (cyclomatic 104) 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.
monoruby::builtins::string::slice_ (cyclomatic 40) monoruby/src/builtins/string.rs:3875— monoruby::builtins::string::slice_ has cyclomatic complexity 40 (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.
monoruby::parse_short_cluster (cyclomatic 40) monoruby/src/main.rs:344— monoruby::parse_short_cluster has cyclomatic complexity 40 (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.
monoruby::codegen::runtime::args::set_callee_frame_arguments (cyclomatic 39) monoruby/src/codegen/runtime/args.rs:807— monoruby::codegen::runtime::args::set_callee_frame_arguments has cyclomatic complexity 39 (threshold 15). Of this number, 38 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.
monoruby::builtins::file::open_impl (cyclomatic 36) monoruby/src/builtins/file.rs:1302— monoruby::builtins::file::open_impl 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.
monoruby::builtins::string::parse_undump (cyclomatic 35) monoruby/src/builtins/string.rs:12983— monoruby::builtins::string::parse_undump 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.
FileTooLong: builtins/string.rs monoruby/src/builtins/string.rs— FileTooLong — 7455 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 308 free functions. The bar is 500 significant lines; this is 6955 over it, 14.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: builtins/io.rs monoruby/src/builtins/io.rs— FileTooLong — 4455 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 174 free functions. The bar is 500 significant lines; this is 3955 over it, 8.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: builtins/kernel.rs monoruby/src/builtins/kernel.rs— FileTooLong — 4102 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 192 free functions. The bar is 500 significant lines; this is 3602 over it, 8.20× 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: string/transcode.rs monoruby/src/value/rvalue/string/transcode.rs— FileTooLong — 4069 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 138 free functions. The bar is 500 significant lines; this is 3569 over it, 8.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: rvalue/string.rs monoruby/src/value/rvalue/string.rs— FileTooLong — 3873 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 104 free functions. The bar is 500 significant lines; this is 3373 over it, 7.75× 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: parser/prism_backend.rs monoruby/src/parser/prism_backend.rs— FileTooLong — 3728 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 80% of them inside a single declaration: Lowerer (2 blocks, 657-5584), declaring 43 free functions. The bar is 500 significant lines; this is 3228 over it, 7.46× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/executor.rs monoruby/src/executor.rs— FileTooLong — 3286 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: Executor (13 blocks, 275-6099). The bar is 500 significant lines; this is 2786 over it, 6.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: builtins/encoding.rs monoruby/src/builtins/encoding.rs— FileTooLong — 2995 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 134 free functions. The bar is 500 significant lines; this is 2495 over it, 5.99× 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: builtins/array.rs monoruby/src/builtins/array.rs— FileTooLong — 2979 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 146 free functions. The bar is 500 significant lines; this is 2479 over it, 5.96× 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: rvalue/regexp.rs monoruby/src/value/rvalue/regexp.rs— FileTooLong — 2530 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 35 free functions. The bar is 500 significant lines; this is 2030 over it, 5.06× 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: builtins/time.rs monoruby/src/builtins/time.rs— FileTooLong — 2514 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 146 free functions. The bar is 500 significant lines; this is 2014 over it, 5.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/value.rs monoruby/src/value.rs— FileTooLong — 2201 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 68% of them inside a single declaration: Value (20 blocks, 240-4090), declaring 33 free functions. The bar is 500 significant lines; this is 1701 over it, 4.40× 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: builtins/module.rs monoruby/src/builtins/module.rs— FileTooLong — 2197 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 116 free functions. The bar is 500 significant lines; this is 1697 over it, 4.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: builtins/hash.rs monoruby/src/builtins/hash.rs— FileTooLong — 2158 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 141 free functions. The bar is 500 significant lines; this is 1658 over it, 4.32× 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: globals/store.rs monoruby/src/globals/store.rs— FileTooLong — 2007 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: Store (20 blocks, 110-3083). The bar is 500 significant lines; this is 1507 over it, 4.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: builtins/json.rs monoruby/src/builtins/json.rs— FileTooLong — 2001 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 84 free functions. The bar is 500 significant lines; this is 1501 over it, 4.00× 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: value/rvalue.rs monoruby/src/value/rvalue.rs— FileTooLong — 1861 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: RValue (12 blocks, 659-3133). The bar is 500 significant lines; this is 1361 over it, 3.72× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/prof.rs monoruby/src/prof.rs— FileTooLong — 1810 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 46 free functions. The bar is 500 significant lines; this is 1310 over it, 3.62× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/ext.rs monoruby/src/ext.rs— FileTooLong — 1804 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 128 free functions. The bar is 500 significant lines; this is 1304 over it, 3.61× 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: builtins/marshal.rs monoruby/src/builtins/marshal.rs— FileTooLong — 1776 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 37 free functions. The bar is 500 significant lines; this is 1276 over it, 3.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: builtins/file.rs monoruby/src/builtins/file.rs— FileTooLong — 1764 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 106 free functions. The bar is 500 significant lines; this is 1264 over it, 3.53× 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: store/class.rs monoruby/src/globals/store/class.rs— FileTooLong — 1712 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 1212 over it, 3.42× 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: bytecodegen/expression.rs monoruby/src/bytecodegen/expression.rs— FileTooLong — 1690 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: BytecodeGen (5 blocks, 52-2674). The bar is 500 significant lines; this is 1190 over it, 3.38× 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: gem/gosu.rb monoruby/gem/gosu.rb— FileTooLong — 1588 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1088 over it, 3.18× 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: string/pack.rs monoruby/src/value/rvalue/string/pack.rs— FileTooLong — 1491 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 35 free functions. The bar is 500 significant lines; this is 991 over it, 2.98× 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.
Hotspot: monoruby/src/codegen/jitgen/asmir/compile_shared.rs monoruby/src/codegen/jitgen/asmir/compile_shared.rs:34— monoruby/src/codegen/jitgen/asmir/compile_shared.rs changed 64 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 209 in Codegen::compile_asmir at line 34. 2 of those changes were fix/bug commits, and the other 62 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/jitgen/asmir/compile_shared.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: monoruby/src/codegen/jitgen/compile.rs monoruby/src/codegen/jitgen/compile.rs:419— monoruby/src/codegen/jitgen/compile.rs changed 84 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 149 in JitContext::compile_instruction_inner at line 419. 9 of those changes were fix/bug commits, and the other 75 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/jitgen/compile.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: monoruby/src/codegen/jitgen/compile/method_call.rs monoruby/src/codegen/jitgen/compile/method_call.rs:781— monoruby/src/codegen/jitgen/compile/method_call.rs changed 94 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 109 in JitContext::compile_method_call at line 781. 10 of those changes were fix/bug commits, and the other 84 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/jitgen/compile/method_call.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: monoruby/src/value/rvalue/string.rs monoruby/src/value/rvalue/string.rs:5600— monoruby/src/value/rvalue/string.rs changed 51 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 197 in monoruby::value::rvalue::string::transcode_bytes_with_opts at line 5600. 8 of those changes were fix/bug commits, and the other 43 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/value/rvalue/string.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: monoruby/src/codegen/arch/x86_64/compile/mod.rs monoruby/src/codegen/arch/x86_64/compile/mod.rs:353— monoruby/src/codegen/arch/x86_64/compile/mod.rs changed 73 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 125 in Codegen::encode_linst at line 353. 3 of those changes were fix/bug commits, and the other 70 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/arch/x86_64/compile/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: monoruby/src/builtins/string.rs monoruby/src/builtins/string.rs:3331— monoruby/src/builtins/string.rs changed 85 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 94 in monoruby::builtins::string::split at line 3331. 11 of those changes were fix/bug commits, and the other 74 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/builtins/string.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: monoruby/src/codegen/arch/aarch64/compile/mod.rs monoruby/src/codegen/arch/aarch64/compile/mod.rs:1575— monoruby/src/codegen/arch/aarch64/compile/mod.rs changed 70 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 113 in Codegen::encode_linst at line 1575. 1 of those changes was a fix/bug commit, and the other 69 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/arch/aarch64/compile/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: monoruby/src/builtins/encoding.rs monoruby/src/builtins/encoding.rs:3264— monoruby/src/builtins/encoding.rs changed 72 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in monoruby::builtins::encoding::converter_primitive_convert at line 3264. 8 of those changes were fix/bug commits, and the other 64 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/builtins/encoding.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: monoruby/src/codegen/jitgen/state/slot.rs monoruby/src/codegen/jitgen/state/slot.rs:3428— monoruby/src/codegen/jitgen/state/slot.rs changed 63 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in AbstractFrame::bridge at line 3428. 3 of those changes were fix/bug commits, and the other 60 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/jitgen/state/slot.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: monoruby/src/bytecodegen/expression.rs monoruby/src/bytecodegen/expression.rs:458— monoruby/src/bytecodegen/expression.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 106 in BytecodeGen::gen_expr_inner at line 458. 1 of those changes was a fix/bug commit, and the other 24 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/bytecodegen/expression.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: monoruby/src/parser/prism_backend.rs monoruby/src/parser/prism_backend.rs:1105— monoruby/src/parser/prism_backend.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 142 in Lowerer::lower_node at line 1105. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/parser/prism_backend.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: monoruby/src/executor.rs monoruby/src/executor.rs:2486— monoruby/src/executor.rs changed 87 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Executor::take_ex_obj at line 2486. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/executor.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: monoruby/src/value.rs monoruby/src/value.rs:3729— monoruby/src/value.rs changed 53 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in Value::from_ast_inner at line 3729. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/value.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: monoruby/src/value/rvalue/regexp.rs monoruby/src/value/rvalue/regexp.rs:846— monoruby/src/value/rvalue/regexp.rs changed 38 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in Preprocess::unescape_nonascii at line 846. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/value/rvalue/regexp.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: monoruby/src/codegen/jitgen.rs monoruby/src/codegen/jitgen.rs:1087— monoruby/src/codegen/jitgen.rs changed 66 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in Codegen::gen_machine_code_inner at line 1087. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/jitgen.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: monoruby/src/codegen/jitgen/asmir.rs monoruby/src/codegen/jitgen/asmir.rs:4432— monoruby/src/codegen/jitgen/asmir.rs changed 80 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in Codegen::gen_asm at line 4432. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/jitgen/asmir.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: monoruby/src/builtins/kernel.rs monoruby/src/builtins/kernel.rs:3560— monoruby/src/builtins/kernel.rs changed 60 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in monoruby::builtins::kernel::system at line 3560. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/builtins/kernel.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: REDACTED REDACTED:1696— REDACTED changed 65 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in monoruby::codegen::runtime::expand_array at line 1696. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- REDACTED`: 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: monoruby/src/codegen/jitgen/context.rs monoruby/src/codegen/jitgen/context.rs:3425— monoruby/src/codegen/jitgen/context.rs changed 86 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in JitContext::resolve_dyn_var_offset_in at line 3425. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/jitgen/context.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: monoruby/src/builtins/io.rs monoruby/src/builtins/io.rs:6806— monoruby/src/builtins/io.rs changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in monoruby::builtins::io::io_copy_stream at line 6806. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/builtins/io.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: monoruby/src/builtins/marshal.rs monoruby/src/builtins/marshal.rs:2499— monoruby/src/builtins/marshal.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 85 in monoruby::builtins::marshal::marshal_dump_value at line 2499. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/builtins/marshal.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: monoruby/src/codegen/jitgen/trace_ir.rs monoruby/src/codegen/jitgen/trace_ir.rs:384— monoruby/src/codegen/jitgen/trace_ir.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 91 in TraceIr::from_pc at line 384. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/codegen/jitgen/trace_ir.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: monoruby/src/value/rvalue/string/pack.rs monoruby/src/value/rvalue/string/pack.rs:731— monoruby/src/value/rvalue/string/pack.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 129 in monoruby::value::rvalue::string::pack::pack at line 731. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/value/rvalue/string/pack.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: monoruby/src/globals/store.rs monoruby/src/globals/store.rs:1561— monoruby/src/globals/store.rs changed 51 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in Store::describe_func at line 1561. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/globals/store.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: monoruby/src/bytecodegen/encode.rs monoruby/src/bytecodegen/encode.rs:186— monoruby/src/bytecodegen/encode.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 87 in BytecodeGen::inst_to_bc at line 186. 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 12:40:57 +09:00' --until='2026-11-17 12:40:57 +09:00' --full-history --no-merges -- monoruby/src/bytecodegen/encode.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.
FunctionTooLong: monoruby::prof::report monoruby/src/prof.rs:2031— FunctionTooLong — monoruby::prof::report runs 625 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 525 over it, 6.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: monoruby::value::rvalue::string::pack::pack monoruby/src/value/rvalue/string/pack.rs:731— FunctionTooLong — monoruby::value::rvalue::string::pack::pack runs 393 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 293 over it, 3.93× 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: monoruby::builtins::marshal::marshal_dump_value monoruby/src/builtins/marshal.rs:2499— FunctionTooLong — monoruby::builtins::marshal::marshal_dump_value 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.
FunctionTooLong: monoruby::builtins::kernel::init monoruby/src/builtins/kernel.rs:26— FunctionTooLong — monoruby::builtins::kernel::init runs 359 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 259 over it, 3.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: monoruby::builtins::string::split monoruby/src/builtins/string.rs:3331— FunctionTooLong — monoruby::builtins::string::split 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: monoruby::value::rvalue::string::pack::unpack monoruby/src/value/rvalue/string/pack.rs:163— FunctionTooLong — monoruby::value::rvalue::string::pack::unpack runs 302 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 202 over it, 3.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.
FunctionTooLong: monoruby::builtins::encoding::init_encoding monoruby/src/builtins/encoding.rs:132— FunctionTooLong — monoruby::builtins::encoding::init_encoding runs 286 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 186 over it, 2.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.
FunctionTooLong: monoruby::main monoruby/src/main.rs:614— FunctionTooLong — monoruby::main runs 277 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 177 over it, 2.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: monoruby::builtins::string::init monoruby/src/builtins/string.rs:18— FunctionTooLong — monoruby::builtins::string::init 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: monoruby::globals::gvar::init_builtin_gvars monoruby/src/globals/gvar.rs:752— FunctionTooLong — monoruby::globals::gvar::init_builtin_gvars runs 239 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 139 over it, 2.39× 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: monoruby::builtins::io::io_copy_stream monoruby/src/builtins/io.rs:6806— FunctionTooLong — monoruby::builtins::io::io_copy_stream runs 232 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 132 over it, 2.32× 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: monoruby::builtins::hash::init monoruby/src/builtins/hash.rs:9— FunctionTooLong — monoruby::builtins::hash::init runs 210 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 110 over it, 2.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.
FunctionTooLong: monoruby::builtins::module::init monoruby/src/builtins/module.rs:7— FunctionTooLong — monoruby::builtins::module::init runs 210 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 110 over it, 2.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.
FunctionTooLong: monoruby::builtins::spawn::parse_exec_args monoruby/src/builtins/spawn.rs:134— FunctionTooLong — monoruby::builtins::spawn::parse_exec_args runs 205 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 105 over it, 2.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: monoruby::builtins::io::io_select monoruby/src/builtins/io.rs:5457— FunctionTooLong — monoruby::builtins::io::io_select runs 195 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 95 over it, 1.95× 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: monoruby::builtins::encoding::converter_primitive_convert monoruby/src/builtins/encoding.rs:3264— FunctionTooLong — monoruby::builtins::encoding::converter_primitive_convert runs 188 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 88 over it, 1.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.
FunctionTooLong: monoruby::builtins::io::io_init_from_fd monoruby/src/builtins/io.rs:273— FunctionTooLong — monoruby::builtins::io::io_init_from_fd runs 165 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 65 over it, 1.65× 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: monoruby::builtins::array::init monoruby/src/builtins/array.rs:14— FunctionTooLong — monoruby::builtins::array::init runs 164 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 64 over it, 1.64× 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: monoruby::builtins::process::init monoruby/src/builtins/process.rs:15— FunctionTooLong — monoruby::builtins::process::init runs 163 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 63 over it, 1.63× 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: monoruby::builtins::io::io_popen monoruby/src/builtins/io.rs:3275— FunctionTooLong — monoruby::builtins::io::io_popen runs 162 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 62 over it, 1.62× 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: monoruby::builtins::file::open_impl monoruby/src/builtins/file.rs:1302— FunctionTooLong — monoruby::builtins::file::open_impl 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: nokogiri_native::node::init ext/nokogiri/src/node.rs:8— FunctionTooLong — nokogiri_native::node::init runs 158 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: monoruby::builtins::io::init monoruby/src/builtins/io.rs:9— FunctionTooLong — monoruby::builtins::io::init runs 155 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 55 over it, 1.55× 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: monoruby::builtins::io::copy_stream_fds monoruby/src/builtins/io.rs:7168— FunctionTooLong — monoruby::builtins::io::copy_stream_fds runs 153 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 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: monoruby::builtins::string::slice_ monoruby/src/builtins/string.rs:3875— FunctionTooLong — monoruby::builtins::string::slice_ runs 151 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
TooManyMethods: Codegen monoruby/src/codegen.rs:983— TooManyMethods — 631 methods, declared across 42 files: compile/mod.rs (110), x86_64/vmgen.rs (63), aarch64/vmgen.rs (56), compile/builtin.rs (39), +38 more file(s). The bar is 30 methods; this is 601 over it, 21.03× 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: Value monoruby/src/value.rs:240— TooManyMethods — 314 methods, declared across 2 files: src/value.rs (283), value/coerce.rs (31). The bar is 30 methods; this is 284 over it, 10.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Executor monoruby/src/executor.rs:275— TooManyMethods — 308 methods, declared across 6 files: src/executor.rs (248), executor/op.rs (28), executor/constants.rs (24), executor/frame.rs (5), +2 more file(s). The bar is 30 methods; this is 278 over it, 10.27× 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: BytecodeGen monoruby/src/bytecodegen.rs:648— TooManyMethods — 204 methods, declared across 8 files: src/bytecodegen.rs (107), bytecodegen/expression.rs (44), bytecodegen/method_call.rs (12), bytecodegen/binary.rs (11), +4 more file(s). The bar is 30 methods; this is 174 over it, 6.80× 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: Store monoruby/src/globals/store.rs:110— TooManyMethods — 199 methods, declared across 6 files: globals/store.rs (142), store/class.rs (32), store/refinement.rs (9), class/instance_var.rs (7), +2 more file(s). The bar is 30 methods; this is 169 over it, 6.63× 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: RValue monoruby/src/value/rvalue.rs:659— TooManyMethods — 181 methods. The bar is 30 methods; this is 151 over it, 6.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.
TooManyMethods: Globals monoruby/src/globals.rs:360— TooManyMethods — 171 methods, declared across 7 files: src/globals.rs (74), globals/method.rs (64), globals/require.rs (13), globals/gvar.rs (11), +3 more file(s). The bar is 30 methods; this is 141 over it, 5.70× 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: MonorubyErr monoruby/src/globals/error.rs:110— TooManyMethods — 139 methods. The bar is 30 methods; this is 109 over it, 4.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: IoInner monoruby/src/value/rvalue/io.rs:621— 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: AbstractMemory monoruby/gem/ffi_c.rb:270— TooManyMethods — 108 methods. The bar is 30 methods; this is 78 over it, 3.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: JitModule monoruby/src/codegen.rs:494— TooManyMethods — 96 methods, declared across 7 files: x86_64/jit_module.rs (27), aarch64/invoker.rs (26), codegen/jitgen.rs (19), src/codegen.rs (9), +3 more file(s). The bar is 30 methods; this is 66 over it, 3.20× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RubyMap rubymap/src/map.rs:76— TooManyMethods — 92 methods. The bar is 30 methods; this is 62 over it, 3.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: Lowerer monoruby/src/parser/prism_backend.rs:657— TooManyMethods — 86 methods. The bar is 30 methods; this is 56 over it, 2.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: ClassInfoTable monoruby/src/globals/store.rs:3085— TooManyMethods — 80 methods, declared across 3 files: store/class.rs (57), class/constants.rs (15), globals/store.rs (8). The bar is 30 methods; this is 50 over it, 2.67× 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: RegexpInner monoruby/src/value/rvalue/regexp.rs:179— 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: Node monoruby/gem/nokogiri/xml/node.rb:56— TooManyMethods — 77 methods. The bar is 30 methods; this is 47 over it, 2.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: Allocator monoruby/src/alloc.rs:789— TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ISeqInfo monoruby/src/globals/store/iseq.rs:262— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RStringInner monoruby/src/value/rvalue/string.rs:3079— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FuncInfo monoruby/src/globals/store/function.rs:934— TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.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: ClassInfo monoruby/src/globals/store/class.rs:325— TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Ctx monoruby_ext/src/lib.rs:163— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× 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: RubySet rubymap/src/set.rs:74— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× 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: Pointer monoruby/stdlib/fiddle.rb:97— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StringScanner monoruby/stdlib/strscan.rb:28— 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.
Duplicated block (7 lines × 2) ext/nokogiri/src/sax.rs:714— ext/nokogiri/src/sax.rs:714-720 | ext/nokogiri/src/sax.rs:733-739 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/sax.rs:714` 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) monoruby/src/builtins/array.rs:2050— monoruby/src/builtins/array.rs:2050-2056 | monoruby/src/builtins/array.rs:2062-2068 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:2050` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/array.rs:2219— monoruby/src/builtins/array.rs:2219-2225 | monoruby/src/builtins/array.rs:2244-2250 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:2219` 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) monoruby/src/builtins/array.rs:3324— monoruby/src/builtins/array.rs:3324-3330 | monoruby/src/builtins/array.rs:3464-3470 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:3324` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/binding.rs:177— monoruby/src/builtins/binding.rs:177-183 | monoruby/src/builtins/binding.rs:206-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.
Duplicated block (7 lines × 2) monoruby/src/builtins/dir.rs:751— monoruby/src/builtins/dir.rs:751-757 | monoruby/src/builtins/dir.rs:793-802 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/dir.rs:751` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/hash.rs:3448— monoruby/src/builtins/hash.rs:3448-3454 | monoruby/src/builtins/hash.rs:3499-3505 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/hash.rs:3448` 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) monoruby/src/builtins/hash.rs:3497— monoruby/src/builtins/hash.rs:3497-3503 | monoruby/src/builtins/hash.rs:3591-3597 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/hash.rs:3497` it does not close everything it opens, so those 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, `monoruby/src/builtins/hash.rs:3598` calls `temp_push`, `hash`, `default` and `monoruby/src/builtins/hash.rs:3504` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) monoruby/src/builtins/io.rs:4982— monoruby/src/builtins/io.rs:4982-4988 | monoruby/src/builtins/io.rs:5716-5727 — both copies are in the same file, so extract the 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 (7 lines × 2) monoruby/src/builtins/io_buffer.rs:775— monoruby/src/builtins/io_buffer.rs:775-781 | monoruby/src/builtins/io_buffer.rs:1602-1608 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) monoruby/src/builtins/kernel.rs:4076— monoruby/src/builtins/kernel.rs:4076-4082 | monoruby/src/scheduler.rs:1720-1726 — 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 `monoruby/src/builtins/kernel.rs:4076` it does not close everything it opens, so those exact lines 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) REDACTED:597— REDACTED:597-603 | REDACTED:684-690 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:597` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) monoruby/src/builtins/string.rs:5068— monoruby/src/builtins/string.rs:5068-5083 | monoruby/src/builtins/string.rs:5695-5701 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:5068` 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) monoruby/src/builtins/string.rs:10838— monoruby/src/builtins/string.rs:10838-10844 | monoruby/src/builtins/string.rs:10935-10941 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:10838` 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) monoruby/src/builtins/string.rs:10865— monoruby/src/builtins/string.rs:10865-10871 | monoruby/src/builtins/string.rs:10962-10968 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:10865` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/string.rs:11034— monoruby/src/builtins/string.rs:11034-11040 | monoruby/src/builtins/string.rs:11062-11068 — both copies are in the same file, so extract the 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) monoruby/src/builtins/string.rs:12899— monoruby/src/builtins/string.rs:12899-12905 | monoruby/src/value/rvalue/string.rs:3959-3965 — 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 `monoruby/src/builtins/string.rs:12899` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/time.rs:366— monoruby/src/builtins/time.rs:366-372 | monoruby/src/builtins/time.rs:760-766 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/time.rs:366` it does not close everything it opens, so those exact lines 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) monoruby/src/bytecodegen/expression.rs:1303— monoruby/src/bytecodegen/expression.rs:1303-1309 | monoruby/src/bytecodegen/expression.rs:1381-1387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/bytecodegen/expression.rs:1303` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:546— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:546-552 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:602-608 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:546` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1309— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1309-1315 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1402-1408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1309` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:379— monoruby/src/codegen/arch/aarch64/compile/mod.rs:379-385 | monoruby/src/codegen/jitgen/asmir.rs:4475-4481 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/jitgen/asmir.rs` as WHOLE FILES: this scan already matched 6 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:379` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2061— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2061-2067 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4249-4255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:2061` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/x86_64/compile/mod.rs:2562— monoruby/src/codegen/arch/x86_64/compile/mod.rs:2562-2568 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2591-2597 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/x86_64/compile/mod.rs:2562` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/asmir/compile_shared.rs:516— monoruby/src/codegen/jitgen/asmir/compile_shared.rs:516-522 | monoruby/src/codegen/jitgen/asmir/compile_shared.rs:533-540 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/asmir/compile_shared.rs:533` 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) ext/nokogiri/src/document.rs:125— ext/nokogiri/src/document.rs:125-133 | ext/nokogiri/src/document.rs:241-249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/document.rs:125` it does not close everything it opens, so those exact lines 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) ext/nokogiri/src/node.rs:256— ext/nokogiri/src/node.rs:256-264 | ext/nokogiri/src/node.rs:281-289 — both copies are in the same file, so extract the 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) monoruby/src/builtins/hash.rs:1768— monoruby/src/builtins/hash.rs:1768-1778 | monoruby/src/builtins/hash.rs:1799-1807 — both copies are in the same file, so extract the 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) monoruby/src/builtins/hash.rs:3033— monoruby/src/builtins/hash.rs:3033-3041 | monoruby/src/builtins/hash.rs:3299-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 `monoruby/src/builtins/hash.rs:3033` 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) monoruby/src/builtins/io.rs:2837— monoruby/src/builtins/io.rs:2837-2845 | monoruby/src/builtins/io.rs:3025-3033 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/io.rs:2837` it does not close everything it opens, so those 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, `monoruby/src/builtins/io.rs:3024` calls `get_block_data` and `monoruby/src/builtins/io.rs:2836` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) monoruby/src/builtins/marshal.rs:2571— monoruby/src/builtins/marshal.rs:2571-2579 | monoruby/src/builtins/marshal.rs:2906-2916 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/marshal.rs:2906` it does not close everything it opens, so those 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 lines × 2) monoruby/src/builtins/process.rs:1442— monoruby/src/builtins/process.rs:1442-1450 | monoruby/src/builtins/process.rs:1473-1481 — both copies are in the same file, so extract the 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 (9 lines × 2) monoruby/src/builtins/range.rs:730— monoruby/src/builtins/range.rs:730-738 | monoruby/src/builtins/range.rs:749-757 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/range.rs:730` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/set.rs:920— monoruby/src/builtins/set.rs:920-928 | monoruby/src/builtins/set.rs:962-970 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/set.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.
Duplicated block (9 lines × 2) monoruby/src/builtins/set.rs:1013— monoruby/src/builtins/set.rs:1013-1021 | monoruby/src/builtins/set.rs:1117-1125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `monoruby/src/builtins/set.rs:1126` calls `is_empty`, `Ok`, `nil` and `monoruby/src/builtins/set.rs:1022` 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) monoruby/src/builtins/set.rs:1046— monoruby/src/builtins/set.rs:1046-1054 | monoruby/src/builtins/set.rs:1081-1089 — both copies are in the same file, so extract the 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, `monoruby/src/builtins/set.rs:1090` calls `is_empty`, `Ok`, `nil` and `monoruby/src/builtins/set.rs:1055` 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) monoruby/src/builtins/string.rs:4775— monoruby/src/builtins/string.rs:4775-4783 | monoruby/src/builtins/string.rs:4798-4806 — both copies are in the same file, so extract the 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) monoruby/src/builtins/string.rs:5947— monoruby/src/builtins/string.rs:5947-5955 | monoruby/src/value/rvalue/regexp.rs:3193-3201 — 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) monoruby/src/builtins/string.rs:7802— monoruby/src/builtins/string.rs:7802-7810 | monoruby/src/builtins/string.rs:7831-7839 — both copies are in the same file, so extract the 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) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:131— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:131-139 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:293-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:131` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1361— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1361-1369 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1410-1418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1361` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1100— monoruby/src/codegen/arch/aarch64/compile/mod.rs:1100-1108 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3421-3429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.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 (9 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2438— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2438-2446 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2452-2460 — both copies are in the same file, so extract the 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, `monoruby/src/codegen/arch/aarch64/compile/mod.rs:2451` calls `a64_fpr_load` and `monoruby/src/codegen/arch/aarch64/compile/mod.rs:2437` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) monoruby/src/codegen/arch/x86_64/invoker.rs:382— monoruby/src/codegen/arch/x86_64/invoker.rs:382-390 | monoruby/src/codegen/arch/x86_64/invoker.rs:413-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/x86_64/invoker.rs:382` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/trace_ir.rs:422— monoruby/src/codegen/jitgen/trace_ir.rs:422-433 | monoruby/src/codegen/jitgen/trace_ir.rs:435-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 `monoruby/src/codegen/jitgen/trace_ir.rs:422` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) monoruby/src/globals/store.rs:1479— monoruby/src/globals/store.rs:1479-1488 | monoruby/src/globals/store/class.rs:309-317 — 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 `monoruby/src/globals/store.rs:1479` it does not close everything it opens, so those exact lines 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) monoruby/src/scheduler.rs:781— monoruby/src/scheduler.rs:781-792 | monoruby/src/scheduler/native.rs:698-706 — before extracting anything, compare `monoruby/src/scheduler.rs` and `monoruby/src/scheduler/native.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/scheduler.rs:781` it does not close everything it opens, so those 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) monoruby/src/value/rvalue/io.rs:329— monoruby/src/value/rvalue/io.rs:329-340 | monoruby/src/value/rvalue/io.rs:357-365 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/io.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `monoruby/src/value/rvalue/io.rs:326` calls `min` and `monoruby/src/value/rvalue/io.rs:354` 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) monoruby/src/value/rvalue/string/transcode.rs:4799— monoruby/src/value/rvalue/string/transcode.rs:4799-4807 | monoruby/src/value/rvalue/string/transcode.rs:8575-8583 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/transcode.rs:4799` it does not close everything it opens, so those exact lines 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) rubymap/src/map/core.rs:487— rubymap/src/map/core.rs:487-495 | rubymap/src/map/core.rs:706-714 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rubymap/src/map/core.rs:487` 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) ext/nokogiri/src/document.rs:82— ext/nokogiri/src/document.rs:82-89 | ext/nokogiri/src/document.rs:203-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/document.rs:82` 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) ext/nokogiri/src/sax.rs:680— ext/nokogiri/src/sax.rs:680-687 | ext/nokogiri/src/sax.rs:751-758 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/sax.rs:680` 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) ext/nokogiri/src/xpath.rs:242— ext/nokogiri/src/xpath.rs:242-249 | ext/nokogiri/src/xpath.rs:435-442 — both copies are in the same file, so extract the 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) ext/sqlite3/src/lib.rs:665— ext/sqlite3/src/lib.rs:665-672 | ext/sqlite3/src/lib.rs:686-693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/sqlite3/src/lib.rs:665` 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) ext/sqlite3/src/lib.rs:892— ext/sqlite3/src/lib.rs:892-899 | ext/sqlite3/src/lib.rs:1751-1758 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ext/sqlite3/src/lib.rs:1759` calls `stmt_handle` and `ext/sqlite3/src/lib.rs:900` 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 (8 lines × 2) monoruby/src/builtins/argf.rs:473— monoruby/src/builtins/argf.rs:473-480 | monoruby/src/builtins/argf.rs:537-544 — both copies are in the same file, so extract the 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) monoruby/src/builtins/array.rs:3168— monoruby/src/builtins/array.rs:3168-3177 | monoruby/src/builtins/array.rs:3280-3287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:3168` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/binding.rs:470— monoruby/src/builtins/binding.rs:470-477 | monoruby/src/builtins/binding.rs:530-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 `monoruby/src/builtins/binding.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 (8 lines × 2) monoruby/src/builtins/encoding.rs:1908— monoruby/src/builtins/encoding.rs:1908-1915 | monoruby/src/builtins/encoding.rs:2120-2127 — both copies are in the same file, so extract the 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) monoruby/src/builtins/encoding.rs:4654— monoruby/src/builtins/encoding.rs:4654-4661 | monoruby/src/builtins/encoding.rs:5092-5099 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/encoding.rs:4654` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/file.rs:2492— monoruby/src/builtins/file.rs:2492-2499 | monoruby/src/builtins/file.rs:2563-2570 — both copies are in the same file, so extract the 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) monoruby/src/builtins/hash.rs:1200— monoruby/src/builtins/hash.rs:1200-1207 | monoruby/src/builtins/hash.rs:1269-1276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/hash.rs:1200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) monoruby/src/builtins/hash.rs:1979— monoruby/src/builtins/hash.rs:1979-1986 | REDACTED:2743-2750 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) monoruby/src/builtins/io.rs:2973— monoruby/src/builtins/io.rs:2973-2980 | monoruby/src/builtins/io.rs:6078-6085 — both copies are in the same file, so extract the 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) monoruby/src/builtins/process.rs:1857— monoruby/src/builtins/process.rs:1857-1864 | monoruby/src/globals/gvar.rs:720-727 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) monoruby/src/builtins/set.rs:939— monoruby/src/builtins/set.rs:939-946 | monoruby/src/builtins/set.rs:981-988 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/set.rs:939` 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) monoruby/src/builtins/string.rs:4806— monoruby/src/builtins/string.rs:4806-4813 | monoruby/src/builtins/string.rs:4856-4863 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:4806` 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) monoruby/src/builtins/string.rs:5981— monoruby/src/builtins/string.rs:5981-5988 | monoruby/src/value/rvalue/regexp.rs:3760-3767 — 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 `monoruby/src/builtins/string.rs:5981` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/string.rs:10873— monoruby/src/builtins/string.rs:10873-10880 | monoruby/src/builtins/string.rs:10970-10977 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:10873` 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) monoruby/src/bytecodegen.rs:563— monoruby/src/bytecodegen.rs:563-570 | monoruby/src/bytecodegen/expression.rs:488-495 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `monoruby/src/bytecodegen/expression.rs:487` calls `Symbol` and `monoruby/src/bytecodegen.rs:562` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:691— monoruby/src/codegen/arch/aarch64/compile/mod.rs:691-698 | monoruby/src/codegen/jitgen.rs:2523-2530 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `monoruby/src/codegen/arch/aarch64/compile/mod.rs:699` calls `a64` and `monoruby/src/codegen/jitgen.rs:2531` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1072— monoruby/src/codegen/arch/aarch64/compile/mod.rs:1072-1079 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3164-3171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:1072` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2016— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2016-2023 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4253-4260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:2016` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2188— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2188-2195 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2201-2208 — both copies are in the same file, so extract the 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) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:735— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:735-742 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:917-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.
Duplicated block (6 lines × 2) ext/sqlite3/src/lib.rs:1280— ext/sqlite3/src/lib.rs:1280-1285 | ext/sqlite3/src/lib.rs:1409-1414 — both copies are in the same file, so extract the 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, `ext/sqlite3/src/lib.rs:1407` calls `aggregate_instance`, `temp_push` and `ext/sqlite3/src/lib.rs:1279` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) monoruby/src/builtins/array.rs:2495— monoruby/src/builtins/array.rs:2495-2500 | monoruby/src/builtins/array.rs:2521-2526 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:2495` 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) monoruby/src/builtins/array.rs:3332— monoruby/src/builtins/array.rs:3332-3337 | monoruby/src/builtins/array.rs:3472-3477 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:3332` 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) monoruby/src/builtins/io.rs:5715— monoruby/src/builtins/io.rs:5715-5725 | monoruby/src/scheduler.rs:1620-1625 — 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 `monoruby/src/builtins/io.rs:5715` it does not close everything it opens, so those 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) monoruby/src/builtins/io_buffer.rs:689— monoruby/src/builtins/io_buffer.rs:689-694 | monoruby/src/builtins/io_buffer.rs:1190-1195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/io_buffer.rs:689` 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) monoruby/src/builtins/marshal.rs:2599— monoruby/src/builtins/marshal.rs:2599-2604 | monoruby/src/builtins/marshal.rs:2613-2619 — both copies are in the same file, so extract the 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 (6 lines × 2) monoruby/src/builtins/regexp.rs:1409— monoruby/src/builtins/regexp.rs:1409-1418 | monoruby/src/builtins/regexp.rs:1570-1575 — both copies are in the same file, so extract the 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) monoruby/src/builtins/set.rs:1300— monoruby/src/builtins/set.rs:1300-1305 | monoruby/src/builtins/set.rs:1350-1355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/set.rs:1300` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) monoruby/src/builtins/spawn.rs:840— monoruby/src/builtins/spawn.rs:840-845 | monoruby/src/builtins/spawn.rs:874-879 — both copies are in the same file, so extract the 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) monoruby/src/builtins/string.rs:5094— monoruby/src/builtins/string.rs:5094-5099 | monoruby/src/builtins/string.rs:5712-5717 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:5094` 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) monoruby/src/builtins/string.rs:10831— monoruby/src/builtins/string.rs:10831-10836 | monoruby/src/builtins/string.rs:10928-10933 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:10831` 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) monoruby/src/bytecodegen/statement.rs:371— monoruby/src/bytecodegen/statement.rs:371-376 | monoruby/src/bytecodegen/statement.rs:397-402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/bytecodegen/statement.rs:371` 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) monoruby/src/codegen.rs:1453— monoruby/src/codegen.rs:1453-1458 | monoruby/src/codegen.rs:1464-1469 — both copies are in the same file, so extract the 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) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1169— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1169-1174 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4248-4253 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1169` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/x86_64/compile/mod.rs:856— monoruby/src/codegen/arch/x86_64/compile/mod.rs:856-861 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:938-943 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/x86_64/compile/mod.rs:856` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/compile/binary_op.rs:820— monoruby/src/codegen/jitgen/compile/binary_op.rs:820-825 | monoruby/src/codegen/jitgen/compile/binary_op.rs:1094-1099 — both copies are in the same file, so extract the 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) monoruby/src/codegen/jitgen/compile/method_call.rs:1404— monoruby/src/codegen/jitgen/compile/method_call.rs:1404-1409 | monoruby/src/codegen/jitgen/compile/method_call.rs:1481-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 (6 lines × 2) monoruby/src/codegen/runtime/args.rs:356— monoruby/src/codegen/runtime/args.rs:356-361 | monoruby/src/codegen/runtime/args.rs:678-683 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) monoruby/src/parser/prism_backend.rs:2056— monoruby/src/parser/prism_backend.rs:2056-2061 | monoruby/src/parser/prism_backend.rs:2080-2085 — both copies are in the same file, so extract the 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) monoruby/src/parser/prism_backend.rs:3019— monoruby/src/parser/prism_backend.rs:3019-3024 | monoruby/src/parser/prism_backend.rs:3145-3150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/parser/prism_backend.rs:3019` it does not close everything it opens, so those exact lines 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) monoruby/src/parser/prism_backend.rs:5100— monoruby/src/parser/prism_backend.rs:5100-5105 | monoruby/src/parser/prism_backend.rs:5192-5197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/parser/prism_backend.rs:5100` it does not close everything it opens, so those exact lines 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) monoruby/src/value/rvalue/io.rs:1778— monoruby/src/value/rvalue/io.rs:1778-1783 | monoruby/src/value/rvalue/io.rs:2158-2163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/io.rs:1778` it does not close everything it opens, so those exact lines 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) monoruby/src/value/rvalue/string/pack.rs:244— monoruby/src/value/rvalue/string/pack.rs:244-249 | monoruby/src/value/rvalue/string/pack.rs:256-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/pack.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. 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, `monoruby/src/value/rvalue/string/pack.rs:249` calls `push`, `nil` and `monoruby/src/value/rvalue/string/pack.rs:262` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) rubymap/src/map/core.rs:832— rubymap/src/map/core.rs:832-837 | rubymap/src/map/core.rs:905-910 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rubymap/src/map/core.rs:832` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) monoruby/src/builtins/dir.rs:206— monoruby/src/builtins/dir.rs:206-211 | monoruby/src/builtins/dir.rs:1017-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.
Duplicated block (5 lines × 2) ext/markly/src/lib.rs:369— ext/markly/src/lib.rs:369-373 | ext/markly/src/lib.rs:382-386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) monoruby/src/builtins/array.rs:3060— monoruby/src/builtins/array.rs:3060-3064 | monoruby/src/builtins/array.rs:3328-3332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:3060` it does not close everything it opens, so those 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, `monoruby/src/builtins/array.rs:3066` calls `push` and `monoruby/src/builtins/array.rs:3333` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) monoruby/src/builtins/array.rs:3731— monoruby/src/builtins/array.rs:3731-3735 | monoruby/src/builtins/array.rs:5136-5140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:3731` 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, `monoruby/src/builtins/array.rs:5135` calls `Ok`, `nil` and `monoruby/src/builtins/array.rs:3730` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) monoruby/src/builtins/hash.rs:2799— monoruby/src/builtins/hash.rs:2799-2803 | monoruby/src/builtins/hash.rs:3597-3601 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/hash.rs:2799` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/hash.rs:3187— monoruby/src/builtins/hash.rs:3187-3191 | monoruby/src/builtins/hash.rs:3274-3278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) monoruby/src/builtins/kernel.rs:2961— monoruby/src/builtins/kernel.rs:2961-2965 | monoruby/src/builtins/kernel.rs:3193-3197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/kernel.rs:2961` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) monoruby/src/builtins/marshal.rs:1315— monoruby/src/builtins/marshal.rs:1315-1322 | monoruby/src/builtins/marshal.rs:1534-1538 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/marshal.rs:1315` 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 (5 lines × 2) monoruby/src/builtins/numeric/complex.rs:497— monoruby/src/builtins/numeric/complex.rs:497-501 | monoruby/src/builtins/numeric/complex.rs:503-507 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) monoruby/src/builtins/object.rs:476— monoruby/src/builtins/object.rs:476-482 | monoruby/src/builtins/symbol.rs:654-658 — 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 `monoruby/src/builtins/object.rs:476` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/range.rs:673— monoruby/src/builtins/range.rs:673-677 | monoruby/src/builtins/range.rs:687-691 — both copies are in the same file, so extract the 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 (5 lines × 2) monoruby/src/builtins/string.rs:1270— monoruby/src/builtins/string.rs:1270-1274 | monoruby/src/builtins/string.rs:1389-1393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:1270` 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) monoruby/src/builtins/string.rs:8067— monoruby/src/builtins/string.rs:8067-8071 | monoruby/src/builtins/string.rs:8141-8148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:292— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:292-296 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:340-344 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:292` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:402— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:402-406 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2061-2065 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:402` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1092— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1092-1097 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1179-1183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:151— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:151-155 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:316-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 `monoruby/src/codegen/arch/x86_64/compile/method_call.rs:151` 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 (5 lines × 2) monoruby/src/globals/store/class.rs:1205— monoruby/src/globals/store/class.rs:1205-1209 | monoruby/src/globals/store/class.rs:1223-1231 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/globals/store/class.rs:1205` 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 (5 lines × 2) monoruby/src/value.rs:4145— monoruby/src/value.rs:4145-4149 | monoruby/src/value.rs:4163-4167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value.rs:4145` it does not close everything it opens, so those exact lines 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) monoruby/src/value.rs:4154— monoruby/src/value.rs:4154-4158 | monoruby/src/value.rs:4172-4176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value.rs:4154` 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 (5 lines × 2) monoruby/src/value/rvalue/fiber.rs:361— monoruby/src/value/rvalue/fiber.rs:361-365 | monoruby/src/value/rvalue/fiber.rs:556-560 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/fiber.rs:361` it does not close everything it opens, so those 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, `monoruby/src/value/rvalue/fiber.rs:367` calls `set_error` and `monoruby/src/value/rvalue/fiber.rs:562` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) ext/nokogiri/src/document.rs:308— ext/nokogiri/src/document.rs:308-312 | ext/nokogiri/src/node.rs:554-558 — 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 (5 lines × 2) monoruby/src/builtins/io_buffer.rs:18— monoruby/src/builtins/io_buffer.rs:18-23 | monoruby/src/fork.rs:267-271 — 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 (5 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:60— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:60-64 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:504-508 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:60` 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) rubymap/src/map.rs:1410— rubymap/src/map.rs:1410-1414 | rubymap/src/set.rs:891-895 — 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 (5 lines × 2) monoruby/src/executor/format.rs:1420— monoruby/src/executor/format.rs:1420-1424 | monoruby/src/executor/format.rs:1470-1475 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/executor/format.rs:1420` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
+ 16 more in this group — see findings.md.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×40
Recursive walk over a caller-supplied document has no depth cap rubymap/src/set/iter.rs:54— `len` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 54 with a piece of the document (and at line 109, line 161) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/set/iter.rs:63— `clone` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 63 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `clone` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/set/iter.rs:145— `as_slice` is public and takes a `Drain` as its receiver from its caller, and it calls itself at line 145 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_slice` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/map/iter.rs:53— `as_slice` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 53 with a piece of the document (and at line 113, line 236, line 293) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_slice` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/map/iter.rs:69— `len` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 69 with a piece of the document (and at line 136, line 257, line 309) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/map/iter.rs:79— `clone` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 79 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `clone` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/map/iter.rs:120— `into_slice` is public and takes a `IterMut` as its receiver from its caller, and it calls itself at line 120 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `into_slice` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/map/iter.rs:241— `as_mut_slice` is public and takes a `IntoIter` as its receiver from its caller, and it calls itself at line 241 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_mut_slice` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/map/core/entry.rs:172— `index` is public and takes a `OccupiedEntry` as its receiver from its caller, and it recurses at line 172 through `get` and back with a piece of the document (and at line 191) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `index` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/map/core/entry.rs:229— `remove` is public and takes a `OccupiedEntry` as its receiver from its caller, and it recurses at line 229 through `swap_remove_entry`, `swap_remove` and back with a piece of the document (and at line 240, line 274) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `remove` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap rubymap/src/map/core/entry.rs:305— `move_index` is public and takes a `OccupiedEntry` as its receiver from its caller, and it calls itself at line 305 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `move_index` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/executor.rs:598— `mark` is public and takes a `Executor` as its receiver from its caller, and it calls itself at line 598 with a piece of the document (and at line 601, line 613, line 621, line 625, line 628, line 633, line 636, line 641, line 644, line 650, line 656, line 658, line 665, line 666, line 669) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `mark` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/executor.rs:831— `method_func_id` is public and takes a `Executor` as its receiver from its caller, and it calls itself at line 831 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `method_func_id` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/executor.rs:5436— `generate_proc_inner` is public and takes a `Executor` as its receiver from its caller, and it recurses at line 5436 through `materialize_escaped_block_handlers` and back with a piece of the document (and at line 5606) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `generate_proc_inner` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/value/rvalue/hash.rs:1958— `next` is public and takes a `Iter` as its receiver from its caller, and it calls itself at line 1958 with a piece of the document (and at line 1959, line 1964) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `next` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/executor/frame.rs:87— `prev` is public, takes a document from its caller (line 93) and hands it to `as_ptr`, which calls itself at line 87 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_ptr` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/codegen/jitgen.rs:759— `format` is public, takes a document from its caller (line 742) and hands it to `format_inner`, which calls itself at line 759 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `format_inner` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/codegen/jitgen.rs:1030— `jit_compile` is public, takes a document from its caller (line 765) and hands it to `unit_inst_len`, which calls itself at line 1030 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `unit_inst_len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/codegen/jitgen/asmir.rs:665— `push` is public and takes a `AsmIr` as its receiver from its caller, and it calls itself at line 665 with a piece of the document (and at line 631) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `push` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/codegen/jitgen/asmir.rs:724— `is_empty` is public and takes a `AsmIr` as its receiver from its caller, and it calls itself at line 724 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `is_empty` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/codegen/jitgen/context.rs:319— `reads_frame_header` is public and takes a `AsmInfo` as its receiver from its caller, and it calls itself at line 319 with a piece of the document (and at line 323, line 327) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `reads_frame_header` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/builtins/array.rs:2860— `min` is public and takes `vm: &mut Executor` from its caller, and it calls itself at line 2860 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `min` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/src/builtins/array.rs:2964— `max` is public and takes `vm: &mut Executor` from its caller, and it calls itself at line 2964 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `max` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/gem/json/generic_object.rb:30— `from_hash` is public and takes `object` — which it walks as a `Hash` — from its caller, and it calls itself at line 30 (`self.from_hash`) with a piece of `object` (and at line 34) — and nowhere in `from_hash` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `from_hash` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap monoruby/builtins/ractor.rb:159— `make_shareable` is public, takes a document from its caller (line 115) and hands it to `__deep_freeze`, which walks `obj` as a `Hash` and calls itself at line 159 (`self.__deep_freeze`) with a piece of `obj` (and at line 161, line 163, line 165, line 166, line 170) — and nowhere in `__deep_freeze` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `__deep_freeze` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
+ 15 more in this group — see findings.md.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×40
Symbol treated as nullable, then dereferenced unguarded rubymap/src/hasher.rs:34— `bytes[..8].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `read8` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded rubymap/src/hasher.rs:39— `bytes[..4].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `read4` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded rubymap/src/map.rs:108— `other.get(k1,&mut(),&mut())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `eq` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded rubymap/src/map.rs:125— `self.get(key,&mut(),&mut())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded rubymap/src/map.rs:125— `self.get(key,&mut(),&mut()).unwrap()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded rubymap/src/map/core.rs:153— `table.find_mut(hash.get(),move|&i,_,_|Ok(i==old),e,g)?` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `update_index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded rubymap/src/map/core/entry.rs:333— `indices.find_entry(hash.get(),move|&i,_,_|Ok(i==index),e,g)?` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `from_index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded rubymap/src/map/core/entry.rs:483— `self.map.swap_remove_index(self.index,e,g)?` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `swap_remove_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded rubymap/src/map/core/entry.rs:494— `self.map.shift_remove_index(self.index,e,g)?` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `shift_remove_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby_ext/src/lib.rs:697— `slot.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `thunk` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby_ext/src/lib.rs:732— `CString::new(s.as_bytes().iter().copied().take_while(|&b|b!=0).collect::<Vec<u8>>(),)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cstring` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:43— `dirs::home_dir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:134— `fs::create_dir_all(&lib_path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:138— `fs::remove_dir_all(&staging)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:141— `fs::create_dir_all(dir)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:203— `copy_dir_all(src,dst)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:221— `hash_tree(&staging,&mut hasher)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:271— `fs::write(&stamp,tree_stamp)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:298— `std::env::var_os("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_extensions` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:399— `std::env::var_os("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:401— `fs::create_dir_all(capi_dir)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:402— `fs::copy(&out,capi_dir.join("libmonoruby_capi.a"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_capi_archive` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:421— `fs::read_to_string(list)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_cruby_header_names` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:429— `path.parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_cruby_header_names` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded monoruby/build.rs:429— `fs::create_dir_all(path.parent().unwrap())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `install_cruby_header_names` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Duplicated block (11 lines × 2) ext/nokogiri/src/document.rs:109— ext/nokogiri/src/document.rs:109-119 | ext/nokogiri/src/document.rs:225-235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/document.rs:109` 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) monoruby/src/builtins/binding.rs:124— monoruby/src/builtins/binding.rs:124-134 | monoruby/src/builtins/kernel.rs:3465-3475 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `monoruby/src/builtins/kernel.rs:3464` calls `nearest_ruby_frame` and `monoruby/src/builtins/binding.rs:123` 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 × 2) monoruby/src/builtins/binding.rs:321— monoruby/src/builtins/binding.rs:321-331 | monoruby/src/builtins/binding.rs:349-359 — both copies are in the same file, so extract the 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) monoruby/src/builtins/io.rs:443— monoruby/src/builtins/io.rs:443-453 | monoruby/src/builtins/io.rs:3168-3178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/io.rs:443` 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) monoruby/src/builtins/kernel.rs:394— monoruby/src/builtins/kernel.rs:394-404 | monoruby/src/builtins/object.rs:85-95 — 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 `monoruby/src/builtins/kernel.rs:394` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) monoruby/src/builtins/marshal.rs:2584— monoruby/src/builtins/marshal.rs:2584-2594 | monoruby/src/builtins/marshal.rs:2923-2933 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/marshal.rs:2584` 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, `monoruby/src/builtins/marshal.rs:2922` calls `push` and `monoruby/src/builtins/marshal.rs:2583` 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) monoruby/src/builtins/method.rs:411— monoruby/src/builtins/method.rs:411-421 | monoruby/src/builtins/method.rs:455-465 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/method.rs:411` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/string.rs:1547— monoruby/src/builtins/string.rs:1547-1557 | monoruby/src/builtins/string.rs:6468-6478 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:1547` 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:406— monoruby/src/codegen/arch/aarch64/compile/mod.rs:406-416 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:536-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:406` 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2338— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2338-2348 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4612-4622 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:2338` 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:4343— monoruby/src/codegen/arch/aarch64/compile/mod.rs:4343-4353 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4366-4376 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:4343` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:566— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:566-576 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:678-688 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/x86_64/compile/method_call.rs:566` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/x86_64/compile/mod.rs:2301— monoruby/src/codegen/arch/x86_64/compile/mod.rs:2301-2311 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2373-2383 — both copies are in the same file, so extract the 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) monoruby/src/codegen/jitgen.rs:1653— monoruby/src/codegen/jitgen.rs:1653-1663 | monoruby/src/codegen/jitgen.rs:1669-1679 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen.rs:1653` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/asmir/compile_shared.rs:1600— monoruby/src/codegen/jitgen/asmir/compile_shared.rs:1600-1610 | monoruby/src/codegen/jitgen/asmir/compile_shared.rs:1683-1693 — both copies are in the same file, so extract the 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) monoruby/src/executor/format.rs:1591— monoruby/src/executor/format.rs:1591-1601 | monoruby/src/executor/format.rs:1612-1622 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/executor/format.rs:1591` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) monoruby/src/executor/format.rs:1611— monoruby/src/executor/format.rs:1611-1621 | monoruby/src/executor/format.rs:1628-1638 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/executor/format.rs:1611` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) monoruby/src/value/rvalue/io.rs:1710— monoruby/src/value/rvalue/io.rs:1710-1720 | monoruby/src/value/rvalue/io.rs:2128-2138 — both copies are in the same file, so extract the 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) monoruby/src/value/rvalue/regexp.rs:2119— monoruby/src/value/rvalue/regexp.rs:2119-2129 | monoruby/src/value/rvalue/regexp.rs:2143-2153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/regexp.rs:2119` 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) monoruby/src/value/rvalue/regexp.rs:3468— monoruby/src/value/rvalue/regexp.rs:3468-3478 | monoruby/src/value/rvalue/regexp.rs:3523-3533 — both copies are in the same file, so extract the 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) rubymap/src/map/core.rs:554— rubymap/src/map/core.rs:554-564 | rubymap/src/map/core.rs:627-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. Read the line range as the matched WINDOW rather than a finished unit: at `rubymap/src/map/core.rs:554` 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) rubymap/src/map/core.rs:570— rubymap/src/map/core.rs:570-580 | rubymap/src/map/core.rs:643-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 `rubymap/src/map/core.rs:570` 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) monoruby/src/builtins/fiber.rs:491— monoruby/src/builtins/fiber.rs:491-501 | monoruby/src/builtins/thread.rs:339-349 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) monoruby/src/builtins/io.rs:2769— monoruby/src/builtins/io.rs:2769-2779 | monoruby/src/builtins/io.rs:6024-6034 — both copies are in the same file, so extract the 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) rubymap/src/map.rs:987— rubymap/src/map.rs:987-997 | rubymap/src/map.rs:1120-1130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rubymap/src/map.rs:987` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
JitContext::compile_method_call (cognitive 196) monoruby/src/codegen/jitgen/compile/method_call.rs:781— JitContext::compile_method_call has cognitive complexity 196 (threshold 15). Drivers by points: if/else 52 (134 pts), boolean chains 37, match/switch 7 (18 pts), loops 2 (7 pts) (nesting depth added 98). 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.
JitContext::compile_instruction_inner (cognitive 159) monoruby/src/codegen/jitgen/compile.rs:419— JitContext::compile_instruction_inner has cognitive complexity 159 (threshold 15). Drivers by points: if/else 68 (130 pts), boolean chains 17, match/switch 4 (7 pts), loops 3 (5 pts) (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.
JitContext::loop_float_candidates (cognitive 114) monoruby/src/codegen/jitgen/compile/loop_analysis.rs:904— JitContext::loop_float_candidates has cognitive complexity 114 (threshold 15). Drivers by points: if/else 28 (74 pts), loops 11 (33 pts), boolean chains 7 (nesting depth added 68). 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.
JitContext::region_summary (cognitive 85) monoruby/src/codegen/jitgen/compile/loop_analysis.rs:728— JitContext::region_summary has cognitive complexity 85 (threshold 15). Drivers by points: if/else 13 (44 pts), match/switch 7 (24 pts), loops 5 (13 pts), boolean chains 4 (nesting depth added 56). 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.
JitContext::record_pre_fixpoint_outer_floats (cognitive 62) monoruby/src/codegen/jitgen/compile/loop_analysis.rs:1201— JitContext::record_pre_fixpoint_outer_floats has cognitive complexity 62 (threshold 15). Drivers by points: if/else 20 (38 pts), loops 6 (11 pts), boolean chains 9, match/switch 2 (4 pts) (nesting depth added 25). 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.
JitContext::incoming_context (cognitive 59) monoruby/src/codegen/jitgen/merge.rs:77— JitContext::incoming_context has cognitive complexity 59 (threshold 15). Drivers by points: if/else 17 (35 pts), boolean chains 13, loops 2 (7 pts), match/switch 1 (4 pts) (nesting depth added 26). 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.
JitContext::compile_binary (cognitive 46) monoruby/src/codegen/jitgen/compile/binary_op.rs:880— JitContext::compile_binary has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 19, match/switch 2 (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.
JitContext::resolve_dyn_var_offset_in (cognitive 38) monoruby/src/codegen/jitgen/context.rs:3425— JitContext::resolve_dyn_var_offset_in has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 3 (8 pts), loops 3 (7 pts) (nesting depth added 22). 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.
JitContext::inline_class_new (cognitive 36) monoruby/src/codegen/jitgen/compile/method_call.rs:2261— JitContext::inline_class_new has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (21 pts), match/switch 4 (6 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 9). 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.
JitContext::method_call (cognitive 35) monoruby/src/codegen/jitgen/compile/method_call.rs:56— JitContext::method_call has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 6, match/switch 2 (4 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.
JitContext::build_return_segments (cognitive 28) monoruby/src/codegen/jitgen/context.rs:4583— JitContext::build_return_segments has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 5 (9 pts), match/switch 1 (4 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JitContext::settle_virtuals (cognitive 27) monoruby/src/codegen/jitgen/compile/escape.rs:287— JitContext::settle_virtuals has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 13, if/else 6 (10 pts), match/switch 2 (3 pts), loops 1 (nesting depth added 5). 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.
JitContext::consume_virtual_index (cognitive 27) monoruby/src/codegen/jitgen/compile/escape.rs:1672— JitContext::consume_virtual_index has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 4 (5 pts), boolean chains 2 (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.
JitContext::specialized_iseq (cognitive 25) monoruby/src/codegen/jitgen/compile/method_call.rs:2640— JitContext::specialized_iseq has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (2 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.
JitContext::analyse_backedge_fixpoint (cognitive 24) monoruby/src/codegen/jitgen/compile/loop_analysis.rs:121— JitContext::analyse_backedge_fixpoint has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (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.
JitContext::attr_reader (cognitive 24) monoruby/src/codegen/jitgen/compile/method_call.rs:2047— JitContext::attr_reader has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JitContext::try_splice_exit (cognitive 24) monoruby/src/codegen/jitgen/context.rs:2595— JitContext::try_splice_exit has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 5, match/switch 4, 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.
JitContext::gen_bridges_for_branches (cognitive 24) monoruby/src/codegen/jitgen/merge.rs:471— JitContext::gen_bridges_for_branches has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (7 pts), match/switch 2 (5 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.
JitContext::may_consume_virtual (cognitive 23) monoruby/src/codegen/jitgen/compile/escape.rs:758— JitContext::may_consume_virtual has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 10, match/switch 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.
JitContext::consume_virtual (cognitive 21) monoruby/src/codegen/jitgen/compile/escape.rs:1130— JitContext::consume_virtual has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 5 (7 pts), boolean chains 5 (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.
JitContext::pic_groups (cognitive 21) monoruby/src/codegen/jitgen/compile/pic.rs:119— JitContext::pic_groups has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, 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.
JitContext::compile_pic_call (cognitive 20) monoruby/src/codegen/jitgen/compile/pic.rs:289— JitContext::compile_pic_call has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, match/switch 1 (2 pts), 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.
JitContext::consume_virtual_expand (cognitive 19) monoruby/src/codegen/jitgen/compile/escape.rs:1268— JitContext::consume_virtual_expand has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (3 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JitContext::load_constant (cognitive 18) monoruby/src/codegen/jitgen/compile/variables.rs:227— JitContext::load_constant has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 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.
JitContext::opt_eq_assumable (cognitive 17) monoruby/src/codegen/jitgen/compile/binary_op.rs:348— JitContext::opt_eq_assumable has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, 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.
+ 3 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×27
Edited copy of a member (13 corresponding lines) monoruby/src/builtins/process.rs:2051— monoruby/src/builtins/process.rs:2051-2065 | monoruby/src/builtins/process.rs:2067-2079 — 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) monoruby/src/builtins/file.rs:961— monoruby/src/builtins/file.rs:961-973 | monoruby/src/builtins/file.rs:3045-3057 — 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) monoruby/src/builtins/file.rs:1563— monoruby/src/builtins/file.rs:1563-1577 | monoruby/src/builtins/io.rs:4923-4935 — 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) rubymap/src/map/core.rs:595— rubymap/src/map/core.rs:595-607 | rubymap/src/map/core.rs:667-679 — 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) monoruby/src/globals/error.rs:1714— monoruby/src/globals/error.rs:1714-1726 | monoruby/src/globals/error.rs:1777-1789 — 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) monoruby/src/value/rvalue/fiber.rs:448— monoruby/src/value/rvalue/fiber.rs:448-460 | monoruby/src/value/rvalue/thread.rs:386-399 — 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) ext/nokogiri/src/node.rs:323— ext/nokogiri/src/node.rs:323-338 | ext/nokogiri/src/node.rs:352-364 — 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) monoruby/src/ext.rs:1850— monoruby/src/ext.rs:1850-1867 | monoruby/src/ext.rs:2444-2456 — 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) monoruby/src/codegen/jitgen.rs:1755— monoruby/src/codegen/jitgen.rs:1755-1767 | monoruby/src/codegen/jitgen.rs:1775-1787 — 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) monoruby/src/ext.rs:1145— monoruby/src/ext.rs:1145-1157 | monoruby/src/ext.rs:1999-2013 — 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) monoruby/src/builtins/method.rs:775— monoruby/src/builtins/method.rs:775-787 | monoruby/src/builtins/method.rs:796-808 — 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) monoruby/src/codegen/arch/x86_64/compile/mod.rs:2561— monoruby/src/codegen/arch/x86_64/compile/mod.rs:2561-2573 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2590-2603 — 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) monoruby/src/value/rvalue/string.rs:169— monoruby/src/value/rvalue/string.rs:169-184 | monoruby/src/value/rvalue/string.rs:1940-1952 — 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) monoruby/src/builtins/array.rs:1982— monoruby/src/builtins/array.rs:1982-1994 | monoruby/src/builtins/array.rs:2580-2592 — 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) monoruby/src/builtins/string.rs:7724— monoruby/src/builtins/string.rs:7724-7736 | monoruby/src/builtins/string.rs:12139-12159 — 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) monoruby/src/builtins/set.rs:516— monoruby/src/builtins/set.rs:516-528 | monoruby/src/builtins/set.rs:625-640 — 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) ext/nokogiri/src/dtd.rs:340— ext/nokogiri/src/dtd.rs:340-353 | ext/nokogiri/src/node.rs:868-880 — 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) monoruby/src/value.rs:2799— monoruby/src/value.rs:2799-2816 | monoruby/src/value.rs:2824-2836 — 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) monoruby/src/value/rvalue/string.rs:7435— monoruby/src/value/rvalue/string.rs:7435-7447 | monoruby/src/value/rvalue/string.rs:7455-7467 — 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) monoruby/src/value/coerce.rs:91— monoruby/src/value/coerce.rs:91-103 | monoruby/src/value/coerce.rs:485-504 — 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) monoruby/src/codegen/runtime/args.rs:124— monoruby/src/codegen/runtime/args.rs:124-143 | monoruby/src/globals/store.rs:3633-3645 — 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) monoruby/src/builtins/regexp.rs:226— monoruby/src/builtins/regexp.rs:226-238 | monoruby/src/value/rvalue/regexp.rs:484-503 — 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) monoruby/src/builtins/enumerator.rs:351— monoruby/src/builtins/enumerator.rs:351-366 | monoruby/src/builtins/object.rs:576-588 — 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) monoruby/src/value/rvalue/string/transcode.rs:4844— monoruby/src/value/rvalue/string/transcode.rs:4844-4856 | monoruby/src/value/rvalue/string/transcode.rs:4862-4874 — 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) monoruby/gem/markly/markly.rb:337— monoruby/gem/markly/markly.rb:337-349 | monoruby/gem/markly/markly.rb:353-365 — 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.
MethodTooLong: Lowerer.lower_node monoruby/src/parser/prism_backend.rs:1105— MethodTooLong — lower_node runs 801 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 701 over it, 8.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Executor.format_by_args monoruby/src/executor/format.rs:825— MethodTooLong — format_by_args runs 602 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 502 over it, 6.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: BytecodeGen.gen_expr_inner monoruby/src/bytecodegen/expression.rs:458— MethodTooLong — gen_expr_inner runs 521 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 421 over it, 5.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.
MethodTooLong: BytecodeGen.inst_to_bc monoruby/src/bytecodegen/encode.rs:186— MethodTooLong — inst_to_bc runs 407 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 307 over it, 4.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Globals.new monoruby/src/globals.rs:792— MethodTooLong — new runs 280 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 180 over it, 2.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BytecodeGen.check_defined monoruby/src/bytecodegen/defined.rs:91— MethodTooLong — check_defined runs 240 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 140 over it, 2.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BytecodeGen.gen_store_expr monoruby/src/bytecodegen/expression.rs:134— MethodTooLong — gen_store_expr runs 233 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 133 over it, 2.33× 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: BytecodeGen.gen_begin monoruby/src/bytecodegen/statement.rs:435— MethodTooLong — gen_begin runs 211 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 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BytecodeGen.level_down monoruby/src/bytecodegen/method_call.rs:428— MethodTooLong — level_down runs 178 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 78 over it, 1.78× 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: Executor.take_ex_obj monoruby/src/executor.rs:2486— MethodTooLong — take_ex_obj runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Lowerer.lower_call monoruby/src/parser/prism_backend.rs:5317— MethodTooLong — lower_call runs 140 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 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Value.from_ast_inner monoruby/src/value.rs:3729— MethodTooLong — from_ast_inner runs 134 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 34 over it, 1.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: BytecodeGen.gen_method_call monoruby/src/bytecodegen/method_call.rs:67— MethodTooLong — gen_method_call runs 133 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 33 over it, 1.33× 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: Lowerer.lower_parameters monoruby/src/parser/prism_backend.rs:5092— MethodTooLong — lower_parameters runs 132 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 32 over it, 1.32× 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: Preprocess.unescape_nonascii monoruby/src/value/rvalue/regexp.rs:846— MethodTooLong — unescape_nonascii runs 131 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 31 over it, 1.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.
MethodTooLong: Plain.node ext/markly/src/lib.rs:1000— MethodTooLong — node runs 130 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 30 over it, 1.30× 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: Store.handle_args monoruby/src/globals/store.rs:2904— MethodTooLong — handle_args runs 130 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 30 over it, 1.30× 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: Codegen.new monoruby/src/codegen.rs:1499— MethodTooLong — new 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.
MethodTooLong: Executor.require monoruby/src/executor.rs:1442— MethodTooLong — require runs 117 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 17 over it, 1.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: MarshalReader.read_user_object monoruby/src/builtins/marshal.rs:905— MethodTooLong — read_user_object runs 113 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 13 over it, 1.13× 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: Lowerer.lower_hash_pattern monoruby/src/parser/prism_backend.rs:4033— MethodTooLong — lower_hash_pattern runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Codegen.construct_vm monoruby/src/codegen.rs:1374— MethodTooLong — construct_vm runs 108 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 8 over it, 1.08× 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: Allocator.gc monoruby/src/alloc.rs:1731— MethodTooLong — gc runs 107 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 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MarshalReader.read_ivar_wrapped monoruby/src/builtins/marshal.rs:652— MethodTooLong — read_ivar_wrapped runs 106 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 6 over it, 1.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: BytecodeGen.gen_case monoruby/src/bytecodegen/statement.rs:296— MethodTooLong — gen_case 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.
TodoComment monoruby/src/globals/store/class.rs:2208— // TODO: we must name the unnamed class when the class object is assigned to constant later. — 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 monoruby/src/executor/frame.rs:247— // TODO: this does not support nested fibers. — 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 monoruby/src/executor/op/binary_ops.rs:507— // TODO: support rhs < 0. — 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 monoruby/src/codegen/arch/aarch64/invoker.rs:276— /// TODO(aarch64): resolve_invalidated_outer (heap-promoted outer frames). — 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 monoruby/src/codegen/arch/aarch64/invoker.rs:281— /// TODO(aarch64): resolve_invalidated_outer (heap-promoted outer frames). — 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 monoruby/src/codegen/arch/aarch64/invoker.rs:675— // TODO(aarch64): illegal_classid — 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 monoruby/src/codegen/arch/aarch64/jit_module.rs:100— /// TODO(aarch64): replace each caller with the real invoker. — 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 monoruby/src/codegen/arch/aarch64/jit_module.rs:138— // TODO(aarch64): emit the real entry stubs (raise/fetch_and_dispatch/ — 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 monoruby/src/codegen/arch/aarch64/vmgen.rs:1286— /// (generic runtime fallback 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 monoruby/src/codegen/arch/aarch64/wrapper.rs:12— /// `gen_vm_stub`). TODO(aarch64): other FuncKinds — 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 monoruby/src/bytecodegen/method_call.rs:385— // TODO: We must check this in parser — 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 monoruby/src/builtins/file.rs:470— /// TODO: support ~USER — 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 monoruby/src/builtins/method.rs:265— // TODO: support keyword arguments — 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 monoruby/src/builtins/proc.rs:321— /// TODO: we must support [] with >2 args. — 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 monoruby/src/builtins/string.rs:3327— /// TODO: support nil and ' ' for sep. — 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 monoruby/gem/bigdecimal.rb:17— # TODO: some methods (example: BigMath.exp) require more precision than specified to coerce. — 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 monoruby/gem/nokogiri/css.rb:8— # TODO: Deprecate this method ahead of 2.0 and delete it in 2.0. — 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 monoruby/gem/nokogiri/xml/document.rb:75— # TODO: should we instead check for respond_to?(:to_path) ? — 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 monoruby/gem/nokogiri/xml/node.rb:1186— # TODO: remove this block when libxml2 < 2.13 is no longer supported — 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 monoruby/gem/nokogiri/xml/node.rb:1418— # TODO: deprecate non-hash options, see 46c68ed 2009-06-20 for context — 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 monoruby/gem/nokogiri/xml/relax_ng.rb:70— # TODO deprecate this method — 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 monoruby/gem/nokogiri/xml/schema.rb:79— # TODO deprecate this method — 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 monoruby/gem/nokogiri/version/info.rb:212— # TODO: replace with Gumbo functionality — 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 monoruby/gem/nokogiri/html4/document_fragment.rb:58— # TODO: this method should take a context node. — 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 monoruby/gem/json/common.rb:51— # TODO: extract :create_additions support to another gem for version 3.0 — 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×24
Edited copy of a member (10 corresponding lines) monoruby/gem/bigdecimal/math.rb:495— monoruby/gem/bigdecimal/math.rb:495-504 | monoruby/gem/bigdecimal/math.rb:523-532 — 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) monoruby/src/builtins/string.rs:10685— monoruby/src/builtins/string.rs:10685-10694 | monoruby/src/builtins/string.rs:11571-11580 — 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) monoruby/src/executor.rs:3769— monoruby/src/executor.rs:3769-3778 | monoruby/src/executor.rs:3786-3795 — 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) monoruby/src/globals/error.rs:1630— monoruby/src/globals/error.rs:1630-1639 | monoruby/src/globals/error.rs:1641-1650 — 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) monoruby/src/builtins/method.rs:871— monoruby/src/builtins/method.rs:871-880 | monoruby/src/builtins/method.rs:887-896 — 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) monoruby/src/builtins/io.rs:2522— monoruby/src/builtins/io.rs:2522-2532 | monoruby/src/builtins/io.rs:4369-4378 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2664— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2664-2673 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2677-2686 — 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) monoruby/src/builtins/data_class.rs:179— monoruby/src/builtins/data_class.rs:179-188 | monoruby/src/builtins/struct_class.rs:475-489 — 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) monoruby/src/builtins/hash.rs:1698— monoruby/src/builtins/hash.rs:1698-1707 | monoruby/src/builtins/hash.rs:1745-1754 — 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) monoruby/src/builtins/module.rs:1084— monoruby/src/builtins/module.rs:1084-1096 | monoruby/src/builtins/object.rs:602-611 — 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) monoruby/src/globals/error.rs:1309— monoruby/src/globals/error.rs:1309-1319 | monoruby/src/globals/error.rs:1324-1333 — 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) monoruby/src/builtins/dir.rs:1076— monoruby/src/builtins/dir.rs:1076-1089 | monoruby/src/builtins/process.rs:1908-1935 — 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) monoruby/src/value/rvalue/regexp.rs:3649— monoruby/src/value/rvalue/regexp.rs:3649-3658 | monoruby/src/value/rvalue/regexp.rs:3671-3680 — 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) ext/nokogiri/src/misc.rs:145— ext/nokogiri/src/misc.rs:145-154 | ext/nokogiri/src/misc.rs:260-269 — 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) ext/nokogiri/src/dtd.rs:301— ext/nokogiri/src/dtd.rs:301-310 | ext/nokogiri/src/dtd.rs:404-413 — 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) monoruby/src/builtins/hash.rs:3218— monoruby/src/builtins/hash.rs:3218-3227 | monoruby/src/builtins/hash.rs:3940-3949 — 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) monoruby/src/ext.rs:1982— monoruby/src/ext.rs:1982-1992 | monoruby/src/ext.rs:2458-2467 — 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) monoruby/src/builtins/hash.rs:576— monoruby/src/builtins/hash.rs:576-589 | monoruby/src/builtins/hash.rs:602-611 — 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) monoruby/src/builtins/kernel.rs:2012— monoruby/src/builtins/kernel.rs:2012-2021 | monoruby/src/builtins/numeric/float.rs:331-340 — 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) monoruby/stdlib/strscan.rb:457— monoruby/stdlib/strscan.rb:457-466 | monoruby/stdlib/strscan.rb:474-483 — 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) monoruby/src/builtins/process.rs:2009— monoruby/src/builtins/process.rs:2009-2018 | monoruby/src/builtins/process.rs:2030-2039 — 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) monoruby/src/codegen/arch/x86_64/compile/mod.rs:2236— monoruby/src/codegen/arch/x86_64/compile/mod.rs:2236-2249 | monoruby/src/codegen/arch/x86_64/compile/variables.rs:432-441 — 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) monoruby/src/builtins/kernel.rs:2025— monoruby/src/builtins/kernel.rs:2025-2034 | monoruby/src/builtins/string.rs:5181-5190 — 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) monoruby/src/builtins/file.rs:1759— monoruby/src/builtins/file.rs:1759-1768 | monoruby/src/value/coerce.rs:613-623 — 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 (12 lines × 2) ext/nokogiri/src/reader.rs:337— ext/nokogiri/src/reader.rs:337-348 | ext/nokogiri/src/reader.rs:362-373 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/reader.rs:337` it does not close everything it opens, so those 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, `ext/nokogiri/src/reader.rs:375` calls `Ok` and `ext/nokogiri/src/reader.rs:349` 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) ext/nokogiri/src/schema.rs:270— ext/nokogiri/src/schema.rs:270-281 | ext/nokogiri/src/schema.rs:293-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/schema.rs:270` it does not close everything it opens, so those exact lines 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) ext/nokogiri/src/xpath.rs:88— ext/nokogiri/src/xpath.rs:88-99 | ext/nokogiri/src/xpath.rs:118-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/xpath.rs:88` it does not close everything it opens, so those 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) hashbrown/src/map.rs:3981— hashbrown/src/map.rs:3981-3992 | rubymap/src/map.rs:1682-1693 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) monoruby/src/builtins/dir.rs:385— monoruby/src/builtins/dir.rs:385-396 | monoruby/src/builtins/dir.rs:446-457 — both copies are in the same file, so extract the 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) monoruby/src/builtins/io.rs:2869— monoruby/src/builtins/io.rs:2869-2880 | monoruby/src/builtins/io.rs:3056-3067 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/io.rs:2869` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/io.rs:3550— monoruby/src/builtins/io.rs:3550-3561 | monoruby/src/builtins/kernel.rs:3740-3751 — 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 (12 lines × 2) monoruby/src/builtins/kernel.rs:1390— monoruby/src/builtins/kernel.rs:1390-1401 | monoruby/src/builtins/kernel.rs:1678-1689 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) monoruby/src/builtins/numeric/float.rs:155— monoruby/src/builtins/numeric/float.rs:155-166 | monoruby/src/builtins/numeric/float.rs:207-218 — both copies are in the same file, so extract the 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) monoruby/src/builtins/process.rs:452— monoruby/src/builtins/process.rs:452-463 | monoruby/src/builtins/process.rs:1734-1745 — both copies are in the same file, so extract the 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) monoruby/src/builtins/set.rs:1087— monoruby/src/builtins/set.rs:1087-1098 | monoruby/src/builtins/set.rs:1123-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 `monoruby/src/builtins/set.rs:1087` 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) monoruby/src/builtins/string.rs:10735— monoruby/src/builtins/string.rs:10735-10746 | monoruby/src/builtins/string.rs:11628-11639 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:10735` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) monoruby/src/builtins/string.rs:10882— monoruby/src/builtins/string.rs:10882-10893 | monoruby/src/builtins/string.rs:10979-10990 — both copies are in the same file, so extract the 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) monoruby/src/bytecodegen/expression.rs:1310— monoruby/src/bytecodegen/expression.rs:1310-1321 | monoruby/src/bytecodegen/expression.rs:1398-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 `monoruby/src/bytecodegen/expression.rs:1310` 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) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:256— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:256-267 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1978-1989 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:256` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/compile/method_call.rs:2133— monoruby/src/codegen/jitgen/compile/method_call.rs:2133-2144 | monoruby/src/codegen/jitgen/compile/method_call.rs:2611-2622 — both copies are in the same file, so extract the 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) monoruby/src/codegen/jitgen/context.rs:3602— monoruby/src/codegen/jitgen/context.rs:3602-3613 | monoruby/src/codegen/jitgen/context.rs:3638-3649 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/context.rs:3602` 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) REDACTED:2197— REDACTED:2197-2208 | REDACTED:2240-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.
Duplicated block (12 lines × 2) monoruby/src/ext.rs:1624— monoruby/src/ext.rs:1624-1635 | monoruby/src/ext.rs:1649-1660 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) monoruby/src/scheduler.rs:857— monoruby/src/scheduler.rs:857-868 | monoruby/src/scheduler/native.rs:826-837 — before extracting anything, compare `monoruby/src/scheduler.rs` and `monoruby/src/scheduler/native.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `monoruby/src/scheduler.rs:854` calls `enabled`, `terminate_all` and `monoruby/src/scheduler/native.rs:825` 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) monoruby/src/value/rvalue/string.rs:1102— monoruby/src/value/rvalue/string.rs:1102-1113 | monoruby/src/value/rvalue/string.rs:1117-1128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string.rs:1102` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) monoruby/gem/gosu.rb:1766— monoruby/gem/gosu.rb:1766-1777 | monoruby/gem/gosu.rb:1791-1802 — both copies are in the same file, so extract the 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) monoruby/gem/strptime/strptime.rb:68— monoruby/gem/strptime/strptime.rb:68-79 | monoruby/gem/zstd-ruby/zstdruby.rb:107-118 — 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. 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) hashbrown/src/map.rs:209— hashbrown/src/map.rs:209-218 | rubymap/src/map.rs:104-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) monoruby/src/builtins/array.rs:1274— monoruby/src/builtins/array.rs:1274-1283 | monoruby/src/builtins/array.rs:1328-1337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:1274` 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) monoruby/src/builtins/array.rs:2416— monoruby/src/builtins/array.rs:2416-2425 | monoruby/src/builtins/array.rs:2439-2448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `monoruby/src/builtins/array.rs:2438` calls `Some`, `check_funcall` and `monoruby/src/builtins/array.rs:2414` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) monoruby/src/builtins/enumerator.rs:383— monoruby/src/builtins/enumerator.rs:383-392 | monoruby/src/builtins/enumerator.rs:572-581 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) monoruby/src/builtins/hash.rs:2395— monoruby/src/builtins/hash.rs:2395-2404 | monoruby/src/builtins/hash.rs:3976-3985 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/hash.rs:2395` 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) monoruby/src/builtins/io_buffer.rs:464— monoruby/src/builtins/io_buffer.rs:464-473 | monoruby/src/builtins/io_buffer.rs:532-541 — both copies are in the same file, so extract the 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, `monoruby/src/builtins/io_buffer.rs:474` calls `Some` and `monoruby/src/builtins/io_buffer.rs:542` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) monoruby/src/builtins/kernel.rs:5049— monoruby/src/builtins/kernel.rs:5049-5058 | monoruby/src/builtins/method.rs:205-214 — 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 `monoruby/src/builtins/kernel.rs:5049` 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) monoruby/src/builtins/method.rs:778— monoruby/src/builtins/method.rs:778-787 | monoruby/src/builtins/method.rs:799-808 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/method.rs:778` 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) monoruby/src/builtins/numeric/complex.rs:342— monoruby/src/builtins/numeric/complex.rs:342-351 | monoruby/src/executor/op/binary_ops.rs:53-62 — 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 `monoruby/src/builtins/numeric/complex.rs:342` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) monoruby/src/builtins/numeric/float.rs:246— monoruby/src/builtins/numeric/float.rs:246-255 | monoruby/src/builtins/numeric/float.rs:272-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:415— monoruby/src/codegen/arch/aarch64/compile/mod.rs:415-424 | monoruby/src/codegen/jitgen/asmir.rs:4499-4508 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/jitgen/asmir.rs` as WHOLE FILES: this scan already matched 6 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:415` 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, `monoruby/src/codegen/arch/aarch64/compile/mod.rs:414` calls `push` and `monoruby/src/codegen/jitgen/asmir.rs:4498` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) monoruby/src/codegen/arch/x86_64/compile/mod.rs:881— monoruby/src/codegen/arch/x86_64/compile/mod.rs:881-890 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:998-1007 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/x86_64/compile/mod.rs:881` 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) REDACTED:2982— REDACTED:2982-2991 | monoruby/src/executor.rs:3947-3956 — 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 `REDACTED:2982` it does not close everything it opens, so those exact lines 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) monoruby/src/executor.rs:4143— monoruby/src/executor.rs:4143-4152 | monoruby/src/executor.rs:4245-4254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/executor.rs:4143` it does not close everything it opens, so those exact lines 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) monoruby/src/scheduler.rs:1608— monoruby/src/scheduler.rs:1608-1617 | monoruby/src/scheduler/native.rs:596-606 — before extracting anything, compare `monoruby/src/scheduler.rs` and `monoruby/src/scheduler/native.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/scheduler.rs:1608` 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) monoruby/src/builtins/file.rs:2210— monoruby/src/builtins/file.rs:2210-2219 | monoruby/src/builtins/file.rs:2236-2245 — both copies are in the same file, so extract the 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) monoruby/src/globals/store/class.rs:653— monoruby/src/globals/store/class.rs:653-662 | monoruby/src/globals/store/class.rs:684-693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/globals/store/class.rs:653` 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) monoruby/src/value/rvalue/regexp.rs:3104— monoruby/src/value/rvalue/regexp.rs:3104-3113 | monoruby/src/value/rvalue/regexp.rs:3336-3345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/regexp.rs:3104` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/file.rs:2503— monoruby/src/builtins/file.rs:2503-2512 | monoruby/src/builtins/file.rs:2581-2590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/file.rs:2503` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/process.rs:572— monoruby/src/builtins/process.rs:572-581 | monoruby/src/builtins/process.rs:637-646 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/process.rs:572` 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) monoruby/builtins/data.rb:58— monoruby/builtins/data.rb:58-67 | monoruby/builtins/struct.rb:48-57 — 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 (10 lines × 2) monoruby/gem/msgpack/msgpack.rb:841— monoruby/gem/msgpack/msgpack.rb:841-850 | monoruby/gem/msgpack/msgpack.rb:854-863 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×21
Edited copy of a member (12 corresponding lines) monoruby/src/builtins/marshal.rs:1531— monoruby/src/builtins/marshal.rs:1531-1542 | monoruby/src/builtins/marshal.rs:1546-1557 — 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) monoruby/src/builtins/encoding.rs:4321— monoruby/src/builtins/encoding.rs:4321-4332 | monoruby/src/builtins/encoding.rs:4340-4351 — 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) hashbrown/src/map.rs:1309— hashbrown/src/map.rs:1309-1320 | hashbrown/src/set.rs:860-873 — 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) monoruby/builtins/struct.rb:66— monoruby/builtins/struct.rb:66-77 | monoruby/builtins/struct.rb:92-105 — 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) monoruby/src/builtins/kernel.rs:774— monoruby/src/builtins/kernel.rs:774-789 | monoruby/src/builtins/kernel.rs:793-804 — 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) monoruby/src/codegen/jitgen/state.rs:592— monoruby/src/codegen/jitgen/state.rs:592-605 | monoruby/src/codegen/jitgen/state.rs:607-618 — 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) monoruby/src/globals/error.rs:64— monoruby/src/globals/error.rs:64-75 | monoruby/src/globals/error.rs:80-93 — 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) monoruby/src/globals/store.rs:2513— monoruby/src/globals/store.rs:2513-2524 | monoruby/src/globals/store.rs:2531-2546 — 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) rubymap/src/map/core.rs:363— rubymap/src/map/core.rs:363-380 | rubymap/src/map/core.rs:383-394 — 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) ext/nokogiri/src/reader.rs:392— ext/nokogiri/src/reader.rs:392-405 | ext/nokogiri/src/reader.rs:408-419 — 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) monoruby/src/value/rvalue/string/transcode.rs:4165— monoruby/src/value/rvalue/string/transcode.rs:4165-4178 | monoruby/src/value/rvalue/string/transcode.rs:4181-4192 — 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) hashbrown/src/map.rs:3586— hashbrown/src/map.rs:3586-3597 | hashbrown/src/map.rs:3893-3904 — 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) monoruby/src/builtins/process.rs:589— monoruby/src/builtins/process.rs:589-601 | monoruby/src/builtins/process.rs:654-665 — 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) monoruby/src/codegen/jitgen/gp_alloc.rs:529— monoruby/src/codegen/jitgen/gp_alloc.rs:529-540 | monoruby/src/codegen/jitgen/gp_alloc.rs:543-554 — 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) monoruby/src/builtins/encoding.rs:1801— monoruby/src/builtins/encoding.rs:1801-1813 | monoruby/src/builtins/io.rs:611-622 — 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) monoruby/src/value/rvalue/match_data.rs:121— monoruby/src/value/rvalue/match_data.rs:121-132 | monoruby/src/value/rvalue/match_data.rs:157-169 — 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) monoruby/src/builtins/module.rs:3060— monoruby/src/builtins/module.rs:3060-3071 | monoruby/src/globals/store/class/constants.rs:266-277 — 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) monoruby/src/codegen/arch/x86_64/compile/mod.rs:2854— monoruby/src/codegen/arch/x86_64/compile/mod.rs:2854-2865 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2875-2887 — 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) monoruby/src/ext.rs:2472— monoruby/src/ext.rs:2472-2483 | monoruby/src/ext.rs:2715-2726 — 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) monoruby/src/codegen/jitgen/context.rs:2251— monoruby/src/codegen/jitgen/context.rs:2251-2262 | monoruby/src/codegen/jitgen/context.rs:2944-2955 — 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) monoruby/src/builtins/regexp.rs:1469— monoruby/src/builtins/regexp.rs:1469-1480 | monoruby/src/value/rvalue/match_data.rs:274-286 — 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 (15 corresponding lines) · ×20
Edited copy of a member (15 corresponding lines) monoruby/src/value.rs:4144— monoruby/src/value.rs:4144-4158 | monoruby/src/value.rs:4162-4176 — 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) monoruby/src/value.rs:1947— monoruby/src/value.rs:1947-1961 | monoruby/src/value.rs:1963-1978 — 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) monoruby/src/builtins/module.rs:2335— monoruby/src/builtins/module.rs:2335-2349 | monoruby/src/builtins/module.rs:2436-2462 — 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) monoruby/src/builtins/hash.rs:3445— monoruby/src/builtins/hash.rs:3445-3459 | monoruby/src/builtins/hash.rs:3496-3510 — 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) monoruby/src/builtins/arithmetic_sequence.rs:459— monoruby/src/builtins/arithmetic_sequence.rs:459-476 | monoruby/src/builtins/arithmetic_sequence.rs:486-500 — 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) monoruby/src/builtins/process.rs:679— monoruby/src/builtins/process.rs:679-702 | monoruby/src/builtins/process.rs:735-749 — 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) monoruby/src/builtins/encoding.rs:4264— monoruby/src/builtins/encoding.rs:4264-4278 | monoruby/src/builtins/encoding.rs:4286-4303 — 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) monoruby/src/builtins/numeric/float.rs:1226— monoruby/src/builtins/numeric/float.rs:1226-1240 | monoruby/src/builtins/numeric/float.rs:1249-1263 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3418— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3418-3432 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3547-3563 — 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) monoruby/src/builtins/module.rs:2362— monoruby/src/builtins/module.rs:2362-2376 | monoruby/src/builtins/module.rs:2496-2515 — 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) REDACTED:2374— REDACTED:2374-2392 | REDACTED:2403-2417 — 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) REDACTED:754— REDACTED:754-768 | REDACTED:869-883 — 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) monoruby/gem/nokogiri/xml/searchable.rb:211— monoruby/gem/nokogiri/html5/document_fragment.rb:191-210 | monoruby/gem/nokogiri/xml/searchable.rb:211-225 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:814— monoruby/src/codegen/arch/aarch64/compile/mod.rs:814-828 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:830-844 — 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) monoruby/src/codegen/jitgen.rs:1652— monoruby/src/codegen/jitgen.rs:1652-1666 | monoruby/src/codegen/jitgen.rs:1668-1684 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2691— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2691-2705 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2708-2722 — 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) monoruby/src/value/rvalue/match_data.rs:139— monoruby/src/value/rvalue/match_data.rs:139-153 | monoruby/src/value/rvalue/match_data.rs:183-198 — 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) monoruby/src/builtins/string.rs:4678— monoruby/src/builtins/string.rs:4678-4692 | monoruby/src/builtins/string.rs:4694-4708 — 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) monoruby_ext/src/lib.rs:618— monoruby_ext/src/lib.rs:618-632 | monoruby_ext/src/lib.rs:641-656 — 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) monoruby/src/value/rvalue/string/transcode.rs:4558— monoruby/src/value/rvalue/string/transcode.rs:4558-4572 | monoruby/src/value/rvalue/string/transcode.rs:4579-4594 — 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.
JitContext::compile_instruction_inner (cyclomatic 149) monoruby/src/codegen/jitgen/compile.rs:419— JitContext::compile_instruction_inner 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.
JitContext::compile_method_call (cyclomatic 109) monoruby/src/codegen/jitgen/compile/method_call.rs:781— JitContext::compile_method_call has cyclomatic complexity 109 (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.
JitContext::loop_float_candidates (cyclomatic 43) monoruby/src/codegen/jitgen/compile/loop_analysis.rs:904— JitContext::loop_float_candidates 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.
JitContext::compile_binary (cyclomatic 38) monoruby/src/codegen/jitgen/compile/binary_op.rs:880— JitContext::compile_binary has cyclomatic complexity 38 (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.
JitContext::record_pre_fixpoint_outer_floats (cyclomatic 37) monoruby/src/codegen/jitgen/compile/loop_analysis.rs:1201— JitContext::record_pre_fixpoint_outer_floats 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.
JitContext::region_summary (cyclomatic 32) monoruby/src/codegen/jitgen/compile/loop_analysis.rs:728— JitContext::region_summary 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.
JitContext::inline_class_new (cyclomatic 30) monoruby/src/codegen/jitgen/compile/method_call.rs:2261— JitContext::inline_class_new has cyclomatic complexity 30 (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.
JitContext::incoming_context (cyclomatic 30) monoruby/src/codegen/jitgen/merge.rs:77— JitContext::incoming_context 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.
JitContext::may_consume_virtual (cyclomatic 26) monoruby/src/codegen/jitgen/compile/escape.rs:758— JitContext::may_consume_virtual has cyclomatic complexity 26 (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.
JitContext::settle_virtuals (cyclomatic 23) monoruby/src/codegen/jitgen/compile/escape.rs:287— JitContext::settle_virtuals has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
JitContext::method_call (cyclomatic 22) monoruby/src/codegen/jitgen/compile/method_call.rs:56— JitContext::method_call 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.
JitContext::resolve_dyn_var_offset_in (cyclomatic 22) monoruby/src/codegen/jitgen/context.rs:3425— JitContext::resolve_dyn_var_offset_in 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.
JitContext::consume_virtual (cyclomatic 20) monoruby/src/codegen/jitgen/compile/escape.rs:1130— JitContext::consume_virtual 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.
JitContext::consume_virtual_index (cyclomatic 20) monoruby/src/codegen/jitgen/compile/escape.rs:1672— JitContext::consume_virtual_index 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.
JitContext::try_splice_exit (cyclomatic 20) monoruby/src/codegen/jitgen/context.rs:2595— JitContext::try_splice_exit 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.
JitContext::build_return_segments (cyclomatic 19) monoruby/src/codegen/jitgen/context.rs:4583— JitContext::build_return_segments has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
JitContext::compile_basic_block (cyclomatic 17) monoruby/src/codegen/jitgen/compile.rs:180— JitContext::compile_basic_block 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.
JitContext::specialized_iseq (cyclomatic 16) monoruby/src/codegen/jitgen/compile/method_call.rs:2640— JitContext::specialized_iseq 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.
JitContext::pic_groups (cyclomatic 16) monoruby/src/codegen/jitgen/compile/pic.rs:119— JitContext::pic_groups 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×18
Edited copy of a member (8 corresponding lines) hashbrown/src/set.rs:636— hashbrown/src/set.rs:636-643 | hashbrown/src/set.rs:681-695 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/object_space.rs:678— monoruby/src/builtins/object_space.rs:678-685 | monoruby/src/builtins/object_space.rs:727-734 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/time.rs:1700— monoruby/src/builtins/time.rs:1700-1710 | monoruby/src/builtins/time.rs:1733-1740 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/executor.rs:3712— monoruby/src/executor.rs:3712-3719 | monoruby/src/executor.rs:3728-3735 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/argf.rs:493— monoruby/src/builtins/argf.rs:493-500 | monoruby/src/builtins/argf.rs:503-514 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/symbol.rs:610— monoruby/src/builtins/symbol.rs:610-617 | monoruby/src/builtins/symbol.rs:626-633 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/codegen/jitgen/state/binop.rs:890— monoruby/src/codegen/jitgen/state/binop.rs:890-898 | monoruby/src/codegen/jitgen/state/binop.rs:905-912 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/builtins/string.rb:100— monoruby/builtins/string.rb:100-107 | monoruby/builtins/string.rb:112-119 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/enumerator.rs:609— monoruby/src/builtins/enumerator.rs:609-623 | monoruby/src/builtins/enumerator.rs:638-645 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/method.rs:488— monoruby/src/builtins/method.rs:488-495 | monoruby/src/builtins/method.rs:548-555 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/array.rs:976— monoruby/src/builtins/array.rs:976-983 | monoruby/src/builtins/array.rs:992-999 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/time.rs:1688— monoruby/src/builtins/time.rs:1688-1695 | monoruby/src/builtins/time.rs:1743-1750 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/value/rvalue.rs:1584— monoruby/src/value/rvalue.rs:1584-1594 | monoruby/src/value/rvalue.rs:1602-1609 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/codegen.rs:635— monoruby/src/codegen.rs:635-642 | monoruby/src/codegen.rs:663-671 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/io_buffer.rs:1776— monoruby/src/builtins/io_buffer.rs:1776-1784 | monoruby/src/builtins/io_buffer.rs:1792-1799 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) ext/sqlite3/src/lib.rs:733— ext/sqlite3/src/lib.rs:733-740 | ext/sqlite3/src/lib.rs:813-820 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) monoruby/src/builtins/numeric/rational.rs:545— monoruby/src/builtins/numeric/rational.rs:545-552 | monoruby/src/builtins/kernel.rs:6404-6413 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) ext/nokogiri/src/node.rs:671— ext/nokogiri/src/node.rs:671-681 | ext/nokogiri/src/node.rs:729-736 — 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.
FixmeComment rubymap/src/map/iter.rs:75— // FIXME(#26925) Remove in favor of `#[derive(Clone)]`
FixmeComment rubymap/src/map/iter.rs:356— // FIXME(#26925) Remove in favor of `#[derive(Clone)]`
FixmeComment rubymap/src/map/iter.rs:527— // FIXME(#26925) Remove in favor of `#[derive(Clone)]`
FixmeComment hashbrown/src/map.rs:1654— // FIXME(#26925) Remove in favor of `#[derive(Clone)]`
FixmeComment hashbrown/src/map.rs:1954— // FIXME(#26925) Remove in favor of `#[derive(Clone)]`
FixmeComment hashbrown/src/map.rs:2002— // FIXME(#26925) Remove in favor of `#[derive(Clone)]`
FixmeComment hashbrown/src/table.rs:1755— // FIXME(#26925) Remove in favor of `#[derive(Clone)]`
FixmeComment hashbrown/src/table.rs:1887— // FIXME(#26925) Remove in favor of `#[derive(Clone)]`
FixmeComment monoruby/builtins/monitor.rb:293— # FIXME: This isn't documented in Nutshell. — 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 hashbrown/tests/hasher.rs:3— // FIXME: takes too long — 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 hashbrown/tests/set.rs:1— // FIXME: takes too long — 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 hashbrown/src/map.rs:4359— // FIXME: takes too long — 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 hashbrown/src/set.rs:11— // Future Optimization (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 hashbrown/src/util.rs:1— // FIXME: Branch prediction hint. This is currently only available on nightly — 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 hashbrown/src/util.rs:5— // FIXME: use strict provenance functions once they are stable. — 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.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×17
Edited copy of a member (9 corresponding lines) ext/zstd/src/lib.rs:476— ext/zstd/src/lib.rs:476-490 | ext/zstd/src/lib.rs:493-501 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2636— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2636-2644 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2650-2658 — 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) ext/markly/src/lib.rs:368— ext/markly/src/lib.rs:368-376 | ext/markly/src/lib.rs:381-389 — 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) monoruby/src/value/coerce.rs:548— monoruby/src/value/coerce.rs:548-556 | monoruby/src/value/coerce.rs:564-572 — 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) monoruby/src/builtins/numeric/complex.rs:585— monoruby/src/builtins/numeric/complex.rs:585-593 | monoruby/src/builtins/time.rs:4434-4446 — 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) monoruby/src/builtins/kernel.rs:3377— monoruby/src/builtins/kernel.rs:3377-3385 | monoruby/src/builtins/module.rs:810-818 — 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) monoruby/builtins/array.rb:212— monoruby/builtins/array.rb:212-220 | monoruby/builtins/hash.rb:298-306 — 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) monoruby/src/builtins/method.rs:232— monoruby/src/builtins/method.rs:232-240 | monoruby/src/builtins/method.rs:249-257 — 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) monoruby/src/bytecodegen/expression.rs:2111— monoruby/src/bytecodegen/expression.rs:2111-2119 | monoruby/src/bytecodegen/expression.rs:2125-2138 — 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) monoruby/src/value/coerce.rs:16— monoruby/src/value/coerce.rs:16-24 | monoruby/src/value/coerce.rs:37-45 — 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) monoruby/src/builtins/file.rs:835— monoruby/src/builtins/file.rs:835-844 | monoruby/src/builtins/file.rs:857-865 — 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) monoruby/src/value.rs:340— monoruby/src/value.rs:340-348 | monoruby/src/value.rs:456-465 — 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) monoruby/src/codegen/jitgen/state/slot.rs:2128— monoruby/src/codegen/jitgen/state/slot.rs:2128-2140 | monoruby/src/codegen/jitgen/state/slot.rs:2142-2150 — 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) monoruby/src/value/coerce.rs:112— monoruby/src/value/coerce.rs:112-120 | monoruby/src/value/coerce.rs:143-156 — 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) monoruby/src/value/rvalue/string.rs:3675— monoruby/src/value/rvalue/string.rs:3675-3689 | monoruby/src/value/rvalue/string.rs:3819-3827 — 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) hashbrown/src/map.rs:3069— hashbrown/src/map.rs:3069-3077 | rubymap/src/map/core/entry.rs:98-106 — 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) monoruby/src/builtins/hash.rs:1901— monoruby/src/builtins/hash.rs:1901-1910 | REDACTED:2949-2957 — 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.
ClassTooLong: Lowerer monoruby/src/parser/prism_backend.rs:657— ClassTooLong — 2979 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 86 methods, 2 blocks, lines 657-5584. The bar is 400 significant lines; this is 2579 over it, 7.45× 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: Executor monoruby/src/executor.rs:275— ClassTooLong — 2888 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 308 methods, 13 blocks, lines 275-6099. The bar is 400 significant lines; this is 2488 over it, 7.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: Store monoruby/src/globals/store.rs:110— ClassTooLong — 1549 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 199 methods, 20 blocks, lines 110-3083. The bar is 400 significant lines; this is 1149 over it, 3.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.
ClassTooLong: Value monoruby/src/value.rs:240— ClassTooLong — 1486 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 314 methods, 20 blocks, lines 240-4090. The bar is 400 significant lines; this is 1086 over it, 3.72× 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: RegexpInner monoruby/src/value/rvalue/regexp.rs:179— ClassTooLong — 1475 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, 7 blocks, lines 179-4119. The bar is 400 significant lines; this is 1075 over it, 3.69× 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: RValue monoruby/src/value/rvalue.rs:659— ClassTooLong — 1344 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 181 methods, 12 blocks, lines 659-3133. The bar is 400 significant lines; this is 944 over it, 3.36× 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: IoInner monoruby/src/value/rvalue/io.rs:621— ClassTooLong — 1138 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, 2 blocks, lines 621-2811. The bar is 400 significant lines; this is 738 over it, 2.85× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MonorubyErr monoruby/src/globals/error.rs:110— ClassTooLong — 957 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 139 methods, 5 blocks, lines 110-1851. The bar is 400 significant lines; this is 557 over it, 2.39× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BytecodeGen monoruby/src/bytecodegen.rs:648— ClassTooLong — 950 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 204 methods, 7 blocks, lines 648-2452. The bar is 400 significant lines; this is 550 over it, 2.38× 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: Globals monoruby/src/globals.rs:360— ClassTooLong — 913 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 171 methods, 12 blocks, lines 360-2358. The bar is 400 significant lines; this is 513 over it, 2.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: MarshalReader monoruby/src/builtins/marshal.rs:255— ClassTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 32 methods, 2 blocks, lines 255-1570. The bar is 400 significant lines; this is 326 over it, 1.82× 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: Allocator monoruby/src/alloc.rs:789— ClassTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 74 methods, 5 blocks, lines 789-2558. The bar is 400 significant lines; this is 263 over it, 1.66× 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: RubyMap rubymap/src/map.rs:76— ClassTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 92 methods, 18 blocks, lines 76-1728. The bar is 400 significant lines; this is 247 over it, 1.62× 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: IndexMapCore rubymap/src/map/core.rs:32— ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 38 methods, 4 blocks, lines 32-1023. The bar is 400 significant lines; this is 150 over it, 1.38× 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: Codegen monoruby/src/codegen.rs:983— ClassTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 631 methods, 7 blocks, lines 983-2229. The bar is 400 significant lines; this is 136 over it, 1.34× 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: ISeqInfo monoruby/src/globals/store/iseq.rs:262— ClassTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 73 methods, 4 blocks, lines 262-1539. The bar is 400 significant lines; this is 117 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×16
Edited copy of a member (7 corresponding lines) monoruby/gem/gosu.rb:1672— monoruby/gem/gosu.rb:1672-1678 | monoruby/gem/gosu.rb:1682-1690 — 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) monoruby/src/builtins/module.rs:2768— monoruby/src/builtins/module.rs:2768-2774 | monoruby/src/builtins/module.rs:2790-2796 — 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) monoruby/src/bytecodegen/expression.rs:2506— monoruby/src/bytecodegen/expression.rs:2506-2512 | monoruby/src/bytecodegen/expression.rs:2520-2527 — 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) monoruby/src/builtins/time.rs:4462— monoruby/src/builtins/time.rs:4462-4472 | monoruby/src/builtins/time.rs:4477-4483 — 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) ext/bcrypt/src/lib.rs:26— ext/bcrypt/src/lib.rs:26-32 | ext/digest/src/lib.rs:39-46 — 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) monoruby/src/builtins/time.rs:2595— monoruby/src/builtins/time.rs:2595-2605 | monoruby/src/builtins/time.rs:2642-2648 — 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) monoruby/src/alloc.rs:2105— monoruby/src/alloc.rs:2105-2111 | monoruby/src/alloc.rs:2278-2284 — 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) monoruby/src/builtins/symbol.rs:508— monoruby/src/builtins/symbol.rs:508-514 | monoruby/src/builtins/symbol.rs:530-543 — 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) monoruby/src/builtins/fiddle.rs:962— monoruby/src/builtins/fiddle.rs:962-972 | monoruby/src/builtins/kernel.rs:4923-4929 — 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) monoruby/src/builtins/file.rs:2124— monoruby/src/builtins/file.rs:2124-2130 | monoruby/src/builtins/file.rs:2141-2147 — 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) ext/nokogiri/src/lib.rs:583— ext/nokogiri/src/lib.rs:583-589 | ext/nokogiri/src/lib.rs:791-797 — 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) ext/zstd/src/lib.rs:130— ext/zstd/src/lib.rs:130-136 | ext/zstd/src/lib.rs:138-144 — 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) monoruby/src/scheduler/native.rs:162— monoruby/src/scheduler/native.rs:162-168 | monoruby/src/scheduler/native.rs:170-176 — 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) monoruby/src/builtins.rs:98— monoruby/src/builtins.rs:98-104 | monoruby/src/value/rvalue/string/pack.rs:1635-1642 — 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) hashbrown/src/raw/mod.rs:1117— hashbrown/src/raw/mod.rs:1117-1123 | hashbrown/src/table.rs:1725-1731 — 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) hashbrown/src/raw/mod.rs:1133— hashbrown/src/raw/mod.rs:1133-1139 | hashbrown/src/table.rs:1797-1803 — 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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×15
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×15
Edited copy of a member (14 corresponding lines) monoruby/src/builtins/io.rs:2688— monoruby/src/builtins/io.rs:2688-2813 | monoruby/src/builtins/io.rs:6016-6056 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/builtins/string.rs:4717— monoruby/src/builtins/string.rs:4717-4733 | monoruby/src/builtins/string.rs:4773-4786 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/builtins/hash.rs:1826— monoruby/src/builtins/hash.rs:1826-1839 | monoruby/src/builtins/hash.rs:1855-1870 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/value/rvalue/ivar_table.rs:223— monoruby/src/value/rvalue/ivar_table.rs:223-236 | monoruby/src/value/rvalue/ivar_table.rs:242-255 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1477— monoruby/src/codegen/arch/aarch64/compile/mod.rs:1477-1490 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:1506-1519 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/codegen/jitgen/state/slot.rs:2229— monoruby/src/codegen/jitgen/state/slot.rs:2229-2242 | monoruby/src/codegen/jitgen/state/slot.rs:2244-2257 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/value/rvalue/array.rs:510— monoruby/src/value/rvalue/array.rs:510-523 | monoruby/src/value/rvalue/array.rs:531-544 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/value/rvalue/io.rs:1380— monoruby/src/value/rvalue/io.rs:1380-1394 | monoruby/src/value/rvalue/io.rs:1420-1433 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/executor.rs:3363— monoruby/src/executor.rs:3363-3387 | monoruby/src/executor.rs:3436-3449 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/globals/store.rs:994— monoruby/src/globals/store.rs:994-1009 | monoruby/src/globals/store.rs:1036-1049 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/globals/store/function.rs:1075— monoruby/src/globals/store/function.rs:1075-1088 | monoruby/src/globals/store/function.rs:1115-1128 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/builtins/json.rs:810— monoruby/src/builtins/json.rs:810-823 | monoruby/src/builtins/json.rs:1853-1871 — 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.
Edited copy of a member (14 corresponding lines) REDACTED:3739— REDACTED:3739-3752 | REDACTED:3790-3803 — 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.
Edited copy of a member (14 corresponding lines) hashbrown/src/table.rs:298— hashbrown/src/table.rs:298-313 | hashbrown/src/table.rs:336-349 — 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.
Edited copy of a member (14 corresponding lines) monoruby/src/ext.rs:1167— monoruby/src/ext.rs:1167-1182 | monoruby/src/ext.rs:2187-2200 — 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.
Executor::format_by_args (cognitive 451) monoruby/src/executor/format.rs:825— Executor::format_by_args has cognitive complexity 451 (threshold 15). Drivers by points: if/else 151 (366 pts), match/switch 14 (39 pts), boolean chains 28, loops 7 (18 pts) (nesting depth added 251). Of this number, 436 points are the body's own statements and 15 belong to 3 function items inside it that branch. 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.
Executor::require (cognitive 46) monoruby/src/executor.rs:1442— Executor::require has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 5 (8 pts), match/switch 4 (8 pts), boolean chains 4 (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.
Executor::probe_constant (cognitive 43) monoruby/src/executor/constants.rs:707— Executor::probe_constant has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (29 pts), match/switch 5 (12 pts), boolean chains 1, loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Executor::take_ex_obj (cognitive 38) monoruby/src/executor.rs:2486— Executor::take_ex_obj has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (29 pts), match/switch 3 (5 pts), loops 1 (3 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.
Executor::callsite_args (cognitive 29) monoruby/src/executor.rs:4355— Executor::callsite_args has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 3 (7 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Executor::get_constant (cognitive 25) monoruby/src/executor/constants.rs:60— Executor::get_constant has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 6 (10 pts), boolean chains 1 (nesting depth added 12). 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.
Executor::search_constant_no_missing (cognitive 24) monoruby/src/executor/constants.rs:468— Executor::search_constant_no_missing has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (20 pts), match/switch 2 (3 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.
Executor::find_constant_impl (cognitive 22) monoruby/src/executor.rs:3020— Executor::find_constant_impl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), match/switch 3 (8 pts), loops 1 (nesting depth added 8). 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.
Executor::eq_values_pure (cognitive 19) monoruby/src/executor/op.rs:883— Executor::eq_values_pure has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, match/switch 3 (4 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.
Executor::mark (cognitive 19) monoruby/src/executor.rs:597— Executor::mark has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 6 (7 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Executor::find_method (cognitive 18) monoruby/src/executor.rs:4023— Executor::find_method has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (5 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.
Executor::define_class (cognitive 17) monoruby/src/executor.rs:5260— Executor::define_class has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Executor::nearest_caller_location (cognitive 16) monoruby/src/executor/op.rs:1526— Executor::nearest_caller_location has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 1 (2 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.
Executor::materialize_escaped_block_handlers (cognitive 16) monoruby/src/executor.rs:5590— Executor::materialize_escaped_block_handlers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×14
Edited copy of a member (16 corresponding lines) monoruby/gem/gosu.rb:1762— monoruby/gem/gosu.rb:1762-1778 | monoruby/gem/gosu.rb:1787-1805 — 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) rubymap/src/map.rs:986— rubymap/src/map.rs:986-1001 | rubymap/src/map.rs:1119-1134 — 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) ext/markly/src/lib.rs:52— ext/markly/src/lib.rs:52-74 | ext/psych/src/lib.rs:34-49 — 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) monoruby/src/builtins/module.rs:3208— monoruby/src/builtins/module.rs:3208-3226 | monoruby/src/builtins/module.rs:3245-3260 — 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) monoruby/src/globals/store.rs:1859— monoruby/src/globals/store.rs:1859-1878 | monoruby/src/globals/store.rs:1887-1902 — 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) ext/nokogiri/src/document.rs:69— ext/nokogiri/src/document.rs:69-89 | ext/nokogiri/src/schema.rs:151-166 — 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) monoruby/src/builtins/array.rs:4083— monoruby/src/builtins/array.rs:4083-4101 | monoruby/src/builtins/array.rs:4133-4148 — 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) monoruby/src/codegen/jitgen/state/slot.rs:2193— monoruby/src/codegen/jitgen/state/slot.rs:2193-2210 | monoruby/src/codegen/jitgen/state/slot.rs:2212-2227 — 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) monoruby/src/ext.rs:2286— monoruby/src/ext.rs:2286-2301 | monoruby/src/ext.rs:2338-2357 — 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) monoruby/src/value/rvalue/hash.rs:1078— monoruby/src/value/rvalue/hash.rs:1078-1097 | monoruby/src/value/rvalue/hash.rs:1103-1118 — 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) hashbrown/src/map.rs:1021— hashbrown/src/map.rs:1021-1036 | hashbrown/src/map.rs:1064-1079 — 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) monoruby/src/value/rvalue.rs:1663— monoruby/src/value/rvalue.rs:1663-1678 | monoruby/src/value/rvalue.rs:1680-1699 — 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) monoruby/src/ext.rs:1800— monoruby/src/ext.rs:1800-1815 | monoruby/src/ext.rs:1821-1836 — 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) monoruby/src/ast/source_info.rs:136— monoruby/src/ast/source_info.rs:136-151 | monoruby/src/ast/source_info.rs:163-178 — 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 copy of a member (11 corresponding lines) · ×14
Edited copy of a member (11 corresponding lines) monoruby/gem/bigdecimal/math.rb:231— monoruby/gem/bigdecimal/math.rb:231-242 | monoruby/gem/bigdecimal/math.rb:257-267 — 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) monoruby/src/codegen/jitgen/state/binop.rs:770— monoruby/src/codegen/jitgen/state/binop.rs:770-780 | monoruby/src/codegen/jitgen/state/binop.rs:793-806 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1153— monoruby/src/codegen/arch/aarch64/compile/mod.rs:1153-1163 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2619-2629 — 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) monoruby/src/executor/op.rs:1771— monoruby/src/executor/op.rs:1771-1781 | monoruby/src/executor/op.rs:1840-1850 — 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) ext/nokogiri/src/node_set.rs:255— ext/nokogiri/src/node_set.rs:255-265 | ext/nokogiri/src/node_set.rs:268-281 — 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) monoruby/src/value/rvalue/fiber.rs:60— monoruby/src/value/rvalue/fiber.rs:60-70 | monoruby/src/value/rvalue/thread.rs:176-186 — 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) monoruby/src/id_table.rs:788— monoruby/src/id_table.rs:788-798 | monoruby/src/id_table.rs:800-810 — 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) monoruby_ext/src/lib.rs:516— monoruby_ext/src/lib.rs:516-527 | monoruby_ext/src/lib.rs:547-557 — 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) monoruby/src/builtins/numeric/float.rs:741— monoruby/src/builtins/numeric/float.rs:741-751 | monoruby/src/builtins/numeric/float.rs:754-764 — 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) monoruby/src/codegen/jitgen/context.rs:318— monoruby/src/codegen/jitgen/context.rs:318-328 | monoruby/src/codegen/jitgen/context.rs:474-484 — 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) rubymap/src/map/core.rs:853— rubymap/src/map/core.rs:853-863 | rubymap/src/map/core.rs:926-936 — 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) monoruby/builtins/hash.rb:316— monoruby/builtins/hash.rb:316-326 | monoruby/builtins/hash.rb:330-340 — 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) ext/nokogiri/src/node.rs:961— ext/nokogiri/src/node.rs:961-971 | ext/nokogiri/src/node.rs:974-984 — 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) monoruby/src/ext.rs:258— monoruby/src/ext.rs:258-271 | monoruby/src/ext.rs:281-291 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×14
Edited copy of a member (4 corresponding lines) monoruby/src/alloc.rs:1042— monoruby/src/alloc.rs:1042-1048 | monoruby/src/executor.rs:6657-6660 — 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) monoruby/src/builtins/main_object.rs:140— monoruby/src/builtins/main_object.rs:140-143 | monoruby/src/builtins/module.rs:3280-3284 — 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) monoruby/src/alloc.rs:968— monoruby/src/alloc.rs:968-971 | monoruby/src/preempt.rs:74-77 — 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) monoruby/src/alloc.rs:977— monoruby/src/alloc.rs:977-980 | monoruby/src/preempt.rs:79-82 — 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) monoruby/src/value/rvalue/complex.rs:26— monoruby/src/value/rvalue/complex.rs:26-29 | monoruby/src/value/rvalue/range.rs:30-33 — 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) rubymap/src/map/iter.rs:479— rubymap/src/map/iter.rs:479-482 | rubymap/src/set/iter.rs:116-119 — 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) rubymap/src/map/iter.rs:143— rubymap/src/map/iter.rs:143-146 | rubymap/src/set/iter.rs:168-171 — 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) monoruby/src/builtins/numeric/float.rs:576— monoruby/src/builtins/numeric/float.rs:576-579 | REDACTED:501-504 — 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) monoruby/src/builtins/numeric/float.rs:588— monoruby/src/builtins/numeric/float.rs:588-591 | REDACTED:654-657 — 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) monoruby/src/builtins/numeric/float.rs:600— monoruby/src/builtins/numeric/float.rs:600-603 | REDACTED:741-744 — 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) monoruby/src/builtins/numeric/float.rs:612— monoruby/src/builtins/numeric/float.rs:612-615 | REDACTED:856-859 — 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) rubymap/src/map/slice.rs:92— rubymap/src/map/slice.rs:92-95 | rubymap/src/set/slice.rs:70-73 — 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) rubymap/src/map/slice.rs:129— rubymap/src/map/slice.rs:129-132 | rubymap/src/set/slice.rs:89-92 — 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) monoruby/src/builtins/hash.rs:2652— monoruby/src/builtins/hash.rs:2652-2657 | monoruby/src/builtins/set.rs:94-97 — 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 (14 lines × 2) monoruby/src/builtins/array.rs:443— monoruby/src/builtins/array.rs:443-456 | monoruby/src/builtins/array.rs:491-504 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:443` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/file.rs:2517— monoruby/src/builtins/file.rs:2517-2530 | monoruby/src/builtins/file.rs:2595-2608 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/file.rs:2517` 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) monoruby/src/builtins/io.rs:854— monoruby/src/builtins/io.rs:854-867 | monoruby/src/builtins/io.rs:3421-3434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/io.rs:854` 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) monoruby/src/builtins/io_buffer.rs:1072— monoruby/src/builtins/io_buffer.rs:1072-1085 | monoruby/src/builtins/io_buffer.rs:1191-1204 — both copies are in the same file, so extract the 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) monoruby/src/builtins/kernel.rs:4234— monoruby/src/builtins/kernel.rs:4234-4247 | monoruby/src/builtins/process.rs:423-436 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) REDACTED:581— REDACTED:581-594 | REDACTED:668-681 — both copies are in the same file, so extract the 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) REDACTED:1811— REDACTED:1811-1824 | REDACTED:1535-1548 — 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 `REDACTED:1811` 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) monoruby/src/bytecodegen/defined.rs:167— monoruby/src/bytecodegen/defined.rs:167-180 | monoruby/src/bytecodegen/defined.rs:370-383 — both copies are in the same file, so extract the 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) monoruby/src/codegen/jitgen/asmir.rs:4503— monoruby/src/codegen/jitgen/asmir.rs:4503-4516 | monoruby/src/codegen/jitgen/asmir.rs:4554-4567 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/asmir.rs:4503` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/compile/method_call.rs:2055— monoruby/src/codegen/jitgen/compile/method_call.rs:2055-2068 | monoruby/src/codegen/jitgen/compile/method_call.rs:2577-2590 — both copies are in the same file, so extract the 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) monoruby/src/value/rvalue/regexp.rs:1781— monoruby/src/value/rvalue/regexp.rs:1781-1794 | monoruby/src/value/rvalue/regexp.rs:1906-1919 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/regexp.rs:1781` 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) monoruby/src/value/rvalue/regexp.rs:3287— monoruby/src/value/rvalue/regexp.rs:3287-3300 | monoruby/src/value/rvalue/regexp.rs:3572-3585 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/regexp.rs:3287` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:222— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:222-235 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:606-619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:222` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/regexp.rs:1510— monoruby/src/builtins/regexp.rs:1510-1523 | monoruby/src/builtins/string.rs:1225-1238 — 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) monoruby/src/builtins/io.rs:2787— monoruby/src/builtins/io.rs:2787-2799 | monoruby/src/builtins/io.rs:6079-6091 — both copies are in the same file, so extract the 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) monoruby/src/builtins/json.rs:343— monoruby/src/builtins/json.rs:343-355 | monoruby/src/builtins/json.rs:1499-1511 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/json.rs:343` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/string.rs:4680— monoruby/src/builtins/string.rs:4680-4692 | monoruby/src/builtins/string.rs:4696-4708 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:4680` 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) monoruby/src/builtins/symbol.rs:123— monoruby/src/builtins/symbol.rs:123-135 | monoruby/src/value.rs:2284-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.
Duplicated block (13 lines × 2) monoruby/src/builtins/time.rs:2321— monoruby/src/builtins/time.rs:2321-2333 | monoruby/src/builtins/time.rs:2335-2347 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `monoruby/src/builtins/time.rs:2332` calls `Err`, `argumenterr` and `monoruby/src/builtins/time.rs:2319` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3365— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3365-3377 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4103-4115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3365` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/compile/frameless_call.rs:781— monoruby/src/codegen/jitgen/compile/frameless_call.rs:781-793 | monoruby/src/codegen/jitgen/compile/frameless_call.rs:941-953 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/compile/frameless_call.rs:781` 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) REDACTED:1338— REDACTED:1338-1350 | REDACTED:1364-1376 — both copies are in the same file, so extract the 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) monoruby/src/globals/prng.rs:255— monoruby/src/globals/prng.rs:255-267 | monoruby/src/globals/prng.rs:387-399 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/globals/prng.rs:255` 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) monoruby/src/value.rs:392— monoruby/src/value.rs:392-404 | monoruby/src/value.rs:427-439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value.rs:392` 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, `monoruby/src/value.rs:389` calls `with`, `borrow_mut`, `remove` and `monoruby/src/value.rs:426` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) monoruby/src/value.rs:2396— monoruby/src/value.rs:2396-2408 | monoruby/src/value.rs:2466-2478 — both copies are in the same file, so extract the 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) monoruby/src/value/rvalue/io.rs:2255— monoruby/src/value/rvalue/io.rs:2255-2267 | monoruby/src/value/rvalue/io.rs:2298-2310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/io.rs:2255` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/compile/frameless_call.rs:522— monoruby/src/codegen/jitgen/compile/frameless_call.rs:522-534 | monoruby/src/codegen/jitgen/compile/frameless_call.rs:567-579 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/compile/frameless_call.rs:522` 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) monoruby/builtins/enumerable.rb:361— monoruby/builtins/enumerable.rb:361-373 | monoruby/builtins/enumerable.rb:580-592 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
BytecodeGen::gen_expr_inner (cognitive 153) monoruby/src/bytecodegen/expression.rs:458— BytecodeGen::gen_expr_inner has cognitive complexity 153 (threshold 15). Drivers by points: if/else 61 (117 pts), match/switch 11 (24 pts), boolean chains 8, loops 2 (4 pts) (nesting depth added 71). 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.
BytecodeGen::level_down (cognitive 65) monoruby/src/bytecodegen/method_call.rs:428— BytecodeGen::level_down has cognitive complexity 65 (threshold 15). Drivers by points: if/else 20 (49 pts), loops 5 (10 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 36). 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.
BytecodeGen::gen_begin (cognitive 63) monoruby/src/bytecodegen/statement.rs:435— BytecodeGen::gen_begin has cognitive complexity 63 (threshold 15). Drivers by points: if/else 29 (53 pts), loops 2 (6 pts), boolean chains 3, match/switch 1 (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.
BytecodeGen::gen_case (cognitive 62) monoruby/src/bytecodegen/statement.rs:296— BytecodeGen::gen_case has cognitive complexity 62 (threshold 15). Drivers by points: if/else 18 (37 pts), loops 7 (24 pts), match/switch 1 (nesting depth added 36). Of this number, 56 points are the body's own statements and 6 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.
BytecodeGen::check_defined (cognitive 53) monoruby/src/bytecodegen/defined.rs:91— BytecodeGen::check_defined has cognitive complexity 53 (threshold 15). Drivers by points: if/else 15 (27 pts), loops 7 (16 pts), match/switch 3 (8 pts), boolean chains 2 (nesting depth added 26). 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.
BytecodeGen::gen_method_call (cognitive 43) monoruby/src/bytecodegen/method_call.rs:67— BytecodeGen::gen_method_call has cognitive complexity 43 (threshold 15). Drivers by points: if/else 26 (31 pts), boolean chains 9, match/switch 3 (nesting depth added 5). 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.
BytecodeGen::gen_store_expr (cognitive 41) monoruby/src/bytecodegen/expression.rs:134— BytecodeGen::gen_store_expr has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (32 pts), match/switch 4 (7 pts), boolean chains 2 (nesting depth added 17). 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.
BytecodeGen::inst_to_bc (cognitive 36) monoruby/src/bytecodegen/encode.rs:186— BytecodeGen::inst_to_bc has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (21 pts), match/switch 7 (11 pts), loops 2 (4 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BytecodeGen::gen_mul_assign (cognitive 29) monoruby/src/bytecodegen/expression.rs:1629— BytecodeGen::gen_mul_assign has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 4 (6 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BytecodeGen::handle_super_forward (cognitive 26) monoruby/src/bytecodegen/method_call/arguments.rs:164— BytecodeGen::handle_super_forward has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (21 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.
BytecodeGen::gen_for (cognitive 20) monoruby/src/bytecodegen/statement.rs:10— BytecodeGen::gen_for has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BytecodeGen::gen_regexp (cognitive 19) monoruby/src/bytecodegen/expression.rs:2255— BytecodeGen::gen_regexp has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 5 (7 pts), loops 2 (3 pts) (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.
BytecodeGen::handle_forward (cognitive 17) monoruby/src/bytecodegen/method_call/arguments.rs:86— BytecodeGen::handle_forward has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (17 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.
BytecodeGen::gen_expr_inner (cyclomatic 106) monoruby/src/bytecodegen/expression.rs:458— BytecodeGen::gen_expr_inner 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.
BytecodeGen::inst_to_bc (cyclomatic 87) monoruby/src/bytecodegen/encode.rs:186— BytecodeGen::inst_to_bc has cyclomatic complexity 87 (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.
BytecodeGen::gen_store_expr (cyclomatic 63) monoruby/src/bytecodegen/expression.rs:134— BytecodeGen::gen_store_expr has cyclomatic complexity 63 (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.
BytecodeGen::check_defined (cyclomatic 59) monoruby/src/bytecodegen/defined.rs:91— BytecodeGen::check_defined has cyclomatic complexity 59 (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.
BytecodeGen::level_down (cyclomatic 50) monoruby/src/bytecodegen/method_call.rs:428— BytecodeGen::level_down has cyclomatic complexity 50 (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.
BytecodeGen::gen_method_call (cyclomatic 33) monoruby/src/bytecodegen/method_call.rs:67— BytecodeGen::gen_method_call has cyclomatic complexity 33 (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.
BytecodeGen::gen_begin (cyclomatic 27) monoruby/src/bytecodegen/statement.rs:435— BytecodeGen::gen_begin 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.
BytecodeGen::gen_case (cyclomatic 21) monoruby/src/bytecodegen/statement.rs:296— BytecodeGen::gen_case has cyclomatic complexity 21 (threshold 15). Of this number, 17 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.
BytecodeGen::gen_regexp (cyclomatic 20) monoruby/src/bytecodegen/expression.rs:2255— BytecodeGen::gen_regexp 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.
BytecodeGen::gen_mul_assign (cyclomatic 17) monoruby/src/bytecodegen/expression.rs:1629— BytecodeGen::gen_mul_assign 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.
BytecodeGen::eval_lvalue (cyclomatic 17) monoruby/src/bytecodegen.rs:2115— BytecodeGen::eval_lvalue 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.
BytecodeGen::hint (cyclomatic 16) monoruby/src/bytecodegen.rs:946— BytecodeGen::hint has cyclomatic complexity 16 (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.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×12
Edited copy of a member (6 corresponding lines) monoruby/src/builtins/module.rs:2934— monoruby/src/builtins/module.rs:2934-2939 | monoruby/src/builtins/module.rs:2953-2958 — 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.
Edited copy of a member (6 corresponding lines) monoruby/src/builtins/range.rs:672— monoruby/src/builtins/range.rs:672-677 | monoruby/src/builtins/range.rs:686-691 — 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.
Edited copy of a member (6 corresponding lines) monoruby/src/value/rvalue/fiber.rs:493— monoruby/src/value/rvalue/fiber.rs:493-498 | monoruby/src/value/rvalue/fiber.rs:511-516 — 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.
Edited copy of a member (6 corresponding lines) monoruby/src/builtins/argf.rs:126— monoruby/src/builtins/argf.rs:126-134 | monoruby/src/builtins/array.rs:276-281 — 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.
Edited copy of a member (6 corresponding lines) monoruby/gem/nokogiri/xml/builder.rb:366— monoruby/gem/nokogiri/xml/builder.rb:366-373 | monoruby/gem/nokogiri/xml/document_fragment.rb:139-144 — 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.
Edited copy of a member (6 corresponding lines) monoruby/src/builtins/io.rs:3613— monoruby/src/builtins/io.rs:3613-3620 | monoruby/src/builtins/io_buffer.rs:1276-1281 — 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.
Edited copy of a member (6 corresponding lines) monoruby/src/executor.rs:5841— monoruby/src/executor.rs:5841-5847 | monoruby/src/value/rvalue/weakmap.rs:85-90 — 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.
Edited copy of a member (6 corresponding lines) hashbrown/src/map.rs:1135— hashbrown/src/map.rs:1135-1141 | rubymap/src/map.rs:961-966 — 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.
Edited copy of a member (6 corresponding lines) hashbrown/src/map.rs:1188— hashbrown/src/map.rs:1188-1194 | rubymap/src/map.rs:1094-1099 — 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.
Edited copy of a member (6 corresponding lines) monoruby/src/codegen/jitgen/state/liveness.rs:47— monoruby/src/codegen/jitgen/state/liveness.rs:47-52 | monoruby/src/codegen/jitgen/state/slot.rs:1608-1614 — 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.
Edited copy of a member (6 corresponding lines) hashbrown/src/map.rs:275— hashbrown/src/map.rs:275-280 | monoruby/src/value/rvalue/hash.rs:220-225 — 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.
Edited copy of a member (6 corresponding lines) monoruby/gem/json/add/ostruct.rb:34— monoruby/gem/json/add/ostruct.rb:34-39 | monoruby/gem/json/add/struct.rb:31-36 — 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.
Codegen::encode_linst (cognitive 78) monoruby/src/codegen/arch/x86_64/compile/mod.rs:353— Codegen::encode_linst has cognitive complexity 78 (threshold 15). Drivers by points: if/else 20 (36 pts), match/switch 19 (36 pts), loops 3 (6 pts) (nesting depth added 36). 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.
Codegen::encode_linst (cognitive 60) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1575— Codegen::encode_linst has cognitive complexity 60 (threshold 15). Drivers by points: if/else 18 (34 pts), match/switch 10 (20 pts), loops 3 (6 pts) (nesting depth added 29). 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.
Codegen::gen_machine_code_inner (cognitive 44) monoruby/src/codegen/jitgen.rs:1087— Codegen::gen_machine_code_inner has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (29 pts), boolean chains 12, loops 3 (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.
Codegen::gen_asm (cognitive 42) monoruby/src/codegen/jitgen/asmir.rs:4432— Codegen::gen_asm has cognitive complexity 42 (threshold 15). Drivers by points: if/else 19 (33 pts), loops 4 (5 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Codegen::compile_asmir (cognitive 41) monoruby/src/codegen/jitgen/asmir/compile_shared.rs:34— Codegen::compile_asmir has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (36 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 19). 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.
Codegen::gen_asm (cognitive 38) monoruby/src/codegen/arch/aarch64/compile/mod.rs:278— Codegen::gen_asm has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (32 pts), boolean chains 2, loops 2, match/switch 1 (2 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.
Codegen::a64_gen_chain_replay_stub (cognitive 23) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1214— Codegen::a64_gen_chain_replay_stub has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (11 pts), loops 7 (10 pts), if/else 1 (2 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.
Codegen::compile (cognitive 23) monoruby/src/codegen/compiler.rs:234— Codegen::compile has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 3, 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.
Codegen::jit_set_arguments_forwarded (cognitive 22) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1125— Codegen::jit_set_arguments_forwarded has cognitive complexity 22 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 5 (8 pts), match/switch 1 (4 pts) (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Codegen::emit_range_cover (cognitive 16) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3450— Codegen::emit_range_cover has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Codegen::emit_range_cover (cognitive 16) monoruby/src/codegen/arch/x86_64/compile/mod.rs:1893— Codegen::emit_range_cover has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×11
Edited copy of a member (18 corresponding lines) monoruby/src/builtins/method.rs:67— monoruby/src/builtins/method.rs:67-84 | monoruby/src/builtins/method.rs:106-123 — 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) monoruby/src/builtins/method.rs:662— monoruby/src/builtins/method.rs:662-679 | monoruby/src/builtins/method.rs:749-766 — 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) monoruby/src/builtins/array.rs:3323— monoruby/src/builtins/array.rs:3323-3340 | monoruby/src/builtins/array.rs:3463-3480 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3779— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3779-3796 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3799-3816 — 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) monoruby/src/value.rs:2339— monoruby/src/value.rs:2339-2356 | monoruby/src/value.rs:2363-2380 — 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) rubymap/src/map/core.rs:1178— rubymap/src/map/core.rs:1178-1195 | rubymap/src/map/core.rs:1207-1225 — 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) REDACTED:1018— REDACTED:1018-1036 | REDACTED:1049-1066 — 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) monoruby/builtins/thread.rb:763— monoruby/builtins/thread.rb:763-780 | monoruby/builtins/thread.rb:859-878 — 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) monoruby/src/value.rs:772— monoruby/src/value.rs:772-789 | monoruby/src/value.rs:815-833 — 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) monoruby/src/bytecodegen.rs:1934— monoruby/src/bytecodegen.rs:1934-1951 | monoruby/src/bytecodegen.rs:1961-1978 — 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) monoruby/stdlib/socket.rb:186— monoruby/stdlib/socket.rb:186-203 | monoruby/stdlib/socket.rb:208-226 — 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 copy of a member (17 corresponding lines) · ×11
Edited copy of a member (17 corresponding lines) monoruby/gem/gosu.rb:907— monoruby/gem/gosu.rb:907-926 | monoruby/gem/gosu.rb:936-952 — 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) monoruby/src/builtins/module.rs:2616— monoruby/src/builtins/module.rs:2616-2636 | monoruby/src/builtins/module.rs:2650-2666 — 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) monoruby/src/builtins/array.rs:2491— monoruby/src/builtins/array.rs:2491-2507 | monoruby/src/builtins/array.rs:2517-2533 — 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) monoruby/src/codegen/jitgen/context.rs:3581— monoruby/src/codegen/jitgen/context.rs:3581-3613 | monoruby/src/codegen/jitgen/context.rs:3633-3649 — 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) ext/nokogiri/src/node.rs:498— ext/nokogiri/src/node.rs:498-514 | ext/nokogiri/src/node.rs:517-533 — 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) monoruby/src/alloc.rs:2183— monoruby/src/alloc.rs:2183-2199 | monoruby/src/alloc.rs:2221-2249 — 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) monoruby/src/bytecodegen.rs:557— monoruby/src/bytecodegen.rs:557-573 | monoruby/src/parser/prism_backend.rs:5722-5738 — 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) hashbrown/src/map.rs:3976— hashbrown/src/map.rs:3976-3992 | rubymap/src/map.rs:1676-1693 — 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) monoruby/src/builtins/numeric/float.rs:785— monoruby/src/builtins/numeric/float.rs:785-803 | monoruby/src/builtins/numeric/float.rs:807-823 — 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) REDACTED:1808— REDACTED:1808-1824 | REDACTED:1532-1548 — 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) monoruby/src/builtins/regexp.rs:608— monoruby/src/builtins/regexp.rs:608-624 | monoruby/src/builtins/regexp.rs:659-677 — 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 (5 corresponding lines) · ×11
Edited copy of a member (5 corresponding lines) monoruby/src/builtins/kernel.rs:3723— monoruby/src/builtins/kernel.rs:3723-3727 | monoruby/src/builtins/kernel.rs:3791-3796 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) monoruby/src/value/rvalue/complex.rs:107— monoruby/src/value/rvalue/complex.rs:107-111 | monoruby/src/value/rvalue/complex.rs:114-118 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) rubymap/src/map.rs:1202— rubymap/src/map.rs:1202-1206 | rubymap/src/set.rs:744-748 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) rubymap/src/map.rs:1246— rubymap/src/map.rs:1246-1250 | rubymap/src/set.rs:775-779 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) monoruby/src/native_pool.rs:119— monoruby/src/native_pool.rs:119-125 | monoruby/src/scheduler/native.rs:135-139 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) monoruby/src/builtins/encoding.rs:5352— monoruby/src/builtins/encoding.rs:5352-5356 | monoruby/src/builtins/io.rs:6060-6066 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) monoruby/src/builtins/object_space.rs:743— monoruby/src/builtins/object_space.rs:743-748 | monoruby/src/builtins/string.rs:11558-11562 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) rubymap/src/map.rs:1264— rubymap/src/map.rs:1264-1268 | rubymap/src/set.rs:793-797 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) ext/nokogiri/src/dtd.rs:267— ext/nokogiri/src/dtd.rs:267-271 | ext/nokogiri/src/node_set.rs:205-209 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) ext/nokogiri/src/node.rs:586— ext/nokogiri/src/node.rs:586-590 | ext/nokogiri/src/reader.rs:477-483 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) ext/nokogiri/src/dtd.rs:313— ext/nokogiri/src/dtd.rs:313-317 | ext/nokogiri/src/node.rs:419-423 — These two members are one piece of code written twice and then edited apart: 5 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) monoruby/src/builtins/array.rs:4615— monoruby/src/builtins/array.rs:4615-4630 | monoruby/src/builtins/array.rs:4643-4658 — both copies are in the same file, so extract the 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) monoruby/src/builtins/io_buffer.rs:1093— monoruby/src/builtins/io_buffer.rs:1093-1108 | monoruby/src/builtins/io_buffer.rs:1207-1222 — both copies are in the same file, so extract the 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, `monoruby/src/builtins/io_buffer.rs:1224` calls `self_val`, `as_iobuffer`, `check_writable` and `monoruby/src/builtins/io_buffer.rs:1109` 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 (16 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:419— monoruby/src/codegen/arch/aarch64/compile/mod.rs:419-434 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:470-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:419` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:2152— monoruby/src/codegen/arch/aarch64/compile/mod.rs:2152-2167 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4803-4818 — both copies are in the same file, so extract the 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, `monoruby/src/codegen/arch/aarch64/compile/mod.rs:2169` calls `label` and `monoruby/src/codegen/arch/aarch64/compile/mod.rs:4819` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) monoruby/src/codegen/jitgen/asmir.rs:4532— monoruby/src/codegen/jitgen/asmir.rs:4532-4547 | monoruby/src/codegen/jitgen/asmir.rs:4590-4605 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/asmir.rs:4532` 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) monoruby/src/globals/store/class.rs:634— monoruby/src/globals/store/class.rs:634-649 | monoruby/src/globals/store/class.rs:665-680 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/globals/store/class.rs:634` it does not close everything it opens, so those exact lines 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) monoruby/src/globals/store/class.rs:3212— monoruby/src/globals/store/class.rs:3212-3227 | monoruby/src/globals/store/class.rs:3391-3406 — both copies are in the same file, so extract the 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) monoruby/src/value/rvalue/string.rs:6499— monoruby/src/value/rvalue/string.rs:6499-6514 | monoruby/src/value/rvalue/string.rs:6684-6699 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string.rs:6499` 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) monoruby/src/value/rvalue/string/transcode.rs:4814— monoruby/src/value/rvalue/string/transcode.rs:4814-4829 | monoruby/src/value/rvalue/string/transcode.rs:8509-8524 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/transcode.rs:4814` it does not close everything it opens, so those 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) monoruby/src/value/rvalue/string/transcode.rs:5412— monoruby/src/value/rvalue/string/transcode.rs:5412-5427 | monoruby/src/value/rvalue/string/transcode.rs:5574-5589 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/transcode.rs:5412` 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) monoruby/builtins/enumerable.rb:912— monoruby/builtins/enumerable.rb:912-927 | monoruby/builtins/enumerable.rb:1036-1051 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: Store (LCOM4 25) monoruby/src/globals/store.rs:110— Store's methods fall into 25 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 25 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Header (LCOM4 24) monoruby/src/globals/store/class_dispatch.rs:28— Header's methods fall into 24 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 24 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ClassInfoTable (LCOM4 16) monoruby/src/globals/store.rs:3085— ClassInfoTable's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Executor (LCOM4 8) monoruby/src/executor.rs:275— Executor's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Module (LCOM4 6) monoruby/src/value/rvalue/module.rs:4— Module's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SourceInfo (LCOM4 5) monoruby/src/ast/source_info.rs:90— SourceInfo's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Globals (LCOM4 5) monoruby/src/globals.rs:360— Globals's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Codegen (LCOM4 4) monoruby/src/codegen.rs:983— Codegen's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Lfp (LCOM4 4) monoruby/src/executor/frame.rs:317— Lfp's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ArrayInner (LCOM4 4) monoruby/src/value/rvalue/array.rs:266— ArrayInner's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Immediate (LCOM4 4) monoruby/src/value.rs:3960— Immediate's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
TooManyFields: VmHandlers monoruby/src/codegen.rs:1225— TooManyFields — 95 stored fields. The bar is 30 stored fields; this is 65 over it, 3.17× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: MrApi monoruby_ext_sys/src/lib.rs:216— TooManyFields — 95 stored fields. The bar is 30 stored fields; this is 65 over it, 3.17× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Codegen monoruby/src/codegen.rs:983— TooManyFields — 51 stored fields beside 631 methods. The bar is 30 stored fields; this is 21 over it, 1.70× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Store monoruby/src/globals/store.rs:110— TooManyFields — 42 stored fields beside 199 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.
TooManyFields: ISeqInfo monoruby/src/globals/store/iseq.rs:262— TooManyFields — 42 stored fields beside 73 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.
TooManyFields: Classes ext/nokogiri/src/lib.rs:170— TooManyFields — 42 stored fields. The bar is 30 stored fields; this is 12 over it, 1.40× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Allocator monoruby/src/alloc.rs:789— TooManyFields — 41 stored fields beside 74 methods. The bar is 30 stored fields; this is 11 over it, 1.37× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Executor monoruby/src/executor.rs:275— TooManyFields — 40 stored fields beside 308 methods. The bar is 30 stored fields; this is 10 over it, 1.33× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Globals monoruby/src/globals.rs:360— TooManyFields — 40 stored fields beside 171 methods. The bar is 30 stored fields; this is 10 over it, 1.33× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Opts monoruby/src/main.rs:83— TooManyFields — 34 stored fields. The bar is 30 stored fields; this is 4 over it, 1.13× 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.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×10
Edited copy of a member (22 corresponding lines) monoruby/src/builtins/set.rs:650— monoruby/src/builtins/set.rs:650-671 | monoruby/src/builtins/set.rs:685-711 — 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) REDACTED:411— REDACTED:411-432 | REDACTED:441-467 — 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) monoruby/src/builtins/enumerator.rs:382— monoruby/src/builtins/enumerator.rs:382-407 | monoruby/src/builtins/enumerator.rs:571-592 — 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) ext/nokogiri/src/node.rs:255— ext/nokogiri/src/node.rs:255-277 | ext/nokogiri/src/node.rs:280-301 — 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) monoruby/src/parser/prism_backend.rs:2951— monoruby/src/parser/prism_backend.rs:2951-2981 | monoruby/src/parser/prism_backend.rs:2983-3004 — 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) monoruby/gem/ffi_c.rb:1027— monoruby/gem/ffi_c.rb:1027-1051 | monoruby/gem/ffi_c.rb:1236-1257 — 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) hashbrown/src/raw/mod.rs:3195— hashbrown/src/raw/mod.rs:3195-3216 | hashbrown/src/raw/mod.rs:3248-3297 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:894— monoruby/src/codegen/arch/aarch64/compile/mod.rs:894-925 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:986-1007 — 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) monoruby/src/codegen/jitgen/compile/binary_op.rs:1346— monoruby/src/codegen/jitgen/compile/binary_op.rs:1346-1367 | monoruby/src/codegen/jitgen/compile/binary_op.rs:1384-1405 — 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) monoruby/builtins/enumerable.rb:474— monoruby/builtins/enumerable.rb:474-495 | monoruby/builtins/enumerable.rb:499-520 — 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 (20 corresponding lines) · ×10
Edited copy of a member (20 corresponding lines) rubymap/src/map/core.rs:825— rubymap/src/map/core.rs:825-844 | rubymap/src/map/core.rs:898-917 — 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) monoruby/src/builtins/array.rs:4613— monoruby/src/builtins/array.rs:4613-4632 | monoruby/src/builtins/array.rs:4641-4661 — 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) monoruby/src/builtins/string.rs:12576— monoruby/src/builtins/string.rs:12576-12598 | monoruby/src/builtins/string.rs:12608-12627 — 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) monoruby/src/executor.rs:4850— monoruby/src/executor.rs:4850-4869 | monoruby/src/executor.rs:4877-4900 — 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) monoruby/src/builtins/module.rs:2547— monoruby/src/builtins/module.rs:2547-2566 | monoruby/src/builtins/module.rs:2574-2602 — 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) monoruby/src/builtins/string.rs:12730— monoruby/src/builtins/string.rs:12730-12749 | monoruby/src/builtins/string.rs:12762-12783 — 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) monoruby/src/executor/format.rs:307— monoruby/src/executor/format.rs:307-329 | monoruby/src/executor/format.rs:341-360 — 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) monoruby/src/builtins/io.rs:2415— monoruby/src/builtins/io.rs:2415-2435 | monoruby/src/builtins/io.rs:2444-2463 — 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) monoruby/builtins/enumerable.rb:1182— monoruby/builtins/enumerable.rb:1182-1206 | monoruby/builtins/enumerable.rb:1213-1232 — 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) monoruby/builtins/enumerable.rb:1127— monoruby/builtins/enumerable.rb:1127-1148 | monoruby/builtins/enumerable.rb:1154-1173 — 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×9
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×9
Members sharing a duplicated core (4 members, 50+ identical tokens) hashbrown/src/control/group/generic.rs:58— hashbrown/src/control/group/generic.rs:58-69 | hashbrown/src/control/group/lsx.rs:33-44 | hashbrown/src/control/group/neon.rs:29-40 | hashbrown/src/control/group/sse2.rs:35-46 — 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) monoruby/src/builtins/hash.rs:2199— monoruby/src/builtins/hash.rs:2199-2230 | monoruby/src/builtins/hash.rs:2378-2404 | monoruby/src/builtins/hash.rs:2414-2445 | monoruby/src/builtins/hash.rs:3959-3985 — 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) monoruby/src/builtins/io_buffer.rs:583— monoruby/src/builtins/io_buffer.rs:583-632 | monoruby/src/builtins/io_buffer.rs:679-713 | monoruby/src/builtins/io_buffer.rs:1070-1126 | monoruby/src/builtins/io_buffer.rs:1181-1247 — 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) monoruby/src/builtins/numeric/float.rs:832— monoruby/src/builtins/numeric/float.rs:832-860 | monoruby/src/builtins/numeric/float.rs:869-897 | monoruby/src/builtins/numeric/float.rs:906-950 | monoruby/src/builtins/numeric/float.rs:960-1077 — 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) monoruby/src/builtins/string.rs:1542— monoruby/src/builtins/string.rs:1542-1571 | monoruby/src/builtins/string.rs:1580-1610 | monoruby/src/builtins/string.rs:3875-4099 | monoruby/src/builtins/string.rs:6417-6483 — 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) monoruby/src/builtins/string.rs:4567— monoruby/src/builtins/string.rs:4567-4662 | monoruby/src/builtins/string.rs:10704-10777 | monoruby/src/builtins/string.rs:11483-11544 | monoruby/src/builtins/string.rs:11590-11680 — 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) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:398— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:398-497 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1163-1241 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:1575-2611 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4242-4301 — 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) monoruby/src/executor/op.rs:385— monoruby/src/executor/op.rs:385-443 | monoruby/src/executor/op.rs:890-980 | monoruby/src/executor/op.rs:1181-1230 | monoruby/src/executor/op.rs:1249-1303 — 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) monoruby/src/value/rvalue/string/transcode.rs:5717— monoruby/src/value/rvalue/string/transcode.rs:5717-5838 | monoruby/src/value/rvalue/string/transcode.rs:5848-6009 | monoruby/src/value/rvalue/string/transcode.rs:6019-6082 | monoruby/src/value/rvalue/string/transcode.rs:6318-8063 — 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.
Codegen::compile_asmir (cyclomatic 209) monoruby/src/codegen/jitgen/asmir/compile_shared.rs:34— Codegen::compile_asmir has cyclomatic complexity 209 (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.
Codegen::encode_linst (cyclomatic 125) monoruby/src/codegen/arch/x86_64/compile/mod.rs:353— Codegen::encode_linst has cyclomatic complexity 125 (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.
Codegen::encode_linst (cyclomatic 113) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1575— Codegen::encode_linst has cyclomatic complexity 113 (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.
Codegen::gen_machine_code_inner (cyclomatic 32) monoruby/src/codegen/jitgen.rs:1087— Codegen::gen_machine_code_inner 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.
Codegen::gen_asm (cyclomatic 25) monoruby/src/codegen/jitgen/asmir.rs:4432— Codegen::gen_asm 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. This is NOT this file's highest cyclomatic complexity: AsmInst::dump (cyclomatic 37) 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.
Codegen::gen_asm (cyclomatic 22) monoruby/src/codegen/arch/aarch64/compile/mod.rs:278— Codegen::gen_asm 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.
Codegen::a64_gen_chain_replay_stub (cyclomatic 17) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1214— Codegen::a64_gen_chain_replay_stub 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.
Codegen::compile (cyclomatic 16) monoruby/src/codegen/compiler.rs:234— Codegen::compile 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.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×8
Edited copy of a member (23 corresponding lines) monoruby/src/value/rvalue/io/buf.rs:324— monoruby/src/value/rvalue/io/buf.rs:324-354 | monoruby/src/value/rvalue/io/buf.rs:401-423 — 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) monoruby/src/builtins/kernel.rs:5045— monoruby/src/builtins/kernel.rs:5045-5067 | monoruby/src/builtins/method.rs:199-223 — 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) monoruby/src/codegen/jitgen/state/read_slot.rs:432— monoruby/src/codegen/jitgen/state/read_slot.rs:432-457 | monoruby/src/codegen/jitgen/state/read_slot.rs:562-584 — 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:51— monoruby/src/codegen/arch/aarch64/compile/mod.rs:51-73 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:79-101 — 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) monoruby/src/builtins/method.rs:408— monoruby/src/builtins/method.rs:408-430 | monoruby/src/builtins/method.rs:452-474 — 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) REDACTED:823— REDACTED:823-847 | REDACTED:922-944 — 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) monoruby/src/codegen/jitgen/state/read_slot.rs:100— monoruby/src/codegen/jitgen/state/read_slot.rs:100-124 | monoruby/src/codegen/jitgen/state/read_slot.rs:239-261 — 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) monoruby/src/builtins/string.rs:5290— monoruby/src/builtins/string.rs:5290-5312 | monoruby/src/value/rvalue/regexp.rs:4138-4160 — 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.
Duplicated block (10 lines × 3) monoruby/src/builtins/io.rs:428— monoruby/src/builtins/io.rs:428-437 | monoruby/src/builtins/io.rs:443-452 | monoruby/src/builtins/io.rs:3168-3177 — 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 `monoruby/src/builtins/io.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 (10 lines × 3) monoruby/src/builtins/kernel.rs:1365— monoruby/src/builtins/kernel.rs:1365-1374 | monoruby/src/builtins/kernel.rs:1393-1402 | monoruby/src/builtins/kernel.rs:1681-1690 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) monoruby/src/builtins/string.rs:7304— monoruby/src/builtins/string.rs:7304-7313 | monoruby/src/builtins/string.rs:7332-7341 | monoruby/src/builtins/string.rs:7359-7368 — 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. 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) monoruby/src/builtins/symbol.rs:90— monoruby/src/builtins/symbol.rs:90-99 | monoruby/src/builtins/symbol.rs:124-133 | monoruby/src/value.rs:2285-2294 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting 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 × 3) monoruby/src/bytecodegen/encode.rs:349— monoruby/src/bytecodegen/encode.rs:349-358 | monoruby/src/bytecodegen/encode.rs:394-403 | monoruby/src/bytecodegen/encode.rs:606-615 — 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 `monoruby/src/bytecodegen/encode.rs:349` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 3) monoruby/src/codegen/arch/aarch64/compile/mod.rs:4317— monoruby/src/codegen/arch/aarch64/compile/mod.rs:4317-4326 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4345-4354 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4368-4377 — 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:4317` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) monoruby/src/codegen/jitgen/compile/method_call.rs:3601— monoruby/src/codegen/jitgen/compile/method_call.rs:3601-3610 | monoruby/src/codegen/jitgen/compile/method_call.rs:3659-3668 | monoruby/src/codegen/jitgen/compile/method_call.rs:3785-3794 — 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 `monoruby/src/codegen/jitgen/compile/method_call.rs:3601` 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 `self` to `super) fn generic_send(&mut` in one and `super) fn compile_yield(&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 (10 lines × 3) monoruby/src/codegen/jitgen/trace_ir.rs:644— monoruby/src/codegen/jitgen/trace_ir.rs:644-653 | monoruby/src/codegen/jitgen/trace_ir.rs:681-690 | monoruby/src/codegen/jitgen/trace_ir.rs:723-732 — 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 (6 lines × 3) monoruby/src/builtins/binding.rs:176— monoruby/src/builtins/binding.rs:176-181 | monoruby/src/builtins/binding.rs:205-210 | monoruby/src/builtins/binding.rs:251-256 — 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. 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, `monoruby/src/builtins/binding.rs:257` calls `arg` and `monoruby/src/builtins/binding.rs:182` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 3) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1676— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1676-1681 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1763-1768 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1794-1799 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1676` it does not close everything it opens, so those exact lines 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 × 3) monoruby/src/codegen/jitgen/compile/escape.rs:1242— monoruby/src/codegen/jitgen/compile/escape.rs:1242-1250 | monoruby/src/codegen/jitgen/compile/escape.rs:1477-1482 | monoruby/src/codegen/jitgen/compile/escape.rs:1782-1787 — 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 (6 lines × 3) monoruby/src/codegen/jitgen/context.rs:3606— monoruby/src/codegen/jitgen/context.rs:3606-3611 | monoruby/src/codegen/jitgen/context.rs:3642-3647 | monoruby/src/codegen/jitgen/context.rs:4276-4281 — 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 (6 lines × 3) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:220— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:220-225 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:548-553 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:604-609 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.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 (6 lines × 3) hashbrown/src/map.rs:2227— hashbrown/src/map.rs:2227-2232 | hashbrown/src/set.rs:1357-1362 | hashbrown/src/table.rs:1078-1083 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) monoruby/src/basic_block.rs:79— monoruby/src/basic_block.rs:79-84 | monoruby/src/bytecode.rs:78-83 | monoruby/src/executor.rs:6317-6322 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) hashbrown/src/map.rs:3226— hashbrown/src/map.rs:3226-3231 | hashbrown/src/map.rs:3812-3817 | rubymap/src/map/core/entry.rs:135-140 — before extracting anything, compare `hashbrown/src/map.rs` and `rubymap/src/map/core/entry.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Executor::format_by_args (cyclomatic 177) monoruby/src/executor/format.rs:825— Executor::format_by_args has cyclomatic complexity 177 (threshold 15). Of this number, 168 points are the body's own statements and 9 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.
Executor::take_ex_obj (cyclomatic 28) monoruby/src/executor.rs:2486— Executor::take_ex_obj 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.
Executor::require (cyclomatic 27) monoruby/src/executor.rs:1442— Executor::require 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.
Executor::eq_values_pure (cyclomatic 25) monoruby/src/executor/op.rs:883— Executor::eq_values_pure has cyclomatic complexity 25 (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.
Executor::probe_constant (cyclomatic 20) monoruby/src/executor/constants.rs:707— Executor::probe_constant 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.
Executor::get_constant (cyclomatic 16) monoruby/src/executor/constants.rs:60— Executor::get_constant has cyclomatic complexity 16 (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.
Executor::mark (cyclomatic 16) monoruby/src/executor.rs:597— Executor::mark 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.
Lowerer::lower_node (cognitive 83) monoruby/src/parser/prism_backend.rs:1105— Lowerer::lower_node has cognitive complexity 83 (threshold 15). Drivers by points: match/switch 18 (38 pts), if/else 13 (24 pts), loops 7 (20 pts), boolean chains 1 (nesting depth added 44). 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.
Lowerer::lower_parameters (cognitive 39) monoruby/src/parser/prism_backend.rs:5092— Lowerer::lower_parameters has cognitive complexity 39 (threshold 15). Drivers by points: match/switch 9 (18 pts), if/else 8 (17 pts), loops 4 (nesting depth added 18). 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.
Lowerer::collect_call_arg (cognitive 31) monoruby/src/parser/prism_backend.rs:3281— Lowerer::collect_call_arg has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 3 (9 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 19). 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.
Lowerer::lower_hash_pattern (cognitive 24) monoruby/src/parser/prism_backend.rs:4033— Lowerer::lower_hash_pattern has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 4 (8 pts), loops 3 (4 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.
Lowerer::lower_call (cognitive 24) monoruby/src/parser/prism_backend.rs:5317— Lowerer::lower_call has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, match/switch 3 (4 pts), loops 1 (2 pts) (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.
Lowerer::lower_integer (cognitive 18) monoruby/src/parser/prism_backend.rs:2287— Lowerer::lower_integer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 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.
Lowerer::lower_array (cognitive 18) monoruby/src/parser/prism_backend.rs:2555— Lowerer::lower_array has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 2 (9 pts), if/else 3 (5 pts), loops 2 (4 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.
ClassInfoTable::search_method_from (cognitive 40) monoruby/src/globals/store/class.rs:1540— ClassInfoTable::search_method_from has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (27 pts), match/switch 2 (6 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 22). 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.
ClassInfoTable::get_method_names_inherit (cognitive 23) monoruby/src/globals/store/class.rs:1997— ClassInfoTable::get_method_names_inherit has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 4, loops 2 (4 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.
ClassInfoTable::propagate_prepend_to_subclasses (cognitive 21) monoruby/src/globals/store/class.rs:1887— ClassInfoTable::propagate_prepend_to_subclasses has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 2 (5 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassInfoTable::propagate_permanent_name (cognitive 19) monoruby/src/globals/store/class/constants.rs:613— ClassInfoTable::propagate_permanent_name has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassInfoTable::get_parents (cognitive 18) monoruby/src/globals/store/class.rs:1192— ClassInfoTable::get_parents has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (2 pts), 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.
ClassInfoTable::walk_method_names (cognitive 17) monoruby/src/globals/store/class.rs:1682— ClassInfoTable::walk_method_names has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (3 pts), boolean chains 2, match/switch 1 (2 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.
ClassInfoTable::duplicate_module (cognitive 17) monoruby/src/globals/store/class.rs:2239— ClassInfoTable::duplicate_module has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 4 (5 pts), boolean chains 2 (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.
TooManyFunctions: monoruby::builtins::math monoruby/src/builtins/math.rs:34— TooManyFunctions — 40 free functions. The bar is 30 free functions; 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.
TooManyFunctions: monoruby::builtins::method monoruby/src/builtins/method.rs:9— TooManyFunctions — 37 free functions. The bar is 30 free functions; this is 7 over it, 1.23× 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.
TooManyFunctions: nokogiri_native::dtd ext/nokogiri/src/dtd.rs:17— TooManyFunctions — 36 free functions. The bar is 30 free functions; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFunctions: nokogiri_native::reader ext/nokogiri/src/reader.rs:37— TooManyFunctions — 36 free functions. The bar is 30 free functions; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFunctions: monoruby::builtins::fiber monoruby/src/builtins/fiber.rs:12— TooManyFunctions — 32 free functions. The bar is 30 free functions; 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.
TooManyFunctions: monoruby::builtins::random monoruby/src/builtins/random.rs:11— TooManyFunctions — 32 free functions. The bar is 30 free functions; 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.
TooManyFunctions: monoruby::builtins::numeric::rational monoruby/src/builtins/numeric/rational.rs:9— TooManyFunctions — 31 free functions. The bar is 30 free functions; 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.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×7
Edited copy of a member (21 corresponding lines) monoruby/src/value/rvalue/hash.rs:966— monoruby/src/value/rvalue/hash.rs:966-986 | monoruby/src/value/rvalue/hash.rs:993-1014 — 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) monoruby/src/builtins/dir.rs:1143— monoruby/src/builtins/dir.rs:1143-1163 | monoruby/src/builtins/dir.rs:1172-1198 — 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) monoruby/src/builtins/hash.rs:2167— monoruby/src/builtins/hash.rs:2167-2187 | monoruby/src/builtins/hash.rs:2347-2368 — 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) monoruby/src/codegen/compiler.rs:1192— monoruby/src/codegen/compiler.rs:1192-1221 | monoruby/src/codegen/compiler.rs:1243-1263 — 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) monoruby/src/builtins/numeric/complex.rs:334— monoruby/src/builtins/numeric/complex.rs:334-354 | monoruby/src/executor/op/binary_ops.rs:41-66 — 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) monoruby/src/value/rvalue/io.rs:314— monoruby/src/value/rvalue/io.rs:314-345 | monoruby/src/value/rvalue/io.rs:349-369 — 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) hashbrown/src/raw/mod.rs:1003— hashbrown/src/raw/mod.rs:1003-1026 | hashbrown/src/raw/mod.rs:1040-1060 — 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.
IoInner::getline (cognitive 62) monoruby/src/value/rvalue/io.rs:2218— IoInner::getline has cognitive complexity 62 (threshold 15). Drivers by points: if/else 14 (35 pts), match/switch 5 (14 pts), loops 4 (9 pts), boolean chains 4 (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.
IoInner::getline_universal (cognitive 44) monoruby/src/value/rvalue/io.rs:2371— IoInner::getline_universal has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (23 pts), match/switch 4 (11 pts), boolean chains 5, loops 3 (5 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.
IoInner::read_underlying (cognitive 33) monoruby/src/value/rvalue/io.rs:1700— IoInner::read_underlying has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (25 pts), match/switch 4 (7 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IoInner::getline_units (cognitive 23) monoruby/src/value/rvalue/io.rs:2461— IoInner::getline_units has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 3 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IoInner::sysread (cognitive 18) monoruby/src/value/rvalue/io.rs:1811— IoInner::sysread has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 4 (7 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.
IoInner::seek (cognitive 16) monoruby/src/value/rvalue/io.rs:2610— IoInner::seek has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (8 pts), if/else 4 (7 pts), boolean chains 1 (nesting depth added 6). 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.
nokogiri_native::node::relink_namespace (cognitive 49) ext/nokogiri/src/node.rs:1109— nokogiri_native::node::relink_namespace has cognitive complexity 49 (threshold 15). Drivers by points: if/else 20 (35 pts), boolean chains 9, loops 3 (5 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.
nokogiri_native::html5::fragment (cognitive 41) ext/nokogiri/src/html5.rs:331— nokogiri_native::html5::fragment has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (29 pts), match/switch 2 (6 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 19). 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.
nokogiri_native::html5::output_node (cognitive 26) ext/nokogiri/src/html5.rs:627— nokogiri_native::html5::output_node has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (7 pts), boolean chains 4, match/switch 1 (nesting depth added 11). 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.
nokogiri_native::node::reparent (cognitive 25) ext/nokogiri/src/node.rs:1207— nokogiri_native::node::reparent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 6, match/switch 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.
nokogiri_native::node_set::slice (cognitive 21) ext/nokogiri/src/node_set.rs:316— nokogiri_native::node_set::slice has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 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.
nokogiri_native::html5::options (cognitive 18) ext/nokogiri/src/html5.rs:53— nokogiri_native::html5::options has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), match/switch 3 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×6
Edited copy of a member (28 corresponding lines) monoruby/src/builtins/string.rs:10820— monoruby/src/builtins/string.rs:10820-10847 | monoruby/src/builtins/string.rs:10917-10944 — 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) monoruby/src/builtins/array.rs:2843— monoruby/src/builtins/array.rs:2843-2872 | monoruby/src/builtins/array.rs:2949-2976 — 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) ext/sqlite3/src/lib.rs:495— ext/sqlite3/src/lib.rs:495-528 | ext/sqlite3/src/lib.rs:1102-1129 — 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) monoruby/builtins/enumerable.rb:360— monoruby/builtins/enumerable.rb:360-387 | monoruby/builtins/enumerable.rb:579-606 — 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) monoruby/src/parser/prism_backend.rs:2491— monoruby/src/parser/prism_backend.rs:2491-2524 | monoruby/src/parser/prism_backend.rs:2526-2553 — 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) monoruby/src/codegen/arch/x86_64/invoker.rs:74— monoruby/src/codegen/arch/x86_64/invoker.rs:74-101 | monoruby/src/codegen/arch/x86_64/invoker.rs:103-130 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×6
Edited copy of a member (30 corresponding lines) monoruby/src/builtins/io.rs:1673— monoruby/src/builtins/io.rs:1673-1702 | monoruby/src/builtins/io.rs:2930-2967 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) monoruby/src/parser/prism_backend.rs:336— monoruby/src/parser/prism_backend.rs:336-365 | monoruby/src/parser/prism_backend.rs:421-451 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) monoruby/src/bytecodegen.rs:1143— monoruby/src/bytecodegen.rs:1143-1172 | monoruby/src/bytecodegen.rs:1538-1569 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) monoruby/src/globals/store/class.rs:633— monoruby/src/globals/store/class.rs:633-662 | monoruby/src/globals/store/class.rs:664-693 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) ext/zstd/src/lib.rs:199— ext/zstd/src/lib.rs:199-235 | ext/zstd/src/lib.rs:267-296 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) monoruby/src/codegen/jitgen/compile/frameless_call.rs:695— monoruby/src/codegen/jitgen/compile/frameless_call.rs:695-737 | monoruby/src/codegen/jitgen/compile/frameless_call.rs:882-911 — These two members are one piece of code written twice and then edited apart: 30 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) · ×6
Edited copy of a member (24 corresponding lines) ext/zstd/src/lib.rs:331— ext/zstd/src/lib.rs:331-362 | ext/zstd/src/lib.rs:368-391 — 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) monoruby/src/builtins/file.rs:1909— monoruby/src/builtins/file.rs:1909-1939 | monoruby/src/builtins/file.rs:2657-2680 — 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) monoruby/src/executor/op/sort.rs:194— monoruby/src/executor/op/sort.rs:194-217 | monoruby/src/executor/op/sort.rs:228-252 — 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) monoruby/gem/msgpack/msgpack.rb:253— monoruby/gem/msgpack/msgpack.rb:253-280 | monoruby/gem/msgpack/msgpack.rb:284-307 — 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) monoruby/src/value/rvalue/string.rs:5043— monoruby/src/value/rvalue/string.rs:5043-5082 | monoruby/src/value/rvalue/string.rs:5133-5156 — 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) rubymap/src/map.rs:591— rubymap/src/map.rs:591-616 | rubymap/src/map.rs:683-706 — 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 (19 corresponding lines) · ×6
Edited copy of a member (19 corresponding lines) monoruby/src/bytecodegen/expression.rs:2632— monoruby/src/bytecodegen/expression.rs:2632-2653 | monoruby/src/bytecodegen/expression.rs:2655-2673 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) monoruby/src/value/rvalue/string.rs:1248— monoruby/src/value/rvalue/string.rs:1248-1268 | monoruby/src/value/rvalue/string.rs:1277-1295 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) monoruby/src/builtins/binding.rs:468— monoruby/src/builtins/binding.rs:468-487 | monoruby/src/builtins/binding.rs:529-547 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) monoruby/src/value.rs:2197— monoruby/src/value.rs:2197-2215 | monoruby/src/value.rs:2228-2250 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) monoruby/src/executor/op.rs:1415— monoruby/src/executor/op.rs:1415-1434 | monoruby/src/globals/gvar.rs:529-547 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) monoruby/src/globals/method.rs:631— monoruby/src/globals/method.rs:631-650 | monoruby/src/globals/method.rs:725-743 — 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 (3 members, 10+ corresponding lines) · ×6
Edited copies of one member (3 members, 10+ corresponding lines) monoruby/src/builtins/time.rs:1094— monoruby/src/builtins/time.rs:1094-1103 | monoruby/src/builtins/time.rs:1114-1123 | monoruby/src/builtins/time.rs:1134-1143 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) ext/psych/src/lib.rs:395— ext/psych/src/lib.rs:395-404 | ext/zstd/src/lib.rs:504-515 | ext/zstd/src/lib.rs:606-617 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) monoruby/src/globals/store/class.rs:2716— monoruby/src/globals/store/class.rs:2716-2725 | monoruby/src/globals/store/class.rs:2747-2757 | monoruby/src/globals/store/class.rs:2769-2779 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) monoruby/src/bytecodegen.rs:1837— monoruby/src/bytecodegen.rs:1837-1850 | monoruby/src/bytecodegen.rs:1863-1877 | monoruby/src/bytecodegen.rs:1885-1894 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) monoruby/src/codegen/jitgen/context.rs:4198— monoruby/src/codegen/jitgen/context.rs:4198-4207 | monoruby/src/codegen/jitgen/context.rs:4217-4226 | monoruby/src/codegen/jitgen/context.rs:4236-4245 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) REDACTED:2298— REDACTED:2298-2307 | monoruby/src/codegen/runtime/args.rs:1671-1680 | monoruby/src/codegen/runtime/args.rs:1689-1698 — 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.
Duplicated block (9 lines × 3) monoruby/src/builtins/file.rs:491— monoruby/src/builtins/file.rs:491-499 | monoruby/src/builtins/file.rs:962-970 | monoruby/src/builtins/file.rs:3046-3054 — 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 × 3) monoruby/src/builtins/marshal.rs:2481— monoruby/src/builtins/marshal.rs:2481-2489 | monoruby/src/builtins/marshal.rs:2585-2593 | monoruby/src/builtins/marshal.rs:2924-2932 — 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 `monoruby/src/builtins/marshal.rs:2481` 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, `monoruby/src/builtins/marshal.rs:2922` calls `push` and `monoruby/src/builtins/marshal.rs:2583` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:707— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:707-715 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:833-841 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1972-1980 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:707` it does not close everything it opens, so those 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, `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1982` calls `get_current_address` and `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:716` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) monoruby/src/parser/prism_backend.rs:1547— monoruby/src/parser/prism_backend.rs:1547-1555 | monoruby/src/parser/prism_backend.rs:1560-1568 | monoruby/src/parser/prism_backend.rs:1574-1582 — 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 × 3) rubymap/src/map/core.rs:521— rubymap/src/map/core.rs:521-529 | rubymap/src/map/core.rs:566-574 | rubymap/src/map/core.rs:639-647 — 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 `rubymap/src/map/core.rs:521` it does not close everything it opens, so those exact lines 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) monoruby/gem/yajl/yajl.rb:637— monoruby/gem/yajl/yajl.rb:637-645 | monoruby/gem/yajl/yajl.rb:658-666 | monoruby/gem/yajl/yajl.rb:683-691 — 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 `monoruby/gem/yajl/yajl.rb:637` 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) monoruby/src/builtins/module.rs:627— monoruby/src/builtins/module.rs:627-635 | monoruby/src/builtins/module.rs:659-665 | monoruby/src/builtins/module.rs:687-693 — 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 `monoruby/src/builtins/module.rs:627` it does not close everything it opens, so those 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, `monoruby/src/builtins/module.rs:637` calls `define_attr_reader`, `temp_array_push`, `symbol` and `monoruby/src/builtins/module.rs:695` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) monoruby/src/builtins/time.rs:1097— monoruby/src/builtins/time.rs:1097-1103 | monoruby/src/builtins/time.rs:1117-1123 | monoruby/src/builtins/time.rs:1137-1143 — 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 `monoruby/src/builtins/time.rs:1097` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:733— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:733-739 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:915-921 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1055-1061 — 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 `monoruby/src/codegen/arch/x86_64/compile/method_call.rs:733` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/jitgen/compile/frameless_call.rs:780— monoruby/src/codegen/jitgen/compile/frameless_call.rs:780-786 | monoruby/src/codegen/jitgen/compile/frameless_call.rs:940-946 | monoruby/src/codegen/jitgen/compile/method_call.rs:4014-4020 — 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.
Duplicated block (7 lines × 3) hashbrown/src/map.rs:2800— hashbrown/src/map.rs:2800-2806 | hashbrown/src/set.rs:1192-1198 | hashbrown/src/set.rs:1231-1237 — 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.
Duplicated block (7 lines × 3) monoruby/src/parser/prism_backend.rs:1588— monoruby/src/parser/prism_backend.rs:1588-1594 | monoruby/src/parser/prism_backend.rs:1600-1606 | monoruby/src/parser/prism_backend.rs:1612-1618 — 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 `monoruby/src/parser/prism_backend.rs:1588` 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–7 lines × 2) monoruby/src/builtins/time.rs:2357— monoruby/src/builtins/time.rs:2357-2362 | monoruby/src/builtins/time.rs:2363-2369 — both copies are in the same file, so extract the 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–7 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:246— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:246-251 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1306-1312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:246` it does not close everything it opens, so those exact lines 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–7 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3681— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3681-3687 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2102-2107 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/arch/x86_64/compile/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6–7 lines × 2) monoruby/src/value/rvalue/string.rs:6530— monoruby/src/value/rvalue/string.rs:6530-6535 | monoruby/src/value/rvalue/string/transcode.rs:7268-7274 — before extracting anything, compare `monoruby/src/value/rvalue/string.rs` and `monoruby/src/value/rvalue/string/transcode.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 `monoruby/src/value/rvalue/string.rs:6530` it does not close everything it opens, so those exact lines 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–7 lines × 2) monoruby/src/value/rvalue/string/pack.rs:203— monoruby/src/value/rvalue/string/pack.rs:203-208 | monoruby/src/value/rvalue/string/pack.rs:215-221 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/pack.rs:215` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `monoruby/src/value/rvalue/string/pack.rs:208` calls `push`, `nil` and `monoruby/src/value/rvalue/string/pack.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–7 lines × 2) monoruby/src/value/rvalue/string/pack.rs:269— monoruby/src/value/rvalue/string/pack.rs:269-274 | monoruby/src/value/rvalue/string/pack.rs:281-287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/pack.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. 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, `monoruby/src/value/rvalue/string/pack.rs:274` calls `push`, `nil` and `monoruby/src/value/rvalue/string/pack.rs:287` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) monoruby/src/builtins/io_buffer.rs:775— monoruby/src/builtins/io_buffer.rs:775-779 | monoruby/src/builtins/io_buffer.rs:1138-1142 | monoruby/src/builtins/io_buffer.rs:1602-1606 — 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 `monoruby/src/builtins/io_buffer.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 (5 lines × 3) ext/nokogiri/src/node.rs:608— ext/nokogiri/src/node.rs:608-612 | ext/nokogiri/src/reader.rs:581-587 | ext/nokogiri/src/reader.rs:590-596 — 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.
Duplicated block (5 lines × 3) monoruby/src/globals/error.rs:1631— monoruby/src/globals/error.rs:1631-1635 | monoruby/src/globals/error.rs:1642-1646 | monoruby/src/globals/error.rs:1653-1657 — 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 `monoruby/src/globals/error.rs:1631` it does not close everything it opens, so those exact lines 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) monoruby/src/parser/prism_backend.rs:3879— monoruby/src/parser/prism_backend.rs:3879-3883 | monoruby/src/parser/prism_backend.rs:3945-3949 | monoruby/src/parser/prism_backend.rs:4084-4088 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) monoruby/src/builtins/io.rs:6732— monoruby/src/builtins/io.rs:6732-6736 | monoruby/src/builtins/io.rs:6756-6760 | monoruby/src/builtins/io.rs:6780-6784 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) monoruby/src/value/rvalue/string.rs:2504— monoruby/src/value/rvalue/string.rs:2504-2508 | monoruby/src/value/rvalue/string.rs:3762-3766 | monoruby/src/value/rvalue/string/transcode.rs:4148-4152 — before extracting anything, compare `monoruby/src/value/rvalue/string.rs` and `monoruby/src/value/rvalue/string/transcode.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.
Lowerer::lower_node (cyclomatic 142) monoruby/src/parser/prism_backend.rs:1105— Lowerer::lower_node has cyclomatic complexity 142 (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: monoruby::parser::prism_backend::node_kind_name (cyclomatic 145) 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.
Lowerer::lower_parameters (cyclomatic 28) monoruby/src/parser/prism_backend.rs:5092— Lowerer::lower_parameters 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: monoruby::parser::prism_backend::node_kind_name (cyclomatic 145) 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.
Lowerer::lower_call (cyclomatic 19) monoruby/src/parser/prism_backend.rs:5317— Lowerer::lower_call has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: monoruby::parser::prism_backend::node_kind_name (cyclomatic 145) 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.
Lowerer::lower_hash_pattern (cyclomatic 17) monoruby/src/parser/prism_backend.rs:4033— Lowerer::lower_hash_pattern 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: monoruby::parser::prism_backend::node_kind_name (cyclomatic 145) 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.
Lowerer::collect_call_arg (cyclomatic 16) monoruby/src/parser/prism_backend.rs:3281— Lowerer::collect_call_arg has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: monoruby::parser::prism_backend::node_kind_name (cyclomatic 145) 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.
nokogiri_native::node::relink_namespace (cyclomatic 31) ext/nokogiri/src/node.rs:1109— nokogiri_native::node::relink_namespace 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.
nokogiri_native::node::reparent (cyclomatic 24) ext/nokogiri/src/node.rs:1207— nokogiri_native::node::reparent 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.
nokogiri_native::html5::fragment (cyclomatic 22) ext/nokogiri/src/html5.rs:331— nokogiri_native::html5::fragment 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.
nokogiri_native::html5::output_node (cyclomatic 21) ext/nokogiri/src/html5.rs:627— nokogiri_native::html5::output_node has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
nokogiri_native::wrap_node_as (cyclomatic 20) ext/nokogiri/src/lib.rs:671— nokogiri_native::wrap_node_as 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.
RegexpInner::tos_bytes (cyclomatic 25) monoruby/src/value/rvalue/regexp.rs:2393— RegexpInner::tos_bytes has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: RegexpInner::onigmo_encoding_for (cyclomatic 47) 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.
RegexpInner::replace_all_hash_plain (cyclomatic 24) monoruby/src/value/rvalue/regexp.rs:3398— RegexpInner::replace_all_hash_plain 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. This is NOT this file's highest cyclomatic complexity: RegexpInner::onigmo_encoding_for (cyclomatic 47) 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.
RegexpInner::expand_backref (cyclomatic 24) monoruby/src/value/rvalue/regexp.rs:3867— RegexpInner::expand_backref 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. This is NOT this file's highest cyclomatic complexity: RegexpInner::onigmo_encoding_for (cyclomatic 47) 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.
RegexpInner::expand_backref_wide (cyclomatic 22) monoruby/src/value/rvalue/regexp.rs:3995— RegexpInner::expand_backref_wide 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. This is NOT this file's highest cyclomatic complexity: RegexpInner::onigmo_encoding_for (cyclomatic 47) 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.
RegexpInner::escape_in (cyclomatic 16) monoruby/src/value/rvalue/regexp.rs:525— RegexpInner::escape_in has cyclomatic complexity 16 (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: RegexpInner::onigmo_encoding_for (cyclomatic 47) 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×5
Change coupling: method.rs ↔ method.rs monoruby/src/builtins/method.rs:1— `monoruby/src/builtins/method.rs` and `monoruby/src/value/rvalue/method.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 `0cf74987` Call a Method object's target directly from JIT code (#1335); `064d9f04` Make core/method and core/unboundmethod ruby/spec fully green (#521); `efb8c79c` method: support Method/UnboundMethod objects from respond_to_missing?… — run `git show` on any of them.
Change coupling: tests.rs ↔ complex.rs monoruby/src/tests.rs:1— `monoruby/src/tests.rs` and `monoruby/src/value/rvalue/complex.rs` change together 60% of the time (6 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 6 shared commits counted here, the most recent 3 are `082afc31` Improve Errno handling, implement new methods, fix coerce protocol (#…; `9296fce1` Refactor.; `eabbd4ed` Refactor. (#57) — run `git show` on any of them.
Change coupling: inline.rs ↔ globals.rs monoruby/src/executor/inline.rs:1— `monoruby/src/executor/inline.rs` and `monoruby/src/globals.rs` change together 50% of the time (9 of the 18 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 9 shared commits counted here, the most recent 3 are `4a974f77` JIT: keep branch conditions in the CPU flags via the compile context …; `f7bfc00b` JIT: key the PIC's arms by target, and fold away the class-independen…; `cd4f0330` JIT: route the numeric unary operators through inline generators (#1117) — run `git show` on any of them.
Change coupling: io.rs ↔ thread.rs monoruby/src/builtins/io.rs:1— `monoruby/src/builtins/io.rs` and `monoruby/src/value/rvalue/thread.rs` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 8 shared commits counted here, the most recent 3 are `29aeddb7` 1:1 threads: a kernel wait reads as "sleep", a thread's child starts …; `994cba8c` Kernel: easy/medium spec gaps — ===, extend, lambda, srand, Integer/S…; `dabb0471` IO.popen extensions, Thread construction protocol, real IO#dup, exact… — run `git show` on any of them.
Change coupling: executor.rs ↔ basic_op.rs monoruby/src/executor.rs:1— `monoruby/src/executor.rs` and `monoruby/src/globals/store/basic_op.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 `eb093795` `!=` is BasicObject's alone and calls `==` the way rb_funcall does (#…; `16009edb` JIT: re-warm BOP-evicted methods, budget loop/specialized recompiles,…; `21ed6aa5` Fix the cheapest ruby/spec core failures (and three bugs they uncover… — run `git show` on any of them.
Duplicated block (22 lines × 2) monoruby/src/builtins/array.rs:897— monoruby/src/builtins/array.rs:897-918 | monoruby/src/builtins/array.rs:922-943 — both copies are in the same file, so extract the 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) monoruby/src/codegen/arch/aarch64/codegen.rs:108— monoruby/src/codegen/arch/aarch64/codegen.rs:108-129 | monoruby/src/codegen/arch/aarch64/codegen.rs:161-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/codegen.rs:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) monoruby/src/codegen/jitgen/compile/escape.rs:1469— monoruby/src/codegen/jitgen/compile/escape.rs:1469-1490 | monoruby/src/codegen/jitgen/compile/escape.rs:1774-1795 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/compile/escape.rs:1469` 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 (22 lines × 2) monoruby/src/parser/prism_backend.rs:4876— monoruby/src/parser/prism_backend.rs:4876-4897 | monoruby/src/parser/prism_backend.rs:4980-5001 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/parser/prism_backend.rs:4876` 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 `node` to `&LambdaNode<'pr>` in one and `&BlockNode<'pr>` 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) monoruby/gem/json/common.rb:693— monoruby/gem/json/common.rb:693-714 | monoruby/gem/json/common.rb:869-890 — both copies are in the same file, so extract the 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) ext/nokogiri/src/document.rs:137— ext/nokogiri/src/document.rs:137-155 | ext/nokogiri/src/document.rs:253-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/document.rs:137` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:919— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:919-937 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1255-1273 — both copies are in the same file, so extract the 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) monoruby/src/codegen/jitgen/trace_ir.rs:642— monoruby/src/codegen/jitgen/trace_ir.rs:642-660 | monoruby/src/codegen/jitgen/trace_ir.rs:679-697 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/trace_ir.rs:642` it does not close everything it opens, so those exact lines 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) monoruby/src/executor/format.rs:1050— monoruby/src/executor/format.rs:1050-1068 | monoruby/src/executor/format.rs:1137-1155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/executor/format.rs:1050` it does not close everything it opens, so those exact lines 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) monoruby/src/scheduler.rs:996— monoruby/src/scheduler.rs:996-1014 | monoruby/src/scheduler/native.rs:755-773 — before extracting anything, compare `monoruby/src/scheduler.rs` and `monoruby/src/scheduler/native.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/scheduler.rs:996` it does not close everything it opens, so those 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) monoruby/src/builtins/hash.rs:2216— monoruby/src/builtins/hash.rs:2216-2230 | monoruby/src/builtins/hash.rs:2431-2445 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/hash.rs:2216` 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) monoruby/src/builtins/io.rs:5217— monoruby/src/builtins/io.rs:5217-5231 | monoruby/src/builtins/io.rs:5316-5330 — both copies are in the same file, so extract the 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, `monoruby/src/builtins/io.rs:5315` calls `nonblock_exception_kw`, `try_arg` and `monoruby/src/builtins/io.rs:5216` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) monoruby/src/builtins/string.rs:2048— monoruby/src/builtins/string.rs:2048-2062 | monoruby/src/builtins/string.rs:6389-6403 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:2048` 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) monoruby/src/builtins/string.rs:7906— monoruby/src/builtins/string.rs:7906-7920 | monoruby/src/builtins/string.rs:7958-7972 — both copies are in the same file, so extract the 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) monoruby/src/executor/format.rs:1024— monoruby/src/executor/format.rs:1024-1038 | monoruby/src/executor/format.rs:1193-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `monoruby/src/executor/format.rs:1188` calls `Some` and `monoruby/src/executor/format.rs:1018` 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–12 lines × 2) monoruby/src/builtins/marshal.rs:906— monoruby/src/builtins/marshal.rs:906-917 | monoruby/src/builtins/marshal.rs:1454-1464 — both copies are in the same file, so extract the 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–12 lines × 2) monoruby/src/builtins/range.rs:865— monoruby/src/builtins/range.rs:865-875 | monoruby/src/builtins/range.rs:901-912 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/range.rs:865` 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, `monoruby/src/builtins/range.rs:913` calls `Ok` and `monoruby/src/builtins/range.rs:876` 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–12 lines × 2) monoruby/src/value/rvalue/fiber.rs:293— monoruby/src/value/rvalue/fiber.rs:293-304 | monoruby/src/value/rvalue/fiber.rs:379-389 — both copies are in the same file, so extract the 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–12 lines × 2) monoruby/src/value/rvalue/string/pack.rs:973— monoruby/src/value/rvalue/string/pack.rs:973-984 | monoruby/src/value/rvalue/string/pack.rs:1153-1163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/pack.rs:973` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–12 lines × 2) monoruby/gem/ffi_c.rb:1040— monoruby/gem/ffi_c.rb:1040-1051 | monoruby/gem/ffi_c.rb:1247-1257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–11 lines × 2) monoruby/src/builtins/hash.rs:1827— monoruby/src/builtins/hash.rs:1827-1835 | monoruby/src/builtins/hash.rs:1856-1866 — both copies are in the same file, so extract the 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–11 lines × 2) monoruby/src/builtins/string.rs:8718— monoruby/src/builtins/string.rs:8718-8726 | monoruby/src/builtins/string.rs:8752-8762 — both copies are in the same file, so extract the 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 (9–11 lines × 2) monoruby/src/bytecodegen/expression.rs:1558— monoruby/src/bytecodegen/expression.rs:1558-1568 | monoruby/src/bytecodegen/expression.rs:1604-1612 — both copies are in the same file, so extract the 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–11 lines × 2) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1023— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1023-1031 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1261-1271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1023` it does not close everything it opens, so those exact lines 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–11 lines × 2) monoruby/src/codegen/jitgen/compile/frameless_call.rs:846— monoruby/src/codegen/jitgen/compile/frameless_call.rs:846-854 | monoruby/src/codegen/jitgen/compile/method_call.rs:4122-4132 — 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 (8 lines × 3) monoruby/src/builtins/hash.rs:3013— monoruby/src/builtins/hash.rs:3013-3020 | monoruby/src/builtins/hash.rs:3104-3111 | monoruby/src/builtins/hash.rs:3325-3332 — 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 (8 lines × 3) monoruby/src/builtins/string.rs:12284— monoruby/src/builtins/string.rs:12284-12291 | monoruby/src/value/rvalue/string.rs:2472-2479 | monoruby/src/value/rvalue/string.rs:4512-4519 — 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.
Duplicated block (8 lines × 3) monoruby/src/codegen/jitgen/compile/binary_op.rs:1270— monoruby/src/codegen/jitgen/compile/binary_op.rs:1270-1277 | monoruby/src/codegen/jitgen/compile/binary_op.rs:1293-1300 | monoruby/src/codegen/jitgen/compile/binary_op.rs:1309-1316 — 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 `monoruby/src/codegen/jitgen/compile/binary_op.rs:1270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 3) monoruby/src/parser/prism_backend.rs:1423— monoruby/src/parser/prism_backend.rs:1423-1430 | monoruby/src/parser/prism_backend.rs:1435-1442 | monoruby/src/parser/prism_backend.rs:1447-1454 — 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 (8 lines × 3) monoruby/builtins/array.rb:213— monoruby/builtins/array.rb:213-220 | monoruby/builtins/hash.rb:299-306 | monoruby/builtins/struct.rb:158-165 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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.
Unfinished branch — a todo!() / unimplemented!() arm in a real function monoruby/src/ast/node.rs:447— `from` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
Unfinished branch — a todo!() / unimplemented!() arm in a real function REDACTED:301— `to_f` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
Unfinished branch — a todo!() / unimplemented!() arm in a real function monoruby/src/codegen/arch/aarch64/compile/mod.rs:1821— `encode_linst` does real work, but one of its branches is `todo!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
Unfinished branch — a todo!() / unimplemented!() arm in a real function monoruby/src/codegen/arch/x86_64/compile/mod.rs:623— `encode_linst` does real work, but one of its branches is `todo!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
Unfinished branch — a todo!() / unimplemented!() arm in a real function monoruby/src/executor.rs:6132— `func_id` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
IoInner::getline (cyclomatic 30) monoruby/src/value/rvalue/io.rs:2218— IoInner::getline 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.
IoInner::getline_universal (cyclomatic 27) monoruby/src/value/rvalue/io.rs:2371— IoInner::getline_universal 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.
IoInner::read_underlying (cyclomatic 20) monoruby/src/value/rvalue/io.rs:1700— IoInner::read_underlying 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.
IoInner::seek (cyclomatic 16) monoruby/src/value/rvalue/io.rs:2610— IoInner::seek has cyclomatic complexity 16 (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.
AbstractState::set_arguments (cognitive 131) monoruby/src/codegen/jitgen/compile/method_call.rs:3966— AbstractState::set_arguments has cognitive complexity 131 (threshold 15). Drivers by points: if/else 36 (69 pts), loops 13 (31 pts), boolean chains 21, match/switch 4 (10 pts) (nesting depth added 57). 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.
AbstractState::binop_integer_gp (cognitive 22) monoruby/src/codegen/jitgen/state/binop.rs:154— AbstractState::binop_integer_gp has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AbstractState::fill_window (cognitive 21) monoruby/src/codegen/jitgen/compile/frameless_call.rs:749— AbstractState::fill_window has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 5, match/switch 2 (4 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractState::unbox_to_S_for_outgoing_block (cognitive 16) monoruby/src/codegen/jitgen/state.rs:420— AbstractState::unbox_to_S_for_outgoing_block has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (5 pts), loops 4 (5 pts), match/switch 2 (5 pts), boolean chains 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.
Globals::require_lib (cognitive 53) monoruby/src/globals/require.rs:190— Globals::require_lib has cognitive complexity 53 (threshold 15). Drivers by points: if/else 16 (36 pts), loops 5 (11 pts), boolean chains 6 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Globals::search_candidate (cognitive 35) monoruby/src/globals/require.rs:456— Globals::search_candidate has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (28 pts), loops 3 (4 pts), boolean chains 3 (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.
Globals::new (cognitive 32) monoruby/src/globals.rs:792— Globals::new has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 6, match/switch 3 (5 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.
Globals::compile_script_eval (cognitive 16) monoruby/src/globals.rs:1596— Globals::compile_script_eval has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), match/switch 4 (7 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.
RegexpInner::expand_backref (cognitive 51) monoruby/src/value/rvalue/regexp.rs:3867— RegexpInner::expand_backref has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (39 pts), loops 3 (9 pts), match/switch 1 (2 pts), boolean chains 1 (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.
RegexpInner::expand_backref_wide (cognitive 45) monoruby/src/value/rvalue/regexp.rs:3995— RegexpInner::expand_backref_wide has cognitive complexity 45 (threshold 15). Drivers by points: if/else 10 (31 pts), loops 4 (11 pts), match/switch 1 (2 pts), boolean chains 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.
RegexpInner::replace_all_hash_plain (cognitive 40) monoruby/src/value/rvalue/regexp.rs:3398— RegexpInner::replace_all_hash_plain has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (26 pts), loops 3 (6 pts), boolean chains 5, match/switch 1 (3 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.
RegexpInner::tos_bytes (cognitive 29) monoruby/src/value/rvalue/regexp.rs:2393— RegexpInner::tos_bytes has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 3 (6 pts), match/switch 3 (6 pts), boolean chains 3 (nesting depth added 9). 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.
RStringInner::scrub (cognitive 42) monoruby/src/value/rvalue/string.rs:4474— RStringInner::scrub has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (34 pts), loops 3 (6 pts), boolean chains 1, match/switch 1 (nesting depth added 19). 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.
RStringInner::inspect (cognitive 39) monoruby/src/value/rvalue/string.rs:3391— RStringInner::inspect has cognitive complexity 39 (threshold 15). Drivers by points: match/switch 8 (20 pts), loops 7 (19 pts) (nesting depth added 24). 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.
RStringInner::propagated_cr (cognitive 19) monoruby/src/value/rvalue/string.rs:4740— RStringInner::propagated_cr has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, match/switch 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.
RStringInner::sub_splice (cognitive 16) monoruby/src/value/rvalue/string.rs:5237— RStringInner::sub_splice has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7 (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.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×4
Edited copies of one member (3 members, 13+ corresponding lines) monoruby/src/value/numeric.rs:247— monoruby/src/value/numeric.rs:247-259 | monoruby/src/value/numeric.rs:427-447 | monoruby/src/value/numeric.rs:452-472 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) monoruby/src/ext.rs:2611— monoruby/src/ext.rs:2611-2626 | monoruby/src/ext.rs:2807-2819 | monoruby/src/ext.rs:2826-2840 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:799— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:799-817 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:1818-1830 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2935-2947 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) monoruby/builtins/enumerable.rb:282— monoruby/builtins/enumerable.rb:282-300 | monoruby/builtins/enumerable.rb:304-322 | monoruby/builtins/enumerable.rb:732-744 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×4
Edited copy of a member (27 corresponding lines) monoruby/src/builtins/hash.rs:2554— monoruby/src/builtins/hash.rs:2554-2586 | monoruby/src/builtins/hash.rs:2598-2624 — 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) monoruby/src/builtins/hash.rs:2674— monoruby/src/builtins/hash.rs:2674-2700 | monoruby/src/builtins/hash.rs:2916-2953 — 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) monoruby/src/builtins/data_class.rs:241— monoruby/src/builtins/data_class.rs:241-267 | monoruby/src/builtins/struct_class.rs:552-584 — 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) ext/sqlite3/src/lib.rs:1184— ext/sqlite3/src/lib.rs:1184-1210 | ext/sqlite3/src/lib.rs:1808-1835 — 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 (31 corresponding lines) · ×4
Edited copy of a member (31 corresponding lines) monoruby/src/codegen/jitgen/compile/frameless_call.rs:502— monoruby/src/codegen/jitgen/compile/frameless_call.rs:502-535 | monoruby/src/codegen/jitgen/compile/frameless_call.rs:550-580 — 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) monoruby/src/builtins/kernel.rs:5126— monoruby/src/builtins/kernel.rs:5126-5168 | monoruby/src/builtins/kernel.rs:6457-6487 — 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) REDACTED:2196— REDACTED:2196-2226 | REDACTED:2239-2270 — 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) monoruby/gem/json/common.rb:684— monoruby/gem/json/common.rb:684-714 | monoruby/gem/json/common.rb:855-890 — 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 (25 corresponding lines) · ×4
Edited copy of a member (25 corresponding lines) monoruby/src/value/rvalue/rational.rs:443— monoruby/src/value/rvalue/rational.rs:443-467 | monoruby/src/value/rvalue/rational.rs:470-495 — 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) monoruby/src/bytecodegen/expression.rs:1557— monoruby/src/bytecodegen/expression.rs:1557-1586 | monoruby/src/bytecodegen/expression.rs:1603-1627 — 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) monoruby/src/value/rvalue/string/pack.rs:2083— monoruby/src/value/rvalue/string/pack.rs:2083-2107 | monoruby/src/value/rvalue/string/pack.rs:2115-2139 — 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) monoruby/builtins/enumerator.rb:193— monoruby/builtins/enumerator.rb:193-224 | monoruby/builtins/enumerator.rb:235-259 — 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 copies of one member (3 members, 14+ corresponding lines) · ×4
Edited copies of one member (3 members, 14+ corresponding lines) monoruby/src/builtins/array.rs:442— monoruby/src/builtins/array.rs:442-462 | monoruby/src/builtins/array.rs:490-510 | monoruby/src/builtins/object.rs:554-567 — 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) monoruby/src/builtins/process.rs:568— monoruby/src/builtins/process.rs:568-581 | monoruby/src/builtins/process.rs:609-622 | monoruby/src/builtins/process.rs:630-646 — 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) monoruby/src/builtins/string.rs:7303— monoruby/src/builtins/string.rs:7303-7320 | monoruby/src/builtins/string.rs:7331-7344 | monoruby/src/builtins/string.rs:7358-7374 — 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) monoruby/src/value/rvalue/regexp.rs:2113— monoruby/src/value/rvalue/regexp.rs:2113-2129 | monoruby/src/value/rvalue/regexp.rs:2140-2153 | monoruby/src/value/rvalue/regexp.rs:2356-2369 — 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 copies of one member (3 members, 8+ corresponding lines) · ×4
Edited copies of one member (3 members, 8+ corresponding lines) monoruby/src/builtins/file.rs:1955— monoruby/src/builtins/file.rs:1955-1962 | monoruby/src/builtins/file.rs:2333-2340 | monoruby/src/builtins/file.rs:2355-2362 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) ext/nokogiri/src/node.rs:705— ext/nokogiri/src/node.rs:705-712 | ext/nokogiri/src/node.rs:739-746 | ext/nokogiri/src/xpath.rs:199-206 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) monoruby/src/builtins/module.rs:353— monoruby/src/builtins/module.rs:353-360 | monoruby/src/builtins/module.rs:3685-3694 | monoruby/src/builtins/module.rs:3709-3720 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) REDACTED:297— REDACTED:297-304 | REDACTED:1377-1384 | REDACTED:1393-1400 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (14–15 lines × 2) monoruby/src/builtins/io.rs:2853— monoruby/src/builtins/io.rs:2853-2867 | monoruby/src/builtins/io.rs:3041-3054 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/io.rs:2853` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) monoruby/src/builtins/string.rs:9122— monoruby/src/builtins/string.rs:9122-9136 | monoruby/src/builtins/string.rs:9157-9170 — both copies are in the same file, so extract the 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–15 lines × 2) monoruby/src/bytecodegen/defined.rs:108— monoruby/src/bytecodegen/defined.rs:108-122 | monoruby/src/bytecodegen/defined.rs:339-352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/bytecodegen/defined.rs:108` 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 (14–15 lines × 2) monoruby/src/value/rvalue/string.rs:6590— monoruby/src/value/rvalue/string.rs:6590-6603 | monoruby/src/value/rvalue/string.rs:6620-6634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string.rs:6590` 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 (11 lines × 3) REDACTED:1538— REDACTED:1538-1548 | REDACTED:1562-1572 | REDACTED:1590-1600 — 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 (11 lines × 3) monoruby/src/builtins/string.rs:3383— monoruby/src/builtins/string.rs:3383-3393 | monoruby/src/builtins/string.rs:3535-3545 | monoruby/src/builtins/string.rs:3561-3571 — 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 `monoruby/src/builtins/string.rs:3383` 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 × 3) monoruby/src/value/rvalue/string.rs:215— monoruby/src/value/rvalue/string.rs:215-225 | monoruby/src/value/rvalue/string.rs:239-249 | monoruby/src/value/rvalue/string.rs:259-269 — 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 `monoruby/src/value/rvalue/string.rs:215` 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 × 3) monoruby/src/codegen/arch/x86_64/invoker.rs:335— monoruby/src/codegen/arch/x86_64/invoker.rs:335-345 | monoruby/src/codegen/arch/x86_64/invoker.rs:367-377 | monoruby/src/codegen/arch/x86_64/invoker.rs:447-457 — 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 `monoruby/src/codegen/arch/x86_64/invoker.rs:335` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) monoruby/src/builtins/kernel.rs:4768— monoruby/src/builtins/kernel.rs:4768-4777 | monoruby/src/builtins/kernel.rs:4787-4796 | monoruby/src/builtins/kernel.rs:4811-4820 | monoruby/src/builtins/kernel.rs:4840-4849 — 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 (10 lines × 4) monoruby/src/builtins/kernel.rs:4768— monoruby/src/builtins/kernel.rs:4768-4777 | monoruby/src/builtins/kernel.rs:4782-4791 | monoruby/src/builtins/kernel.rs:4801-4810 | monoruby/src/builtins/kernel.rs:4825-4834 — 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 (10 lines × 4) monoruby/src/builtins/marshal.rs:2156— monoruby/src/builtins/marshal.rs:2156-2165 | monoruby/src/builtins/marshal.rs:2168-2177 | monoruby/src/builtins/marshal.rs:2816-2825 | monoruby/src/builtins/marshal.rs:2866-2875 — 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 `monoruby/src/builtins/marshal.rs:2156` 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, `monoruby/src/builtins/marshal.rs:2876` calls `as_struct` and `monoruby/src/builtins/marshal.rs:2826` 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 × 4) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3142— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3142-3151 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3342-3351 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3583-3592 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4166-4175 — 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 before the matched lines, `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3341` calls `a64_frame_load` and `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3582` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–10 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:573— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:573-582 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:625-633 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:573` it does not close everything it opens, so those exact lines 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–10 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3648— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3648-3656 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3718-3727 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3648` it does not close everything it opens, so those exact lines 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–10 lines × 2) monoruby/src/codegen/jitgen/context.rs:350— monoruby/src/codegen/jitgen/context.rs:350-359 | monoruby/src/codegen/jitgen/context.rs:960-968 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/context.rs:350` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 2) monoruby/src/parser/prism_backend.rs:343— monoruby/src/parser/prism_backend.rs:343-352 | monoruby/src/parser/prism_backend.rs:430-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/parser/prism_backend.rs:343` it does not close everything it opens, so those 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) monoruby/src/builtins/set.rs:760— monoruby/src/builtins/set.rs:760-766 | monoruby/src/builtins/set.rs:787-793 | monoruby/src/builtins/set.rs:819-825 | monoruby/src/builtins/set.rs:851-857 — 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 (7 lines × 4) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:248— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:248-254 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:705-711 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:831-837 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1970-1976 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:248` it does not close everything it opens, so those 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, `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:246` calls `as_ptr` and `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:827` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 4) monoruby/src/parser/prism_backend.rs:2574— monoruby/src/parser/prism_backend.rs:2574-2580 | monoruby/src/parser/prism_backend.rs:2621-2627 | monoruby/src/parser/prism_backend.rs:3352-3358 | monoruby/src/parser/prism_backend.rs:3384-3390 — 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 `monoruby/src/parser/prism_backend.rs:2574` 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 × 4) monoruby/src/executor/op.rs:403— monoruby/src/executor/op.rs:403-409 | monoruby/src/executor/op.rs:926-932 | monoruby/src/executor/op.rs:1214-1220 | monoruby/src/executor/op.rs:1283-1289 — 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.
Off the main sequence: host_ruby — host_ruby: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: libxml2-src — libxml2-src: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: monoruby-ext-sys — monoruby-ext-sys: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: monoruby-ext — monoruby-ext: abstractness 0.14, instability 0.13, distance 0.73 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
AbstractFrame::bridge (cyclomatic 44) monoruby/src/codegen/jitgen/state/slot.rs:3428— AbstractFrame::bridge has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AbstractFrame::decide_join (cyclomatic 25) monoruby/src/codegen/jitgen/state/join.rs:295— AbstractFrame::decide_join has cyclomatic complexity 25 (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.
AbstractFrame::apply_join (cyclomatic 16) monoruby/src/codegen/jitgen/state/join.rs:383— AbstractFrame::apply_join 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.
Value::from_ast_inner (cyclomatic 41) monoruby/src/value.rs:3729— Value::from_ast_inner has cyclomatic complexity 41 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Value::from_const_ast (cyclomatic 19) monoruby/src/value.rs:3906— Value::from_const_ast has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Value::coerce_to_char (cyclomatic 16) monoruby/src/value/coerce.rs:706— Value::coerce_to_char 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.
Globals::require_lib (cyclomatic 27) monoruby/src/globals/require.rs:190— Globals::require_lib 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.
Globals::new (cyclomatic 22) monoruby/src/globals.rs:792— Globals::new 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.
Globals::search_candidate (cyclomatic 19) monoruby/src/globals/require.rs:456— Globals::search_candidate 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.
Store::describe_func (cognitive 64) monoruby/src/globals/store.rs:1561— Store::describe_func has cognitive complexity 64 (threshold 15). Drivers by points: if/else 25 (49 pts), match/switch 5 (9 pts), boolean chains 3, loops 1 (3 pts) (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.
Store::check_super_at (cognitive 24) monoruby/src/globals/store/class.rs:3523— Store::check_super_at has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 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.
Store::jit_forget_unit (cognitive 20) monoruby/src/globals/store.rs:698— Store::jit_forget_unit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (4 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.
Generator::object (cognitive 45) monoruby/src/builtins/json.rs:2235— Generator::object has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (34 pts), match/switch 2 (5 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator::generate (cognitive 29) monoruby/src/builtins/json.rs:1876— Generator::generate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (24 pts), match/switch 1 (3 pts), boolean chains 1, 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.
Generator::ensure_valid_encoding (cognitive 20) monoruby/src/builtins/json.rs:2048— Generator::ensure_valid_encoding has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 2 (3 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.
Parser::unescape (cognitive 37) monoruby/src/builtins/json.rs:1131— Parser::unescape has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (30 pts), match/switch 2 (5 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.
Parser::parse_object (cognitive 16) monoruby/src/builtins/json.rs:875— Parser::parse_object has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 1 (2 pts), boolean chains 1, 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.
Parser::parse_number (cognitive 16) monoruby/src/builtins/json.rs:1258— Parser::parse_number has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) monoruby/src/builtins/encoding.rs:1189— monoruby/src/builtins/encoding.rs:1189-1217 | monoruby/src/builtins/encoding.rs:1233-1258 — 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) monoruby/src/value/coerce.rs:434— monoruby/src/value/coerce.rs:434-463 | monoruby/src/value/rvalue/string/pack.rs:1550-1575 — 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) ext/sqlite3/src/lib.rs:1269— ext/sqlite3/src/lib.rs:1269-1294 | ext/sqlite3/src/lib.rs:1395-1423 — 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 copies of one member (3 members, 19+ corresponding lines) · ×3
Edited copies of one member (3 members, 19+ corresponding lines) monoruby/src/builtins/string.rs:4742— monoruby/src/builtins/string.rs:4742-4764 | monoruby/src/builtins/string.rs:4795-4813 | monoruby/src/builtins/string.rs:4845-4863 — 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.
Edited copies of one member (3 members, 19+ corresponding lines) monoruby/src/builtins/string.rs:12349— monoruby/src/builtins/string.rs:12349-12367 | monoruby/src/builtins/string.rs:12377-12399 | monoruby/src/builtins/string.rs:12470-12488 — 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.
Edited copies of one member (3 members, 19+ corresponding lines) monoruby/src/value/rvalue/string.rs:50— monoruby/src/value/rvalue/string.rs:50-68 | monoruby/src/value/rvalue/string.rs:116-147 | monoruby/src/value/rvalue/string.rs:829-847 — 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, 15+ corresponding lines) · ×3
Edited copies of one member (3 members, 15+ corresponding lines) monoruby/src/builtins/module.rs:626— monoruby/src/builtins/module.rs:626-644 | monoruby/src/builtins/module.rs:658-672 | monoruby/src/builtins/module.rs:686-700 — 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.
Edited copies of one member (3 members, 15+ corresponding lines) REDACTED:1537— REDACTED:1537-1552 | REDACTED:1561-1575 | REDACTED:1589-1604 — 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.
Edited copies of one member (3 members, 15+ corresponding lines) monoruby/src/codegen/jitgen.rs:1692— monoruby/src/codegen/jitgen.rs:1692-1706 | monoruby/src/codegen/jitgen.rs:1713-1727 | monoruby/src/codegen/jitgen.rs:1733-1747 — 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 (3 members, 9+ corresponding lines) · ×3
Edited copies of one member (3 members, 9+ corresponding lines) monoruby/src/ext.rs:1622— monoruby/src/ext.rs:1622-1637 | monoruby/src/ext.rs:1647-1662 | monoruby/src/ext.rs:2029-2037 — 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.
Edited copies of one member (3 members, 9+ corresponding lines) monoruby/src/builtins/kernel.rs:6756— monoruby/src/builtins/kernel.rs:6756-6764 | monoruby/src/builtins/kernel.rs:6778-6786 | monoruby/src/builtins/kernel.rs:6804-6812 — 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.
Edited copies of one member (3 members, 9+ corresponding lines) monoruby/src/builtins/module.rs:2270— monoruby/src/builtins/module.rs:2270-2278 | monoruby/src/builtins/module.rs:2292-2300 | monoruby/src/builtins/module.rs:2314-2327 — 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, 7+ corresponding lines) · ×3
Edited copies of one member (4 members, 7+ corresponding lines) monoruby/src/builtins/hash.rs:939— monoruby/src/builtins/hash.rs:939-945 | monoruby/src/builtins/hash.rs:955-961 | monoruby/src/builtins/hash.rs:971-977 | monoruby/src/builtins/hash.rs:987-993 — 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.
Edited copies of one member (4 members, 7+ corresponding lines) monoruby/src/value/rvalue/rational.rs:331— monoruby/src/value/rvalue/rational.rs:331-337 | monoruby/src/value/rvalue/rational.rs:339-345 | monoruby/src/value/rvalue/rational.rs:347-353 | monoruby/src/value/rvalue/rational.rs:355-364 — 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.
Edited copies of one member (4 members, 7+ corresponding lines) monoruby/src/builtins/time.rs:4378— monoruby/src/builtins/time.rs:4378-4384 | monoruby/src/builtins/time.rs:4387-4393 | monoruby/src/builtins/time.rs:4396-4402 | monoruby/src/builtins/time.rs:4405-4411 — 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.
Duplicated block (24 lines × 2) monoruby/src/codegen/arch/aarch64/codegen.rs:130— monoruby/src/codegen/arch/aarch64/codegen.rs:130-153 | monoruby/src/codegen/arch/aarch64/codegen.rs:185-208 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/codegen.rs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) monoruby/src/value/rvalue/string.rs:931— monoruby/src/value/rvalue/string.rs:931-954 | monoruby/src/value/rvalue/string.rs:1130-1153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) monoruby/gem/nokogiri/xml/node/save_options.rb:48— monoruby/gem/nokogiri/xml/node/save_options.rb:48-71 | monoruby/gem/nokogiri/xml/parse_options.rb:170-213 — 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 (17 lines × 2) monoruby/src/builtins/io.rs:5172— monoruby/src/builtins/io.rs:5172-5188 | monoruby/src/builtins/io.rs:5234-5250 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/io.rs:5172` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) monoruby/src/builtins/process.rs:952— monoruby/src/builtins/process.rs:952-968 | monoruby/src/builtins/process.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 `monoruby/src/builtins/process.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. 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) monoruby/src/codegen/arch/x86_64/invoker.rs:75— monoruby/src/codegen/arch/x86_64/invoker.rs:75-91 | monoruby/src/codegen/arch/x86_64/invoker.rs:104-120 — both copies are in the same file, so extract the 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–16 lines × 2) monoruby/src/builtins/file.rs:1388— monoruby/src/builtins/file.rs:1388-1403 | monoruby/src/builtins/file.rs:1541-1554 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/file.rs:1388` 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 (14–16 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:436— monoruby/src/codegen/arch/aarch64/compile/mod.rs:436-451 | monoruby/src/codegen/jitgen/asmir.rs:4521-4534 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/jitgen/asmir.rs` as WHOLE FILES: this scan already matched 6 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:436` 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–16 lines × 2) monoruby/src/value/rvalue/string/pack.rs:1088— monoruby/src/value/rvalue/string/pack.rs:1088-1103 | monoruby/src/value/rvalue/string/pack.rs:1130-1143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/pack.rs:1088` it does not close everything it opens, so those exact lines 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–15 lines × 2) monoruby/src/builtins/module.rs:2617— monoruby/src/builtins/module.rs:2617-2631 | monoruby/src/builtins/module.rs:2651-2661 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/module.rs:2617` it does not close everything it opens, so those exact lines 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–15 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1989— monoruby/src/codegen/arch/aarch64/compile/mod.rs:1989-1999 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:741-755 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/arch/x86_64/compile/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:1989` 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–15 lines × 2) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1190— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1190-1200 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1247-1261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1190` it does not close everything it opens, so those exact lines 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–14 lines × 2) monoruby/src/builtins/regexp.rs:1590— monoruby/src/builtins/regexp.rs:1590-1599 | monoruby/src/builtins/regexp.rs:1714-1727 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/regexp.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.
Duplicated block (10–14 lines × 2) monoruby/src/builtins/string.rs:6540— monoruby/src/builtins/string.rs:6540-6553 | monoruby/src/builtins/string.rs:6660-6669 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:6540` 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–14 lines × 2) monoruby/src/codegen/jitgen/compile/method_call.rs:1204— monoruby/src/codegen/jitgen/compile/method_call.rs:1204-1213 | monoruby/src/codegen/jitgen/compile/method_call.rs:1233-1246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/compile/method_call.rs:1204` 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, `monoruby/src/codegen/jitgen/compile/method_call.rs:1247` calls `load_fpr`, `pin_fpr` and `monoruby/src/codegen/jitgen/compile/method_call.rs:1214` 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–12 lines × 2) monoruby/src/builtins/kernel.rs:1644— monoruby/src/builtins/kernel.rs:1644-1655 | monoruby/src/builtins/kernel.rs:1688-1696 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/kernel.rs:1644` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–12 lines × 2) monoruby/src/builtins/marshal.rs:2332— monoruby/src/builtins/marshal.rs:2332-2343 | monoruby/src/builtins/marshal.rs:2353-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 `monoruby/src/builtins/marshal.rs:2332` it does not close everything it opens, so those exact lines 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–12 lines × 2) monoruby/src/value/rvalue/io.rs:1849— monoruby/src/value/rvalue/io.rs:1849-1860 | monoruby/src/value/rvalue/io.rs:1872-1880 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/io.rs:1849` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) monoruby/src/builtins/array.rs:1264— monoruby/src/builtins/array.rs:1264-1273 | monoruby/src/builtins/array.rs:1302-1312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:1264` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) monoruby/src/builtins/module.rs:3209— monoruby/src/builtins/module.rs:3209-3218 | monoruby/src/builtins/module.rs:3246-3256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/module.rs:3209` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) monoruby/src/codegen/jitgen/compile/frameless_call.rs:504— monoruby/src/codegen/jitgen/compile/frameless_call.rs:504-514 | monoruby/src/codegen/jitgen/compile/frameless_call.rs:552-561 — both copies are in the same file, so extract the 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–10 lines × 2) monoruby/src/builtins/file.rs:2460— monoruby/src/builtins/file.rs:2460-2469 | monoruby/src/builtins/file.rs:2471-2478 — both copies are in the same file, so extract the 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–10 lines × 2) monoruby/src/builtins/string.rs:10745— monoruby/src/builtins/string.rs:10745-10752 | monoruby/src/builtins/string.rs:11517-11526 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:10745` 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–10 lines × 2) monoruby/src/value/rvalue.rs:1775— monoruby/src/value/rvalue.rs:1775-1782 | monoruby/src/value/rvalue.rs:1988-1997 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue.rs:1775` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/set.rs:1010— monoruby/src/builtins/set.rs:1010-1017 | monoruby/src/builtins/set.rs:1043-1050 | monoruby/src/builtins/set.rs:1078-1085 | monoruby/src/builtins/set.rs:1114-1121 — 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 `monoruby/src/builtins/set.rs:1010` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 4) monoruby/src/builtins/string.rs:4603— monoruby/src/builtins/string.rs:4603-4610 | monoruby/src/builtins/string.rs:10742-10749 | monoruby/src/builtins/string.rs:11514-11521 | monoruby/src/builtins/string.rs:11635-11642 — 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, `monoruby/src/builtins/string.rs:11643` calls `is_empty` and `monoruby/src/builtins/string.rs:10751` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 4) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1667— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1667-1674 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1712-1719 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1754-1761 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1785-1792 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1667` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 2) ext/bcrypt/src/lib.rs:51— ext/bcrypt/src/lib.rs:51-57 | ext/bcrypt/src/lib.rs:58-65 — both copies are in the same file, so extract the 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–8 lines × 2) monoruby/src/value/rvalue/string/pack.rs:823— monoruby/src/value/rvalue/string/pack.rs:823-829 | monoruby/src/value/rvalue/string/pack.rs:836-843 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/pack.rs:836` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `monoruby/src/value/rvalue/string/pack.rs:829` calls `extend_from_slice`, `Err`, `argumenterr` and `monoruby/src/value/rvalue/string/pack.rs:843` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–8 lines × 2) monoruby/src/codegen/runtime/args.rs:299— monoruby/src/codegen/runtime/args.rs:299-305 | monoruby/src/codegen/runtime/args.rs:620-627 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Hollow method — returns a constant without doing the work ext/nokogiri/src/lib.rs:1095— `io_close` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work monoruby/src/builtins/string.rs:12535— `succ_walks_its_own_encoding` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work monoruby/src/globals.rs:250— `noinline_gen` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
IC1 · Incompleteness & stubs· Empty method body · ×3
Empty method body — does nothing with its inputs monoruby/src/ast/source_info.rs:225— `show_loc` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs REDACTED:3863— `_dump_reg` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs monoruby/src/scheduler/native.rs:64— `ubf_handler` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Encoding::try_from_str (cyclomatic 109) monoruby/src/value/rvalue/string.rs:2536— Encoding::try_from_str has cyclomatic complexity 109 (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.
Encoding::classify (cyclomatic 32) monoruby/src/value/rvalue/string.rs:2397— Encoding::classify 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.
TraceIr::from_pc (cyclomatic 91) monoruby/src/codegen/jitgen/trace_ir.rs:384— TraceIr::from_pc has cyclomatic complexity 91 (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.
TraceIr::format (cyclomatic 82) monoruby/src/codegen/jitgen/trace_ir.rs:960— TraceIr::format has cyclomatic complexity 82 (threshold 15). Of this number, 80 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
AbstractState::set_arguments (cyclomatic 68) monoruby/src/codegen/jitgen/compile/method_call.rs:3966— AbstractState::set_arguments 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.
AbstractState::binop_integer_gp (cyclomatic 17) monoruby/src/codegen/jitgen/state/binop.rs:154— AbstractState::binop_integer_gp has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
markly_native::to_tuple (cyclomatic 37) ext/markly/src/lib.rs:395— markly_native::to_tuple has cyclomatic complexity 37 (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.
markly_native::build (cyclomatic 36) ext/markly/src/lib.rs:722— markly_native::build 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.
MarshalReader::read_user_object (cyclomatic 31) monoruby/src/builtins/marshal.rs:905— MarshalReader::read_user_object 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.
MarshalReader::read_ivar_wrapped (cyclomatic 28) monoruby/src/builtins/marshal.rs:652— MarshalReader::read_ivar_wrapped 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.
RStringInner::inspect (cyclomatic 27) monoruby/src/value/rvalue/string.rs:3391— RStringInner::inspect has cyclomatic complexity 27 (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: Encoding::name (cyclomatic 28) 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.
RStringInner::scrub (cyclomatic 21) monoruby/src/value/rvalue/string.rs:4474— RStringInner::scrub 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. This is NOT this file's highest cyclomatic complexity: Encoding::name (cyclomatic 28) 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.
Store::describe_func (cyclomatic 26) monoruby/src/globals/store.rs:1561— Store::describe_func 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.
Store::handle_args (cyclomatic 17) monoruby/src/globals/store.rs:2904— Store::handle_args 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.
psych_native::yaml_emit (cyclomatic 25) ext/psych/src/lib.rs:421— psych_native::yaml_emit 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.
psych_native::yaml_parse (cyclomatic 18) ext/psych/src/lib.rs:77— psych_native::yaml_parse has cyclomatic complexity 18 (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.
Generator::generate (cyclomatic 20) monoruby/src/builtins/json.rs:1876— Generator::generate 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.
Generator::object (cyclomatic 19) monoruby/src/builtins/json.rs:2235— Generator::object 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.
Plain::node (cognitive 82) ext/markly/src/lib.rs:1000— Plain::node has cognitive complexity 82 (threshold 15). Drivers by points: if/else 32 (59 pts), match/switch 3 (10 pts), loops 2 (7 pts), boolean chains 6 (nesting depth added 39). 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.
Plain::out (cognitive 16) ext/markly/src/lib.rs:932— Plain::out has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 2 (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.
MarshalReader::read_user_object (cognitive 61) monoruby/src/builtins/marshal.rs:905— MarshalReader::read_user_object has cognitive complexity 61 (threshold 15). Drivers by points: if/else 18 (38 pts), match/switch 4 (14 pts), loops 5 (9 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.
MarshalReader::read_ivar_wrapped (cognitive 55) monoruby/src/builtins/marshal.rs:652— MarshalReader::read_ivar_wrapped has cognitive complexity 55 (threshold 15). Drivers by points: if/else 11 (32 pts), loops 5 (12 pts), match/switch 3 (8 pts), boolean chains 3 (nesting depth added 33). 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.
AbstractFrame::bridge (cognitive 56) monoruby/src/codegen/jitgen/state/slot.rs:3428— AbstractFrame::bridge has cognitive complexity 56 (threshold 15). Drivers by points: if/else 32 (51 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 20). 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.
AbstractFrame::guard_class_state (cognitive 19) monoruby/src/codegen/jitgen/state/slot.rs:2379— AbstractFrame::guard_class_state has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TraceIr::from_pc (cognitive 46) monoruby/src/codegen/jitgen/trace_ir.rs:384— TraceIr::from_pc has cognitive complexity 46 (threshold 15). Drivers by points: if/else 18 (34 pts), match/switch 3 (7 pts), boolean chains 5 (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.
TraceIr::format (cognitive 27) monoruby/src/codegen/jitgen/trace_ir.rs:960— TraceIr::format has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 2 (4 pts), match/switch 3 (4 pts) (nesting depth added 12). Of this number, 24 points are the body's own statements and 3 belong to 2 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.
Value::from_ast_inner (cognitive 37) monoruby/src/value.rs:3729— Value::from_ast_inner has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 6 (13 pts), loops 2 (5 pts) (nesting depth added 17). 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.
Value::coerce_to_char (cognitive 34) monoruby/src/value/coerce.rs:706— Value::coerce_to_char has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (32 pts), boolean chains 1, match/switch 1 (nesting depth added 20). 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.
RationalInner::rational_round (cognitive 34) monoruby/src/value/rvalue/rational.rs:556— RationalInner::rational_round has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (30 pts), match/switch 1 (3 pts), boolean chains 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.
RationalInner::round_small (cognitive 18) monoruby/src/value/rvalue/rational.rs:520— RationalInner::round_small has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 1 (2 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.
psych_native::yaml_emit (cognitive 28) ext/psych/src/lib.rs:421— psych_native::yaml_emit has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3, loops 1 (3 pts), match/switch 3 (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.
psych_native::yaml_parse (cognitive 19) ext/psych/src/lib.rs:77— psych_native::yaml_parse has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 5 (13 pts), loops 2 (4 pts), if/else 1 (2 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.
SlotState::new_method (cognitive 28) monoruby/src/codegen/jitgen/state/slot.rs:407— SlotState::new_method has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 6 (10 pts), match/switch 1 (3 pts), boolean chains 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.
SlotState::discard_above (cognitive 18) monoruby/src/codegen/jitgen/state/slot.rs:991— SlotState::discard_above has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 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.
Allocator::gc (cognitive 22) monoruby/src/alloc.rs:1731— Allocator::gc has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (17 pts), match/switch 3, 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, 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.
Allocator::sweep (cognitive 17) monoruby/src/alloc.rs:2350— Allocator::sweep has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 5 (7 pts) (nesting depth added 5). Of this number, 10 points are the body's own statements and 7 belong to 2 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.
markly_native::build (cognitive 18) ext/markly/src/lib.rs:722— markly_native::build has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 4 (7 pts), boolean chains 1 (nesting depth added 8). 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.
markly_native::to_tuple (cognitive 16) ext/markly/src/lib.rs:395— markly_native::to_tuple has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (4 pts) (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:188— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:188-269 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:655-741 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:758-871 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1305-1369 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1399-1418 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1893-2010 — 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) monoruby/src/value/rvalue/string.rs:149— monoruby/src/value/rvalue/string.rs:149-162 | monoruby/src/value/rvalue/string.rs:192-205 | monoruby/src/value/rvalue/string.rs:212-225 | monoruby/src/value/rvalue/string.rs:236-249 | monoruby/src/value/rvalue/string.rs:256-269 | monoruby/src/value/rvalue/string.rs:277-300 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) monoruby/src/builtins/set.rs:1004— monoruby/src/builtins/set.rs:1004-1027 | monoruby/src/builtins/set.rs:1037-1060 | monoruby/src/builtins/set.rs:1072-1098 | monoruby/src/builtins/set.rs:1108-1134 | monoruby/src/builtins/set.rs:1146-1180 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3134— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3134-3151 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3219-3237 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3330-3351 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3573-3592 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4156-4175 — 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 (63 corresponding lines) · ×2
Edited copy of a member (63 corresponding lines) monoruby/src/executor/op/binary_ops.rs:668— monoruby/src/executor/op/binary_ops.rs:668-730 | monoruby/src/executor/op/binary_ops.rs:740-805 — 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.
Edited copy of a member (63 corresponding lines) monoruby/src/builtins/module.rs:1000— monoruby/src/builtins/module.rs:1000-1065 | monoruby/src/builtins/object.rs:639-701 — 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 (51 corresponding lines) · ×2
Edited copy of a member (51 corresponding lines) monoruby/src/builtins/struct_class.rs:669— monoruby/src/builtins/struct_class.rs:669-719 | monoruby/src/builtins/struct_class.rs:734-785 — These two members are one piece of code written twice and then edited apart: 51 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 (51 corresponding lines) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:730— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:730-782 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:1052-1102 — These two members are one piece of code written twice and then edited apart: 51 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) monoruby/src/builtins/string.rs:5049— monoruby/src/builtins/string.rs:5049-5114 | monoruby/src/builtins/string.rs:5676-5723 — 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) monoruby/src/codegen/jitgen/compile/method_call.rs:3620— monoruby/src/codegen/jitgen/compile/method_call.rs:3620-3668 | monoruby/src/codegen/jitgen/compile/method_call.rs:3747-3794 — 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 (43 corresponding lines) · ×2
Edited copy of a member (43 corresponding lines) monoruby/src/builtins/kernel.rs:2917— monoruby/src/builtins/kernel.rs:2917-2973 | monoruby/src/builtins/kernel.rs:3163-3205 — 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.
Edited copy of a member (43 corresponding lines) monoruby/builtins/array.rb:284— monoruby/builtins/array.rb:284-326 | monoruby/builtins/array.rb:604-650 — 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 (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) monoruby/src/value/rvalue/string.rs:3832— monoruby/src/value/rvalue/string.rs:3832-3863 | monoruby/src/value/rvalue/string.rs:3907-3938 — 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) monoruby/src/builtins/hash.rs:2851— monoruby/src/builtins/hash.rs:2851-2893 | monoruby/src/builtins/hash.rs:3885-3916 — 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 (40 corresponding lines) · ×2
Edited copy of a member (40 corresponding lines) monoruby/src/builtins/io_buffer.rs:463— monoruby/src/builtins/io_buffer.rs:463-502 | monoruby/src/builtins/io_buffer.rs:531-579 — 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.
Edited copy of a member (40 corresponding lines) monoruby/src/builtins/array.rs:219— monoruby/src/builtins/array.rs:219-258 | monoruby/src/builtins/range.rs:77-118 — 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 (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) monoruby/src/builtins/array.rs:3165— monoruby/src/builtins/array.rs:3165-3207 | monoruby/src/builtins/array.rs:3278-3311 — 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) monoruby/src/builtins/set.rs:919— monoruby/src/builtins/set.rs:919-952 | monoruby/src/builtins/set.rs:961-994 — 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 (38 corresponding lines) · ×2
Edited copy of a member (38 corresponding lines) monoruby/src/builtins/string.rs:2307— monoruby/src/builtins/string.rs:2307-2354 | monoruby/src/builtins/string.rs:2357-2394 — 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) monoruby/src/builtins/array.rs:526— monoruby/src/builtins/array.rs:526-563 | monoruby/src/builtins/array.rs:5116-5155 — 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 (36 corresponding lines) · ×2
Edited copy of a member (36 corresponding lines) monoruby/src/builtins/string.rs:4354— monoruby/src/builtins/string.rs:4354-4389 | monoruby/src/builtins/string.rs:4415-4452 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) monoruby/builtins/enumerable.rb:761— monoruby/builtins/enumerable.rb:761-796 | monoruby/builtins/enumerable.rb:800-835 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) monoruby/src/builtins/array.rs:1263— monoruby/src/builtins/array.rs:1263-1292 | monoruby/src/builtins/set.rs:721-749 — 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) monoruby/gem/strptime/strptime.rb:85— monoruby/gem/strptime/strptime.rb:85-118 | monoruby/gem/strptime/strptime.rb:341-369 — 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 copies of one member (3 members, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) monoruby/src/builtins/io.rs:6731— monoruby/src/builtins/io.rs:6731-6742 | monoruby/src/builtins/io.rs:6755-6766 | monoruby/src/builtins/io.rs:6779-6790 — 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) monoruby/src/builtins/range.rs:387— monoruby/src/builtins/range.rs:387-398 | monoruby/src/builtins/range.rs:729-743 | monoruby/src/builtins/range.rs:748-762 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) monoruby/src/value/rvalue/io.rs:1178— monoruby/src/value/rvalue/io.rs:1178-1193 | monoruby/src/value/rvalue/io.rs:1230-1248 | monoruby/src/value/rvalue/io.rs:1290-1310 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) monoruby/src/builtins/numeric/complex.rs:612— monoruby/src/builtins/numeric/complex.rs:612-627 | monoruby/src/builtins/numeric/complex.rs:640-655 | monoruby/src/builtins/numeric/complex.rs:944-960 — 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 (4 members, 10+ corresponding lines) · ×2
Edited copies of one member (4 members, 10+ corresponding lines) monoruby/src/builtins/array.rs:3421— monoruby/src/builtins/array.rs:3421-3434 | monoruby/src/builtins/array.rs:3444-3453 | monoruby/src/builtins/array.rs:3490-3503 | monoruby/src/builtins/array.rs:3513-3522 — 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.
Edited copies of one member (4 members, 10+ corresponding lines) monoruby/src/ancestry.rs:39— monoruby/src/ancestry.rs:39-48 | monoruby/src/builtins/marshal.rs:1779-1788 | monoruby/src/globals/store/class.rs:1391-1400 | monoruby/src/value.rs:1051-1060 — 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 (3 members, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) monoruby/src/builtins/kernel.rs:1992— monoruby/src/builtins/kernel.rs:1992-2008 | monoruby/src/builtins/kernel.rs:2415-2431 | monoruby/src/builtins/kernel.rs:2869-2885 — 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) hashbrown/src/map.rs:1543— hashbrown/src/map.rs:1543-1560 | monoruby/src/value/rvalue/hash.rs:1257-1280 | rubymap/src/map.rs:1711-1727 — 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 copies of one member (3 members, 11+ corresponding lines) · ×2
Edited copies of one member (3 members, 11+ corresponding lines) REDACTED:72— REDACTED:72-83 | REDACTED:88-98 | REDACTED:103-113 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) monoruby/src/builtins/numeric/float.rs:137— monoruby/src/builtins/numeric/float.rs:137-147 | REDACTED:949-959 | REDACTED:962-972 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×2
Edited copies of one member (4 members, 8+ corresponding lines) monoruby/src/builtins/hash.rs:3372— monoruby/src/builtins/hash.rs:3372-3379 | monoruby/src/builtins/hash.rs:3382-3395 | monoruby/src/builtins/hash.rs:3406-3413 | monoruby/src/builtins/hash.rs:3416-3427 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 8+ corresponding lines) monoruby/src/builtins/method.rs:564— monoruby/src/builtins/method.rs:564-571 | monoruby/src/builtins/method.rs:715-722 | monoruby/src/builtins/method.rs:829-836 | monoruby/src/builtins/method.rs:850-857 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×2
Edited copies of one member (3 members, 7+ corresponding lines) REDACTED:18— REDACTED:18-26 | REDACTED:31-37 | REDACTED:42-50 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) monoruby/src/builtins/symbol.rs:317— monoruby/src/builtins/symbol.rs:317-323 | monoruby/src/builtins/symbol.rs:335-348 | monoruby/src/builtins/symbol.rs:362-368 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Duplicated block (22–23 lines × 2) monoruby/src/builtins/string.rs:8033— monoruby/src/builtins/string.rs:8033-8055 | monoruby/src/builtins/string.rs:8112-8133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:8033` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–23 lines × 2) monoruby/src/value/rvalue/string.rs:5747— monoruby/src/value/rvalue/string.rs:5747-5769 | monoruby/src/value/rvalue/string.rs:6155-6176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string.rs:5747` 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 (21–23 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:487— monoruby/src/codegen/arch/aarch64/compile/mod.rs:487-509 | monoruby/src/codegen/jitgen/asmir.rs:4573-4593 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/jitgen/asmir.rs` as WHOLE FILES: this scan already matched 6 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:487` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–23 lines × 2) monoruby/src/value/rvalue/string.rs:884— monoruby/src/value/rvalue/string.rs:884-906 | monoruby/src/value/rvalue/string.rs:1067-1087 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string.rs:884` 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–21 lines × 2) monoruby/src/builtins/kernel.rs:2141— monoruby/src/builtins/kernel.rs:2141-2161 | monoruby/src/builtins/kernel.rs:2258-2277 — both copies are in the same file, so extract the 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–21 lines × 2) monoruby/src/builtins/numeric/complex.rs:862— monoruby/src/builtins/numeric/complex.rs:862-881 | monoruby/src/builtins/numeric/complex.rs:884-904 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/numeric/complex.rs:884` 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 (19–20 lines × 2) monoruby/src/builtins/array.rs:877— monoruby/src/builtins/array.rs:877-895 | monoruby/src/builtins/array.rs:947-966 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:947` 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 (19–20 lines × 2) monoruby/src/builtins/string.rs:4045— monoruby/src/builtins/string.rs:4045-4063 | monoruby/src/builtins/string.rs:4079-4098 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:4079` 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) monoruby/src/value/rvalue/string/transcode.rs:7243— monoruby/src/value/rvalue/string/transcode.rs:7243-7262 | monoruby/src/value/rvalue/string/transcode.rs:7384-7403 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/transcode.rs:7243` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) monoruby/gem/msgpack/msgpack.rb:253— monoruby/gem/msgpack/msgpack.rb:253-272 | monoruby/gem/msgpack/msgpack.rb:284-303 — both copies are in the same file, so extract the 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 (19 lines × 3) monoruby/src/executor/format.rs:1001— monoruby/src/executor/format.rs:1001-1019 | monoruby/src/executor/format.rs:1106-1124 | monoruby/src/executor/format.rs:1209-1227 — 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 (19 lines × 3) monoruby/src/value/rvalue/thread.rs:238— monoruby/src/value/rvalue/thread.rs:238-256 | monoruby/src/value/rvalue/thread.rs:279-297 | monoruby/src/value/rvalue/thread.rs:312-330 — 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 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:449— monoruby/src/codegen/arch/aarch64/compile/mod.rs:449-466 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:506-523 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:449` 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:521— monoruby/src/codegen/arch/aarch64/compile/mod.rs:521-538 | monoruby/src/codegen/jitgen/asmir.rs:4603-4620 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/jitgen/asmir.rs` as WHOLE FILES: this scan already matched 6 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:521` 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–18 lines × 2) monoruby/src/globals/store/class.rs:2327— monoruby/src/globals/store/class.rs:2327-2344 | monoruby/src/globals/store/class.rs:2396-2411 — both copies are in the same file, so extract the 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–18 lines × 2) monoruby/src/parser/prism_backend.rs:4817— monoruby/src/parser/prism_backend.rs:4817-4832 | monoruby/src/parser/prism_backend.rs:4916-4933 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/parser/prism_backend.rs:4817` it does not close everything it opens, so those 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 `node` to `&LambdaNode<'pr>` in one and `&BlockNode<'pr>` 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–17 lines × 2) monoruby/src/builtins/regexp.rs:1443— monoruby/src/builtins/regexp.rs:1443-1456 | monoruby/src/builtins/regexp.rs:1759-1775 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/regexp.rs:1443` 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–17 lines × 2) monoruby/src/builtins/string.rs:1833— monoruby/src/builtins/string.rs:1833-1846 | monoruby/src/builtins/string.rs:1868-1884 — both copies are in the same file, so extract the 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–16 lines × 3) monoruby/src/builtins/kernel.rs:5157— monoruby/src/builtins/kernel.rs:5157-5168 | monoruby/src/builtins/kernel.rs:6193-6208 | monoruby/src/builtins/kernel.rs:6474-6487 — 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 `monoruby/src/builtins/kernel.rs:5157` 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–16 lines × 3) monoruby/src/executor.rs:2789— monoruby/src/executor.rs:2789-2804 | monoruby/src/executor/op.rs:1494-1505 | monoruby/src/executor/op.rs:1538-1549 — 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 `monoruby/src/executor.rs:2789` it does not close everything it opens, so those exact lines 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 × 3) monoruby/src/bytecodegen/defined.rs:104— monoruby/src/bytecodegen/defined.rs:104-118 | monoruby/src/bytecodegen/defined.rs:230-244 | monoruby/src/bytecodegen/defined.rs:291-305 — 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 `monoruby/src/bytecodegen/defined.rs:104` 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 × 3) monoruby/src/parser/prism_backend.rs:2568— monoruby/src/parser/prism_backend.rs:2568-2582 | monoruby/src/parser/prism_backend.rs:2615-2629 | monoruby/src/parser/prism_backend.rs:3346-3360 — 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 `monoruby/src/parser/prism_backend.rs:2568` it does not close everything it opens, so those exact lines 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–15 lines × 2) monoruby/src/builtins/string.rs:12579— monoruby/src/builtins/string.rs:12579-12593 | monoruby/src/builtins/string.rs:12611-12622 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:12579` it does not close everything it opens, so those exact lines 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–15 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:464— monoruby/src/codegen/arch/aarch64/compile/mod.rs:464-475 | monoruby/src/codegen/jitgen/asmir.rs:4545-4559 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/jitgen/asmir.rs` as WHOLE FILES: this scan already matched 6 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:464` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13–14 lines × 2) monoruby/src/builtins/marshal.rs:676— monoruby/src/builtins/marshal.rs:676-688 | monoruby/src/builtins/marshal.rs:694-707 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/marshal.rs:676` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13–14 lines × 2) monoruby/src/bytecodegen/expression.rs:540— monoruby/src/bytecodegen/expression.rs:540-552 | monoruby/src/bytecodegen/expression.rs:618-631 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/bytecodegen/expression.rs:540` 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–14 lines × 2) monoruby/src/codegen/jitgen/compile/method_call.rs:3655— monoruby/src/codegen/jitgen/compile/method_call.rs:3655-3666 | monoruby/src/codegen/jitgen/compile/method_call.rs:3779-3792 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/compile/method_call.rs:3655` 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 `self` to `super) fn generic_send(&mut` in one and `super) fn compile_yield(&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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `monoruby/src/codegen/jitgen/compile/method_call.rs:3654` calls `pc` and `monoruby/src/codegen/jitgen/compile/method_call.rs:3778` 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–14 lines × 2) monoruby/src/value/rvalue/string.rs:6436— monoruby/src/value/rvalue/string.rs:6436-6449 | monoruby/src/value/rvalue/string.rs:6531-6542 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string.rs:6531` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12–13 lines × 3) REDACTED:1285— REDACTED:1285-1296 | monoruby/src/executor/op.rs:1932-1944 | monoruby/src/executor/op.rs:1972-1983 — 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 `REDACTED:1285` it does not close everything it opens, so those exact lines 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 × 3) monoruby/src/value/rvalue/string/pack.rs:1029— monoruby/src/value/rvalue/string/pack.rs:1029-1040 | monoruby/src/value/rvalue/string/pack.rs:1048-1059 | monoruby/src/value/rvalue/string/pack.rs:1067-1079 — 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 `monoruby/src/value/rvalue/string/pack.rs:1029` it does not close everything it opens, so those 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, `monoruby/src/value/rvalue/string/pack.rs:1080` calls `push` and `monoruby/src/value/rvalue/string/pack.rs:1041` 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 (10–13 lines × 2) monoruby/src/builtins/array.rs:4377— monoruby/src/builtins/array.rs:4377-4386 | monoruby/src/builtins/array.rs:4408-4420 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/array.rs:4377` it does not close everything it opens, so those exact lines 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–13 lines × 2) monoruby/src/codegen/jitgen/context.rs:1402— monoruby/src/codegen/jitgen/context.rs:1402-1411 | monoruby/src/codegen/jitgen/context.rs:1476-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.
Duplicated block (8–13 lines × 2) monoruby/src/value/rvalue/string.rs:5103— monoruby/src/value/rvalue/string.rs:5103-5110 | monoruby/src/value/rvalue/string.rs:5141-5153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string.rs:5103` 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–13 lines × 2) ext/nokogiri/src/document.rs:93— ext/nokogiri/src/document.rs:93-105 | ext/nokogiri/src/document.rs:214-221 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/document.rs:93` it does not close everything it opens, so those exact lines 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–12 lines × 2) monoruby/src/builtins/match_data.rs:675— monoruby/src/builtins/match_data.rs:675-684 | monoruby/src/builtins/match_data.rs:814-825 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–12 lines × 2) monoruby/src/scheduler.rs:488— monoruby/src/scheduler.rs:488-499 | monoruby/src/scheduler/native.rs:905-914 — before extracting anything, compare `monoruby/src/scheduler.rs` and `monoruby/src/scheduler/native.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/scheduler.rs:488` it does not close everything it opens, so those 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, `monoruby/src/scheduler.rs:500` calls `retain`, `Some` and `monoruby/src/scheduler/native.rs:915` 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 (8–11 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:561— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:561-571 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:616-623 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:561` 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–11 lines × 2) monoruby/src/codegen/arch/x86_64/compile/mod.rs:2064— monoruby/src/codegen/arch/x86_64/compile/mod.rs:2064-2071 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2150-2160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/x86_64/compile/mod.rs:2064` 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) monoruby/src/builtins/numeric/complex.rs:613— monoruby/src/builtins/numeric/complex.rs:613-621 | monoruby/src/builtins/numeric/complex.rs:945-952 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/numeric/complex.rs:613` it does not close everything it opens, so those 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–9 lines × 2) REDACTED:618— REDACTED:618-626 | REDACTED:702-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 `REDACTED:618` 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 × 5) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3142— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3142-3149 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3229-3236 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3342-3349 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3583-3590 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4166-4173 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3142` it does not close everything it opens, so those 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, `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3341` calls `a64_frame_load` and `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3228` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 5) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1639— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1639-1646 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1696-1703 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1742-1749 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1772-1779 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2817-2824 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1639` it does not close everything it opens, so those 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 `super) fn a64_call_recompile( &mut` in one and `super) fn a64_call_recompile_with_recovery(&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 (7 lines × 6) monoruby/src/builtins/time.rs:1349— monoruby/src/builtins/time.rs:1349-1355 | monoruby/src/builtins/time.rs:1356-1362 | monoruby/src/builtins/time.rs:1363-1369 | monoruby/src/builtins/time.rs:2698-2704 | monoruby/src/builtins/time.rs:2705-2711 | monoruby/src/builtins/time.rs:2712-2718 — 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 `monoruby/src/builtins/time.rs:1349` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 6) monoruby/src/value/rvalue/string.rs:150— monoruby/src/value/rvalue/string.rs:150-156 | monoruby/src/value/rvalue/string.rs:193-199 | monoruby/src/value/rvalue/string.rs:213-219 | monoruby/src/value/rvalue/string.rs:237-243 | monoruby/src/value/rvalue/string.rs:257-263 | monoruby/src/value/rvalue/string.rs:278-284 — 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 `monoruby/src/value/rvalue/string.rs:150` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Weak hash algorithm ext/digest/src/lib.rs:60— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm ext/digest/src/lib.rs:61— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
X12 · Unreachable branch· Statement is unreachable · ×2
Statement is unreachable — control never gets past the statement before it ext/nokogiri/src/reader.rs:343— `let node = expand(ctx, this, args, reader) ?;` follows `{ return Ok(hash); }` (line 340) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run.
Statement is unreachable — control never gets past the statement before it ext/nokogiri/src/reader.rs:368— `let node = expand(ctx, this, args, reader) ?;` follows `{ return Ok(hash); }` (line 365) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run.
X18 · Disposal-pattern correctness· Explicit release owed and not made on every path · ×2
Explicit release owed and not made on every path monoruby/src/prof.rs:1687— `f` (line 1687) is a `BufWriter` this function owns and never releases: no `flush()` (or `into_inner()`) on any path, and it is not handed on. Rust drops it at the end of the scope, and a buffered writer that is dropped flushes and throws the error away, so a failed write reports success. Release it where the work ends.
Explicit release owed and not made on every path hashbrown/src/raw/mod.rs:1804— `group` (line 1804) is a `Group` this function owns and never releases: no `store_aligned()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Group` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends.
X18 · Disposal-pattern correctness· Owned value's release suppressed and never restored · ×2
Owned value's release suppressed and never restored monoruby/src/value/rvalue/io/buf.rs:43— `StdFd.0` is a `ManuallyDrop<std::fs::File>` (line 43): wrapping it switched its `Drop` off, and no method of `StdFd` ever switches it back on — no `ManuallyDrop::drop`, `take` or `into_inner` of `self.0`, and `StdFd` has no `Drop` that does it. Every `StdFd` that goes away leaks what the field owns. Release it in `impl Drop for StdFd` (`unsafe { ManuallyDrop::drop(&mut self.0) }`), or hold the value plainly if nothing needs to control its drop order.
Owned value's release suppressed and never restored hashbrown/src/raw/mod.rs:3083— `mem::forget(guard)` (line 3083) takes `guard` out of Rust's ownership: its `Drop` never runs, so whatever it holds — a descriptor, a socket, a buffer, a lock — is never given back, and nothing can give it back later because the value is gone. Let it drop (or call its explicit close) where its work ends; if the handle must outlive this function, turn it into a raw handle with `into_raw`/`into_raw_fd` and reclaim it with the matching `from_raw` when the owner is done.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark .github/bench-pages/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Socket.tcp_with_fast_fallback (cyclomatic 78) monoruby/stdlib/socket.rb:693— Socket.tcp_with_fast_fallback has cyclomatic complexity 78 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strptime.__exec0 (cyclomatic 71) monoruby/gem/strptime/strptime.rb:147— Strptime.__exec0 has cyclomatic complexity 71 (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.
Preprocess::unescape_nonascii (cyclomatic 57) monoruby/src/value/rvalue/regexp.rs:846— Preprocess::unescape_nonascii has cyclomatic complexity 57 (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.
BigDecimal.power (cyclomatic 56) monoruby/gem/bigdecimal.rb:97— BigDecimal.power 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.
Plain::node (cyclomatic 54) ext/markly/src/lib.rs:1000— Plain::node 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.
Numeric.step (cyclomatic 49) monoruby/builtins/numeric.rb:191— Numeric.step has cyclomatic complexity 49 (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.
Parser.__do_parse (cyclomatic 41) monoruby/gem/yajl/yajl.rb:542— Parser.__do_parse has cyclomatic complexity 41 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Loop.__ev_run (cyclomatic 39) monoruby/gem/cool.io_ext.rb:130— Loop.__ev_run has cyclomatic complexity 39 (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.
Enumerable.minmax (cyclomatic 32) monoruby/builtins/enumerable.rb:843— Enumerable.minmax 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.
Range.__range_step_numeric (cyclomatic 32) monoruby/builtins/range.rb:758— Range.__range_step_numeric 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.
aobench-cpu.html.drawFlame (cyclomatic 30) docs/src/profiler/aobench-cpu.html:813— aobench-cpu.html.drawFlame 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.
optcarrot.html.drawFlame (cyclomatic 30) docs/src/profiler/optcarrot.html:813— optcarrot.html.drawFlame 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.
viewer.html.drawFlame (cyclomatic 30) monoruby/src/prof/viewer.html:813— viewer.html.drawFlame 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.
aobench-cpu.html.viewFlame (cyclomatic 29) docs/src/profiler/aobench-cpu.html:880— aobench-cpu.html.viewFlame has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 930, updateCrumbs, a function literal at line 944, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
optcarrot.html.viewFlame (cyclomatic 29) docs/src/profiler/optcarrot.html:880— optcarrot.html.viewFlame has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 930, updateCrumbs, a function literal at line 944, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
viewer.html.viewFlame (cyclomatic 29) monoruby/src/prof/viewer.html:880— viewer.html.viewFlame has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 930, updateCrumbs, a function literal at line 944, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Range.step (cyclomatic 28) monoruby/builtins/range.rb:453— Range.step 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.
Range.__range_step_size (cyclomatic 26) monoruby/builtins/range.rb:948— Range.__range_step_size 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.
XPathVisitor.visit_function (cyclomatic 26) monoruby/gem/nokogiri/css/xpath_visitor.rb:103— XPathVisitor.visit_function 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.
String.upto (cyclomatic 25) monoruby/builtins/string.rb:144— String.upto 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.
Parser.__lex_string (cyclomatic 25) monoruby/gem/yajl/yajl.rb:345— Parser.__lex_string 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.
ArithmeticSequence.each (cyclomatic 24) monoruby/builtins/arithmetic_sequence.rb:107— ArithmeticSequence.each 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.
Window._pump_events (cyclomatic 24) monoruby/gem/gosu.rb:661— Window._pump_events 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.
Parser.__lex_number (cyclomatic 24) monoruby/gem/yajl/yajl.rb:390— Parser.__lex_number 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.
SlotAnalysis::new (cyclomatic 23) monoruby/src/codegen/jitgen/slot_analysis.rs:233— SlotAnalysis::new 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.
Range.reverse_each (cyclomatic 23) monoruby/builtins/range.rb:76— Range.reverse_each 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.
Range.__cover_range_q (cyclomatic 23) monoruby/builtins/range.rb:697— Range.__cover_range_q has cyclomatic complexity 23 (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.
Parser.__decode_string (cyclomatic 23) monoruby/gem/yajl/yajl.rb:488— Parser.__decode_string 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.
aobench-cpu.html.drawTimeline (cyclomatic 23) docs/src/profiler/aobench-cpu.html:517— aobench-cpu.html.drawTimeline has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
optcarrot.html.drawTimeline (cyclomatic 23) docs/src/profiler/optcarrot.html:517— optcarrot.html.drawTimeline has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
viewer.html.drawTimeline (cyclomatic 23) monoruby/src/prof/viewer.html:517— viewer.html.drawTimeline has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Range.each (cyclomatic 22) monoruby/builtins/range.rb:4— Range.each 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.
Window._gosu_pad_button_id (cyclomatic 22) monoruby/gem/gosu.rb:757— Window._gosu_pad_button_id has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Encoder.__encode_part (cyclomatic 22) monoruby/gem/yajl/yajl.rb:796— Encoder.__encode_part 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.
Encoder.__escape (cyclomatic 22) monoruby/gem/yajl/yajl.rb:907— Encoder.__escape 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.
GenConfig::configure (cyclomatic 21) monoruby/src/builtins/json.rs:1495— GenConfig::configure 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.
CharByteIter::next (cyclomatic 21) monoruby/src/value/rvalue/string.rs:371— CharByteIter::next 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. This is NOT this file's highest cyclomatic complexity: Encoding::name (cyclomatic 28) 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.
Ractor.__shareable? (cyclomatic 21) monoruby/builtins/ractor.rb:203— Ractor.__shareable? 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.
aobench-cpu.html.initTimeline (cyclomatic 21) docs/src/profiler/aobench-cpu.html:613— aobench-cpu.html.initTimeline has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 657, 638, 647, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
aobench-cpu.html.viewMethods (cyclomatic 21) docs/src/profiler/aobench-cpu.html:995— aobench-cpu.html.viewMethods has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (drawDetail, a function literal at line 1034, a function literal at line 1007, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
optcarrot.html.initTimeline (cyclomatic 21) docs/src/profiler/optcarrot.html:613— optcarrot.html.initTimeline has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 657, 638, 647, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
optcarrot.html.viewMethods (cyclomatic 21) docs/src/profiler/optcarrot.html:995— optcarrot.html.viewMethods has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (drawDetail, a function literal at line 1034, a function literal at line 1007, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
viewer.html.initTimeline (cyclomatic 21) monoruby/src/prof/viewer.html:613— viewer.html.initTimeline has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 657, 638, 647, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
viewer.html.viewMethods (cyclomatic 21) monoruby/src/prof/viewer.html:995— viewer.html.viewMethods has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (drawDetail, a function literal at line 1034, a function literal at line 1007, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Allocator::gc (cyclomatic 20) monoruby/src/alloc.rs:1731— Allocator::gc has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Parser::unescape (cyclomatic 20) monoruby/src/builtins/json.rs:1131— Parser::unescape 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.
AsmInst::fpr_operands (cyclomatic 20) monoruby/src/codegen/jitgen/asmir.rs:4226— AsmInst::fpr_operands 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. This is NOT this file's highest cyclomatic complexity: AsmInst::dump (cyclomatic 37) 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.
Open3.__drain (cyclomatic 20) REDACTED:120— Open3.__drain 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.
LinkMode::from_caller_inner (cyclomatic 19) monoruby/src/codegen/jitgen/state/slot.rs:2943— LinkMode::from_caller_inner 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 is NOT this file's highest cyclomatic complexity: SlotState::write_back (cyclomatic 20) 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.
ClassInfoTable::search_method_from (cyclomatic 19) monoruby/src/globals/store/class.rs:1540— ClassInfoTable::search_method_from 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 is NOT this file's highest cyclomatic complexity: ClassId::fmt (cyclomatic 59) 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.
Range.include? (cyclomatic 19) monoruby/builtins/range.rb:241— Range.include? 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.
Strptime.__compile (cyclomatic 19) monoruby/gem/strptime/strptime.rb:84— Strptime.__compile has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Socket.udp_server_sockets (cyclomatic 19) monoruby/stdlib/socket.rb:1349— Socket.udp_server_sockets 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.
JitModule::gen_chain_replay_stub (cyclomatic 18) monoruby/src/codegen/jitgen.rs:2005— JitModule::gen_chain_replay_stub has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Kernel.warn (cyclomatic 18) monoruby/builtins/kernel.rb:153— Kernel.warn 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. This is NOT this file's highest cyclomatic complexity: Kernel.test (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 method is counted neither in this dimension's figures nor in its score.
Pathname.plus (cyclomatic 18) REDACTED:671— Pathname.plus has cyclomatic complexity 18 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Range.max (cyclomatic 18) monoruby/builtins/range.rb:339— Range.max 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.
Range.__bsearch_float (cyclomatic 18) monoruby/builtins/range.rb:615— Range.__bsearch_float has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Range.__range_step_generic (cyclomatic 18) monoruby/builtins/range.rb:901— Range.__range_step_generic 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.
aobench-cpu.html.viewJit (cyclomatic 18) docs/src/profiler/aobench-cpu.html:1093— aobench-cpu.html.viewJit has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
optcarrot.html.viewJit (cyclomatic 18) docs/src/profiler/optcarrot.html:1093— optcarrot.html.viewJit has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
viewer.html.viewJit (cyclomatic 18) monoruby/src/prof/viewer.html:1093— viewer.html.viewJit has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
AsmIr::push (cyclomatic 17) monoruby/src/codegen/jitgen/asmir.rs:622— AsmIr::push has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: AsmInst::dump (cyclomatic 37) 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.
Enumerable.minmax_by (cyclomatic 17) monoruby/builtins/enumerable.rb:992— Enumerable.minmax_by 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.
Range.__bsearch_int (cyclomatic 17) monoruby/builtins/range.rb:544— Range.__bsearch_int 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.
Packer.__write_integer_value (cyclomatic 17) monoruby/gem/msgpack/msgpack.rb:598— Packer.__write_integer_value 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: Unpacker.__parse (cyclomatic 37) 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 method is counted neither in this dimension's figures nor in its score.
aobench-cpu.html.makeTable::draw (cyclomatic 17) docs/src/profiler/aobench-cpu.html:378— aobench-cpu.html.makeTable::draw 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.
optcarrot.html.makeTable::draw (cyclomatic 17) docs/src/profiler/optcarrot.html:378— optcarrot.html.makeTable::draw 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.
viewer.html.makeTable::draw (cyclomatic 17) monoruby/src/prof/viewer.html:378— viewer.html.makeTable::draw 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.
RationalInner::rational_round (cyclomatic 16) monoruby/src/value/rvalue/rational.rs:556— RationalInner::rational_round 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.
Array.bsearch_index (cyclomatic 16) monoruby/builtins/array.rb:329— Array.bsearch_index 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.
Array.permutation (cyclomatic 16) monoruby/builtins/array.rb:374— Array.permutation 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.
Enumerable.cycle (cyclomatic 16) monoruby/builtins/enumerable.rb:1079— Enumerable.cycle 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.
Exception.full_message (cyclomatic 16) monoruby/builtins/exception.rb:111— Exception.full_message 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.
Range.overlap? (cyclomatic 16) monoruby/builtins/range.rb:408— Range.overlap? 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.
Struct.dig (cyclomatic 16) monoruby/builtins/struct.rb:138— Struct.dig 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.
BigMath.atan2 (cyclomatic 16) monoruby/gem/bigdecimal/math.rb:319— BigMath.atan2 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.
Gosu.button_down? (cyclomatic 16) monoruby/gem/gosu.rb:1915— Gosu.button_down? has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Packer.__write_value (cyclomatic 16) monoruby/gem/msgpack/msgpack.rb:567— Packer.__write_value has cyclomatic complexity 16 (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: Unpacker.__parse (cyclomatic 37) 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 method is counted neither in this dimension's figures nor in its score.
Strftime.__compile (cyclomatic 16) monoruby/gem/strptime/strptime.rb:340— Strftime.__compile has cyclomatic complexity 16 (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.
Strftime.__exec0 (cyclomatic 16) monoruby/gem/strptime/strptime.rb:378— Strftime.__exec0 has cyclomatic complexity 16 (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.
aobench-cpu.html.viewOverview (cyclomatic 16) docs/src/profiler/aobench-cpu.html:680— aobench-cpu.html.viewOverview 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.
optcarrot.html.viewOverview (cyclomatic 16) docs/src/profiler/optcarrot.html:680— optcarrot.html.viewOverview 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.
viewer.html.viewOverview (cyclomatic 16) monoruby/src/prof/viewer.html:680— viewer.html.viewOverview 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.
XxxComment REDACTED:457— # xxx: Is File.join is appropriate to add separator? — 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.
Socket.tcp_with_fast_fallback (cognitive 157) monoruby/stdlib/socket.rb:693— Socket.tcp_with_fast_fallback has cognitive complexity 157 (threshold 15). Drivers by points: if/else 50 (97 pts), ternaries 9 (29 pts), boolean chains 22, loops 3 (6 pts), error handling 1 (3 pts) (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.
Strptime.__exec0 (cognitive 145) monoruby/gem/strptime/strptime.rb:147— Strptime.__exec0 has cognitive complexity 145 (threshold 15). Drivers by points: if/else 49 (123 pts), boolean chains 12, loops 2 (4 pts), match/switch 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 78). 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.
Preprocess::unescape_nonascii (cognitive 122) monoruby/src/value/rvalue/regexp.rs:846— Preprocess::unescape_nonascii has cognitive complexity 122 (threshold 15). Drivers by points: if/else 25 (85 pts), match/switch 4 (14 pts), boolean chains 12, loops 4 (11 pts) (nesting depth added 77). 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.
BigDecimal.power (cognitive 101) monoruby/gem/bigdecimal.rb:97— BigDecimal.power has cognitive complexity 101 (threshold 15). Drivers by points: if/else 35 (60 pts), ternaries 7 (21 pts), boolean chains 16, loops 2 (4 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.
Range.__range_step_numeric (cognitive 95) monoruby/builtins/range.rb:758— Range.__range_step_numeric has cognitive complexity 95 (threshold 15). Drivers by points: if/else 25 (60 pts), loops 5 (19 pts), ternaries 2 (10 pts), boolean chains 6 (nesting depth added 57). 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.
Enumerable.minmax (cognitive 90) monoruby/builtins/enumerable.rb:843— Enumerable.minmax has cognitive complexity 90 (threshold 15). Drivers by points: if/else 36 (90 pts) (nesting depth added 54). 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.
Numeric.step (cognitive 89) monoruby/builtins/numeric.rb:191— Numeric.step has cognitive complexity 89 (threshold 15). Drivers by points: if/else 30 (51 pts), boolean chains 16, loops 4 (12 pts), ternaries 4 (10 pts) (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.
ArithmeticSequence.each (cognitive 57) monoruby/builtins/arithmetic_sequence.rb:107— ArithmeticSequence.each has cognitive complexity 57 (threshold 15). Drivers by points: if/else 18 (34 pts), loops 8 (22 pts), boolean chains 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.
Encoding::classify (cognitive 52) monoruby/src/value/rvalue/string.rs:2397— Encoding::classify has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (28 pts), match/switch 5 (12 pts), loops 5 (10 pts), boolean chains 2 (nesting depth added 25). 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.
Range.reverse_each (cognitive 48) monoruby/builtins/range.rb:76— Range.reverse_each has cognitive complexity 48 (threshold 15). Drivers by points: if/else 17 (30 pts), ternaries 3 (10 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 22). 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.
Range.__range_step_size (cognitive 46) monoruby/builtins/range.rb:948— Range.__range_step_size has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 8 (26 pts), if/else 12 (14 pts), boolean chains 6 (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.
Range.each (cognitive 45) monoruby/builtins/range.rb:4— Range.each has cognitive complexity 45 (threshold 15). Drivers by points: if/else 14 (29 pts), loops 3 (7 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1 (2 pts) (nesting depth added 22). 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.
Loop.__ev_run (cognitive 45) monoruby/gem/cool.io_ext.rb:130— Loop.__ev_run has cognitive complexity 45 (threshold 15). Drivers by points: if/else 26 (30 pts), boolean chains 11, error handling 1 (2 pts), ternaries 2 (nesting depth added 5). 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.
aobench-cpu.html.drawFlame (cognitive 45) docs/src/profiler/aobench-cpu.html:813— aobench-cpu.html.drawFlame has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 10, loops 3 (6 pts), ternaries 1 (nesting depth added 19). 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.
optcarrot.html.drawFlame (cognitive 45) docs/src/profiler/optcarrot.html:813— optcarrot.html.drawFlame has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 10, loops 3 (6 pts), ternaries 1 (nesting depth added 19). 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.
viewer.html.drawFlame (cognitive 45) monoruby/src/prof/viewer.html:813— viewer.html.drawFlame has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 10, loops 3 (6 pts), ternaries 1 (nesting depth added 19). 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.
Parser.__lex_number (cognitive 43) monoruby/gem/yajl/yajl.rb:390— Parser.__lex_number has cognitive complexity 43 (threshold 15). Drivers by points: if/else 21 (38 pts), boolean chains 3, loops 1 (2 pts) (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.
SlotAnalysis::new (cognitive 41) monoruby/src/codegen/jitgen/slot_analysis.rs:233— SlotAnalysis::new has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (23 pts), loops 6 (10 pts), match/switch 2 (5 pts), boolean chains 3 (nesting depth added 22). 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.
Array::get_elem1 (cognitive 40) monoruby/src/value/rvalue/array.rs:693— Array::get_elem1 has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (35 pts), match/switch 2 (5 pts) (nesting depth added 21). 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.
Integer.fdiv (cognitive 40) monoruby/builtins/integer.rb:119— Integer.fdiv has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 5 (19 pts), boolean chains 1 (nesting depth added 23). 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.
Parser.__do_parse (cognitive 40) monoruby/gem/yajl/yajl.rb:542— Parser.__do_parse has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (21 pts), match/switch 8 (15 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 18). 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.
Enumerable.cycle (cognitive 38) monoruby/builtins/enumerable.rb:1079— Enumerable.cycle has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 7 (21 pts), if/else 10 (17 pts) (nesting depth added 21). 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.
Parser.__decode_string (cognitive 38) monoruby/gem/yajl/yajl.rb:488— Parser.__decode_string has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 4, ternaries 1 (4 pts), match/switch 1 (3 pts), loops 1 (nesting depth added 20). 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.
Range.__range_step_generic (cognitive 37) monoruby/builtins/range.rb:901— Range.__range_step_generic has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 5 (14 pts), boolean chains 3 (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.
Open3.__drain (cognitive 37) REDACTED:120— Open3.__drain has cognitive complexity 37 (threshold 15). Drivers by points: if/else 5 (14 pts), error handling 4 (12 pts), boolean chains 6, ternaries 2 (4 pts), loops 1 (nesting depth added 19). 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.
aobench-cpu.html.viewFlame (cognitive 36) docs/src/profiler/aobench-cpu.html:880— aobench-cpu.html.viewFlame has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 6 (8 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 9). Most of this is not in the body itself: 11 of the 36 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 930, updateCrumbs, updateMatched::walk, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
optcarrot.html.viewFlame (cognitive 36) docs/src/profiler/optcarrot.html:880— optcarrot.html.viewFlame has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 6 (8 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 9). Most of this is not in the body itself: 11 of the 36 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 930, updateCrumbs, updateMatched::walk, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
viewer.html.viewFlame (cognitive 36) monoruby/src/prof/viewer.html:880— viewer.html.viewFlame has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 6 (8 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 9). Most of this is not in the body itself: 11 of the 36 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 930, updateCrumbs, updateMatched::walk, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SourceInfo::get_location (cognitive 35) monoruby/src/ast/source_info.rs:230— SourceInfo::get_location has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (25 pts), loops 3 (7 pts), match/switch 1 (2 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.
Parser.__lex_string (cognitive 35) monoruby/gem/yajl/yajl.rb:345— Parser.__lex_string has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 8, ternaries 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.
Enumerable.min (cognitive 34) monoruby/builtins/enumerable.rb:760— Enumerable.min has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (34 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. This shape REPEATS in the file: one other method here (Enumerable.max) 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.
Enumerable.max (cognitive 34) monoruby/builtins/enumerable.rb:799— Enumerable.max has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (34 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. This shape REPEATS in the file: one other method here (Enumerable.min) 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.
Range.step (cognitive 34) monoruby/builtins/range.rb:453— Range.step has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 16, if/else 10 (13 pts), ternaries 2 (5 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.
aobench-cpu.html.makeTable::draw (cognitive 33) docs/src/profiler/aobench-cpu.html:378— aobench-cpu.html.makeTable::draw has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 4 (17 pts), if/else 6 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 19). 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.
optcarrot.html.makeTable::draw (cognitive 33) docs/src/profiler/optcarrot.html:378— optcarrot.html.makeTable::draw has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 4 (17 pts), if/else 6 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 19). 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.
viewer.html.makeTable::draw (cognitive 33) monoruby/src/prof/viewer.html:378— viewer.html.makeTable::draw has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 4 (17 pts), if/else 6 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 19). 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.
Enumerable.minmax_by (cognitive 31) monoruby/builtins/enumerable.rb:992— Enumerable.minmax_by has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (31 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.
String.upto (cognitive 31) monoruby/builtins/string.rb:144— String.upto has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 11, ternaries 2 (4 pts), loops 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.
Range.max (cognitive 30) monoruby/builtins/range.rb:339— Range.max has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (2 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.
CharByteIter::next (cognitive 29) monoruby/src/value/rvalue/string.rs:371— CharByteIter::next has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (20 pts), match/switch 4 (7 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IO.__class_write (cognitive 29) monoruby/builtins/io.rb:198— IO.__class_write has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 2 (6 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.
Range.overlap? (cognitive 29) monoruby/builtins/range.rb:408— Range.overlap? has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (27 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.
LUSolve.ludecomp (cognitive 29) monoruby/gem/bigdecimal/ludcmp.rb:13— LUSolve.ludecomp has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 6 (12 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.
Encoder.__escape (cognitive 29) monoruby/gem/yajl/yajl.rb:907— Encoder.__escape has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (25 pts), match/switch 1 (2 pts), boolean chains 1, 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.
Range.size (cognitive 28) monoruby/builtins/range.rb:1037— Range.size has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 2 (7 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.
Packer.__write_integer_value (cognitive 28) monoruby/gem/msgpack/msgpack.rb:598— Packer.__write_integer_value has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 3 (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.
Range.__cover_range_q (cognitive 27) monoruby/builtins/range.rb:697— Range.__cover_range_q has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 7, ternaries 1 (2 pts), error handling 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.
Window._pump_events (cognitive 27) monoruby/gem/gosu.rb:661— Window._pump_events has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (22 pts), boolean chains 2, match/switch 1 (2 pts), loops 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.
Socket.udp_server_sockets (cognitive 27) monoruby/stdlib/socket.rb:1349— Socket.udp_server_sockets has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 5, error handling 1 (2 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.
StringScanner.[] (cognitive 27) monoruby/stdlib/strscan.rb:272— StringScanner.[] has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Array.bsearch_index (cognitive 26) monoruby/builtins/array.rb:329— Array.bsearch_index has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 2 (3 pts), boolean chains 2, match/switch 1 (2 pts), 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.
Array.permutation (cognitive 26) monoruby/builtins/array.rb:374— Array.permutation has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (19 pts), ternaries 3 (5 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Exception.full_message (cognitive 26) monoruby/builtins/exception.rb:111— Exception.full_message has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 2 (5 pts), boolean chains 3 (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.
Hash.transform_keys (cognitive 26) monoruby/builtins/hash.rb:168— Hash.transform_keys has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (6 pts), ternaries 1 (4 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.
aobench-cpu.html.drawTimeline (cognitive 26) docs/src/profiler/aobench-cpu.html:517— aobench-cpu.html.drawTimeline has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 5 (7 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
optcarrot.html.drawTimeline (cognitive 26) docs/src/profiler/optcarrot.html:517— optcarrot.html.drawTimeline has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 5 (7 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
viewer.html.drawTimeline (cognitive 26) monoruby/src/prof/viewer.html:517— viewer.html.drawTimeline has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 5 (7 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LinkMode::from_caller_inner (cognitive 25) monoruby/src/codegen/jitgen/state/slot.rs:2943— LinkMode::from_caller_inner has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 7, match/switch 3 (5 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.
JitModule::gen_chain_replay_stub (cognitive 25) monoruby/src/codegen/jitgen.rs:2005— JitModule::gen_chain_replay_stub has cognitive complexity 25 (threshold 15). Drivers by points: loops 8 (12 pts), match/switch 4 (11 pts), if/else 1 (2 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Array.initialize (cognitive 25) monoruby/builtins/array.rb:43— Array.initialize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 2, 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.
Enumerable.inject (cognitive 25) monoruby/builtins/enumerable.rb:40— Enumerable.inject has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (24 pts), match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Pathname.plus (cognitive 25) REDACTED:671— Pathname.plus has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 4 (6 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 7). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
BigMath.atan2 (cognitive 25) monoruby/gem/bigdecimal/math.rb:319— BigMath.atan2 has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 8 (17 pts), if/else 6, boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aobench-cpu.html.initTimeline (cognitive 25) docs/src/profiler/aobench-cpu.html:613— aobench-cpu.html.initTimeline has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 4, loops 3, ternaries 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 638, 657, 647, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
aobench-cpu.html.relatives (cognitive 25) docs/src/profiler/aobench-cpu.html:969— aobench-cpu.html.relatives has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 4 (10 pts), boolean chains 3, loops 1 (nesting depth added 11). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 972). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
optcarrot.html.initTimeline (cognitive 25) docs/src/profiler/optcarrot.html:613— optcarrot.html.initTimeline has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 4, loops 3, ternaries 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 638, 657, 647, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
optcarrot.html.relatives (cognitive 25) docs/src/profiler/optcarrot.html:969— optcarrot.html.relatives has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 4 (10 pts), boolean chains 3, loops 1 (nesting depth added 11). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 972). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
viewer.html.initTimeline (cognitive 25) monoruby/src/prof/viewer.html:613— viewer.html.initTimeline has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 4, loops 3, ternaries 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 638, 657, 647, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
viewer.html.relatives (cognitive 25) monoruby/src/prof/viewer.html:969— viewer.html.relatives has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 4 (10 pts), boolean chains 3, loops 1 (nesting depth added 11). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 972). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Array.bsearch (cognitive 24) monoruby/builtins/array.rb:169— Array.bsearch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 2, match/switch 1 (2 pts), loops 1, ternaries 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.
Kernel.warn (cognitive 24) monoruby/builtins/kernel.rb:153— Kernel.warn has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (16 pts), error handling 2 (3 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XPathVisitor.visit_function (cognitive 24) monoruby/gem/nokogiri/css/xpath_visitor.rb:103— XPathVisitor.visit_function has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, ternaries 1 (3 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.
Encoder.__encode_part (cognitive 24) monoruby/gem/yajl/yajl.rb:796— Encoder.__encode_part has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Stacks::json (cognitive 23) monoruby/src/prof.rs:1808— Stacks::json has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 4 (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.
ArrayInner::set_index2 (cognitive 23) monoruby/src/value/rvalue/array.rs:567— ArrayInner::set_index2 has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 2, 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.
Enumerable.one? (cognitive 23) monoruby/builtins/enumerable.rb:325— Enumerable.one? has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (23 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.
Comparable.clamp (cognitive 22) monoruby/builtins/comparable.rb:54— Comparable.clamp has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (20 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.
Range.__range_step_succ (cognitive 22) monoruby/builtins/range.rb:863— Range.__range_step_succ has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 4 (7 pts), loops 1 (2 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.
Struct.dig (cognitive 22) monoruby/builtins/struct.rb:138— Struct.dig has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5, ternaries 2 (4 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.
aobench-cpu.html.viewMethods (cognitive 22) docs/src/profiler/aobench-cpu.html:995— aobench-cpu.html.viewMethods has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 6, boolean chains 3 (nesting depth added 3). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (drawDetail, a function literal at line 1034, a function literal at line 1007, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
optcarrot.html.viewMethods (cognitive 22) docs/src/profiler/optcarrot.html:995— optcarrot.html.viewMethods has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 6, boolean chains 3 (nesting depth added 3). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (drawDetail, a function literal at line 1034, a function literal at line 1007, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
viewer.html.viewMethods (cognitive 22) monoruby/src/prof/viewer.html:995— viewer.html.viewMethods has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 6, boolean chains 3 (nesting depth added 3). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (drawDetail, a function literal at line 1034, a function literal at line 1007, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Hash.to_h (cognitive 21) monoruby/builtins/hash.rb:94— Hash.to_h has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Ractor.__shareable? (cognitive 21) monoruby/builtins/ractor.rb:203— Ractor.__shareable? has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 8, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Struct.values_at (cognitive 21) monoruby/builtins/struct.rb:108— Struct.values_at has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 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.
Encoder.initialize (cognitive 21) monoruby/gem/yajl/yajl.rb:732— Encoder.initialize has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (21 pts) (nesting depth added 12). 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.
aobench-cpu.html.el (cognitive 21) docs/src/profiler/aobench-cpu.html:174— aobench-cpu.html.el has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (4 pts), loops 2 (3 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.
optcarrot.html.el (cognitive 21) docs/src/profiler/optcarrot.html:174— optcarrot.html.el has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (4 pts), loops 2 (3 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.
viewer.html.el (cognitive 21) monoruby/src/prof/viewer.html:174— viewer.html.el has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (4 pts), loops 2 (3 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.
HashRef::debug (cognitive 20) monoruby/src/value/rvalue/hash.rs:1183— HashRef::debug has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 8). 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.
Array.rindex (cognitive 20) monoruby/builtins/array.rb:498— Array.rindex has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (4 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.
Numeric.__step_size (cognitive 20) monoruby/builtins/numeric.rb:358— Numeric.__step_size has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 6, boolean chains 4 (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.
Range.include? (cognitive 20) monoruby/builtins/range.rb:241— Range.include? has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 8 (10 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
XPathVisitor.visit_element_name (cognitive 20) monoruby/gem/nokogiri/css/xpath_visitor.rb:260— XPathVisitor.visit_element_name has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aobench-cpu.html.viewOverview (cognitive 20) docs/src/profiler/aobench-cpu.html:680— aobench-cpu.html.viewOverview has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
optcarrot.html.viewOverview (cognitive 20) docs/src/profiler/optcarrot.html:680— optcarrot.html.viewOverview has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
viewer.html.viewOverview (cognitive 20) monoruby/src/prof/viewer.html:680— viewer.html.viewOverview has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Array.cycle (cognitive 19) monoruby/builtins/array.rb:246— Array.cycle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (5 pts), loops 1 (2 pts), boolean chains 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.
Factory.register_type_internal (cognitive 19) monoruby/gem/msgpack/msgpack.rb:1155— Factory.register_type_internal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aobench-cpu.html.flameAt (cognitive 19) docs/src/profiler/aobench-cpu.html:866— aobench-cpu.html.flameAt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 2 (4 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.
optcarrot.html.flameAt (cognitive 19) docs/src/profiler/optcarrot.html:866— optcarrot.html.flameAt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 2 (4 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.
viewer.html.flameAt (cognitive 19) monoruby/src/prof/viewer.html:866— viewer.html.flameAt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 2 (4 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.
RawTableInner::rehash_in_place (cognitive 18) hashbrown/src/raw/mod.rs:2661— RawTableInner::rehash_in_place has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (5 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.
CallSiteInfo::format_args (cognitive 18) monoruby/src/globals/store.rs:3658— CallSiteInfo::format_args has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (3 pts), match/switch 1 (2 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.
HashRefMut::insert (cognitive 18) monoruby/src/value/rvalue/hash.rs:1442— HashRefMut::insert has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 2 (4 pts), boolean chains 3 (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.
Array.combination (cognitive 18) monoruby/builtins/array.rb:283— Array.combination has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 1 (2 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.
Range.__bsearch_int (cognitive 18) monoruby/builtins/range.rb:544— Range.__bsearch_int has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JSON.load (cognitive 18) monoruby/gem/json/common.rb:854— JSON.load has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5 (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, 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.
Document.parse (cognitive 18) monoruby/gem/nokogiri/html4/document.rb:189— Document.parse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 1 (3 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VersionInfo.to_hash (cognitive 18) monoruby/gem/nokogiri/version/info.rb:96— VersionInfo.to_hash has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (18 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.
Parser.__lex_comment (cognitive 18) monoruby/gem/yajl/yajl.rb:456— Parser.__lex_comment has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (18 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.
Socket.tcp_without_fast_fallback (cognitive 18) monoruby/stdlib/socket.rb:947— Socket.tcp_without_fast_fallback has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 3 (4 pts), boolean chains 2, error handling 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, 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.
EncBuf::append (cognitive 17) monoruby/src/value/rvalue/string.rs:2936— EncBuf::append has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3 (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.
Array.repeated_combination (cognitive 17) monoruby/builtins/array.rb:603— Array.repeated_combination has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 1 (2 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.
Array.values_at (cognitive 17) monoruby/builtins/array.rb:654— Array.values_at has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (4 pts), loops 1 (2 pts), boolean chains 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.
Enumerable.chunk (cognitive 17) monoruby/builtins/enumerable.rb:426— Enumerable.chunk has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Range.__cover_val_q (cognitive 17) monoruby/builtins/range.rb:676— Range.__cover_val_q has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (17 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.
BigMath.atan (cognitive 17) monoruby/gem/bigdecimal/math.rb:281— BigMath.atan has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 2 (4 pts), boolean chains 1, 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.
BigMath.lgamma (cognitive 17) monoruby/gem/bigdecimal/math.rb:757— BigMath.lgamma has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Addrinfo.connect_internal (cognitive 17) monoruby/stdlib/socket.rb:54— Addrinfo.connect_internal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 1 (3 pts), loops 1 (2 pts), boolean chains 1, error handling 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.
BasicSocket.connect_address (cognitive 17) monoruby/stdlib/socket.rb:262— BasicSocket.connect_address has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (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.
aobench-cpu.html.methodStats (cognitive 17) docs/src/profiler/aobench-cpu.html:448— aobench-cpu.html.methodStats has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (5 pts), boolean chains 3, loops 2 (nesting depth added 4). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aobench-cpu.html.viewJit (cognitive 17) docs/src/profiler/aobench-cpu.html:1093— aobench-cpu.html.viewJit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 5, boolean chains 4, loops 1 (nesting depth added 2). Of this number, 10 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
optcarrot.html.methodStats (cognitive 17) docs/src/profiler/optcarrot.html:448— optcarrot.html.methodStats has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (5 pts), boolean chains 3, loops 2 (nesting depth added 4). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
optcarrot.html.viewJit (cognitive 17) docs/src/profiler/optcarrot.html:1093— optcarrot.html.viewJit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 5, boolean chains 4, loops 1 (nesting depth added 2). Of this number, 10 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
viewer.html.methodStats (cognitive 17) monoruby/src/prof/viewer.html:448— viewer.html.methodStats has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (5 pts), boolean chains 3, loops 2 (nesting depth added 4). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
viewer.html.viewJit (cognitive 17) monoruby/src/prof/viewer.html:1093— viewer.html.viewJit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 5, boolean chains 4, loops 1 (nesting depth added 2). Of this number, 10 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
AsmIr::push (cognitive 16) monoruby/src/codegen/jitgen/asmir.rs:622— AsmIr::push has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (2 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.
Enumerable.min_by (cognitive 16) monoruby/builtins/enumerable.rb:359— Enumerable.min_by has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 1 (2 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. This shape REPEATS in the file: one other method here (Enumerable.max_by) 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.
Enumerable.max_by (cognitive 16) monoruby/builtins/enumerable.rb:578— Enumerable.max_by has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 1 (2 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. This shape REPEATS in the file: one other method here (Enumerable.min_by) 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.
Pathname.cleanpath_conservative (cognitive 16) REDACTED:474— Pathname.cleanpath_conservative has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 4). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Range.reject (cognitive 16) monoruby/builtins/range.rb:166— Range.reject has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 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.
Backtrace.__slice (cognitive 16) monoruby/builtins/thread.rb:1029— Backtrace.__slice has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 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.
Function.initialize (cognitive 16) monoruby/gem/ffi_c.rb:704— Function.initialize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (5 pts), error handling 1 (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.
XPathVisitor.nth (cognitive 16) monoruby/gem/nokogiri/css/xpath_visitor.rb:346— XPathVisitor.nth has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (6 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Near-duplicate member family (4 members, 16 shared lines) · ×1
Near-duplicate member family (4 members, 16 shared lines) monoruby/src/builtins/set.rs:759— monoruby/src/builtins/set.rs:759-776 | monoruby/src/builtins/set.rs:786-803 | monoruby/src/builtins/set.rs:818-835 | monoruby/src/builtins/set.rs:850-867 — These 4 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 17 shared lines) · ×1
Near-duplicate member family (3 members, 17 shared lines) monoruby/src/builtins/fiber.rs:464— monoruby/src/builtins/fiber.rs:464-524 | monoruby/src/builtins/kernel.rs:989-1031 | monoruby/src/builtins/thread.rs:311-352 — These 3 members are variants of one another: a block of 17 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 (85 shared lines) monoruby/src/codegen/arch/aarch64/compile/mod.rs:291— monoruby/src/codegen/arch/aarch64/compile/mod.rs:291-596 | monoruby/src/codegen/jitgen/asmir.rs:4445-4685 — These two members are variants of one another: 85 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 (41 shared lines) monoruby/src/builtins/kernel.rs:5870— monoruby/src/builtins/kernel.rs:5870-5943 | monoruby/src/builtins/module.rs:1920-2063 — These two members are variants of one another: 41 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 (35 shared lines) monoruby/src/builtins/io.rs:2831— monoruby/src/builtins/io.rs:2831-2889 | monoruby/src/builtins/io.rs:2995-3083 — These two members are variants of one another: 35 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 (32 shared lines) monoruby/src/builtins/file.rs:2491— monoruby/src/builtins/file.rs:2491-2530 | monoruby/src/builtins/file.rs:2562-2608 — These two members are variants of one another: 32 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 (29 shared lines) REDACTED:580— REDACTED:580-638 | REDACTED:667-732 — These two members are variants of one another: 29 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 (27 shared lines) monoruby/src/builtins/string.rs:10856— monoruby/src/builtins/string.rs:10856-10904 | monoruby/src/builtins/string.rs:10953-11001 — These two members are variants of one another: 27 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 (25 shared lines) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:545— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:545-589 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:601-640 — These two members are variants of one another: 25 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 (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) monoruby/src/codegen/arch/aarch64/codegen.rs:105— monoruby/src/codegen/arch/aarch64/codegen.rs:105-153 | monoruby/src/codegen/arch/aarch64/codegen.rs:158-208 | monoruby/src/codegen/arch/aarch64/codegen.rs:217-272 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1638-1681 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1694-1728 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1740-1768 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1770-1799 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2784-2861 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Edited copy of a member (87 corresponding lines) · ×1
Edited copy of a member (87 corresponding lines) monoruby/src/value/rvalue/regexp.rs:3873— monoruby/src/value/rvalue/regexp.rs:3873-3989 | monoruby/src/value/rvalue/regexp.rs:4001-4087 — These two members are one piece of code written twice and then edited apart: 87 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (88 corresponding lines) · ×1
Edited copy of a member (88 corresponding lines) monoruby/src/value/rvalue/string.rs:874— monoruby/src/value/rvalue/string.rs:874-961 | monoruby/src/value/rvalue/string.rs:1056-1160 — These two members are one piece of code written twice and then edited apart: 88 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 (94 corresponding lines) · ×1
Edited copy of a member (94 corresponding lines) monoruby/src/parser/prism_backend.rs:4815— monoruby/src/parser/prism_backend.rs:4815-4908 | monoruby/src/parser/prism_backend.rs:4910-5012 — These two members are one piece of code written twice and then edited apart: 94 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 (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) monoruby/src/value/rvalue/regexp.rs:3249— monoruby/src/value/rvalue/regexp.rs:3249-3321 | monoruby/src/value/rvalue/regexp.rs:3545-3598 — These two members are one piece of code written twice and then edited apart: 54 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) monoruby/src/builtins/io.rs:5140— monoruby/src/builtins/io.rs:5140-5188 | monoruby/src/builtins/io.rs:5206-5250 — 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 (4 members, 29+ corresponding lines) · ×1
Edited copies of one member (4 members, 29+ corresponding lines) rubymap/src/map/core.rs:467— rubymap/src/map/core.rs:467-495 | rubymap/src/map/core.rs:506-535 | rubymap/src/map/core.rs:550-580 | rubymap/src/map/core.rs:623-653 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 29 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) monoruby/src/builtins/hash.rs:760— monoruby/src/builtins/hash.rs:760-800 | monoruby/src/builtins/hash.rs:811-858 — 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 (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) monoruby/src/builtins/module.rs:1531— monoruby/src/builtins/module.rs:1531-1575 | monoruby/src/builtins/module.rs:1588-1631 — These two members are one piece of code written twice and then edited apart: 44 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 (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) monoruby/src/codegen/jitgen/context.rs:1391— monoruby/src/codegen/jitgen/context.rs:1391-1432 | monoruby/src/codegen/jitgen/context.rs:1460-1513 — These two members are one piece of code written twice and then edited apart: 42 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, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) ext/nokogiri/src/document.rs:92— ext/nokogiri/src/document.rs:92-121 | ext/nokogiri/src/document.rs:124-157 | ext/nokogiri/src/document.rs:213-237 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) monoruby/src/builtins/string.rs:9212— monoruby/src/builtins/string.rs:9212-9248 | monoruby/src/builtins/string.rs:9250-9287 — 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 copies of one member (4 members, 25+ corresponding lines) · ×1
Edited copies of one member (4 members, 25+ corresponding lines) monoruby/src/builtins/numeric/rational.rs:216— monoruby/src/builtins/numeric/rational.rs:216-240 | monoruby/src/builtins/numeric/rational.rs:243-267 | monoruby/src/builtins/numeric/rational.rs:270-294 | monoruby/src/builtins/numeric/rational.rs:297-321 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 25 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, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) monoruby/src/builtins/array.rs:1125— monoruby/src/builtins/array.rs:1125-1151 | monoruby/src/builtins/array.rs:1180-1213 | monoruby/src/builtins/hash.rs:1106-1128 — 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, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) ext/nokogiri/src/schema.rs:267— ext/nokogiri/src/schema.rs:267-287 | ext/nokogiri/src/schema.rs:290-310 | ext/nokogiri/src/schema.rs:318-338 — 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 copies of one member (4 members, 19+ corresponding lines) · ×1
Edited copies of one member (4 members, 19+ corresponding lines) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3360— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3360-3380 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3389-3408 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4098-4118 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4126-4144 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 23+ corresponding lines) · ×1
Edited copies of one member (4 members, 23+ corresponding lines) monoruby/src/codegen/arch/x86_64/invoker.rs:322— monoruby/src/codegen/arch/x86_64/invoker.rs:322-345 | monoruby/src/codegen/arch/x86_64/invoker.rs:354-377 | monoruby/src/codegen/arch/x86_64/invoker.rs:381-403 | monoruby/src/codegen/arch/x86_64/invoker.rs:435-457 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) monoruby/src/value/rvalue/thread.rs:231— monoruby/src/value/rvalue/thread.rs:231-259 | monoruby/src/value/rvalue/thread.rs:272-300 | monoruby/src/value/rvalue/thread.rs:305-333 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 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, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) monoruby/src/builtins/range.rs:192— monoruby/src/builtins/range.rs:192-209 | monoruby/src/builtins/range.rs:230-247 | monoruby/src/builtins/range.rs:360-377 | monoruby/src/builtins/string.rs:7384-7404 — These 4 members are one piece of code written 4 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 4 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) ext/nokogiri/src/sax.rs:673— ext/nokogiri/src/sax.rs:673-687 | ext/nokogiri/src/sax.rs:705-722 | ext/nokogiri/src/sax.rs:725-741 | ext/nokogiri/src/sax.rs:744-758 — 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 copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) monoruby/src/builtins/json.rs:241— monoruby/src/builtins/json.rs:241-262 | monoruby/src/builtins/string.rs:2037-2062 | monoruby/src/builtins/string.rs:6382-6403 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1398— monoruby/src/codegen/arch/aarch64/compile/mod.rs:1398-1420 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:1431-1447 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4333-4354 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4361-4377 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 9+ corresponding lines) · ×1
Edited copies of one member (5 members, 9+ corresponding lines) monoruby/src/builtins/match_data.rs:341— monoruby/src/builtins/match_data.rs:341-349 | monoruby/src/builtins/match_data.rs:360-368 | monoruby/src/builtins/match_data.rs:379-390 | monoruby/src/builtins/match_data.rs:938-949 | monoruby/src/builtins/match_data.rs:960-971 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 12+ corresponding lines) · ×1
Edited copies of one member (5 members, 12+ corresponding lines) monoruby/src/builtins/arithmetic_sequence.rs:210— monoruby/src/builtins/arithmetic_sequence.rs:210-221 | monoruby/src/builtins/arithmetic_sequence.rs:233-246 | monoruby/src/builtins/array.rs:403-415 | monoruby/src/builtins/hash.rs:1767-1782 | monoruby/src/builtins/hash.rs:1798-1811 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) monoruby/src/codegen/arch/x86_64/compile/mod.rs:1796— monoruby/src/codegen/arch/x86_64/compile/mod.rs:1796-1809 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2413-2424 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2438-2449 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:2477-2488 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) monoruby/src/builtins/math.rs:164— monoruby/src/builtins/math.rs:164-173 | monoruby/src/builtins/math.rs:330-339 | monoruby/src/builtins/math.rs:346-355 | monoruby/src/builtins/math.rs:424-434 | monoruby/src/builtins/math.rs:690-699 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) monoruby/src/globals/store/class.rs:1639— monoruby/src/globals/store/class.rs:1639-1651 | monoruby/src/globals/store/class.rs:1658-1670 | monoruby/src/globals/store/class.rs:1963-1975 | monoruby/src/globals/store/class.rs:2058-2073 — These 4 members are one piece of code written 4 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 4 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) monoruby/src/bytecodegen.rs:1060— monoruby/src/bytecodegen.rs:1060-1069 | monoruby/src/bytecodegen.rs:1078-1091 | monoruby/src/bytecodegen.rs:1093-1101 | monoruby/src/bytecodegen.rs:1103-1111 — 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, 11+ corresponding lines) · ×1
Edited copies of one member (5 members, 11+ corresponding lines) monoruby/src/codegen/arch/x86_64/compile/variables.rs:445— monoruby/src/codegen/arch/x86_64/compile/variables.rs:445-455 | monoruby/src/codegen/arch/x86_64/compile/variables.rs:457-467 | monoruby/src/codegen/arch/x86_64/compile/variables.rs:469-480 | monoruby/src/codegen/arch/x86_64/compile/variables.rs:482-492 | monoruby/src/codegen/arch/x86_64/compile/variables.rs:494-505 — These 5 members are one piece of code written 5 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 5 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) hashbrown/src/control/group/generic.rs:91— hashbrown/src/control/group/generic.rs:91-94 | hashbrown/src/control/group/neon.rs:62-65 | hashbrown/src/control/group/sse2.rs:68-71 — 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 copies of one member (4 members, 4+ corresponding lines) · ×1
Edited copies of one member (4 members, 4+ corresponding lines) hashbrown/src/control/group/generic.rs:82— hashbrown/src/control/group/generic.rs:82-85 | hashbrown/src/control/group/lsx.rs:57-60 | hashbrown/src/control/group/neon.rs:53-56 | hashbrown/src/control/group/sse2.rs:59-62 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) monoruby/src/builtins/kernel.rs:6422— monoruby/src/builtins/kernel.rs:6422-6424 | monoruby/src/builtins/object.rs:396-398 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) ext/nokogiri/src/dtd.rs:377— ext/nokogiri/src/dtd.rs:377-381 | ext/nokogiri/src/misc.rs:157-161 | ext/nokogiri/src/node.rs:538-542 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 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 (117 lines × 2) monoruby/src/value/rvalue.rs:1868— monoruby/src/value/rvalue.rs:1868-1984 | monoruby/src/value/rvalue.rs:1991-2107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue.rs:1868` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26–42 lines × 2) monoruby/src/builtins/kernel.rs:5918— monoruby/src/builtins/kernel.rs:5918-5943 | monoruby/src/builtins/module.rs:2022-2063 — before extracting anything, compare `monoruby/src/builtins/kernel.rs` and `monoruby/src/builtins/module.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `monoruby/src/builtins/kernel.rs:5918` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27–36 lines × 2) monoruby/src/codegen/jitgen.rs:2581— monoruby/src/codegen/jitgen.rs:2581-2607 | monoruby/src/codegen/jitgen.rs:2688-2723 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen.rs:2581` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (23–33 lines × 2) monoruby/src/codegen/jitgen/compile/frameless_call.rs:705— monoruby/src/codegen/jitgen/compile/frameless_call.rs:705-737 | monoruby/src/codegen/jitgen/compile/frameless_call.rs:889-911 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/jitgen/compile/frameless_call.rs:705` 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 (32 lines × 2) monoruby/src/builtins/struct_class.rs:670— monoruby/src/builtins/struct_class.rs:670-701 | monoruby/src/builtins/struct_class.rs:735-766 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/struct_class.rs:670` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/string.rs:9214— monoruby/src/builtins/string.rs:9214-9244 | monoruby/src/builtins/string.rs:9252-9282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:9214` it does not close everything it opens, so those exact lines 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–28 lines × 2) monoruby/src/builtins/string.rs:6052— monoruby/src/builtins/string.rs:6052-6079 | monoruby/src/builtins/string.rs:6323-6346 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:6052` it does not close everything it opens, so those exact lines 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–28 lines × 2) monoruby/src/bytecodegen.rs:1147— monoruby/src/bytecodegen.rs:1147-1172 | monoruby/src/bytecodegen.rs:1542-1569 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/bytecodegen.rs:1147` 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 (22–27 lines × 2) monoruby/src/parser/prism_backend.rs:4853— monoruby/src/parser/prism_backend.rs:4853-4874 | monoruby/src/parser/prism_backend.rs:4934-4960 — both copies are in the same file, so extract the 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 (25–26 lines × 2) hashbrown/src/raw/mod.rs:1509— hashbrown/src/raw/mod.rs:1509-1533 | hashbrown/src/raw/mod.rs:1719-1744 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `hashbrown/src/raw/mod.rs:1509` it does not close everything it opens, so those exact lines 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–26 lines × 2) monoruby/src/builtins/encoding.rs:462— monoruby/src/builtins/encoding.rs:462-485 | monoruby/src/builtins/encoding.rs:487-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. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/encoding.rs:487` it does not close everything it opens, so those 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, `monoruby/src/builtins/encoding.rs:486` calls `define_builtin_func`, `id` and `monoruby/src/builtins/encoding.rs:512` 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 (23–26 lines × 2) monoruby/src/builtins/string.rs:2329— monoruby/src/builtins/string.rs:2329-2354 | monoruby/src/builtins/string.rs:2372-2394 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/string.rs:2329` 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–26 lines × 2) monoruby/src/bytecodegen/expression.rs:1141— monoruby/src/bytecodegen/expression.rs:1141-1153 | monoruby/src/bytecodegen/expression.rs:1154-1179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/bytecodegen/expression.rs:1141` 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–26 lines × 2) monoruby/src/parser/prism_backend.rs:2493— monoruby/src/parser/prism_backend.rs:2493-2518 | monoruby/src/parser/prism_backend.rs:2528-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 `monoruby/src/parser/prism_backend.rs:2493` it does not close everything it opens, so those 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 `node` to `&WhileNode<'pr>` in one and `&UntilNode<'pr>` 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–25 lines × 3) monoruby/src/builtins/kernel.rs:4782— monoruby/src/builtins/kernel.rs:4782-4796 | monoruby/src/builtins/kernel.rs:4801-4820 | monoruby/src/builtins/kernel.rs:4825-4849 — 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 (24 lines × 3) monoruby/src/codegen/arch/aarch64/compile/mod.rs:639— monoruby/src/codegen/arch/aarch64/compile/mod.rs:639-662 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:759-782 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2550-2573 — 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 (21–24 lines × 2) monoruby/src/builtins/hash.rs:761— monoruby/src/builtins/hash.rs:761-784 | monoruby/src/builtins/hash.rs:812-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 2) monoruby/src/builtins/io.rs:1675— monoruby/src/builtins/io.rs:1675-1699 | monoruby/src/builtins/io.rs:2939-2963 — both copies are in the same file, so extract the 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–23 lines × 2) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:711— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:711-730 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:837-859 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:711` it does not close everything it opens, so those exact lines 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) monoruby/src/executor/format.rs:1097— monoruby/src/executor/format.rs:1097-1119 | monoruby/src/executor/format.rs:1200-1222 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/executor/format.rs:1097` 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 (21–22 lines × 2) monoruby/src/builtins/module.rs:1022— monoruby/src/builtins/module.rs:1022-1043 | monoruby/src/builtins/object.rs:649-669 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `globals` to `&Globals` in one and `&mut Globals` 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–22 lines × 2) monoruby/src/value/rvalue/string/transcode.rs:7216— monoruby/src/value/rvalue/string/transcode.rs:7216-7234 | monoruby/src/value/rvalue/string/transcode.rs:7354-7375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value/rvalue/string/transcode.rs:7216` 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 × 3) monoruby/src/builtins/numeric/float.rs:833— monoruby/src/builtins/numeric/float.rs:833-852 | monoruby/src/builtins/numeric/float.rs:870-889 | monoruby/src/builtins/numeric/float.rs:907-926 — 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 `monoruby/src/builtins/numeric/float.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.
Duplicated block (14–20 lines × 2) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1401— monoruby/src/codegen/arch/aarch64/compile/mod.rs:1401-1420 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:1434-1447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:1401` 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–21 lines × 3) monoruby/src/parser/prism_backend.rs:1678— monoruby/src/parser/prism_backend.rs:1678-1695 | monoruby/src/parser/prism_backend.rs:1746-1763 | monoruby/src/parser/prism_backend.rs:5333-5353 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `monoruby/src/parser/prism_backend.rs:1696` calls `default` and `monoruby/src/parser/prism_backend.rs:1764` 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 (10–19 lines × 2) monoruby/src/builtins/kernel.rs:1362— monoruby/src/builtins/kernel.rs:1362-1371 | monoruby/src/builtins/kernel.rs:1618-1636 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/kernel.rs:1362` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (43–50 lines × 2) monoruby/src/builtins/time.rs:1336— monoruby/src/builtins/time.rs:1336-1378 | monoruby/src/builtins/time.rs:2685-2734 — both copies are in the same file, so extract the 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–19 lines × 2) monoruby/src/bytecodegen/encode.rs:408— monoruby/src/bytecodegen/encode.rs:408-426 | monoruby/src/bytecodegen/encode.rs:433-446 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/bytecodegen/encode.rs:408` 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 (15–18 lines × 2) monoruby/src/builtins/io.rs:3494— monoruby/src/builtins/io.rs:3494-3511 | monoruby/src/builtins/kernel.rs:3677-3691 — 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 `monoruby/src/builtins/io.rs:3494` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) REDACTED:1290— REDACTED:1290-1306 | monoruby/src/executor/op.rs:1937-1954 — 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 `REDACTED:1290` 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–18 lines × 2) monoruby/src/parser/prism_backend.rs:4841— monoruby/src/parser/prism_backend.rs:4841-4852 | monoruby/src/parser/prism_backend.rs:4961-4978 — both copies are in the same file, so extract the 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 × 3) monoruby/src/builtins/fiber.rs:468— monoruby/src/builtins/fiber.rs:468-484 | monoruby/src/builtins/kernel.rs:996-1012 | monoruby/src/builtins/thread.rs:317-333 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (12–17 lines × 2) monoruby/src/parser/prism_backend.rs:5107— monoruby/src/parser/prism_backend.rs:5107-5123 | monoruby/src/parser/prism_backend.rs:5199-5210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/parser/prism_backend.rs:5107` 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 × 4) monoruby/src/builtins/numeric/float.rs:837— monoruby/src/builtins/numeric/float.rs:837-852 | monoruby/src/builtins/numeric/float.rs:874-889 | monoruby/src/builtins/numeric/float.rs:911-926 | monoruby/src/builtins/numeric/float.rs:971-986 — 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 `monoruby/src/builtins/numeric/float.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.
Duplicated block (13–16 lines × 3) monoruby/src/builtins/set.rs:592— monoruby/src/builtins/set.rs:592-607 | monoruby/src/builtins/set.rs:651-664 | monoruby/src/builtins/set.rs:686-698 — 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 `monoruby/src/builtins/set.rs:592` it does not close everything it opens, so those exact lines 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–16 lines × 2) monoruby/src/codegen/jitgen/state/binop.rs:612— monoruby/src/codegen/jitgen/state/binop.rs:612-621 | monoruby/src/codegen/jitgen/state/binop.rs:637-652 — both copies are in the same file, so extract the 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–16 lines × 2) monoruby/src/value/rvalue/string.rs:6001— monoruby/src/value/rvalue/string.rs:6001-6016 | monoruby/src/value/rvalue/string/transcode.rs:5281-5295 — before extracting anything, compare `monoruby/src/value/rvalue/string.rs` and `monoruby/src/value/rvalue/string/transcode.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 `monoruby/src/value/rvalue/string.rs:6001` it does not close everything it opens, so those exact lines 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) monoruby/src/builtins/array.rs:3182— monoruby/src/builtins/array.rs:3182-3196 | monoruby/src/builtins/array.rs:3290-3302 — both copies are in the same file, so extract the 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–14 lines × 4) monoruby/src/value/rvalue/string/transcode.rs:5822— monoruby/src/value/rvalue/string/transcode.rs:5822-5834 | monoruby/src/value/rvalue/string/transcode.rs:5991-6004 | monoruby/src/value/rvalue/string/transcode.rs:6067-6079 | monoruby/src/value/rvalue/string/transcode.rs:6957-6969 — 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 `monoruby/src/value/rvalue/string/transcode.rs:5822` 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, `monoruby/src/value/rvalue/string/transcode.rs:5835` calls `len_utf8` and `monoruby/src/value/rvalue/string/transcode.rs:6080` 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–14 lines × 3) monoruby/src/builtins/module.rs:1532— monoruby/src/builtins/module.rs:1532-1545 | monoruby/src/builtins/module.rs:1589-1597 | monoruby/src/builtins/module.rs:1774-1782 — 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 `monoruby/src/builtins/module.rs:1532` it does not close everything it opens, so those exact lines 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–14 lines × 3) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:717— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:717-727 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:843-856 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1985-1996 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:717` it does not close everything it opens, so those exact lines 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–14 lines × 2) monoruby/src/builtins/array.rs:1133— monoruby/src/builtins/array.rs:1133-1146 | monoruby/src/builtins/hash.rs:1109-1119 — 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 `monoruby/src/builtins/array.rs:1133` 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–13 lines × 4) monoruby/src/codegen/arch/aarch64/compile/mod.rs:1964— monoruby/src/codegen/arch/aarch64/compile/mod.rs:1964-1972 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:1992-2000 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:723-731 | monoruby/src/codegen/arch/x86_64/compile/mod.rs:744-756 — before extracting anything, compare `monoruby/src/codegen/arch/aarch64/compile/mod.rs` and `monoruby/src/codegen/arch/x86_64/compile/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/compile/mod.rs:1964` 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–13 lines × 3) monoruby/src/builtins/regexp.rs:1419— monoruby/src/builtins/regexp.rs:1419-1427 | monoruby/src/builtins/regexp.rs:1590-1598 | monoruby/src/builtins/regexp.rs:1714-1726 — 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 `monoruby/src/builtins/regexp.rs:1419` it does not close everything it opens, so those exact lines 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) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3223— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3223-3235 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:3577-3589 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4160-4172 — 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3223` it does not close everything it opens, so those exact lines 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) monoruby/src/value.rs:2166— monoruby/src/value.rs:2166-2178 | monoruby/src/value.rs:2234-2245 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value.rs:2166` 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) monoruby/src/builtins/hash.rs:2203— monoruby/src/builtins/hash.rs:2203-2214 | monoruby/src/builtins/hash.rs:2382-2393 | monoruby/src/builtins/hash.rs:2418-2429 | monoruby/src/builtins/hash.rs:3963-3974 — 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 `monoruby/src/builtins/hash.rs:2203` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 5) monoruby/src/bytecodegen/defined.rs:108— monoruby/src/bytecodegen/defined.rs:108-118 | monoruby/src/bytecodegen/defined.rs:171-184 | monoruby/src/bytecodegen/defined.rs:234-244 | monoruby/src/bytecodegen/defined.rs:295-305 | monoruby/src/bytecodegen/defined.rs:335-349 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/bytecodegen/defined.rs:108` 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, `monoruby/src/bytecodegen/defined.rs:104` calls `emit` and `monoruby/src/bytecodegen/defined.rs:167` 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 × 4) hashbrown/src/control/group/generic.rs:59— hashbrown/src/control/group/generic.rs:59-69 | hashbrown/src/control/group/lsx.rs:34-44 | hashbrown/src/control/group/neon.rs:30-40 | hashbrown/src/control/group/sse2.rs:36-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6–11 lines × 3) monoruby/src/builtins/string.rs:1545— monoruby/src/builtins/string.rs:1545-1555 | monoruby/src/builtins/string.rs:1590-1600 | monoruby/src/builtins/string.rs:3978-3983 — 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 `monoruby/src/builtins/string.rs:1545` it does not close everything it opens, so those 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–11 lines × 3) monoruby/src/codegen/arch/aarch64/compile/mod.rs:3371— monoruby/src/codegen/arch/aarch64/compile/mod.rs:3371-3380 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4109-4118 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:4134-4144 — 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 `monoruby/src/codegen/arch/aarch64/compile/mod.rs:4134` 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, `monoruby/src/codegen/arch/aarch64/compile/mod.rs:3370` calls `a64_frame_load` and `monoruby/src/codegen/arch/aarch64/compile/mod.rs:4134` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–11 lines × 3) monoruby/src/value/rvalue/string.rs:174— monoruby/src/value/rvalue/string.rs:174-184 | monoruby/src/value/rvalue/string.rs:288-295 | monoruby/src/value/rvalue/string.rs:1942-1952 — 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 `monoruby/src/value/rvalue/string.rs:174` 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–10 lines × 4) monoruby/src/builtins/string.rs:3384— monoruby/src/builtins/string.rs:3384-3391 | monoruby/src/builtins/string.rs:3536-3543 | monoruby/src/builtins/string.rs:3562-3569 | monoruby/src/builtins/string.rs:3851-3860 — 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. 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 × 3) monoruby/src/codegen/arch/x86_64/compile/method_call.rs:563— monoruby/src/codegen/arch/x86_64/compile/method_call.rs:563-572 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:675-684 | monoruby/src/codegen/arch/x86_64/compile/method_call.rs:897-905 — 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 `monoruby/src/codegen/arch/x86_64/compile/method_call.rs:563` it does not close everything it opens, so those exact lines 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–10 lines × 3) monoruby/src/parser/prism_backend.rs:1199— monoruby/src/parser/prism_backend.rs:1199-1206 | monoruby/src/parser/prism_backend.rs:2961-2970 | monoruby/src/parser/prism_backend.rs:2986-2993 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `node` to `&ClassNode<'pr>` in one and `&ModuleNode<'pr>` 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 (7–10 lines × 2) monoruby/src/builtins/kernel.rs:5886— monoruby/src/builtins/kernel.rs:5886-5892 | monoruby/src/builtins/module.rs:1939-1948 — before extracting anything, compare `monoruby/src/builtins/kernel.rs` and `monoruby/src/builtins/module.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `monoruby/src/builtins/kernel.rs:5886` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) monoruby/src/builtins/set.rs:768— monoruby/src/builtins/set.rs:768-776 | monoruby/src/builtins/set.rs:795-803 | monoruby/src/builtins/set.rs:827-835 | monoruby/src/builtins/set.rs:859-867 — 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 `monoruby/src/builtins/set.rs:768` 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–9 lines × 2) monoruby/src/codegen/jitgen/compile/frameless_call.rs:642— monoruby/src/codegen/jitgen/compile/frameless_call.rs:642-650 | monoruby/src/codegen/jitgen/compile/method_call.rs:2805-2811 — 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–8 lines × 2) REDACTED:1026— REDACTED:1026-1031 | REDACTED:1051-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 `REDACTED:1026` it does not close everything it opens, so those exact lines 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–25 lines × 2) monoruby/src/value.rs:3742— monoruby/src/value.rs:3742-3766 | monoruby/src/value.rs:3909-3931 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/value.rs:3742` it does not close everything it opens, so those 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 × 5) monoruby/src/builtins/set.rs:1008— monoruby/src/builtins/set.rs:1008-1014 | monoruby/src/builtins/set.rs:1041-1047 | monoruby/src/builtins/set.rs:1076-1082 | monoruby/src/builtins/set.rs:1112-1118 | monoruby/src/builtins/set.rs:1150-1156 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/builtins/set.rs:1008` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8–9 lines × 3) monoruby/src/builtins/regexp.rs:1249— monoruby/src/builtins/regexp.rs:1249-1257 | monoruby/src/builtins/regexp.rs:1445-1452 | monoruby/src/builtins/regexp.rs:1764-1771 — 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 `monoruby/src/builtins/regexp.rs:1249` it does not close everything it opens, so those 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 × 6) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:247— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:247-252 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:704-709 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:830-835 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1308-1313 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1401-1406 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1969-1974 — 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 `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:247` it does not close everything it opens, so those 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, `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:246` calls `as_ptr` and `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:827` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) monoruby/src/codegen/arch/aarch64/compile/method_call.rs:262— monoruby/src/codegen/arch/aarch64/compile/method_call.rs:262-267 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:716-721 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:842-847 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1984-1989 — 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 before the matched lines, `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:260` calls `get_current_address` and `monoruby/src/codegen/arch/aarch64/compile/method_call.rs:715` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5–6 lines × 2) monoruby/src/builtins/hash.rs:455— monoruby/src/builtins/hash.rs:455-459 | monoruby/src/builtins/hash.rs:469-474 — both copies are in the same file, so extract the 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 (4–6 lines × 3) monoruby/src/codegen/compiler.rs:1198— monoruby/src/codegen/compiler.rs:1198-1201 | monoruby/src/codegen/compiler.rs:1245-1250 | monoruby/src/codegen/compiler.rs:1309-1313 — 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 `monoruby/src/codegen/compiler.rs:1198` it does not close everything it opens, so those 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 (5 lines × 8) monoruby/src/codegen/arch/aarch64/codegen.rs:123— monoruby/src/codegen/arch/aarch64/codegen.rs:123-127 | monoruby/src/codegen/arch/aarch64/codegen.rs:176-180 | monoruby/src/codegen/arch/aarch64/codegen.rs:255-259 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1642-1646 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1699-1703 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1745-1749 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1775-1779 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2820-2824 — there are 8 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 8 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `monoruby/src/codegen/arch/aarch64/codegen.rs:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 6) monoruby/src/codegen/arch/aarch64/codegen.rs:263— monoruby/src/codegen/arch/aarch64/codegen.rs:263-267 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1672-1676 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1717-1721 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1759-1763 | monoruby/src/codegen/arch/aarch64/compile/method_call.rs:1790-1794 | monoruby/src/codegen/arch/aarch64/compile/mod.rs:2838-2842 — 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 `monoruby/src/codegen/arch/aarch64/codegen.rs:263` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) rubymap/src/map/core.rs:487— rubymap/src/map/core.rs:487-491 | rubymap/src/map/core.rs:572-576 | rubymap/src/map/core.rs:645-649 | rubymap/src/map/core.rs:706-710 — 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 `rubymap/src/map/core.rs:487` it does not close everything it opens, so those exact lines 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 × 10) ext/nokogiri/src/node.rs:561— ext/nokogiri/src/node.rs:561-565 | ext/nokogiri/src/node.rs:645-649 | ext/nokogiri/src/reader.rs:554-558 | ext/nokogiri/src/reader.rs:562-578 | ext/nokogiri/src/reader.rs:562-572 | ext/nokogiri/src/reader.rs:562-573 | ext/nokogiri/src/reader.rs:562-574 | ext/nokogiri/src/reader.rs:562-575 | ext/nokogiri/src/reader.rs:562-576 | ext/nokogiri/src/reader.rs:562-577 — there are 10 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 10 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `ext/nokogiri/src/reader.rs:562` 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 (37 lines × 2) monoruby/builtins/array.rb:171— monoruby/builtins/array.rb:171-207 | monoruby/builtins/array.rb:331-367 — both copies are in the same file, so extract the 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 (19–21 lines × 2) monoruby/builtins/enumerator.rb:202— monoruby/builtins/enumerator.rb:202-222 | monoruby/builtins/enumerator.rb:239-257 — both copies are in the same file, so extract the 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–15 lines × 2) monoruby/builtins/numeric.rb:294— monoruby/builtins/numeric.rb:294-308 | monoruby/builtins/range.rb:791-800 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11–13 lines × 2) monoruby/gem/nokogiri/xml/searchable.rb:211— monoruby/gem/nokogiri/html5/document_fragment.rb:191-203 | monoruby/gem/nokogiri/xml/searchable.rb:211-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
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.
Third-party script without Subresource Integrity .github/bench-pages/index.html:7— `https://cdn.jsdelivr.net/npm/chart.js@4` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 2 such include(s) across the repository's markup.
Configuration option is read nowhere monoruby/src/bin/irm/main.rs:19— `CommandLineArgs.import` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Duplicated predicate monoruby/builtins/numeric.rb:371— `(endv > 0 && unit > 0) || (endv < 0 && unit < 0)` appears character-identically in 2 files — monoruby/builtins/numeric.rb, monoruby/builtins/range.rb. 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 monoruby/gem/cool.io_ext.rb:663— `@s.byteslice(n, @s.bytesize - n) || "".b` appears character-identically in 2 files — monoruby/gem/cool.io_ext.rb, monoruby/gem/msgpack/msgpack.rb. 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 monoruby/gem/nokogiri/html5/document_fragment.rb:197— `Hash === params.last || params.last.nil?` appears character-identically in 2 files — monoruby/gem/nokogiri/html5/document_fragment.rb, monoruby/gem/nokogiri/xml/searchable.rb. 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 monoruby/gem/strptime/strptime.rb:122— `b == 0x20 || b == 0x09 || b == 0x0a || b == 0x0b || b == 0x0c || b == 0x0d` appears character-identically in 2 files — monoruby/gem/strptime/strptime.rb, monoruby/gem/yajl/yajl.rb. 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 monoruby/gem/json/add/bigdecimal.rb:2— `defined?(::JSON::JSON_LOADED) and ::JSON::JSON_LOADED` appears character-identically in 14 files — monoruby/gem/json/add/bigdecimal.rb, monoruby/gem/json/add/complex.rb, monoruby/gem/json/add/date.rb, monoruby/gem/json/add/date_time.rb. 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 monoruby/builtins/method.rb:3— `g.is_a?(Proc) || g.is_a?(Method) || g.respond_to?(:call, true)` appears character-identically in 2 files — monoruby/builtins/method.rb, monoruby/builtins/proc.rb. 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 monoruby/src/builtins/bool_class.rs:46— `!callsite.is_simple() || callsite.pos_num != 1` appears character-identically in 5 files — monoruby/src/builtins/bool_class.rs, REDACTED, monoruby/src/builtins/object.rs, monoruby/src/builtins/string.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 monoruby/src/builtins/fiddle.rs:803— `!callsite.is_simple() || callsite.pos_num != 2` appears character-identically in 3 files — monoruby/src/builtins/fiddle.rs, monoruby/src/builtins/io_buffer.rs, monoruby/src/builtins/string.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 monoruby/src/builtins/fiddle.rs:880— `!callsite.is_simple() || callsite.pos_num != 3` appears character-identically in 2 files — monoruby/src/builtins/fiddle.rs, monoruby/src/builtins/io_buffer.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 monoruby/src/bytecodegen/expression.rs:228— `arglist.args.is_empty() && arglist.block.is_none() && arglist.kw_args.is_empty()` appears character-identically in 2 files — monoruby/src/bytecodegen/expression.rs, monoruby/src/bytecodegen/statement.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 monoruby/src/builtins/fiber.rs:491— `cause_kwarg.is_none() && err.explicit_cause.is_none()` appears character-identically in 2 files — monoruby/src/builtins/fiber.rs, monoruby/src/builtins/thread.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 monoruby/src/value/rvalue/string.rs:5789— `dst_enc == stateless_kddi_enc() && !kddi_wrapper(src_enc)` appears character-identically in 2 files — monoruby/src/value/rvalue/string.rs, monoruby/src/value/rvalue/string/transcode.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 monoruby/src/builtins/string.rs:2844— `enc.is_ascii_compatible() && bytes.is_ascii()` appears character-identically in 2 files — monoruby/src/builtins/string.rs, monoruby/src/value/rvalue/string.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 monoruby/src/codegen/arch/aarch64/compile/mod.rs:3210— `len <= HASH_INLINE_CAP && !self.alloc_free_head_addr.is_null()` appears character-identically in 2 files — monoruby/src/codegen/arch/aarch64/compile/mod.rs, monoruby/src/codegen/arch/x86_64/compile/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 monoruby/src/executor.rs:5760— `meta.is_native() || meta.is_internal_builtin()` appears character-identically in 2 files — monoruby/src/executor.rs, monoruby/src/globals/store/class.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 monoruby/src/builtins/string.rs:6838— `next < s.len() && !s.is_char_boundary(next)` appears character-identically in 2 files — monoruby/src/builtins/string.rs, monoruby/src/value/rvalue/regexp.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 monoruby/src/codegen/arch/aarch64/compile/mod.rs:4244— `rest_pos.is_some() || len == 0 || len > MAX_INLINE_EXPAND` appears character-identically in 2 files — monoruby/src/codegen/arch/aarch64/compile/mod.rs, monoruby/src/codegen/arch/x86_64/compile/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 monoruby/src/codegen/arch/aarch64/compile/mod.rs:3681— `self.alloc_free_head_addr.is_null() || !v.heap_copyable_array()` appears character-identically in 2 files — monoruby/src/codegen/arch/aarch64/compile/mod.rs, monoruby/src/codegen/arch/x86_64/compile/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 monoruby/src/codegen/arch/aarch64/compile/mod.rs:4392— `spliced_break.is_none() && spliced_ret.is_none()` appears character-identically in 2 files — monoruby/src/codegen/arch/aarch64/compile/mod.rs, monoruby/src/codegen/arch/x86_64/compile/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 monoruby/src/value/rvalue/string.rs:5739— `src_enc == stateless_kddi_enc() && !kddi_wrapper(dst_enc)` appears character-identically in 2 files — monoruby/src/value/rvalue/string.rs, monoruby/src/value/rvalue/string/transcode.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.
Silent fallback default on parse failure REDACTED:552— `parse_integer` answers `0` when `ArgumentError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
Silent fallback default on parse failure REDACTED:559— `parse_float` answers `0.0` when `ArgumentError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
Silent fallback default on parse failure REDACTED:587— `parse_rational` answers `0r` when `ArgumentError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
Silent fallback default on Err monoruby/src/prof.rs:1460— `elf_functions` turns every `Err` into `vec![]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err monoruby/src/value/rvalue/string/transcode.rs:4883— `mac_held_len` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
No ADRs found monoruby/Cargo.toml:15— 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 `monoruby/Cargo.toml` makes this repository a deployable product (line 15).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion monoruby/Cargo.toml:1— `monoruby` (396347 LoC, 1581 module-visible types across 80 directories) overshoots its size bounds. 1 of 18 build unit(s) (Cargo) overshoot their size bounds, lowering Project Cohesion to 8.9/10. 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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No dependency-update automation ext/bcrypt/Cargo.toml:13— `ext/bcrypt/Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No release approval gate REDACTED:80— The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
Benchmarks don't track allocations benchmark/app_fib.yml— A Ruby benchmark-ips/Benchmark/rspec-benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
Outdated: cc — `cc` is locked at 1.4.3 but 1.11.2 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in libsqlite3-src/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cc` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.6 but 4.6.8 is the current stable release on crates.io, and it already satisfies the `"4.6.1"` requirement declared in monoruby/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: encoding_rs — `encoding_rs` is locked at 0.8.35 but 0.8.44 is the current stable release on crates.io, and it already satisfies the `"0.8"` requirement declared in monoruby/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p encoding_rs` 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.14.0"` requirement declared in monoruby/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.189 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2.186"` requirement declared in monoruby/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
Outdated: libz-sys — `libz-sys` is locked at 1.1.29 but 1.1.33 is the current stable release on crates.io, and it already satisfies the `"1.1"` requirement declared in monoruby/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libz-sys` and commit the updated REDACTED.
Outdated: unicode-normalization — `unicode-normalization` is locked at 0.1.25 but 0.1.26 is the current stable release on crates.io, and it already satisfies the `"0.1.25"` requirement declared in monoruby/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p unicode-normalization` and commit the updated REDACTED.
Outdated: zstd-safe — `zstd-safe` is locked at 8.0.0 but 8.3.0 is the current stable release on crates.io, and it already satisfies the `"8.0"` requirement declared in ext/zstd/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zstd-safe` 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 01a1e7e7-c73e-76de-a3b2-5b8e88d88ba3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 69 · Warnings: 2441 · Recommendations: 36 · Info: 8 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 05:08 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.