Public report of FyroxEngine/Fyrox, published 14 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 14 November 2026, 16:37 UTC · Survey ID cd_b18ab18fc7fa434b864b27f50cc1e917

FyroxEngine/Fyrox

Measured 14 November 2026, 16:36 UTC, at code version bd50aaa

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 60out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 260,141 lines of product code in 24 projects, tests not counted · Estimated rebuild effort: about 1.9 person-years · Weakest lens: Event Sourcing, 49

Findings by how serious they are

41 critical 1656 serious 54 minor

14 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 16:36 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 ▸

40of 40 dimensions measured by tools.
1743of 1751 findings point to an exact file and line, so you can open each one in the code. The other 8 concern the repository as a whole, such as missing documentation.
40dimensions across 7 lenses, read from 260,141 lines of product code in 24 projects.
Chapters

Executive summary

FyroxEngine/Fyrox falls short of our standard for production, held back most by its Event Sourcing lens, the way the code stores and replays its history of events. It scores 60 out of 100 and is rated Adequate, and 33 of its 41 critical findings are security problems.

Event Sourcing, at 49, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Making event replay repeatable would lift Event Sourcing itself, worth about 10 points. Raising Event Sourcing to 70 would lift the score to about 67.

Twenty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps install packages that can change without warning, and six parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version, pinning what the pipeline installs and having someone learn the forgotten files would close these risks. The password or key in the code and the password or key in the code's history need replacing, with the old ones switched off. Rebuilding state only from the recorded events would take care of the history replay that reads the clock or random values.

The product code is 260,141 lines, about €280,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 for The 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.
Event Sourcing 49 · counts for 46%Maturity 58 · counts for 25%Production Readiness 72 · counts for 14%Security and Compliance 80 · counts for 8%Code Health 83 · counts for 4%Architecture 96 · counts for 2%Performance 100 · counts for 1%

If Event Sourcing rose from 49 to 70, the lowest score rated Strong, the score would rise from 60 to about 67.

Code composition: what the lines of code are
Product code 99%Tests 1%
New since the last survey: 499 findings

These 499 critical or serious findings weren't in the previous survey, on 27 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · AudioPreviewPanel::handle_ui_message (cyclomatic 17) editor/src/audio/preview.rs
  • Cyclomatic Complexity · ExportWindow::handle_ui_message (cyclomatic 16) editor/src/plugins/export.rs
  • Cognitive Complexity · Editor::handle_reloaded_resources (cognitive 28) editor/src/lib.rs
  • Cognitive Complexity · LightPanel::handle_ui_message (cognitive 27) editor/src/plugins/light.rs
  • Cognitive Complexity · ExportWindow::handle_ui_message (cognitive 20) editor/src/plugins/export.rs
  • God Classes · MethodTooLong: ExportWindow.new editor/src/plugins/export.rs
  • God Classes · FileTooLong: inspector/mod.rs editor/src/plugins/inspector/mod.rs
  • God Classes · MethodTooLong: InspectorPlugin.on_ui_message editor/src/plugins/inspector/mod.rs
  • Code Duplication · Near-duplicate member family (3 members, 27 shared lines) fyrox-graphics/src/gpu_texture.rs
  • Code Duplication · Near-duplicate member pair (101 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Near-duplicate member pair (97 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Near-duplicate member pair (89 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) fyrox-impl/src/engine/mod.rs
  • Code Duplication · Edited copy of a member (50 corresponding lines) fyrox-impl/src/scene/terrain/mod.rs
  • Code Duplication · Edited copy of a member (75 corresponding lines) fyrox-ui/src/draw.rs
  • Code Duplication · Edited copy of a member (99 corresponding lines) editor/src/plugins/light.rs
  • Code Duplication · Edited copy of a member (74 corresponding lines) fyrox-impl/src/scene/graph/physics/mod.rs
  • Code Duplication · Edited copy of a member (84 corresponding lines) fyrox-ui/src/inspector/editors/array.rs
  • Code Duplication · Edited copy of a member (63 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Edited copy of a member (90 corresponding lines) fyrox-graph/src/lib.rs
  • Code Duplication · Edited copy of a member (39 corresponding lines) fyrox-impl/src/resource/gltf/surface.rs
  • Code Duplication · Edited copies of one member (3 members, 69+ corresponding lines) editor/src/interaction/move_mode.rs
  • Code Duplication · Edited copy of a member (67 corresponding lines) editor/src/asset/dependency.rs
  • Code Duplication · Edited copy of a member (55 corresponding lines) editor/src/plugins/inspector/editors/dyntype.rs
  • Code Duplication · Edited copies of one member (3 members, 69+ corresponding lines) editor/src/asset/menu.rs
  • Code Duplication · Edited copy of a member (23 corresponding lines) fyrox-ui/src/draw.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Edited copy of a member (47 corresponding lines) editor/src/plugins/absm/mod.rs
  • Code Duplication · Edited copy of a member (41 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Edited copy of a member (36 corresponding lines) editor/src/plugins/tilemap/autotile.rs
  • Code Duplication · Edited copy of a member (50 corresponding lines) editor/src/plugins/absm/selection.rs
  • Code Duplication · Edited copy of a member (53 corresponding lines) editor/src/interaction/gizmo/move_gizmo.rs
  • Code Duplication · Edited copy of a member (84 corresponding lines) fyrox-impl/src/scene/dim2/rectangle.rs
  • Code Duplication · Edited copy of a member (54 corresponding lines) editor/src/plugins/tilemap/palette.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) fyrox-ui/src/matrix.rs
  • Code Duplication · Edited copy of a member (51 corresponding lines) editor/src/asset/selection.rs
  • Code Duplication · Edited copy of a member (50 corresponding lines) editor/src/plugins/tilemap/palette.rs
  • Code Duplication · Edited copy of a member (46 corresponding lines) fyrox-graphics-gl/src/framebuffer.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) editor/src/interaction/rotate_mode.rs
  • Code Duplication · Edited copy of a member (43 corresponding lines) fyrox-graph/src/lib.rs
  • Code Duplication · Edited copy of a member (49 corresponding lines) editor/src/ui_scene/utils.rs
  • Code Duplication · Edited copy of a member (47 corresponding lines) fyrox-ui/src/color/mod.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) fyrox-impl/src/renderer/convolution.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) fyrox-ui/src/color/mod.rs
  • Code Duplication · Edited copy of a member (46 corresponding lines) editor/src/scene/commands/mod.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) fyrox-math/src/frustum.rs
  • Code Duplication · Edited copy of a member (35 corresponding lines) fyrox-ui/src/key.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) editor/src/plugins/absm/mod.rs
  • Code Duplication · Edited copy of a member (44 corresponding lines) fyrox-build-tools/src/export/android.rs
  • Code Duplication · Edited copy of a member (44 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Edited copy of a member (30 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Edited copies of one member (3 members, 55+ corresponding lines) editor/src/plugins/absm/state_graph/context.rs
  • Code Duplication · Edited copy of a member (52 corresponding lines) fyrox-resource/src/manager.rs
  • Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) editor/src/plugins/tilemap/interaction_mode.rs
  • Code Duplication · Edited copy of a member (31 corresponding lines) fyrox-impl/src/scene/dim2/physics/character.rs
  • Code Duplication · Edited copies of one member (5 members, 34+ corresponding lines) editor/src/interaction/mod.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) editor/src/plugins/ragdoll.rs
  • Code Duplication · Edited copy of a member (54 corresponding lines) editor/src/plugins/absm/command/mod.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) fyrox-impl/src/scene/collider.rs
  • Code Duplication · Edited copy of a member (23 corresponding lines) fyrox-core/src/reflect/mod.rs
  • Code Duplication · Edited copy of a member (36 corresponding lines) fyrox-impl/src/scene/terrain/brushstroke/mod.rs
  • Code Duplication · Edited copies of one member (3 members, 38+ corresponding lines) editor/src/plugins/tilemap/colliders_tab.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) editor/src/plugins/absm/state_graph/mod.rs
  • Code Duplication · Edited copy of a member (37 corresponding lines) fyrox-ui/src/inspector/editors/inspectable.rs
  • Code Duplication · Edited copy of a member (47 corresponding lines) fyrox-core/src/pool/mod.rs
  • Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) fyrox-impl/src/scene/tilemap/effect.rs
  • Code Duplication · Edited copy of a member (32 corresponding lines) editor/src/plugins/tilemap/tile_editor.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) fyrox-core/src/visitor/reader/ascii.rs
  • Code Duplication · Edited copy of a member (21 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Edited copy of a member (40 corresponding lines) fyrox-ui/src/file_browser/field.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Edited copy of a member (40 corresponding lines) fyrox-impl/src/renderer/bloom/mod.rs
  • Code Duplication · Edited copy of a member (30 corresponding lines) editor/src/scene/commands/mesh.rs
  • Code Duplication · Edited copy of a member (19 corresponding lines) fyrox-impl/src/scene/terrain/brushstroke/mod.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) editor/src/plugins/inspector/editors/dyntype.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) fyrox-ui/src/utils.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) fyrox-impl/src/scene/dim2/joint.rs
  • Code Duplication · Edited copy of a member (37 corresponding lines) fyrox-ui/src/inspector/editors/array.rs
  • Code Duplication · Edited copy of a member (21 corresponding lines) fyrox-impl/src/scene/dim2/rigidbody.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) fyrox-impl/src/scene/tilemap/tileset.rs
  • Code Duplication · Edited copies of one member (4 members, 21+ corresponding lines) fyrox-impl/src/scene/dim2/rigidbody.rs
  • Code Duplication · Edited copy of a member (21 corresponding lines) editor/src/plugins/collider/cuboid.rs
  • Code Duplication · Edited copy of a member (19 corresponding lines) editor/src/plugins/collider/cuboid.rs
  • Code Duplication · Edited copy of a member (26 corresponding lines) fyrox-impl/src/scene/terrain/mod.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) fyrox-impl/src/scene/debug.rs
  • Code Duplication · Edited copy of a member (28 corresponding lines) editor/src/interaction/move_mode.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) fyrox-build-tools/src/export/utils.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) editor/src/plugins/tilemap/interaction_mode.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) editor/src/plugins/tilemap/panel.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) fyrox-impl/src/renderer/shadow/point.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) editor/src/plugins/absm/command/mod.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) editor/src/ui_scene/utils.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) fyrox-impl/src/resource/gltf/animation.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) editor/src/plugins/tilemap/mod.rs
  • Code Duplication · Edited copy of a member (21 corresponding lines) editor/src/plugins/tilemap/tile_inspector.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) fyrox-graphics-wgpu/src/geometry_buffer.rs
  • Code Duplication · Edited copy of a member (34 corresponding lines) editor/src/plugins/inspector/editors/dyntype.rs
  • Code Duplication · Edited copy of a member (32 corresponding lines) editor/src/command/mod.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) fyrox-animation/src/container.rs
  • Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) fyrox-impl/src/resource/fbx/document/attribute.rs

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 112 findings

These 112 critical or serious findings were in the previous survey, on 27 October 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · WidgetContextMenu::handle_ui_message (cyclomatic 19) editor/src/ui_scene/menu.rs
  • Cognitive Complexity · WidgetContextMenu::handle_ui_message (cognitive 36) editor/src/ui_scene/menu.rs
  • Cognitive Complexity · LightPanel::handle_ui_message (cognitive 25) editor/src/light.rs
  • Cognitive Complexity · ExportWindow::handle_ui_message (cognitive 18) editor/src/export/mod.rs
  • God Classes · MethodTooLong: ExportWindow.new editor/src/export/mod.rs
  • God Classes · TooManyMethods: Transform fyrox-impl/src/scene/transform.rs
  • Code Duplication · Near-duplicate member pair (100 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Near-duplicate member pair (97 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Near-duplicate member pair (89 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Near-duplicate member pair (55 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) fyrox-graphics/src/gpu_texture.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) editor/src/plugins/tilemap/autotile.rs
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) fyrox-impl/src/engine/mod.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) editor/src/asset/creator.rs
  • Code Duplication · Duplicated block (53 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (47–48 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (26 lines × 2) editor/src/plugins/tilemap/interaction_mode.rs
  • Code Duplication · Duplicated block (25 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (25 lines × 2) fyrox-ui/src/lib.rs
  • Code Duplication · Duplicated block (24 lines × 2) fyrox-graphics-gl/src/framebuffer.rs
  • Code Duplication · Duplicated block (24 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (22 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (21 lines × 3) fyrox-ui/src/lib.rs
  • Code Duplication · Duplicated block (20 lines × 3) fyrox-graphics/src/gpu_texture.rs
  • Code Duplication · Duplicated block (20 lines × 2) editor/src/plugins/absm/mod.rs
  • Code Duplication · Duplicated block (19 lines × 2) editor/src/interaction/rotate_mode.rs
  • Code Duplication · Duplicated block (18–19 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (13–18 lines × 2) fyrox-ui/src/border.rs
  • Code Duplication · Duplicated block (16–17 lines × 2) editor/src/light.rs
  • Code Duplication · Duplicated block (17 lines × 2) editor/src/plugins/absm/state_graph/mod.rs
  • Code Duplication · Duplicated block (17 lines × 2) fyrox-core/src/pool/mod.rs
  • Code Duplication · Duplicated block (17 lines × 2) fyrox-impl/src/scene/tilemap/effect.rs
  • Code Duplication · Duplicated block (17 lines × 2) fyrox-ui/src/color/mod.rs
  • Code Duplication · Duplicated block (16 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (16 lines × 2) fyrox-ui/src/inspector/editors/array.rs
  • Code Duplication · Duplicated block (15 lines × 2) editor/src/plugins/absm/mod.rs
  • Code Duplication · Duplicated block (14 lines × 2) editor/src/interaction/rotate_mode.rs
  • Code Duplication · Duplicated block (12–14 lines × 2) editor/src/scene/clipboard.rs
  • Code Duplication · Duplicated block (14 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (13 lines × 2) fyrox-core/src/visitor/reader/ascii.rs
  • Code Duplication · Duplicated block (10–13 lines × 2) fyrox-graph/src/lib.rs
  • Code Duplication · Duplicated block (13 lines × 2) fyrox-impl/src/resource/gltf/animation.rs
  • Code Duplication · Duplicated block (12–13 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (13 lines × 2) fyrox-impl/src/scene/graph/physics/mod.rs
  • Code Duplication · Duplicated block (13 lines × 2) fyrox-ui/src/text_box.rs
  • Code Duplication · Duplicated block (12 lines × 2) editor/src/export/mod.rs
  • Code Duplication · Duplicated block (12 lines × 2) editor/src/plugins/tilemap/commands.rs
  • Code Duplication · Duplicated block (12 lines × 2) fyrox-ui/src/file_browser/fs_tree.rs
  • Code Duplication · Duplicated block (11 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs
  • Code Duplication · Duplicated block (11 lines × 2) editor/src/plugins/tilemap/tile_editor.rs
  • Code Duplication · Duplicated block (11 lines × 2) fyrox-impl/src/resource/fbx/mod.rs
  • Code Duplication · Duplicated block (11 lines × 2) fyrox-impl/src/resource/gltf/animation.rs
  • Code Duplication · Duplicated block (11 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (10 lines × 2) editor/src/plugins/collider/mod.rs
  • Code Duplication · Duplicated block (10 lines × 2) editor/src/plugins/ragdoll.rs
  • Code Duplication · Duplicated block (10 lines × 2) editor/src/plugins/tilemap/palette.rs
  • Code Duplication · Duplicated block (10 lines × 2) fyrox-impl/src/resource/gltf/animation.rs
  • Code Duplication · Duplicated block (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (10 lines × 2) fyrox-impl/src/scene/graph/mod.rs
  • Code Duplication · Duplicated block (10 lines × 2) fyrox-ui/src/input.rs
  • Code Duplication · Duplicated block (10 lines × 2) fyrox-ui/src/messagebox.rs
  • Code Duplication · Duplicated block (9 lines × 4) editor/src/plugins/collider/mod.rs
  • Code Duplication · Duplicated block (9 lines × 2) editor/src/plugins/tilemap/commands.rs
  • Code Duplication · Duplicated block (9 lines × 2) editor/src/scene/property.rs
  • Code Duplication · Duplicated block (9 lines × 2) fyrox-graph/src/lib.rs
  • Code Duplication · Duplicated block (9 lines × 2) fyrox-impl/src/scene/terrain/mod.rs
  • Code Duplication · Duplicated block (9 lines × 2) fyrox-ui/src/messagebox.rs
  • Code Duplication · Duplicated block (8 lines × 3) fyrox-impl/src/scene/terrain/brushstroke/mod.rs
  • Code Duplication · Duplicated block (8 lines × 2) editor/src/plugins/absm/state_graph/mod.rs
  • Code Duplication · Duplicated block (8 lines × 2) editor/src/plugins/absm/state_viewer/mod.rs
  • Code Duplication · Duplicated block (8 lines × 2) editor/src/plugins/tilemap/autotile.rs
  • Code Duplication · Duplicated block (8 lines × 2) fyrox-animation/src/machine/node/blend.rs
  • Code Duplication · Duplicated block (8 lines × 2) fyrox-impl/src/renderer/gbuffer.rs
  • Code Duplication · Duplicated block (7 lines × 3) editor/src/plugins/tilemap/commands.rs
  • Code Duplication · Duplicated block (7 lines × 2) editor/src/plugins/ragdoll.rs
  • Code Duplication · Duplicated block (7 lines × 2) fyrox-impl/src/resource/gltf/surface.rs
  • Code Duplication · Duplicated block (7 lines × 2) fyrox-impl/src/scene/tilemap/tileset.rs
  • Code Duplication · Duplicated block (7 lines × 2) fyrox-ui/src/key.rs
  • Code Duplication · Duplicated block (6 lines × 3) fyrox-ui/src/inspector/editors/texture_slice.rs
  • Code Duplication · Duplicated block (6 lines × 2) editor/src/lib.rs
  • Code Duplication · Duplicated block (6 lines × 2) editor/src/plugins/absm/mod.rs
  • Code Duplication · Duplicated block (6 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (5 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs
  • Code Duplication · Duplicated block (5 lines × 2) fyrox-impl/src/scene/debug.rs
  • Code Duplication · Duplicated block (5 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (5 lines × 2) fyrox-ui/src/inspector/editors/texture_slice.rs
  • Code Duplication · Duplicated block (5 lines × 2) editor/src/plugins/absm/mod.rs
  • Code Duplication · Duplicated block (5 lines × 2) editor/src/plugins/tilemap/autotile.rs
  • Code Duplication · Duplicated block (5 lines × 2) editor/src/plugins/tilemap/autotile.rs
  • Code Duplication · Duplicated block (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs
  • Code Duplication · Duplicated block (8 lines × 3) editor/src/interaction/move_mode.rs
  • Code Duplication · Duplicated block (5 lines × 6) editor/src/plugins/tilemap/brush_macro.rs
  • Code Duplication · Duplicated block (7 lines × 2) editor/src/ui_scene/selection.rs
  • Code Duplication · Duplicated block (7 lines × 2) fyrox-graphics-gl/src/program.rs
  • Code Duplication · Duplicated block (5 lines × 2) fyrox-graphics-wgpu/src/buffer.rs
  • Code Duplication · Duplicated block (10 lines × 2) fyrox-ui/src/stack_panel.rs
  • Code Duplication · Duplicated block (14 lines × 2) fyrox-ui/src/curve/mod.rs
  • Code Duplication · Duplicated block (12 lines × 3) editor/src/asset/mod.rs
  • Code Duplication · Duplicated block (10 lines × 2) editor/src/interaction/gizmo/scale_gizmo.rs
  • Code Duplication · Duplicated block (9 lines × 2) fyrox-impl/src/scene/collider.rs
Rebuild cost: about €280,000 · Estimate
Cost to rebuild€94,000 to €470,000, for 1,562 to 4,956 hours of work, about 1.9 person-years for 1 to 4 engineers
Difficulty of the problemStandard, 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 60. 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.
SizeLarge: 260,141 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 5 points · Low effort · ADR Quality
2
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
Raises the score by about 10 points · Medium effort · Fold determinism
3
Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with update.rs, commands.rs, wave.rs.
Raises the score by about 3 points · Low effort · Knowledge Freshness

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €280,000 to build again, about 1.9 person-years of work. Its weakest lens is Event Sourcing, at 49 (Weak). Event Sourcing is about whether the stored history the system is built on can be trusted. Because the weakest lens counts most in the score, work on Event Sourcing also moves the score most.
Based on: the rebuild estimate · the Event Sourcing grade · how much each lens counts
What to do: Start with the Event Sourcing actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 38,812 lines over the last 90 days, which is about 157,404 lines a year. At that pace, the extra work comes to an estimated 12.2 to 73.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch fyrox fyrox fyrox-dylib fyrox-dylib fyrox->fyrox-dylib fyrox-impl fyrox-impl fyrox->fyrox-impl fyrox-animation fyrox-animation fyrox-core fyrox-core fyrox-animation->fyrox-core fyrox-resource fyrox-resource fyrox-animation->fyrox-resource fyrox-build-tools fyrox-build-tools fyrox-build-tools->fyrox-core fyrox-build-tools->fyrox-resource fyrox-ui fyrox-ui fyrox-build-tools->fyrox-ui fyrox-core-derive fyrox-core-derive fyrox-core->fyrox-core-derive fyrox-dylib->fyrox-impl fyrox-graph fyrox-graph fyrox-graph->fyrox-core fyrox-graph->fyrox-resource fyrox-graphics fyrox-graphics fyrox-graphics->fyrox-core fyrox-graphics-gl fyrox-graphics-gl fyrox-graphics-gl->fyrox-core fyrox-graphics-gl->fyrox-graphics fyrox-graphics-wgpu fyrox-graphics-wgpu fyrox-graphics-wgpu->fyrox-core fyrox-graphics-wgpu->fyrox-graphics fyrox-impl->fyrox-animation fyrox-impl->fyrox-core fyrox-impl->fyrox-core-derive fyrox-impl->fyrox-graph fyrox-impl->fyrox-graphics fyrox-impl->fyrox-graphics-gl fyrox-impl->fyrox-graphics-wgpu fyrox-material fyrox-material fyrox-impl->fyrox-material fyrox-impl->fyrox-resource fyrox-sound fyrox-sound fyrox-impl->fyrox-sound fyrox-texture fyrox-texture fyrox-impl->fyrox-texture fyrox-impl->fyrox-ui fyrox-material->fyrox-core fyrox-material->fyrox-graphics fyrox-material->fyrox-resource fyrox-material->fyrox-texture fyrox-project-manager fyrox-project-manager fyrox-project-manager->fyrox fyrox-project-manager->fyrox-build-tools fyrox-template-core fyrox-template-core fyrox-project-manager->fyrox-template-core fyrox-resource->fyrox-core fyrox-sound->fyrox-core fyrox-sound->fyrox-resource fyrox-texture->fyrox-core fyrox-texture->fyrox-resource fyrox-ui->fyrox-animation fyrox-ui->fyrox-core fyrox-ui->fyrox-graph fyrox-ui->fyrox-material fyrox-ui->fyrox-resource fyrox-ui->fyrox-texture fyroxed fyroxed fyroxed->fyrox fyroxed_base fyroxed_base fyroxed->fyroxed_base fyroxed_base->fyrox fyroxed_base->fyrox-build-tools __more__ +4 more projects

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.

629 modules, with 3616 dependencies between them. 13 loops run through 123 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 589 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.
uses →1 fyrox_math.aabb2 fyroxed_base.settings3 fyrox_core.reflect.array4 fyrox_core.pool5 fyrox_core.visitor6 fyrox_core.math7 fyrox_core.reflect.impls8 fyrox_impl.scene.tilemap.tile_source9 fyrox_core.reflect10 fyrox_graphics.gpu_texture11 fyrox_core.pool.handle12 fyrox_core.variable13 fyrox_resource14 fyrox_core.color15 fyrox_graph.constructor16 fyrox_impl.scene.base17 fyrox_resource.manager18 fyrox_ui.message19 fyrox_graphics.framebuffer20 fyrox_impl.scene21 fyrox_impl.scene.tilemap.tileset22 fyrox_ui.draw23 fyrox_ui.style24 fyrox_impl.scene.node25 fyrox_ui.widget26 fyrox_impl.scene.graph27 fyrox_ui28 fyrox_impl.renderer.bundle29 fyrox_ui.control30 fyrox_ui.inspector.editors31 fyrox_impl.renderer32 fyrox_impl.scene.tilemap33 fyrox_ui.inspector34 fyrox_impl.engine35 fyroxed_base.command36 fyroxed_base.message37 fyroxed_base.scene.container38 fyroxed_base.scene39 fyroxed_base40 fyroxed_base.plugins.collider
1 fyrox_math.aabb
2 fyroxed_base.settings
3 fyrox_core.reflect.array2212
4 fyrox_core.pool14121
5 fyrox_core.visitor12
6 fyrox_core.math2
7 fyrox_core.reflect.impls6
8 fyrox_impl.scene.tilemap.tile_source42
9 fyrox_core.reflect4
10 fyrox_graphics.gpu_texture2
11 fyrox_core.pool.handle212
12 fyrox_core.variable212
13 fyrox_resource331
14 fyrox_core.color1
15 fyrox_graph.constructor211
16 fyrox_impl.scene.base19151
17 fyrox_resource.manager31
18 fyrox_ui.message11
19 fyrox_graphics.framebuffer141
20 fyrox_impl.scene1321311132
21 fyrox_impl.scene.tilemap.tileset5122329
22 fyrox_ui.draw472
23 fyrox_ui.style5111
24 fyrox_impl.scene.node1331211121
25 fyrox_ui.widget2123114114
26 fyrox_impl.scene.graph11221312
27 fyrox_ui154111811721
28 fyrox_impl.renderer.bundle11142222
29 fyrox_ui.control1111211
30 fyrox_ui.inspector.editors2116
31 fyrox_impl.renderer14312431
32 fyrox_impl.scene.tilemap1219211412114312
33 fyrox_ui.inspector26232513
34 fyrox_impl.engine516451
35 fyroxed_base.command111
36 fyroxed_base.message11
37 fyroxed_base.scene.container21212112121
38 fyroxed_base.scene11113121124443
39 fyroxed_base144123131331
40 fyroxed_base.plugins.collider114121211
Uses a module listed above itPart of a loopThe module itself
1 fyrox_math.aabb2 fyroxed_base.settings3 fyrox_core.reflect.array4 fyrox_core.pool5 fyrox_core.visitor6 fyrox_core.math7 fyrox_core.reflect.impls8 fyrox_impl.scene.tilemap.tile_source9 fyrox_core.reflect10 fyrox_graphics.gpu_texture11 fyrox_core.pool.handle12 fyrox_core.variable13 fyrox_resource14 fyrox_core.color15 fyrox_graph.constructor16 fyrox_impl.scene.base17 fyrox_resource.manager18 fyrox_ui.message19 fyrox_graphics.framebuffer20 fyrox_impl.scene21 fyrox_impl.scene.tilemap.tileset22 fyrox_ui.draw23 fyrox_ui.style24 fyrox_impl.scene.node25 fyrox_ui.widget26 fyrox_impl.scene.graph27 fyrox_ui28 fyrox_impl.renderer.bundle29 fyrox_ui.control30 fyrox_ui.inspector.editors31 fyrox_impl.renderer32 fyrox_impl.scene.tilemap33 fyrox_ui.inspector34 fyrox_impl.engine35 fyroxed_base.command36 fyroxed_base.message37 fyroxed_base.scene.container38 fyroxed_base.scene39 fyroxed_base40 fyroxed_base.plugins.colliderfyrox_math.aabb1fyroxed_base.settings2fyrox_core.reflect.array3fyrox_core.pool4fyrox_core.visitor5fyrox_core.math6fyrox_core.reflect.impls7fyrox_impl.scene.tilemap.tile_source8fyrox_core.reflect9fyrox_graphics.gpu_texture10fyrox_core.pool.handle11fyrox_core.variable12fyrox_resource13fyrox_core.color14fyrox_graph.constructor15fyrox_impl.scene.base16fyrox_resource.manager17fyrox_ui.message18fyrox_graphics.framebuffer19fyrox_impl.scene20fyrox_impl.scene.tilemap.tileset21fyrox_ui.draw22fyrox_ui.style23fyrox_impl.scene.node24fyrox_ui.widget25fyrox_impl.scene.graph26fyrox_ui27fyrox_impl.renderer.bundle28fyrox_ui.control29fyrox_ui.inspector.editors30fyrox_impl.renderer31fyrox_impl.scene.tilemap32fyrox_ui.inspector33fyrox_impl.engine34fyroxed_base.command35fyroxed_base.message36fyroxed_base.scene.container37fyroxed_base.scene38fyroxed_base39fyroxed_base.plugins.collider402212141211226424221221233112111915131111411321311132512232947251111331211121212311411411221312154111811721111422221111211211614312431121921141211431226232513516451111112121211212111113121124443144123131331114121211+589 more modules (most-connected shown)

At a glance — Code Health · 83% · Strong ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 58% · Adequate · gated by M2 ·

At a glance — Readiness · 72% · Strong ·

At a glance — Security · 80% · Strong ·

At a glance — Event Sourcing · 49% · Weak · gated by ES1 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection31High / Critical
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; 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.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.+5.5 ptsLowADR Quality
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.+9.8 ptsMediumFold determinism
Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with update.rs, commands.rs, wave.rs.+2.5 ptsLowKnowledge Freshness
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.+4.4 ptsMediumArchitecture documentation
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+2.0 ptsLowSecret Scanning
Reconcile the README with reality: fyrox-impl/README.md links to `CONTRIBUTING.md`, but `fyrox-impl/CONTRIBUTING.md` does not exist; fyrox/README.md links to `CONTRIBUTING.md`, but `fyrox/CONTRIBUTING.md` does not exist.+2.0 ptsMediumDocumentation accuracy
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).+0.7 ptsLowStatic Analysis (SAST)
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.+1.3 ptsMediumDocumentation (README)

File quality

Per-file score 0–10 — a quality signature. Of 349 files carrying findings, judged against the Production bar: 0% slop · 71% mixed · 29% near-clean.

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
fyrox-impl/src/scene/tilemap/update.rs4.8MixedCyclomatic Complexity: TileDataUpdate::swap_with_data (cyclomatic 17)
editor/src/lib.rs5.0MixedChange Coupling: Boundary-crossing change coupling: lib.rs ↔ executor.rs
fyrox-core/src/pool/mod.rs5.5MixedGod Classes: TooManyMethods: Pool
editor/src/plugins/tilemap/autotile.rs5.5MixedGod Classes: FileTooLong: tilemap/autotile.rs
editor/src/plugins/absm/state_graph/mod.rs5.5MixedCyclomatic Complexity: StateGraphViewer::sync_to_model (cyclomatic 25)
editor/src/interaction/gizmo/move_gizmo.rs5.5MixedCode Duplication: Edited copy of a member (53 corresponding lines)
editor/src/plugins/tilemap/wfc.rs5.6MixedCyclomatic Complexity: WfcMacro::on_instance_ui_message (cyclomatic 18)
fyrox-ui/src/widget.rs5.6MixedGod Classes: TooManyMethods: Widget
editor/src/interaction/move_mode.rs5.6MixedCode Duplication: Edited copies of one member (3 members, 69+ corresponding lines)
fyrox-ui/src/color/gradient.rs5.7MixedCognitive Complexity: ColorGradientEditor::preview_message (cognitive 23)
editor/src/ui_scene/selection.rs5.7MixedCode Duplication: Edited copy of a member (29 corresponding lines)
fyrox-ui/src/curve/mod.rs6.0MixedExplicit Debt: TodoComment
fyrox-ui/src/lib.rs6.0MixedExplicit Debt: TodoComment
editor/src/plugins/absm/canvas.rs6.0MixedExplicit Debt: TodoComment
fyrox-ui/src/menu.rs6.0MixedExplicit Debt: TodoComment
fyrox-impl/src/renderer/light.rs6.0MixedExplicit Debt: TodoComment
fyrox-texture/src/lib.rs6.0MixedExplicit Debt: TodoComment
editor/src/plugins/tilemap/palette.rs6.0MixedExplicit Debt: TodoComment

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 41

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 — 1656

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 — 54

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 14

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 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, 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 — 40 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D17D19D20D26D28D29D34D35AX10AX3AX4AX9ES1ES2M1M2M3M4P1P10P2P3P6PF3X1X15X21X27X28X30

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
  1. 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, 1743 of 1751 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1daea-c832-783f-820e-ef14c889eddb.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 192 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 (98 contributor(s) across 8592 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 97 hold 0.1% 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.
  • 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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: 1 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).
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.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").
  • 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.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • 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.

Dimensions

D1 · Cyclomatic Complexity6.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Prevented

139 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TextBox::handle_routed_message at 99. A further 25 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 fyrox_impl::utils::translate_key_to_ui at 195 — they are counted neither in the figure above nor in this dimension's score. 12 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: fyrox-impl/src/utils/mod.rs (fyrox_impl::utils::translate_key_to_ui at 195), fyrox-ui/src/message.rs (KeyCode::to_char at 73), fyrox-core/src/visitor/reader/binary.rs (BinaryReader::read_field at 54), fyrox-core/src/visitor/writer/binary.rs (BinaryWriter::write_field at 53), fyrox-impl/src/renderer/cache/texture.rs (fyrox_impl::renderer::cache::texture::convert_pixel_kind at 27), and 7 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.

fyrox_impl::resource::fbx::create_materials (cyclomatic 32) · ×10fyrox-impl/src/resource/fbx/mod.rs:292
Editor::update (cyclomatic 58) · ×5editor/src/lib.rs:2558
PaletteWidget::draw (cyclomatic 38) · ×4editor/src/plugins/tilemap/palette.rs:1695
Tile::handle_routed_message (cyclomatic 68) · ×3fyrox-ui/src/dock/tile.rs:448
TrackList::handle_ui_message (cyclomatic 56) · ×3editor/src/plugins/animation/track.rs:929

+ 95 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with TextBox::handle_routed_message (cyclomatic 99), Window::handle_routed_message (cyclomatic 90), CurveEditor::handle_routed_message (cyclomatic 80). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity4.6 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 4.6 / 10 · rule-coverage 100% · ceiling Prevented

302 method(s) exceeded the cognitive complexity threshold of 15; the worst was CurveEditor::handle_routed_message at 289.

fyrox_impl::resource::fbx::create_materials (cognitive 110) · ×14fyrox-impl/src/resource/fbx/mod.rs:292
Editor::handle_hotkeys (cognitive 73) · ×8editor/src/lib.rs:1198
UserInterface::process_os_event (cognitive 192) · ×7fyrox-ui/src/lib.rs:2775
PaletteWidget::draw (cognitive 60) · ×6editor/src/plugins/tilemap/palette.rs:1695
fyroxed_base::update (cognitive 57) · ×6editor/src/lib.rs:3226

+ 186 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with CurveEditor::handle_routed_message (cognitive 289). — Refactoring it lifts Cognitive Complexity from 4.6 to about 4.9/10.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes7.6 / 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.

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 100% · ceiling Prevented

260 god class(es) detected.

MethodTooLong: DeferredLightRenderer.render · ×94fyrox-impl/src/renderer/light.rs:254
FileTooLong: src/lib.rs · ×81fyrox-ui/src/lib.rs
ClassTooLong: UserInterface · ×46fyrox-ui/src/lib.rs:736
TooManyMethods: Widget · ×28fyrox-ui/src/widget.rs:572
FunctionTooLong: fyroxed_base::plugins::inspector::editors::make_property_editors_container · ×7editor/src/plugins/inspector/editors/mod.rs:314

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 94 MethodTooLong finding(s) in God Classes — start with mod.rs (26), menu.rs (5), lib.rs (4). — One of this dimension's main actionable groups (94 warning-level).
  2. Resolve the 81 FileTooLong finding(s) in God Classes — start with mod.rs (32), lib.rs (6), tileset.rs (2). — One of this dimension's main actionable groups (81 warning-level).
  3. Resolve the 46 ClassTooLong finding(s) in God Classes — start with mod.rs (16), lib.rs (3), manager.rs (2). — One of this dimension's main actionable groups (46 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication6.5 / 10Adequate✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.5 / 10 · rule-coverage 100% · ceiling Verified

434 duplicated block group(s) detected. 8.7 % of the production lines (22,543 of 260,141) are in a reported copy. A further 379 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 3 of the 813 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (10 lines × 2) · ×36editor/src/plugins/animation/toolbar.rs:427
Duplicated block (9 lines × 2) · ×35editor/src/interaction/gizmo/move_gizmo.rs:350
Duplicated block (11 lines × 2) · ×31editor/src/interaction/gizmo/move_gizmo.rs:185
Duplicated block (7 lines × 2) · ×30editor/src/plugins/absm/command/mod.rs:196
Duplicated block (6 lines × 2) · ×24editor/src/plugins/absm/mod.rs:714

+ 202 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 36 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with mod.rs (9), colliders_tab.rs (3), toolbar.rs. — One of this dimension's main actionable groups (36 warning-level).
  2. Resolve the 35 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with mod.rs (7), rigidbody.rs (5), autotile.rs (3). — One of this dimension's main actionable groups (35 warning-level).
  3. Resolve the 31 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with mod.rs (5), dyntype.rs (2), ball.rs (2). — One of this dimension's main actionable groups (31 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling8.9 / 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.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Prevented

24 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 20 of the 24 (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: fyrox-math · ×2
Unstable project fyrox-impl

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Unstable project fyrox-impl finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 10 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Verified

10 of 766 classes have LCOM4 above 3.

Low cohesion: TileSetUpdate (LCOM4 11) · ×10fyrox-impl/src/scene/tilemap/update.rs:120

What to do

  1. Resolve the 10 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (3), update.rs (2), autotile.rs. — One of this dimension's main actionable groups (10 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 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 Cargo.lock there.

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md.

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 533 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.6 / 10Stronggated by 19 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: fyrox-ui/src/text_box.rs (6×99=594); editor/src/scene_viewer/mod.rs (9×53=477); editor/src/plugins/inspector/mod.rs (16×22=352) Repeated repair below the complexity floor: fyrox-ui/src/nine_patch.rs (3 of 5 changes were fixes); fyrox-core-derive/src/reflect.rs (3 of 4 changes were fixes)

Hotspot: fyrox-ui/src/text_box.rs · ×17fyrox-ui/src/text_box.rs:1147
Repeated repair: fyrox-ui/src/nine_patch.rs · ×2fyrox-ui/src/nine_patch.rs:516

What to do

  1. Resolve the 17 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (5), menu.rs (3), text_box.rs. — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with nine_patch.rs, reflect.rs. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt9.9 / 10Stronggated by 85 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

103 deducted task-comment markers across 260141 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×75template-core/src/lib.rs:819
HackComment · ×4fyrox-impl/src/scene/graph/physics/mod.rs:690
FixmeComment · ×4fyrox-core/src/visitor/impls.rs:416
XxxCommentfyrox-material/src/shader/mod.rs:410
TodoComment repeated across 15 filesfyrox-impl/src/scene/accel.rs:21

What to do

  1. Resolve the 75 TodoComment finding(s) in Explicit Debt — start with mod.rs (20), lib.rs (8), control.rs (3). — One of this dimension's main actionable groups (75 warning-level).
  2. Resolve the 4 HackComment finding(s) in Explicit Debt — start with mod.rs (4). — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with impls.rs (2), mod.rs (2). — One of this dimension's main actionable groups (4 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 16 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundtemplate/src/main.rs:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — 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.

D26 · Project Cohesion7.5 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 7.5 / 10 · rule-coverage 100% · ceiling Documented

3 of 24 build units (Cargo) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)7.1 / 10Adequategated by 31 critical findings✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 7.1 / 10 · rule-coverage 100% · ceiling Documented

31 finding(s): 0 critical, 31 high, 0 medium, 0 low. 29 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `fyrox-core/src/safelock.rs` (lines 38–39) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED

What to do

  1. 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).
  2. No action in Static Analysis (SAST) — all 29 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (29 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness9.7 / 10Adequategated by 6 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

20 of 600 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is fyrox-impl/src/scene/tilemap/update.rs. Counted over 600 of the 649 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×6fyrox-impl/src/scene/tilemap/update.rs:1
Orphaned file · ×14fyrox-impl/src/scene/terrain/brushstroke/brushraster.rs:1
Further orphaned files (smaller)

What to do

  1. Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with update.rs, commands.rs, wave.rs. — One of this dimension's main actionable groups (6 issue-level).
  2. Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with brushraster.rs, strokechunks.rs, bbcode.rs. — One of this dimension's main actionable groups (14 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: point.rs↔spot.rs 100%; point.rs↔spot.rs 86%; move_gizmo.rs↔scale_gizmo.rs 85%

Boundary-crossing change coupling: lib.rs ↔ executor.rseditor/src/lib.rs:1
Change coupling: selection.rs ↔ selection.rs · ×11editor/src/ui_scene/selection.rs:1
Change coupling clique: directional.rs, point.rs, spot.rs · ×4fyrox-impl/src/scene/light/directional.rs
Change-coupling hub: selection.rs → mod.rs, selection.rs, selection.rs, selection.rseditor/src/plugins/absm/selection.rs

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with lib.rs. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 11 Change coupling finding(s) in Change Coupling — start with selection.rs (3), mod.rs (2), enumeration.rs. — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 4 Change coupling clique finding(s) in Change Coupling — start with directional.rs, gbuffer.rs, move_gizmo.rs. — One of this dimension's main actionable groups (4 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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.

ES1 · Fold determinism1.0 / 10Critical✓ Tool-verified

Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.

Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.

  • `StateAction.apply` folds a domain event but reads a clock/random source (`Instant::now`/`Utc::now`/`rand`/`Uuid::new_v4`) on the replay path — a replay must derive state PURELY from the event's own fields, or two replays of the same log diverge. Stamp the timestamp/id into the event in the COMMAND, then read it from the event in the fold. — fyrox-animation/src/machine/state.rs:109

What to do

  • Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.

Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.

M1 · Documentation (README)7.1 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

M4 · Documentation accuracy6.0 / 10Adequate✓ Tool-verified

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.

  • fyrox-impl/README.md links to `CONTRIBUTING.md`, but `fyrox-impl/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — fyrox-impl/README.md:43
  • fyrox/README.md links to `CONTRIBUTING.md`, but `fyrox/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — fyrox/README.md:43

What to do

  • Reconcile the README with reality: fyrox-impl/README.md links to `CONTRIBUTING.md`, but `fyrox-impl/CONTRIBUTING.md` does not exist; fyrox/README.md links to `CONTRIBUTING.md`, but `fyrox/CONTRIBUTING.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

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.

P2 · Observability6.8 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 14/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `template`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X15 · Unvalidated length from an untrusted reader1.6 / 10Critical✓ Tool-verified

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

  • `compressed_length` is read from the bytes being parsed at line 54 (`read_u32`), then used to size a `vec![…; n]` at line 62 — and nowhere in its scope is `compressed_length` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `compressed_length` against the bytes actually remaining and a maximum the format allows before allocating. — fyrox-impl/src/resource/fbx/document/binary.rs:62
  • `length` is read from the bytes being parsed at line 78 (`read_u32`), then used to size a `vec![…; n]` at line 79 — and nowhere in its scope is `length` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `length` against the bytes actually remaining and a maximum the format allows before allocating. — fyrox-impl/src/resource/fbx/document/binary.rs:79
  • `name_len` is read from the bytes being parsed at line 66 (`read_u32`), then used to size a `vec![…; n]` at line 67 — and nowhere in its scope is `name_len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `name_len` against the bytes actually remaining and a maximum the format allows before allocating. — fyrox-core/src/visitor/reader/binary.rs:67
  • `len` is read from the bytes being parsed at line 104 (`read_u32`), then used to size a `vec![…; n]` at line 105 — and nowhere in its scope is `len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining and a maximum the format allows before allocating. — fyrox-core/src/visitor/reader/binary.rs:105
  • `data_size` is read from the bytes being parsed at line 142 (`read_u64`), then used to size a `vec![…; n]` at line 143 — and nowhere in its scope is `data_size` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `data_size` against the bytes actually remaining and a maximum the format allows before allocating. — fyrox-core/src/visitor/reader/binary.rs:143
  • `len` is read from the bytes being parsed at line 194 (`read_u32`), then used to size a `vec![…; n]` at line 195 — and nowhere in its scope is `len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining and a maximum the format allows before allocating. — fyrox-core/src/visitor/reader/binary.rs:195
  • `name_len` is read from the bytes being parsed at line 208 (`read_u32`), then used to size a `vec![…; n]` at line 209 — and nowhere in its scope is `name_len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `name_len` against the bytes actually remaining and a maximum the format allows before allocating. — fyrox-core/src/visitor/reader/binary.rs:209
  • `child_count` is read from the bytes being parsed at line 225 (`read_u32`), then used to size a `Vec::with_capacity` at line 226 — and nowhere in its scope is `child_count` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `child_count` against the bytes actually remaining and a maximum the format allows before allocating. — fyrox-core/src/visitor/reader/binary.rs:226

What to do

  • Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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.

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.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health83%StrongSolid.
Architecture96%ExemplarySolid.
Maturity58%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness72%StrongSolid.
Security80%StrongSolid.
Event Sourcing49%Weak — gated by ES1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 4 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • X10 Duplicated predicate — 27 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 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 — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
  • AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • 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 — ~3133 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
  • D16 Bus Factor — single-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 — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .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.
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
  • 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.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — Rust suite
  • DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 158 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one
  • 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
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface: 647 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
  • X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (260,141 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

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.

Critical — 41 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 4 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned knowledge · ×6
  • Orphaned knowledge fyrox-impl/src/scene/tilemap/update.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge editor/src/plugins/tilemap/commands.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge fyrox-autotile/src/wave.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge fyrox-impl/src/scene/tilemap/transform.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
  • Orphaned knowledge fyrox-impl/src/scene/tilemap/tile_rect.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
  • Orphaned knowledge fyrox-impl/src/scene/tilemap/autotile.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: lib.rs ↔ executor.rs editor/src/lib.rs:1 — `editor/src/lib.rs` (context editor) and `fyrox-impl/src/engine/executor.rs` (context fyrox-impl) sit in DIFFERENT parts of the tree yet change together 52% of the time (28 of the 54 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 28 shared commits counted here, the most recent 3 are `589b4f15` improved resource hot reloading in the editor; `66d1b34f` pass dyn type constructors when deserializing scenes/uis; `f433968e` process file system events on every frame — run `git show` on any of them.
ES1 · Fold determinism · Non-deterministic recovery fold · ×1
  • Non-deterministic recovery fold: StateAction.apply fyrox-animation/src/machine/state.rs:109 — `StateAction.apply` folds a domain event but reads a clock/random source (`Instant::now`/`Utc::now`/`rand`/`Uuid::new_v4`) on the replay path — a replay must derive state PURELY from the event's own fields, or two replays of the same log diverge. Stamp the timestamp/id into the event in the COMMAND, then read it from the event in the fold.
Serious — 1656 finding(s)
D3 · God Classes · MethodTooLong · ×94
  • MethodTooLong: DeferredLightRenderer.render fyrox-impl/src/renderer/light.rs:254 — MethodTooLong — render runs 616 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 516 over it, 6.16× 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: RagdollPreset.create_and_send_command editor/src/plugins/ragdoll.rs:481 — MethodTooLong — create_and_send_command runs 415 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 315 over it, 4.15× 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: ProjectManager.new project-manager/src/manager.rs:336 — MethodTooLong — new runs 389 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 289 over it, 3.89× 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: PropertyEditorDefinitionContainer.with_default_editors fyrox-ui/src/inspector/editors/mod.rs:456 — MethodTooLong — with_default_editors runs 308 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 208 over it, 3.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: CurveEditor.handle_routed_message fyrox-ui/src/curve/mod.rs:574 — MethodTooLong — handle_routed_message runs 305 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 205 over it, 3.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UserInterface.process_os_event fyrox-ui/src/lib.rs:2775 — MethodTooLong — process_os_event runs 284 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 184 over it, 2.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TextBox.handle_routed_message fyrox-ui/src/text_box.rs:1147 — MethodTooLong — handle_routed_message runs 283 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 183 over it, 2.83× 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: Toolbar.new editor/src/plugins/animation/toolbar.rs:400 — MethodTooLong — new runs 268 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 168 over it, 2.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Window.handle_routed_message fyrox-ui/src/window.rs:393 — MethodTooLong — handle_routed_message runs 262 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 162 over it, 2.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.
  • MethodTooLong: Renderer.render_scene_observer fyrox-impl/src/renderer/mod.rs:964 — MethodTooLong — render_scene_observer runs 255 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 155 over it, 2.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.
  • MethodTooLong: SceneViewer.new editor/src/scene_viewer/mod.rs:286 — MethodTooLong — new 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.
  • MethodTooLong: TileSetEditor.new editor/src/plugins/tilemap/tileset.rs:208 — MethodTooLong — new 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: Tile.handle_routed_message fyrox-ui/src/dock/tile.rs:448 — MethodTooLong — handle_routed_message runs 229 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 129 over it, 2.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: PropertiesTab.new editor/src/plugins/tilemap/properties_tab.rs:252 — MethodTooLong — new runs 223 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 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: WgpuFrameBuffer.do_draw fyrox-graphics-wgpu/src/framebuffer.rs:489 — MethodTooLong — do_draw runs 222 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 122 over it, 2.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TileMapPanel.new editor/src/plugins/tilemap/panel.rs:167 — MethodTooLong — new runs 214 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 114 over it, 2.14× 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: GlGraphicsServer.new fyrox-graphics-gl/src/server.rs:593 — MethodTooLong — new runs 196 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 96 over it, 1.96× 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: ScriptProcessor.handle_scripts fyrox-impl/src/engine/mod.rs:645 — MethodTooLong — handle_scripts runs 193 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 93 over it, 1.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.
  • MethodTooLong: ExportWindow.new editor/src/plugins/export.rs:103 — MethodTooLong — new runs 192 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 92 over it, 1.92× 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: WgpuFrameBuffer.get_or_create_pipeline fyrox-graphics-wgpu/src/framebuffer.rs:253 — MethodTooLong — get_or_create_pipeline runs 185 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 85 over it, 1.85× 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: AssetBrowser.handle_ui_message editor/src/asset/mod.rs:632 — MethodTooLong — handle_ui_message runs 177 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UserInterface.poll_single_message fyrox-ui/src/lib.rs:2353 — MethodTooLong — poll_single_message runs 176 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: GlTexture.set_data fyrox-graphics-gl/src/texture.rs:397 — MethodTooLong — set_data runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UiRenderer.render fyrox-impl/src/renderer/ui_renderer.rs:289 — MethodTooLong — render runs 171 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 71 over it, 1.71× 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: CurveEditorBuilder.build fyrox-ui/src/curve/mod.rs:1833 — MethodTooLong — build runs 171 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 71 over it, 1.71× 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.
  • + 69 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×81
  • FileTooLong: src/lib.rs fyrox-ui/src/lib.rs — FileTooLong — 2394 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: UserInterface (12 blocks, 736-4039). The bar is 500 significant lines; this is 1894 over it, 4.79× 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: engine/mod.rs fyrox-impl/src/engine/mod.rs — FileTooLong — 1772 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 1272 over it, 3.54× 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: terrain/mod.rs fyrox-impl/src/scene/terrain/mod.rs — FileTooLong — 1630 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 1130 over it, 3.26× 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: tilemap/palette.rs editor/src/plugins/tilemap/palette.rs — FileTooLong — 1585 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 66% of them inside a single declaration: PaletteWidget (4 blocks, 173-1977). The bar is 500 significant lines; this is 1085 over it, 3.17× 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: curve/mod.rs fyrox-ui/src/curve/mod.rs — FileTooLong — 1341 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: CurveEditor (4 blocks, 426-1735). The bar is 500 significant lines; this is 841 over it, 2.68× 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: physics/mod.rs fyrox-impl/src/scene/graph/physics/mod.rs — FileTooLong — 1287 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 787 over it, 2.57× 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: tilemap/tileset.rs fyrox-impl/src/scene/tilemap/tileset.rs — FileTooLong — 1273 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 773 over it, 2.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: animation/track.rs editor/src/plugins/animation/track.rs — FileTooLong — 1265 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 63% of them inside a single declaration: TrackList (2 blocks, 611-1740). The bar is 500 significant lines; this is 765 over it, 2.53× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: graph/mod.rs fyrox-impl/src/scene/graph/mod.rs — FileTooLong — 1239 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: Graph (10 blocks, 130-2178). The bar is 500 significant lines; this is 739 over it, 2.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/lib.rs fyrox-texture/src/lib.rs — FileTooLong — 1200 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 700 over it, 2.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/manager.rs fyrox-resource/src/manager.rs — FileTooLong — 1124 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 624 over it, 2.25× 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: inspector/mod.rs fyrox-ui/src/inspector/mod.rs — FileTooLong — 1122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 622 over it, 2.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/widget.rs fyrox-ui/src/widget.rs — FileTooLong — 1096 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 596 over it, 2.19× 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/text_box.rs fyrox-ui/src/text_box.rs — FileTooLong — 1077 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: TextBox (5 blocks, 432-1556). The bar is 500 significant lines; this is 577 over it, 2.15× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/lib.rs fyrox-graph/src/lib.rs — FileTooLong — 1042 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 542 over it, 2.08× 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/manager.rs project-manager/src/manager.rs — FileTooLong — 1008 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: ProjectManager (2 blocks, 130-1331). The bar is 500 significant lines; this is 508 over it, 2.02× 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: renderer/mod.rs fyrox-impl/src/renderer/mod.rs — FileTooLong — 986 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: Renderer (2 blocks, 414-1511). The bar is 500 significant lines; this is 486 over it, 1.97× 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: physics/mod.rs fyrox-impl/src/scene/dim2/physics/mod.rs — FileTooLong — 962 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: PhysicsWorld (6 blocks, 466-1512). The bar is 500 significant lines; this is 462 over it, 1.92× 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: plugins/ragdoll.rs editor/src/plugins/ragdoll.rs — FileTooLong — 961 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 63% of them inside a single declaration: RagdollPreset (3 blocks, 79-1011). The bar is 500 significant lines; this is 461 over it, 1.92× 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: tilemap/tile_inspector.rs editor/src/plugins/tilemap/tile_inspector.rs — FileTooLong — 955 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 455 over it, 1.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: tilemap/mod.rs fyrox-impl/src/scene/tilemap/mod.rs — FileTooLong — 950 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 450 over it, 1.90× 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/formatted_text.rs fyrox-ui/src/formatted_text.rs — FileTooLong — 947 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: FormattedText (2 blocks, 265-1252). The bar is 500 significant lines; this is 447 over it, 1.89× 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: scene/mod.rs editor/src/scene/mod.rs — FileTooLong — 940 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: GameScene (3 blocks, 133-1125). The bar is 500 significant lines; this is 440 over it, 1.88× 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: mesh/surface.rs fyrox-impl/src/scene/mesh/surface.rs — FileTooLong — 928 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: SurfaceData (4 blocks, 225-1066). The bar is 500 significant lines; this is 428 over it, 1.86× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/server.rs fyrox-graphics-gl/src/server.rs — FileTooLong — 922 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: GlGraphicsServer (3 blocks, 517-1551). The bar is 500 significant lines; this is 422 over it, 1.84× 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.
  • + 56 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×75
  • TodoComment template-core/src/lib.rs:819 — // TODO: This will be obsolete in 1.0 and should be removed. — 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 fyrox-ui/src/build.rs:70 — /// # 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 fyrox-ui/src/node/mod.rs:182 — /// # 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 fyrox-ui/src/control.rs:70 — // TODO: Remove this method, use `self.type_info_ref().type_uuid` instead. — 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 fyrox-ui/src/control.rs:227 — /// # 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 fyrox-ui/src/control.rs:288 — /// # 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 fyrox-ui/src/draw.rs:711 — // TODO: This could give gaps between segments on sharp turns, it should be either patched — 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 fyrox-ui/src/lib.rs:567 — // TODO Add rest of buttons — 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 fyrox-ui/src/lib.rs:1920 — // TODO: Use post draw as well. — 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 fyrox-ui/src/lib.rs:1962 — // TODO: Use post draw as well. — 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 fyrox-ui/src/lib.rs:3015 — // TODO: Is message needed for focused 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 fyrox-ui/src/log.rs:293 — // TODO: This is suboptimal, because it creates a message per each excessive entry, which — 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 fyrox-ui/src/markdown.rs:126 — // TODO: Add navigation for links. — 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 fyrox-ui/src/markdown.rs:211 — // TODO: Support checked items. — 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 fyrox-ui/src/menu.rs:295 — // TODO: Make picking more accurate - right now it works only with rects. — 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 fyrox-ui/src/style/mod.rs:199 — // TODO: Replace this with derived impl in Fyrox 2.0 and remove backward compatibility. — 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 fyrox-ui/src/inspector/editors/array.rs:455 — // TODO: Refactor `create_message` into `create_messages` to support multiple — 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 fyrox-ui/src/inspector/editors/collection.rs:650 — // TODO: Refactor `create_message` into `create_messages` to support multiple — 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 fyrox-ui/src/inspector/editors/enumeration.rs:149 — // TODO. Send context in Variant message instead of creating it here. — 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 fyrox-ui/src/curve/mod.rs:397 — // TODO: This will be slow for curves with lots of keys. — 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 fyrox-ui/src/curve/mod.rs:402 — // TODO: This will be slow for curves with lots of keys. — 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 fyrox-ui/src/curve/mod.rs:951 — // TODO: Layout system could take up to 10 frames in worst cases. This is super hackish solution — 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 fyrox-texture/src/lib.rs:1433 — // TODO: This could be done without loop. — 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 fyrox-texture/src/lib.rs:1500 — // TODO: Add support for DXGI formats. — 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 fyrox-sound/src/effects/reverb.rs:114 — // TODO: According to many papers delay line lengths should be prime numbers to — 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.
  • + 50 more in this group — see findings.md.
D3 · God Classes · ClassTooLong · ×46
  • ClassTooLong: UserInterface fyrox-ui/src/lib.rs:736 — ClassTooLong — 1763 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 95 methods, 12 blocks, lines 736-4039. The bar is 400 significant lines; this is 1363 over it, 4.41× 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: Graph fyrox-impl/src/scene/graph/mod.rs:130 — ClassTooLong — 1093 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 72 methods, 10 blocks, lines 130-2178. The bar is 400 significant lines; this is 693 over it, 2.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PaletteWidget editor/src/plugins/tilemap/palette.rs:173 — ClassTooLong — 1044 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 49 methods, 4 blocks, lines 173-1977. The bar is 400 significant lines; this is 644 over it, 2.61× 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: Engine fyrox-impl/src/engine/mod.rs:319 — ClassTooLong — 961 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 36 methods, 3 blocks, lines 319-2831. The bar is 400 significant lines; this is 561 over it, 2.40× 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: Terrain fyrox-impl/src/scene/terrain/mod.rs:1036 — ClassTooLong — 854 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 64 methods, 8 blocks, lines 1036-2603. The bar is 400 significant lines; this is 454 over it, 2.14× 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: ProjectManager project-manager/src/manager.rs:130 — ClassTooLong — 802 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 130-1331. The bar is 400 significant lines; this is 402 over it, 2.01× 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: CurveEditor fyrox-ui/src/curve/mod.rs:426 — ClassTooLong — 802 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 4 blocks, lines 426-1735. The bar is 400 significant lines; this is 402 over it, 2.01× 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: TrackList editor/src/plugins/animation/track.rs:611 — ClassTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 2 blocks, lines 611-1740. The bar is 400 significant lines; this is 399 over it, 2.00× 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: TextBox fyrox-ui/src/text_box.rs:432 — ClassTooLong — 763 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 33 methods, 5 blocks, lines 432-1556. The bar is 400 significant lines; this is 363 over it, 1.91× 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: SceneDrawingContext fyrox-impl/src/scene/debug.rs:90 — ClassTooLong — 752 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 4 blocks, lines 90-1114. The bar is 400 significant lines; this is 352 over it, 1.88× 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: DeferredLightRenderer fyrox-impl/src/renderer/light.rs:74 — ClassTooLong — 742 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 2 blocks, lines 74-1079. The bar is 400 significant lines; this is 342 over it, 1.86× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PhysicsWorld fyrox-impl/src/scene/graph/physics/mod.rs:916 — ClassTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 5 blocks, lines 916-2036. The bar is 400 significant lines; this is 279 over it, 1.70× 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: GameScene editor/src/scene/mod.rs:133 — ClassTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 3 blocks, lines 133-1125. The bar is 400 significant lines; this is 274 over it, 1.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: ResourceManagerState fyrox-resource/src/manager.rs:86 — ClassTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 53 methods, 2 blocks, lines 86-2095. The bar is 400 significant lines; this is 267 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: FormattedText fyrox-ui/src/formatted_text.rs:265 — 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), 71 methods, 2 blocks, lines 265-1252. 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: AssetBrowser editor/src/asset/mod.rs:119 — ClassTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 2 blocks, lines 119-1079. The bar is 400 significant lines; this is 235 over it, 1.59× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Color fyrox-core/src/color.rs:37 — ClassTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 15 methods, 13 blocks, lines 37-979. The bar is 400 significant lines; this is 233 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: WgpuFrameBuffer fyrox-graphics-wgpu/src/framebuffer.rs:202 — ClassTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 3 blocks, lines 202-1058. The bar is 400 significant lines; this is 231 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Renderer fyrox-impl/src/renderer/mod.rs:414 — ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 23 methods, 2 blocks, lines 414-1511. The bar is 400 significant lines; this is 227 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PhysicsWorld fyrox-impl/src/scene/dim2/physics/mod.rs:466 — ClassTooLong — 621 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 6 blocks, lines 466-1512. The bar is 400 significant lines; this is 221 over it, 1.55× 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: Tile fyrox-ui/src/dock/tile.rs:263 — ClassTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 4 blocks, lines 263-1201. The bar is 400 significant lines; this is 218 over it, 1.55× 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: RagdollPreset editor/src/plugins/ragdoll.rs:79 — ClassTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 79-1011. The bar is 400 significant lines; this is 210 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Toolbar editor/src/plugins/animation/toolbar.rs:81 — ClassTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 2 blocks, lines 81-1154. The bar is 400 significant lines; this is 207 over it, 1.52× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Widget fyrox-ui/src/widget.rs:572 — ClassTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 110 methods, 2 blocks, lines 572-1644. The bar is 400 significant lines; this is 206 over it, 1.52× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Pool fyrox-core/src/pool/mod.rs:69 — ClassTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 52 methods, 15 blocks, lines 69-1488. The bar is 400 significant lines; this is 205 over it, 1.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • + 21 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×36
  • Duplicated block (10 lines × 2) editor/src/plugins/animation/toolbar.rs:427 — editor/src/plugins/animation/toolbar.rs:427-436 | editor/src/plugins/animation/toolbar.rs:555-564 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/animation/toolbar.rs:427` it does not close everything it opens, so those exact lines 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) editor/src/plugins/collider/mod.rs:411 — editor/src/plugins/collider/mod.rs:411-420 | editor/src/plugins/probe.rs:182-191 — 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 `editor/src/plugins/collider/mod.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 (10 lines × 2) editor/src/plugins/ragdoll.rs:717 — editor/src/plugins/ragdoll.rs:717-726 | editor/src/plugins/ragdoll.rs:753-762 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/ragdoll.rs:717` 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) editor/src/plugins/tilemap/colliders_tab.rs:128 — editor/src/plugins/tilemap/colliders_tab.rs:128-137 | editor/src/plugins/tilemap/macro_tab.rs:135-144 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/plugins/tilemap/colliders_tab.rs:128` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/tilemap/colliders_tab.rs:122 — editor/src/plugins/tilemap/colliders_tab.rs:122-131 | editor/src/plugins/tilemap/properties_tab.rs:147-156 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 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 `editor/src/plugins/tilemap/colliders_tab.rs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:149 — editor/src/plugins/tilemap/colliders_tab.rs:149-158 | editor/src/plugins/tilemap/properties_tab.rs:253-262 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `editor/src/plugins/tilemap/colliders_tab.rs:161` calls `make_button` and `editor/src/plugins/tilemap/properties_tab.rs:265` 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) editor/src/plugins/tilemap/interaction_mode.rs:514 — editor/src/plugins/tilemap/interaction_mode.rs:514-523 | editor/src/plugins/tilemap/interaction_mode.rs:698-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `editor/src/plugins/tilemap/interaction_mode.rs:696` calls `pick_grid` and `editor/src/plugins/tilemap/interaction_mode.rs:513` 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) editor/src/plugins/tilemap/palette.rs:1557 — editor/src/plugins/tilemap/palette.rs:1557-1566 | editor/src/plugins/tilemap/palette.rs:1602-1611 — both copies are in the same file, so extract the 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) editor/src/plugins/tilemap/panel.rs:359 — editor/src/plugins/tilemap/panel.rs:359-368 | editor/src/plugins/tilemap/properties_tab.rs:265-274 — 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) fyrox-animation/src/container.rs:191 — fyrox-animation/src/container.rs:191-200 | fyrox-animation/src/container.rs:216-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-animation/src/container.rs:191` it begins part-way through the construct above it, so those exact lines 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) fyrox-graphics-wgpu/src/framebuffer.rs:952 — fyrox-graphics-wgpu/src/framebuffer.rs:952-961 | fyrox-graphics-wgpu/src/read_buffer.rs:124-133 — 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 `fyrox-graphics-wgpu/src/framebuffer.rs:952` 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) fyrox-impl/src/resource/gltf/animation.rs:518 — fyrox-impl/src/resource/gltf/animation.rs:518-527 | fyrox-impl/src/resource/gltf/animation.rs:583-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.
  • Duplicated block (10 lines × 2) fyrox-impl/src/scene/collider.rs:824 — fyrox-impl/src/scene/collider.rs:824-833 | fyrox-impl/src/scene/dim2/collider.rs:627-636 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1124 — fyrox-impl/src/scene/dim2/physics/mod.rs:1124-1133 | fyrox-impl/src/scene/graph/physics/mod.rs:1623-1632 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1124` 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) fyrox-impl/src/scene/dim2/physics/mod.rs:1473 — fyrox-impl/src/scene/dim2/physics/mod.rs:1473-1482 | fyrox-impl/src/scene/graph/physics/mod.rs:1995-2004 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) fyrox-impl/src/scene/graph/mod.rs:503 — fyrox-impl/src/scene/graph/mod.rs:503-512 | fyrox-ui/src/lib.rs:1290-1299 — 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 (10 lines × 2) fyrox-impl/src/scene/graph/mod.rs:554 — fyrox-impl/src/scene/graph/mod.rs:554-563 | fyrox-impl/src/scene/graph/mod.rs:592-601 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/graph/mod.rs:554` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/bit.rs:299 — fyrox-ui/src/bit.rs:299-308 | fyrox-ui/src/bit.rs:311-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/bit.rs:299` it begins part-way through the construct above it, so those exact lines 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) fyrox-ui/src/input.rs:161 — fyrox-ui/src/input.rs:161-170 | fyrox-ui/src/messagebox.rs:245-254 — 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 after the matched lines, `fyrox-ui/src/input.rs:172` calls `Some`, `send`, `Text` and `fyrox-ui/src/messagebox.rs:256` 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) fyrox-ui/src/inspector/editors/array.rs:407 — fyrox-ui/src/inspector/editors/array.rs:407-416 | fyrox-ui/src/inspector/editors/collection.rs:604-613 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `fyrox-ui/src/inspector/editors/array.rs:407` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/inspector/editors/texture_slice.rs:249 — fyrox-ui/src/inspector/editors/texture_slice.rs:249-258 | fyrox-ui/src/nine_patch.rs:299-308 — 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 (10 lines × 2) editor/src/plugins/tilemap/commands.rs:841 — editor/src/plugins/tilemap/commands.rs:841-850 | editor/src/plugins/tilemap/commands.rs:992-1001 — both copies are in the same file, so extract the 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) fyrox-impl/src/scene/tilemap/mod.rs:595 — fyrox-impl/src/scene/tilemap/mod.rs:595-604 | fyrox-impl/src/scene/tilemap/mod.rs:606-615 — both copies are in the same file, so extract the 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) editor/src/plugins/tilemap/autotile.rs:879 — editor/src/plugins/tilemap/autotile.rs:879-888 | editor/src/plugins/tilemap/wfc.rs:892-901 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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. 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) fyrox-ui/src/draw.rs:362 — fyrox-ui/src/draw.rs:362-371 | fyrox-ui/src/draw.rs:439-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/draw.rs:362` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 11 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×35
  • Duplicated block (9 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:350 — editor/src/interaction/gizmo/move_gizmo.rs:350-358 | editor/src/interaction/gizmo/scale_gizmo.rs:261-269 — before extracting anything, compare `editor/src/interaction/gizmo/move_gizmo.rs` and `editor/src/interaction/gizmo/scale_gizmo.rs` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) editor/src/interaction/navmesh/mod.rs:268 — editor/src/interaction/navmesh/mod.rs:268-276 | editor/src/interaction/navmesh/mod.rs:432-440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/interaction/navmesh/mod.rs:268` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) editor/src/interaction/navmesh/selection.rs:99 — editor/src/interaction/navmesh/selection.rs:99-107 | editor/src/world/selection.rs:103-112 — 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 `editor/src/interaction/navmesh/selection.rs:99` it does not close everything it opens, so those exact lines 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) editor/src/plugins/absm/connection.rs:94 — editor/src/plugins/absm/connection.rs:94-102 | editor/src/plugins/absm/transition.rs:136-144 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/absm/connection.rs:94` it does not close everything it opens, so those exact lines 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) editor/src/plugins/absm/mod.rs:297 — editor/src/plugins/absm/mod.rs:297-305 | editor/src/plugins/absm/mod.rs:309-317 — both copies are in the same file, so extract the 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) editor/src/plugins/collider/cone.rs:116 — editor/src/plugins/collider/cone.rs:116-124 | editor/src/plugins/collider/cylinder.rs:118-127 — before extracting anything, compare `editor/src/plugins/collider/cone.rs` and `editor/src/plugins/collider/cylinder.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/collider/cone.rs:116` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:171 — editor/src/plugins/tilemap/colliders_tab.rs:171-179 | editor/src/plugins/tilemap/properties_tab.rs:291-299 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 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 `editor/src/plugins/tilemap/colliders_tab.rs:171` it begins part-way through the construct above it, so those 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, `editor/src/plugins/tilemap/properties_tab.rs:290` calls `add_column`, `stretch` and `editor/src/plugins/tilemap/colliders_tab.rs:170` 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) editor/src/scene/container.rs:146 — editor/src/scene/container.rs:146-154 | editor/src/scene/container.rs:182-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/scene/container.rs:146` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) editor/src/scene/property.rs:97 — editor/src/scene/property.rs:97-105 | editor/src/scene/selector.rs:219-227 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) fyrox-autotile/src/auto.rs:173 — fyrox-autotile/src/auto.rs:173-181 | fyrox-autotile/src/auto.rs:184-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-autotile/src/auto.rs:173` it begins part-way through the construct above it, so those exact lines 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) fyrox-core/src/pool/mod.rs:916 — fyrox-core/src/pool/mod.rs:916-924 | fyrox-core/src/pool/mod.rs:963-971 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-core/src/pool/mod.rs:916` it does not close everything it opens, so those 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 `handles` to `(Handle<T>, Handle<T>, Handle<T>)` in one and `(Handle<T>, Handle<T>, Handle<T>, Handle<T>)` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `fyrox-core/src/pool/mod.rs:972` calls `borrow_mut` and `fyrox-core/src/pool/mod.rs:925` 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) fyrox-graph/src/lib.rs:1696 — fyrox-graph/src/lib.rs:1696-1704 | fyrox-graph/src/lib.rs:1764-1772 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-graph/src/lib.rs:1696` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) fyrox-impl/src/resource/fbx/mod.rs:450 — fyrox-impl/src/resource/fbx/mod.rs:450-458 | fyrox-impl/src/resource/fbx/mod.rs:463-471 — both copies are in the same file, so extract the 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) fyrox-impl/src/scene/dim2/physics/mod.rs:624 — fyrox-impl/src/scene/dim2/physics/mod.rs:624-632 | fyrox-impl/src/scene/graph/physics/mod.rs:1067-1075 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:163 — fyrox-impl/src/scene/dim2/rigidbody.rs:163-171 | fyrox-impl/src/scene/rigidbody.rs:247-255 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/rigidbody.rs:163` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/dim2/rigidbody.rs:201 — fyrox-impl/src/scene/dim2/rigidbody.rs:201-209 | fyrox-impl/src/scene/rigidbody.rs:290-298 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/rigidbody.rs:201` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/dim2/rigidbody.rs:211 — fyrox-impl/src/scene/dim2/rigidbody.rs:211-219 | fyrox-impl/src/scene/rigidbody.rs:302-310 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `fyrox-impl/src/scene/rigidbody.rs:311` calls `clone` and `fyrox-impl/src/scene/dim2/rigidbody.rs:220` 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) fyrox-impl/src/scene/dim2/rigidbody.rs:662 — fyrox-impl/src/scene/dim2/rigidbody.rs:662-670 | fyrox-impl/src/scene/rigidbody.rs:838-846 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/rigidbody.rs:662` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/mesh/surface.rs:420 — fyrox-impl/src/scene/mesh/surface.rs:420-428 | fyrox-impl/src/scene/mesh/surface.rs:458-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/mesh/surface.rs:420` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/particle_system/emitter/base.rs:103 — fyrox-impl/src/scene/particle_system/emitter/base.rs:103-111 | fyrox-impl/src/scene/particle_system/emitter/base.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.
  • Duplicated block (9 lines × 2) fyrox-ui/src/matrix.rs:142 — fyrox-ui/src/matrix.rs:142-150 | fyrox-ui/src/vec.rs:178-186 — before extracting anything, compare `fyrox-ui/src/matrix.rs` and `fyrox-ui/src/vec.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/matrix.rs:142` it does not close everything it opens, so those exact lines 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) editor/src/plugins/tilemap/colliders_tab.rs:311 — editor/src/plugins/tilemap/colliders_tab.rs:311-319 | editor/src/plugins/tilemap/properties_tab.rs:618-626 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 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 `editor/src/plugins/tilemap/colliders_tab.rs:311` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) editor/src/plugins/collider/cone.rs:79 — editor/src/plugins/collider/cone.rs:79-87 | editor/src/plugins/collider/cylinder.rs:80-88 — before extracting anything, compare `editor/src/plugins/collider/cone.rs` and `editor/src/plugins/collider/cylinder.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/collider/cone.rs:79` it begins part-way through the construct above it, so those exact lines 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) fyrox-ui/src/screen.rs:158 — fyrox-ui/src/screen.rs:158-166 | fyrox-ui/src/widget.rs:1442-1450 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) editor/src/plugins/collider/ball.rs:104 — editor/src/plugins/collider/ball.rs:104-112 | editor/src/plugins/collider/ball2d.rs:104-112 — before extracting anything, compare `editor/src/plugins/collider/ball.rs` and `editor/src/plugins/collider/ball2d.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/collider/ball.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.
  • + 10 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×31
  • Duplicated block (11 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:185 — editor/src/interaction/gizmo/move_gizmo.rs:185-195 | editor/src/interaction/gizmo/rotate_gizmo.rs:107-117 — 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) editor/src/plugins/absm/mod.rs:846 — editor/src/plugins/absm/mod.rs:846-856 | editor/src/plugins/animation/mod.rs:1010-1020 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/absm/mod.rs:846` 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) editor/src/plugins/collider/cone.rs:96 — editor/src/plugins/collider/cone.rs:96-106 | editor/src/plugins/collider/cylinder.rs:97-108 — before extracting anything, compare `editor/src/plugins/collider/cone.rs` and `editor/src/plugins/collider/cylinder.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/collider/cone.rs:96` 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) editor/src/plugins/curve_editor.rs:283 — editor/src/plugins/curve_editor.rs:283-293 | editor/src/plugins/settings.rs:159-169 — 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 `editor/src/plugins/curve_editor.rs:283` 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) editor/src/plugins/inspector/editors/dyntype.rs:116 — editor/src/plugins/inspector/editors/dyntype.rs:116-126 | editor/src/plugins/inspector/editors/script.rs:182-192 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/dyntype.rs:116` it does not close everything it opens, so those 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, `editor/src/plugins/inspector/editors/dyntype.rs:115` calls `preview_message` and `editor/src/plugins/inspector/editors/script.rs:180` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:315 — editor/src/plugins/inspector/editors/dyntype.rs:315-325 | editor/src/plugins/inspector/editors/script.rs:411-421 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/dyntype.rs:315` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) editor/src/plugins/tilemap/macro_tab.rs:245 — editor/src/plugins/tilemap/macro_tab.rs:245-255 | editor/src/plugins/tilemap/properties_tab.rs:301-311 — before extracting anything, compare `editor/src/plugins/tilemap/macro_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 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 `editor/src/plugins/tilemap/macro_tab.rs:245` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/tilemap/tile_editor.rs:259 — editor/src/plugins/tilemap/tile_editor.rs:259-269 | editor/src/plugins/tilemap/tile_editor.rs:296-306 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/tilemap/tile_editor.rs:259` it does not close everything it opens, so those exact lines 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) editor/src/plugins/tilemap/tileset.rs:296 — editor/src/plugins/tilemap/tileset.rs:296-306 | editor/src/plugins/tilemap/tileset.rs:310-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 `editor/src/plugins/tilemap/tileset.rs:296` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/tilemap/wfc.rs:119 — editor/src/plugins/tilemap/wfc.rs:119-129 | editor/src/plugins/tilemap/wfc.rs:174-184 — both copies are in the same file, so extract the 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) editor/src/scene/property.rs:186 — editor/src/scene/property.rs:186-196 | editor/src/scene/property.rs:221-231 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/scene/property.rs:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) fyrox-impl/src/resource/fbx/mod.rs:320 — fyrox-impl/src/resource/fbx/mod.rs:320-330 | fyrox-impl/src/resource/gltf/material.rs:418-428 — 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 `fyrox-impl/src/resource/fbx/mod.rs:320` 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, `fyrox-impl/src/resource/gltf/material.rs:429` calls `resource_io` and `fyrox-impl/src/resource/fbx/mod.rs:331` 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) fyrox-impl/src/resource/gltf/animation.rs:485 — fyrox-impl/src/resource/gltf/animation.rs:485-495 | fyrox-impl/src/resource/gltf/animation.rs:544-554 — both copies are in the same file, so extract the 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) fyrox-impl/src/scene/debug.rs:709 — fyrox-impl/src/scene/debug.rs:709-719 | fyrox-impl/src/scene/debug.rs:766-776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/debug.rs:709` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/character.rs:129 — fyrox-impl/src/scene/dim2/physics/character.rs:129-139 | fyrox-impl/src/scene/graph/physics/character.rs:207-217 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/character.rs` and `fyrox-impl/src/scene/graph/physics/character.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/character.rs:129` 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) fyrox-impl/src/scene/dim2/physics/mod.rs:1251 — fyrox-impl/src/scene/dim2/physics/mod.rs:1251-1261 | fyrox-impl/src/scene/graph/physics/mod.rs:1763-1773 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1251` 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) fyrox-impl/src/scene/mesh/surface.rs:823 — fyrox-impl/src/scene/mesh/surface.rs:823-833 | fyrox-impl/src/scene/mesh/surface.rs:839-849 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/mesh/surface.rs:823` it does not close everything it opens, so those exact lines 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) fyrox-math/src/lib.rs:558 — fyrox-math/src/lib.rs:558-568 | fyrox-math/src/lib.rs:598-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 `fyrox-math/src/lib.rs:558` 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) fyrox-ui/src/file_browser/selector.rs:367 — fyrox-ui/src/file_browser/selector.rs:367-377 | fyrox-ui/src/file_browser/selector.rs:417-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/file_browser/selector.rs:367` it does not close everything it opens, so those exact lines 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) editor/src/plugins/tilemap/palette.rs:1496 — editor/src/plugins/tilemap/palette.rs:1496-1506 | editor/src/plugins/tilemap/palette.rs:1510-1520 — both copies are in the same file, so extract the 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) fyrox-ui/src/list_view.rs:346 — fyrox-ui/src/list_view.rs:346-356 | fyrox-ui/src/scroll_panel.rs:287-297 — 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) editor/src/plugins/collider/ball.rs:56 — editor/src/plugins/collider/ball.rs:56-66 | editor/src/plugins/collider/ball2d.rs:56-66 — before extracting anything, compare `editor/src/plugins/collider/ball.rs` and `editor/src/plugins/collider/ball2d.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/collider/ball.rs:56` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/collider/ball.rs:86 — editor/src/plugins/collider/ball.rs:86-96 | editor/src/plugins/collider/ball2d.rs:86-96 — before extracting anything, compare `editor/src/plugins/collider/ball.rs` and `editor/src/plugins/collider/ball2d.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/collider/ball.rs:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) editor/src/plugins/tilemap/autotile.rs:349 — editor/src/plugins/tilemap/autotile.rs:349-359 | editor/src/plugins/tilemap/wfc.rs:385-395 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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 `editor/src/plugins/tilemap/autotile.rs:349` it begins part-way through the construct above it, so those exact lines 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) editor/src/ui_scene/utils.rs:186 — editor/src/ui_scene/utils.rs:186-196 | editor/src/world/graph.rs:160-170 — 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.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×30
  • Duplicated block (7 lines × 2) editor/src/plugins/absm/command/mod.rs:196 — editor/src/plugins/absm/command/mod.rs:196-202 | editor/src/plugins/animation/command/mod.rs:56-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 `editor/src/plugins/absm/command/mod.rs:196` it does not close everything it opens, so those exact lines 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) editor/src/plugins/collider/cuboid.rs:79 — editor/src/plugins/collider/cuboid.rs:79-85 | editor/src/plugins/collider/cuboid2d.rs:75-81 — before extracting anything, compare `editor/src/plugins/collider/cuboid.rs` and `editor/src/plugins/collider/cuboid2d.rs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `editor/src/plugins/collider/cuboid.rs:79` 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, `editor/src/plugins/collider/cuboid.rs:87` calls `Some` and `editor/src/plugins/collider/cuboid2d.rs:83` 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) editor/src/plugins/collider/cuboid.rs:129 — editor/src/plugins/collider/cuboid.rs:129-135 | editor/src/plugins/collider/cuboid2d.rs:117-123 — before extracting anything, compare `editor/src/plugins/collider/cuboid.rs` and `editor/src/plugins/collider/cuboid2d.rs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `editor/src/plugins/collider/cuboid.rs:129` 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) editor/src/plugins/ragdoll.rs:738 — editor/src/plugins/ragdoll.rs:738-744 | editor/src/plugins/ragdoll.rs:774-780 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/ragdoll.rs:738` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) editor/src/plugins/tilemap/tile_inspector.rs:597 — editor/src/plugins/tilemap/tile_inspector.rs:597-603 | editor/src/plugins/tilemap/tile_inspector.rs:671-677 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/tilemap/tile_inspector.rs:597` it does not close everything it opens, so those exact lines 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) editor/src/scene/property.rs:308 — editor/src/scene/property.rs:308-314 | editor/src/scene/selector.rs:304-310 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/scene/property.rs:308` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/renderer/convolution.rs:98 — fyrox-impl/src/renderer/convolution.rs:98-104 | fyrox-impl/src/renderer/convolution.rs:181-187 — both copies are in the same file, so extract the 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) fyrox-impl/src/resource/gltf/surface.rs:490 — fyrox-impl/src/resource/gltf/surface.rs:490-496 | fyrox-impl/src/resource/gltf/surface.rs:535-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.
  • Duplicated block (7 lines × 2) fyrox-impl/src/scene/debug.rs:605 — fyrox-impl/src/scene/debug.rs:605-611 | fyrox-impl/src/scene/debug.rs:614-620 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/debug.rs:605` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/mod.rs:941 — fyrox-impl/src/scene/dim2/physics/mod.rs:941-947 | fyrox-impl/src/scene/graph/physics/mod.rs:1382-1388 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:941` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/rigidbody.rs:518 — fyrox-impl/src/scene/dim2/rigidbody.rs:518-524 | fyrox-impl/src/scene/rigidbody.rs:659-665 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/rigidbody.rs:518` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) fyrox-impl/src/scene/tilemap/tileset.rs:389 — fyrox-impl/src/scene/tilemap/tileset.rs:389-395 | fyrox-impl/src/scene/tilemap/tileset.rs:422-428 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/tilemap/tileset.rs:389` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/color/mod.rs:135 — fyrox-ui/src/color/mod.rs:135-141 | fyrox-ui/src/color/mod.rs:416-422 — both copies are in the same file, so extract the 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 (7 lines × 2) fyrox-ui/src/image.rs:247 — fyrox-ui/src/image.rs:247-253 | fyrox-ui/src/image.rs:263-269 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/image.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.
  • Duplicated block (7 lines × 2) fyrox-ui/src/key.rs:284 — fyrox-ui/src/key.rs:284-290 | fyrox-ui/src/key.rs:483-489 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/key.rs:284` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) fyrox-impl/src/scene/debug.rs:1056 — fyrox-impl/src/scene/debug.rs:1056-1062 | fyrox-impl/src/scene/debug.rs:1064-1070 — both copies are in the same file, so extract the 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) editor/src/plugins/collider/capsule.rs:41 — editor/src/plugins/collider/capsule.rs:41-47 | editor/src/plugins/collider/capsule2d.rs:41-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) editor/src/plugins/collider/triangle.rs:41 — editor/src/plugins/collider/triangle.rs:41-47 | editor/src/plugins/collider/triangle2d.rs:41-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) fyrox-impl/src/scene/tilemap/brush.rs:322 — fyrox-impl/src/scene/tilemap/brush.rs:322-328 | fyrox-impl/src/scene/tilemap/tileset.rs:2013-2019 — 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 after the matched lines, `fyrox-impl/src/scene/tilemap/brush.rs:330` calls `page_icon`, `get` and `fyrox-impl/src/scene/tilemap/tileset.rs:2021` 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) fyrox-ui/src/draw.rs:925 — fyrox-ui/src/draw.rs:925-931 | fyrox-ui/src/vector_image.rs:106-112 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) editor/src/plugins/inspector/editors/handle.rs:486 — editor/src/plugins/inspector/editors/handle.rs:486-493 | fyrox-ui/src/inspector/editors/rect.rs:89-95 — 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 `editor/src/plugins/inspector/editors/handle.rs:486` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/inspector/editors/triangle_buffer.rs:75 — editor/src/plugins/inspector/editors/triangle_buffer.rs:75-81 | editor/src/plugins/inspector/editors/vertex_buffer.rs:75-81 — 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 `editor/src/plugins/inspector/editors/triangle_buffer.rs:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) editor/src/scene/property.rs:509 — editor/src/scene/property.rs:509-515 | editor/src/scene/selector.rs:452-459 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) editor/src/ui_scene/selection.rs:180 — editor/src/ui_scene/selection.rs:180-186 | editor/src/world/selection.rs:183-189 — 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 first that the copies are not typed on the same thing: the declarations holding them bind `handle` to `Handle<UiNode>` in one and `Handle<Node>` 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 × 2) fyrox-graphics-gl/src/program.rs:334 — fyrox-graphics-gl/src/program.rs:334-340 | fyrox-graphics-gl/src/sampler.rs:133-139 — 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.
  • + 5 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×28
  • TooManyMethods: Widget fyrox-ui/src/widget.rs:572 — TooManyMethods — 110 methods. The bar is 30 methods; this is 80 over it, 3.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: UserInterface fyrox-ui/src/lib.rs:736 — TooManyMethods — 95 methods. The bar is 30 methods; this is 65 over it, 3.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Base fyrox-impl/src/scene/base.rs:389 — TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Graph fyrox-impl/src/scene/graph/mod.rs:130 — TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× 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: FormattedText fyrox-ui/src/formatted_text.rs:265 — TooManyMethods — 71 methods. The bar is 30 methods; this is 41 over it, 2.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Terrain fyrox-impl/src/scene/terrain/mod.rs:1036 — 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: TileSet fyrox-impl/src/scene/tilemap/tileset.rs:1337 — TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ResourceManagerState fyrox-resource/src/manager.rs:86 — TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Pool fyrox-core/src/pool/mod.rs:69 — TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PaletteWidget editor/src/plugins/tilemap/palette.rs:173 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.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: Animation fyrox-animation/src/lib.rs:269 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.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: OptionTileSet fyrox-impl/src/scene/tilemap/tileset.rs:859 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RigidBody fyrox-impl/src/scene/rigidbody.rs:175 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: WidgetBuilder fyrox-ui/src/widget.rs:1677 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SoundSource fyrox-sound/src/source.rs:81 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MachineLayer fyrox-animation/src/machine/layer.rs:86 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RigidBody fyrox-impl/src/scene/dim2/rigidbody.rs:98 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Texture fyrox-texture/src/lib.rs:258 — TooManyMethods — 37 methods. The bar is 30 methods; 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.
  • TooManyMethods: Engine fyrox-impl/src/engine/mod.rs:319 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TileEditorState editor/src/plugins/tilemap/tile_inspector.rs:97 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Camera fyrox-impl/src/scene/camera.rs:359 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.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: ResourceManager fyrox-resource/src/manager.rs:122 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.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: TextBox fyrox-ui/src/text_box.rs:432 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.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: SpriteSheetAnimation fyrox-animation/src/spritesheet/mod.rs:165 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Visitor fyrox-core/src/visitor/mod.rs:312 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • + 3 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×24
  • Duplicated block (6 lines × 2) editor/src/plugins/absm/mod.rs:714 — editor/src/plugins/absm/mod.rs:714-719 | editor/src/plugins/absm/mod.rs:727-732 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/absm/mod.rs:714` it does not close everything it opens, so those exact lines 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) editor/src/scene/property.rs:374 — editor/src/scene/property.rs:374-379 | editor/src/scene/selector.rs:256-261 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/scene/property.rs:374` 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) fyrox-core-derive/src/reflect.rs:207 — fyrox-core-derive/src/reflect.rs:207-212 | fyrox-core-derive/src/reflect.rs:324-329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-core-derive/src/reflect.rs:207` it begins part-way through the construct above it, so those exact lines 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) fyrox-graphics-gl/src/texture.rs:358 — fyrox-graphics-gl/src/texture.rs:358-363 | fyrox-graphics-wgpu/src/texture.rs:450-456 — 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 `fyrox-graphics-gl/src/texture.rs:358` it does not close everything it opens, so those 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, `fyrox-graphics-gl/src/texture.rs:363` calls `image_2d_size_bytes` and `fyrox-graphics-wgpu/src/texture.rs:456` 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 × 2) fyrox-impl/src/renderer/light_volume.rs:127 — fyrox-impl/src/renderer/light_volume.rs:127-132 | fyrox-impl/src/renderer/light_volume.rs:187-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/renderer/light_volume.rs:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `fyrox-impl/src/renderer/light_volume.rs:125` calls `clear`, `Some` and `fyrox-impl/src/renderer/light_volume.rs:185` 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) fyrox-impl/src/renderer/ui_renderer.rs:145 — fyrox-impl/src/renderer/ui_renderer.rs:145-150 | fyrox-impl/src/renderer/ui_renderer.rs:155-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/renderer/ui_renderer.rs:145` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/tilemap/mod.rs:201 — fyrox-impl/src/scene/tilemap/mod.rs:201-206 | fyrox-impl/src/scene/tilemap/mod.rs:246-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/tilemap/mod.rs:201` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/tilemap/tileset.rs:399 — fyrox-impl/src/scene/tilemap/tileset.rs:399-404 | fyrox-impl/src/scene/tilemap/tileset.rs:432-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/tilemap/tileset.rs:399` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/inspector/editors/texture_slice.rs:124 — fyrox-ui/src/inspector/editors/texture_slice.rs:124-129 | fyrox-ui/src/inspector/editors/texture_slice.rs:247-255 — both copies are in the same file, so extract the 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) fyrox-ui/src/utils.rs:146 — fyrox-ui/src/utils.rs:146-151 | fyrox-ui/src/utils.rs:174-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/utils.rs:146` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/wrap_panel.rs:190 — fyrox-ui/src/wrap_panel.rs:190-195 | fyrox-ui/src/wrap_panel.rs:208-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/wrap_panel.rs:190` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/rectangle.rs:336 — fyrox-impl/src/scene/dim2/rectangle.rs:336-341 | fyrox-impl/src/scene/sprite.rs:335-340 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rectangle.rs` and `fyrox-impl/src/scene/sprite.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/rectangle.rs:336` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/node/mod.rs:144 — fyrox-impl/src/scene/node/mod.rs:144-149 | fyrox-ui/src/control.rs:166-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) fyrox-impl/src/scene/tilemap/tileset.rs:609 — fyrox-impl/src/scene/tilemap/tileset.rs:609-614 | fyrox-impl/src/scene/tilemap/tileset.rs:1479-1484 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/tilemap/tileset.rs:609` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) fyrox-impl/src/scene/collider.rs:816 — fyrox-impl/src/scene/collider.rs:816-821 | fyrox-impl/src/scene/dim2/collider.rs:619-624 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/collider.rs:816` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/rectangle.rs:289 — fyrox-impl/src/scene/dim2/rectangle.rs:289-294 | fyrox-impl/src/scene/sprite.rs:291-296 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rectangle.rs` and `fyrox-impl/src/scene/sprite.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) editor/src/plugins/absm/state_graph/mod.rs:73 — editor/src/plugins/absm/state_graph/mod.rs:73-78 | editor/src/plugins/absm/state_viewer/mod.rs:108-113 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/absm/state_viewer/mod.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.
  • Duplicated block (6 lines × 2) fyrox-impl/src/scene/animation/mod.rs:83 — fyrox-impl/src/scene/animation/mod.rs:83-88 | fyrox-ui/src/animation.rs:83-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) fyrox-impl/src/scene/collider.rs:872 — fyrox-impl/src/scene/collider.rs:872-877 | fyrox-impl/src/scene/dim2/collider.rs:675-680 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) editor/src/plugins/tilemap/commands.rs:1065 — editor/src/plugins/tilemap/commands.rs:1065-1070 | editor/src/plugins/tilemap/commands.rs:1100-1105 — both copies are in the same file, so extract the 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) editor/src/plugins/animation/track.rs:882 — editor/src/plugins/animation/track.rs:882-887 | editor/src/plugins/animation/track.rs:888-893 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/animation/track.rs:882` it begins part-way through the construct above it, so those exact lines 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) editor/src/mesh.rs:227 — editor/src/mesh.rs:227-232 | editor/src/mesh.rs:245-250 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/mesh.rs:227` it does not close everything it opens, so those exact lines 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) editor/src/interaction/gizmo/move_gizmo.rs:257 — editor/src/interaction/gizmo/move_gizmo.rs:257-262 | editor/src/interaction/gizmo/scale_gizmo.rs:193-198 — before extracting anything, compare `editor/src/interaction/gizmo/move_gizmo.rs` and `editor/src/interaction/gizmo/scale_gizmo.rs` as WHOLE FILES: this scan already matched 4 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `editor/src/interaction/gizmo/scale_gizmo.rs:192` calls `set_mesh_diffuse_color`, `opaque` and `editor/src/interaction/gizmo/move_gizmo.rs:256` 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 (6 lines × 2) fyrox-impl/src/renderer/occlusion/grid.rs:97 — fyrox-impl/src/renderer/occlusion/grid.rs:97-102 | fyrox-impl/src/renderer/visibility.rs:67-72 — 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.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×23
  • Edited copy of a member (15 corresponding lines) fyrox-impl/src/scene/debug.rs:489 — fyrox-impl/src/scene/debug.rs:489-503 | fyrox-impl/src/scene/debug.rs:516-533 — 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) fyrox-ui/src/text_box.rs:639 — fyrox-ui/src/text_box.rs:639-653 | fyrox-ui/src/text_box.rs:656-671 — 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) fyrox-impl/src/engine/mod.rs:2260 — fyrox-impl/src/engine/mod.rs:2260-2274 | fyrox-impl/src/engine/mod.rs:2278-2292 — 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) editor/src/plugins/inspector/editors/dyntype.rs:196 — editor/src/plugins/inspector/editors/dyntype.rs:196-210 | editor/src/plugins/inspector/editors/script.rs:267-288 — 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) fyrox-impl/src/scene/dim2/rigidbody.rs:436 — fyrox-impl/src/scene/dim2/rigidbody.rs:436-450 | fyrox-impl/src/scene/rigidbody.rs:575-591 — 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) fyrox-impl/src/scene/mesh/buffer.rs:633 — fyrox-impl/src/scene/mesh/buffer.rs:633-647 | fyrox-impl/src/scene/mesh/buffer.rs:1003-1017 — 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) fyrox-impl/src/scene/tilemap/update.rs:395 — fyrox-impl/src/scene/tilemap/update.rs:395-410 | fyrox-impl/src/scene/tilemap/update.rs:416-430 — 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) fyrox-math/src/lib.rs:553 — fyrox-math/src/lib.rs:553-568 | fyrox-math/src/lib.rs:594-608 — 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) editor/src/scene/commands/mod.rs:77 — editor/src/scene/commands/mod.rs:77-96 | editor/src/ui_scene/commands/mod.rs:61-75 — 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) fyrox-impl/src/scene/collider.rs:514 — fyrox-impl/src/scene/collider.rs:514-528 | fyrox-impl/src/scene/dim2/collider.rs:317-331 — 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) fyrox-impl/src/scene/tilemap/mod.rs:785 — fyrox-impl/src/scene/tilemap/mod.rs:785-799 | fyrox-impl/src/scene/tilemap/mod.rs:837-851 — 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) editor/src/plugins/tilemap/autotile.rs:407 — editor/src/plugins/tilemap/autotile.rs:407-421 | editor/src/plugins/tilemap/wfc.rs:443-457 — 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) fyrox-impl/src/scene/collider.rs:879 — fyrox-impl/src/scene/collider.rs:879-893 | fyrox-impl/src/scene/dim2/collider.rs:682-698 — 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) fyrox-impl/src/scene/graph/mod.rs:1143 — fyrox-impl/src/scene/graph/mod.rs:1143-1157 | fyrox-impl/src/scene/graph/mod.rs:1159-1174 — 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) fyrox-impl/src/renderer/convolution.rs:56 — fyrox-impl/src/renderer/convolution.rs:56-72 | fyrox-impl/src/renderer/convolution.rs:144-158 — 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) fyrox-impl/src/scene/terrain/mod.rs:301 — fyrox-impl/src/scene/terrain/mod.rs:301-315 | fyrox-impl/src/scene/terrain/mod.rs:321-336 — 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) fyrox-impl/src/resource/fbx/document/mod.rs:95 — fyrox-impl/src/resource/fbx/document/mod.rs:95-109 | fyrox-impl/src/resource/fbx/document/mod.rs:112-126 — 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) fyrox-impl/src/scene/tilemap/brush.rs:270 — fyrox-impl/src/scene/tilemap/brush.rs:270-287 | fyrox-impl/src/scene/tilemap/brush.rs:290-304 — 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) editor/src/plugins/tilemap/tile_editor.rs:161 — editor/src/plugins/tilemap/tile_editor.rs:161-175 | editor/src/plugins/tilemap/tile_inspector.rs:555-570 — 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) editor/src/scene/container.rs:258 — editor/src/scene/container.rs:258-272 | editor/src/scene/container.rs:280-294 — 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) fyrox-impl/src/scene/dim2/joint.rs:590 — fyrox-impl/src/scene/dim2/joint.rs:590-604 | fyrox-impl/src/scene/joint.rs:670-684 — 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) editor/src/plugins/inspector/editors/dyntype.rs:215 — editor/src/plugins/inspector/editors/dyntype.rs:215-229 | editor/src/plugins/inspector/editors/script.rs:293-307 — 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) fyrox-impl/src/scene/node/mod.rs:536 — fyrox-impl/src/scene/node/mod.rs:536-550 | fyrox-ui/src/node/mod.rs:248-265 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×23
  • Edited copy of a member (9 corresponding lines) fyrox-impl/src/scene/tilemap/update.rs:447 — fyrox-impl/src/scene/tilemap/update.rs:447-457 | fyrox-impl/src/scene/tilemap/update.rs:463-471 — 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) fyrox-impl/src/scene/terrain/mod.rs:1792 — fyrox-impl/src/scene/terrain/mod.rs:1792-1800 | fyrox-impl/src/scene/terrain/mod.rs:1803-1812 — 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) fyrox-ui/src/scroll_panel.rs:178 — fyrox-ui/src/scroll_panel.rs:178-186 | fyrox-ui/src/widget.rs:1425-1436 — 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) fyrox-math/src/lib.rs:212 — fyrox-math/src/lib.rs:212-221 | fyrox-math/src/lib.rs:224-232 — 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) editor/src/plugins/tilemap/tile_editor.rs:232 — editor/src/plugins/tilemap/tile_editor.rs:232-240 | editor/src/plugins/tilemap/tile_editor.rs:241-249 — 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) fyrox-core/src/pool/mod.rs:832 — fyrox-core/src/pool/mod.rs:832-840 | fyrox-core/src/pool/mod.rs:848-856 — 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) fyrox-ui/src/text_box.rs:516 — fyrox-ui/src/text_box.rs:516-524 | fyrox-ui/src/text_box.rs:526-537 — 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) editor/src/plugins/inspector/editors/animation.rs:198 — editor/src/plugins/inspector/editors/animation.rs:198-206 | editor/src/plugins/inspector/editors/animation.rs:254-262 — 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) editor/src/plugins/tilemap/collider_editor.rs:206 — editor/src/plugins/tilemap/collider_editor.rs:206-219 | editor/src/plugins/tilemap/tile_editor.rs:461-469 — 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) fyrox-impl/src/scene/dim2/rigidbody.rs:454 — fyrox-impl/src/scene/dim2/rigidbody.rs:454-462 | fyrox-impl/src/scene/rigidbody.rs:595-603 — 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) fyrox-impl/src/scene/collider.rs:862 — fyrox-impl/src/scene/collider.rs:862-870 | fyrox-impl/src/scene/dim2/collider.rs:665-673 — 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) fyrox-impl/src/scene/dim2/joint.rs:564 — fyrox-impl/src/scene/dim2/joint.rs:564-572 | fyrox-impl/src/scene/joint.rs:644-652 — 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) editor/src/mesh.rs:77 — editor/src/mesh.rs:77-85 | editor/src/plugins/tilemap/macro_inspector.rs:109-119 — 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) editor/src/plugins/inspector/editors/surface.rs:178 — editor/src/plugins/inspector/editors/surface.rs:178-188 | editor/src/plugins/material/editor.rs:193-201 — 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) fyrox-impl/src/scene/graph/mod.rs:200 — fyrox-impl/src/scene/graph/mod.rs:200-209 | fyrox-impl/src/scene/mod.rs:570-578 — 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) editor/src/plugins/inspector/editors/resource.rs:260 — editor/src/plugins/inspector/editors/resource.rs:260-268 | editor/src/plugins/inspector/editors/texture.rs:166-174 — 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) editor/src/plugins/tilemap/autotile.rs:377 — editor/src/plugins/tilemap/autotile.rs:377-385 | editor/src/plugins/tilemap/wfc.rs:413-421 — 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) editor/src/plugins/tilemap/autotile.rs:392 — editor/src/plugins/tilemap/autotile.rs:392-400 | editor/src/plugins/tilemap/wfc.rs:428-436 — 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) fyrox-ui/src/lib.rs:1342 — fyrox-ui/src/lib.rs:1342-1350 | fyrox-ui/src/test.rs:68-76 — 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) editor/src/audio/preview.rs:57 — editor/src/audio/preview.rs:57-65 | editor/src/plugins/tilemap/macro_tab.rs:165-173 — 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) editor/src/ui_scene/utils.rs:92 — editor/src/ui_scene/utils.rs:92-100 | editor/src/world/graph.rs:91-100 — 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) editor/src/plugins/absm/mod.rs:436 — editor/src/plugins/absm/mod.rs:436-444 | editor/src/plugins/animation/mod.rs:698-706 — 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) editor/src/plugins/tilemap/autotile.rs:818 — editor/src/plugins/tilemap/autotile.rs:818-826 | editor/src/plugins/tilemap/wfc.rs:818-826 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×23
  • Duplicated block (13 lines × 2) editor/src/interaction/move_mode.rs:229 — editor/src/interaction/move_mode.rs:229-241 | editor/src/scene/mod.rs:641-653 — 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 `editor/src/interaction/move_mode.rs:229` 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) editor/src/plugins/absm/mod.rs:249 — editor/src/plugins/absm/mod.rs:249-261 | editor/src/plugins/animation/mod.rs:322-334 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/absm/mod.rs:249` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/absm/state_graph/mod.rs:202 — editor/src/plugins/absm/state_graph/mod.rs:202-214 | editor/src/plugins/absm/state_viewer/mod.rs:298-310 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/absm/state_graph/mod.rs:202` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) editor/src/plugins/animation/toolbar.rs:586 — editor/src/plugins/animation/toolbar.rs:586-598 | editor/src/plugins/animation/toolbar.rs:619-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 `editor/src/plugins/animation/toolbar.rs:586` 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) editor/src/plugins/tilemap/tile_inspector.rs:623 — editor/src/plugins/tilemap/tile_inspector.rs:623-635 | editor/src/plugins/tilemap/tile_inspector.rs:697-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 `editor/src/plugins/tilemap/tile_inspector.rs:623` 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) fyrox-core/src/visitor/reader/ascii.rs:356 — fyrox-core/src/visitor/reader/ascii.rs:356-368 | fyrox-core/src/visitor/reader/binary.rs:228-240 — 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 `fyrox-core/src/visitor/reader/ascii.rs:356` 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) fyrox-impl/src/resource/gltf/animation.rs:494 — fyrox-impl/src/resource/gltf/animation.rs:494-506 | fyrox-impl/src/resource/gltf/animation.rs:629-641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/resource/gltf/animation.rs:494` 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) fyrox-impl/src/resource/gltf/animation.rs:620 — fyrox-impl/src/resource/gltf/animation.rs:620-632 | fyrox-impl/src/resource/gltf/animation.rs:651-663 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/resource/gltf/animation.rs:620` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/collider.rs:965 — fyrox-impl/src/scene/collider.rs:965-977 | fyrox-impl/src/scene/dim2/collider.rs:770-782 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:602 — fyrox-impl/src/scene/dim2/physics/mod.rs:602-614 | fyrox-impl/src/scene/graph/physics/mod.rs:1045-1057 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) fyrox-impl/src/scene/graph/physics/mod.rs:580 — fyrox-impl/src/scene/graph/physics/mod.rs:580-592 | fyrox-impl/src/scene/graph/physics/mod.rs:669-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 (13 lines × 2) fyrox-impl/src/scene/tilemap/mod.rs:209 — fyrox-impl/src/scene/tilemap/mod.rs:209-221 | fyrox-impl/src/scene/tilemap/mod.rs:254-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/tilemap/mod.rs:209` 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) fyrox-ui/src/inspector/editors/hashmap/mod.rs:402 — fyrox-ui/src/inspector/editors/hashmap/mod.rs:402-414 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:440-452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/inspector/editors/hashmap/mod.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 (13 lines × 2) fyrox-ui/src/inspector/editors/immutable_string.rs:56 — fyrox-ui/src/inspector/editors/immutable_string.rs:56-68 | fyrox-ui/src/inspector/editors/string.rs:52-64 — before extracting anything, compare `fyrox-ui/src/inspector/editors/immutable_string.rs` and `fyrox-ui/src/inspector/editors/string.rs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `fyrox-ui/src/inspector/editors/immutable_string.rs:56` 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) fyrox-ui/src/text_box.rs:1255 — fyrox-ui/src/text_box.rs:1255-1267 | fyrox-ui/src/text_box.rs:1279-1291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/text_box.rs:1255` it does not close everything it opens, so those 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, `fyrox-ui/src/text_box.rs:1292` calls `remove_char` and `fyrox-ui/src/text_box.rs:1268` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) project-manager/src/manager.rs:198 — project-manager/src/manager.rs:198-210 | project-manager/src/manager.rs:212-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `project-manager/src/manager.rs:198` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/tilemap/tileset.rs:78 — fyrox-impl/src/scene/tilemap/tileset.rs:78-90 | fyrox-ui/src/style/resource.rs:57-69 — 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) fyrox-impl/src/resource/curve/mod.rs:47 — fyrox-impl/src/resource/curve/mod.rs:47-59 | fyrox-impl/src/scene/tilemap/brush.rs:70-82 — 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) editor/src/plugins/animation/toolbar.rs:603 — editor/src/plugins/animation/toolbar.rs:603-616 | editor/src/plugins/animation/toolbar.rs:635-647 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/animation/toolbar.rs:603` it begins part-way through the construct above it, so those 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, `editor/src/plugins/animation/toolbar.rs:648` calls `with_min_value` and `editor/src/plugins/animation/toolbar.rs:617` 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 (13 lines × 2) fyrox-impl/src/renderer/shadow/point.rs:81 — fyrox-impl/src/renderer/shadow/point.rs:81-93 | fyrox-impl/src/renderer/shadow/spot.rs:66-78 — 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 `fyrox-impl/src/renderer/shadow/point.rs:81` it does not close everything it opens, so those exact lines 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) editor/src/configurator.rs:234 — editor/src/configurator.rs:234-246 | editor/src/scene/dialog.rs:116-128 — 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 `editor/src/configurator.rs:234` it begins part-way through the construct above it, so those 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, `editor/src/configurator.rs:231` calls `with_tab_index`, `Some`, `with_enabled` and `editor/src/scene/dialog.rs:114` 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) fyrox-build-tools/src/lib.rs:117 — fyrox-build-tools/src/lib.rs:117-129 | fyrox-build-tools/src/lib.rs:244-256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-build-tools/src/lib.rs:117` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/mesh/surface.rs:576 — fyrox-impl/src/scene/mesh/surface.rs:576-588 | fyrox-impl/src/scene/mesh/surface.rs:591-603 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/mesh/surface.rs:576` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×21
  • Edited copy of a member (8 corresponding lines) editor/src/plugins/tilemap/palette.rs:1582 — editor/src/plugins/tilemap/palette.rs:1582-1589 | editor/src/plugins/tilemap/palette.rs:1590-1597 — 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) fyrox-ui/src/decorator.rs:328 — fyrox-ui/src/decorator.rs:328-335 | fyrox-ui/src/decorator.rs:338-345 — 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) editor/src/plugins/tilemap/commands.rs:501 — editor/src/plugins/tilemap/commands.rs:501-508 | editor/src/plugins/tilemap/commands.rs:533-540 — 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) fyrox-resource/src/state.rs:185 — fyrox-resource/src/state.rs:185-192 | fyrox-resource/src/state.rs:196-209 — 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) fyrox-core/src/color.rs:60 — fyrox-core/src/color.rs:60-67 | fyrox-core/src/color.rs:71-78 — 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) fyrox-impl/src/scene/tilemap/tileset.rs:326 — fyrox-impl/src/scene/tilemap/tileset.rs:326-333 | fyrox-impl/src/scene/tilemap/tileset.rs:607-614 — 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) fyrox-core/src/visitor/reader/ascii.rs:157 — fyrox-core/src/visitor/reader/ascii.rs:157-164 | fyrox-core/src/visitor/reader/ascii.rs:171-178 — 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) fyrox-ui/src/color/mod.rs:134 — fyrox-ui/src/color/mod.rs:134-141 | fyrox-ui/src/color/mod.rs:415-422 — 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) fyrox-ui/src/popup.rs:352 — fyrox-ui/src/popup.rs:352-359 | fyrox-ui/src/popup.rs:368-375 — 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) editor/src/plugins/tilemap/commands.rs:492 — editor/src/plugins/tilemap/commands.rs:492-499 | editor/src/plugins/tilemap/commands.rs:524-531 — 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) editor/src/plugins/absm/command/blend.rs:111 — editor/src/plugins/absm/command/blend.rs:111-118 | editor/src/plugins/absm/command/blend.rs:120-129 — 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) editor/src/plugins/tilemap/commands.rs:58 — editor/src/plugins/tilemap/commands.rs:58-65 | editor/src/plugins/tilemap/commands.rs:122-129 — 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) editor/src/asset/preview/mod.rs:480 — editor/src/asset/preview/mod.rs:480-489 | editor/src/asset/preview/mod.rs:495-502 — 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) editor/src/plugins/tilemap/commands.rs:311 — editor/src/plugins/tilemap/commands.rs:311-318 | editor/src/plugins/tilemap/commands.rs:320-329 — 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) editor/src/plugins/ragdoll.rs:1243 — editor/src/plugins/ragdoll.rs:1243-1250 | editor/src/plugins/curve_editor.rs:556-563 — 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) fyrox-animation/src/lib.rs:753 — fyrox-animation/src/lib.rs:753-761 | fyrox-animation/src/lib.rs:802-809 — 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) fyrox-impl/src/renderer/hdr/mod.rs:60 — fyrox-impl/src/renderer/hdr/mod.rs:60-67 | fyrox-impl/src/renderer/ssao/blur.rs:50-58 — 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) fyrox-impl/src/resource/curve/loader.rs:52 — fyrox-impl/src/resource/curve/loader.rs:52-59 | fyrox-material/src/shader/loader.rs:45-52 — 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) editor/src/interaction/navmesh/mod.rs:594 — editor/src/interaction/navmesh/mod.rs:594-601 | editor/src/plugins/collider/mod.rs:386-394 — 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) editor/src/plugins/animation/mod.rs:708 — editor/src/plugins/animation/mod.rs:708-715 | editor/src/plugins/material/mod.rs:382-390 — 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) fyrox-core/src/sstorage.rs:75 — fyrox-core/src/sstorage.rs:75-86 | fyrox-core/src/visitor/impls.rs:315-322 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×21
  • Duplicated block (14 lines × 2) editor/src/asset/creator.rs:145 — editor/src/asset/creator.rs:145-158 | editor/src/plugins/light.rs:170-183 — before extracting anything, compare `editor/src/asset/creator.rs` and `editor/src/plugins/light.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/asset/creator.rs:145` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/absm/state_graph/context.rs:236 — editor/src/plugins/absm/state_graph/context.rs:236-249 | editor/src/plugins/absm/state_viewer/context.rs:253-266 — 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 `editor/src/plugins/absm/state_graph/context.rs:236` it begins part-way through the construct above it, so those exact lines 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) editor/src/scene/mod.rs:577 — editor/src/scene/mod.rs:577-590 | editor/src/ui_scene/mod.rs:188-201 — 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 `editor/src/scene/mod.rs:577` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/engine/mod.rs:2358 — fyrox-impl/src/engine/mod.rs:2358-2371 | fyrox-impl/src/engine/mod.rs:2386-2399 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/engine/mod.rs:2358` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/accel.rs:98 — fyrox-impl/src/scene/accel.rs:98-111 | fyrox-math/src/octree.rs:83-96 — 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 `fyrox-impl/src/scene/accel.rs:98` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `buffer` to `&mut Vec<Entry>` in one and `&mut Vec<u32>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (14 lines × 2) fyrox-impl/src/scene/accel.rs:125 — fyrox-impl/src/scene/accel.rs:125-138 | fyrox-math/src/octree.rs:110-123 — 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 `fyrox-impl/src/scene/accel.rs:125` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `buffer` to `&mut Vec<Entry>` in one and `&mut Vec<u32>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (14 lines × 2) fyrox-impl/src/scene/collider.rs:1035 — fyrox-impl/src/scene/collider.rs:1035-1048 | fyrox-impl/src/scene/dim2/collider.rs:840-853 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) fyrox-impl/src/scene/dim2/joint.rs:348 — fyrox-impl/src/scene/dim2/joint.rs:348-361 | fyrox-impl/src/scene/joint.rs:407-420 — before extracting anything, compare `fyrox-impl/src/scene/dim2/joint.rs` and `fyrox-impl/src/scene/joint.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) fyrox-impl/src/scene/dim2/joint.rs:420 — fyrox-impl/src/scene/dim2/joint.rs:420-433 | fyrox-impl/src/scene/joint.rs:479-492 — before extracting anything, compare `fyrox-impl/src/scene/dim2/joint.rs` and `fyrox-impl/src/scene/joint.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) fyrox-impl/src/scene/dim2/physics/character.rs:144 — fyrox-impl/src/scene/dim2/physics/character.rs:144-157 | fyrox-impl/src/scene/graph/physics/character.rs:222-235 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/character.rs` and `fyrox-impl/src/scene/graph/physics/character.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/character.rs:144` 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) fyrox-impl/src/scene/dim2/physics/mod.rs:708 — fyrox-impl/src/scene/dim2/physics/mod.rs:708-721 | fyrox-impl/src/scene/graph/physics/mod.rs:1151-1164 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:708` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `crate) fn update(&mut` in one and `super) fn update(&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 (14 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:926 — fyrox-impl/src/scene/dim2/physics/mod.rs:926-939 | fyrox-impl/src/scene/graph/physics/mod.rs:1367-1380 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `rapier2d::pipeline::QueryFilter<'a>` in one and `rapier3d::pipeline::QueryFilter<'a>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (14 lines × 2) fyrox-ui/src/inspector/editors/hashmap/mod.rs:495 — fyrox-ui/src/inspector/editors/hashmap/mod.rs:495-508 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:516-529 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/inspector/editors/hashmap/mod.rs:495` 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) fyrox-ui/src/matrix.rs:52 — fyrox-ui/src/matrix.rs:52-65 | fyrox-ui/src/vec.rs:56-69 — before extracting anything, compare `fyrox-ui/src/matrix.rs` and `fyrox-ui/src/vec.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/matrix.rs:52` 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) fyrox-ui/src/utils.rs:235 — fyrox-ui/src/utils.rs:235-248 | fyrox-ui/src/utils.rs:285-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/utils.rs:235` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/mod.rs:968 — fyrox-impl/src/scene/dim2/physics/mod.rs:968-981 | fyrox-impl/src/scene/graph/physics/mod.rs:1409-1422 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:968` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/character.rs:169 — fyrox-impl/src/scene/dim2/physics/character.rs:169-182 | fyrox-impl/src/scene/graph/physics/character.rs:247-260 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/character.rs` and `fyrox-impl/src/scene/graph/physics/character.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/character.rs:169` it begins part-way through the construct above it, so those exact lines 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) editor/src/particle.rs:90 — editor/src/particle.rs:90-103 | editor/src/particle.rs:112-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/particle.rs:90` 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, `editor/src/particle.rs:87` calls `build` and `editor/src/particle.rs:110` 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 (14 lines × 2) fyrox-ui/src/curve/mod.rs:1866 — fyrox-ui/src/curve/mod.rs:1866-1879 | fyrox-ui/src/curve/mod.rs:1889-1902 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/curve/mod.rs:1866` it begins part-way through the construct above it, so those exact lines 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) editor/src/particle.rs:176 — editor/src/particle.rs:176-189 | fyrox-ui/src/path.rs:209-222 — 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 `editor/src/particle.rs:176` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `editor/src/particle.rs:191` calls `add_column`, `auto` and `fyrox-ui/src/path.rs:224` 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 (14 lines × 2) fyrox-ui/src/curve/mod.rs:1973 — fyrox-ui/src/curve/mod.rs:1973-1986 | fyrox-ui/src/inspector/mod.rs:1574-1587 — `fyrox-ui/src/curve/mod.rs` and `fyrox-ui/src/inspector/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/curve/mod.rs:1973` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×20
  • Edited copy of a member (10 corresponding lines) fyrox-impl/src/scene/particle_system/emitter/cylinder.rs:72 — fyrox-impl/src/scene/particle_system/emitter/cylinder.rs:72-81 | fyrox-impl/src/scene/particle_system/emitter/sphere.rs:87-102 — 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) fyrox-impl/src/scene/terrain/mod.rs:1709 — fyrox-impl/src/scene/terrain/mod.rs:1709-1718 | fyrox-impl/src/scene/terrain/mod.rs:1721-1730 — 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) fyrox-graph/src/lib.rs:919 — fyrox-graph/src/lib.rs:919-928 | fyrox-graph/src/lib.rs:1078-1087 — 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) fyrox-impl/src/resource/gltf/material.rs:331 — fyrox-impl/src/resource/gltf/material.rs:331-340 | fyrox-impl/src/resource/gltf/mod.rs:428-437 — 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) editor/src/command/mod.rs:760 — editor/src/command/mod.rs:760-773 | editor/src/command/mod.rs:805-814 — 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) fyrox-impl/src/scene/collider.rs:837 — fyrox-impl/src/scene/collider.rs:837-846 | fyrox-impl/src/scene/dim2/collider.rs:640-649 — 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) fyrox-impl/src/scene/mod.rs:287 — fyrox-impl/src/scene/mod.rs:287-296 | fyrox-impl/src/scene/mod.rs:471-481 — 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) project-manager/src/manager.rs:968 — project-manager/src/manager.rs:968-977 | project-manager/src/manager.rs:979-988 — 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) template-core/src/lib.rs:40 — template-core/src/lib.rs:40-49 | template-core/src/lib.rs:51-60 — 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) fyrox-impl/src/scene/dim2/rectangle.rs:472 — fyrox-impl/src/scene/dim2/rectangle.rs:472-481 | fyrox-impl/src/scene/sprite.rs:483-494 — 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) fyrox-ui/src/file_browser/field.rs:63 — fyrox-ui/src/file_browser/field.rs:63-72 | fyrox-ui/src/file_browser/mod.rs:154-163 — 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) editor/src/scene/commands/mod.rs:246 — editor/src/scene/commands/mod.rs:246-255 | editor/src/ui_scene/commands/graph.rs:299-309 — 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) editor/src/plugins/absm/mod.rs:144 — editor/src/plugins/absm/mod.rs:144-153 | editor/src/plugins/animation/mod.rs:231-240 — 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) fyrox-impl/src/scene/tilemap/property.rs:640 — fyrox-impl/src/scene/tilemap/property.rs:640-649 | fyrox-impl/src/scene/tilemap/property.rs:655-664 — 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) editor/src/plugins/absm/mod.rs:105 — editor/src/plugins/absm/mod.rs:105-114 | editor/src/plugins/animation/mod.rs:213-222 — 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) fyrox-ui/src/bit.rs:104 — fyrox-ui/src/bit.rs:104-113 | fyrox-ui/src/vector_image.rs:213-222 — 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) fyrox-impl/src/scene/node/container.rs:58 — fyrox-impl/src/scene/node/container.rs:58-67 | fyrox-ui/src/node/container.rs:58-67 — 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) fyrox-ui/src/matrix.rs:105 — fyrox-ui/src/matrix.rs:105-114 | fyrox-ui/src/matrix.rs:198-208 — 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) editor/src/plugins/tilemap/autotile.rs:361 — editor/src/plugins/tilemap/autotile.rs:361-370 | editor/src/plugins/tilemap/wfc.rs:397-406 — 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) fyrox-impl/src/scene/dim2/joint.rs:619 — fyrox-impl/src/scene/dim2/joint.rs:619-628 | fyrox-impl/src/scene/joint.rs:700-710 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×19
  • Duplicated block (8 lines × 2) editor/src/audio/preview.rs:324 — editor/src/audio/preview.rs:324-331 | editor/src/particle.rs:328-335 — 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 `editor/src/audio/preview.rs:324` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) editor/src/interaction/rotate_mode.rs:200 — editor/src/interaction/rotate_mode.rs:200-207 | editor/src/interaction/scale_mode.rs:192-199 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/interaction/rotate_mode.rs:200` it does not close everything it opens, so those exact lines 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) editor/src/plugins/absm/state_viewer/mod.rs:634 — editor/src/plugins/absm/state_viewer/mod.rs:634-641 | editor/src/plugins/absm/state_viewer/mod.rs:651-658 — both copies are in the same file, so extract the 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) editor/src/plugins/tilemap/autotile.rs:226 — editor/src/plugins/tilemap/autotile.rs:226-233 | editor/src/plugins/tilemap/wfc.rs:273-280 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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 `editor/src/plugins/tilemap/autotile.rs:226` it does not close everything it opens, so those exact lines 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) editor/src/plugins/tilemap/autotile.rs:584 — editor/src/plugins/tilemap/autotile.rs:584-591 | editor/src/plugins/tilemap/wfc.rs:561-568 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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 `editor/src/plugins/tilemap/autotile.rs:584` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/tilemap/collider_editor.rs:255 — editor/src/plugins/tilemap/collider_editor.rs:255-262 | editor/src/plugins/tilemap/tile_prop_editor.rs:398-405 — 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 `editor/src/plugins/tilemap/collider_editor.rs:255` it does not close everything it opens, so those exact lines 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) editor/src/plugins/tilemap/commands.rs:1147 — editor/src/plugins/tilemap/commands.rs:1147-1154 | editor/src/plugins/tilemap/commands.rs:1197-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. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/tilemap/commands.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 (8 lines × 2) editor/src/plugins/tilemap/properties_tab.rs:308 — editor/src/plugins/tilemap/properties_tab.rs:308-315 | editor/src/plugins/tilemap/properties_tab.rs:458-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 `editor/src/plugins/tilemap/properties_tab.rs:308` it begins part-way through the construct above it, so those exact lines 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) editor/src/scene/property.rs:522 — editor/src/scene/property.rs:522-529 | editor/src/scene/selector.rs:466-473 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/scene/property.rs:522` it does not close everything it opens, so those exact lines 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) fyrox-animation/src/machine/node/blend.rs:197 — fyrox-animation/src/machine/node/blend.rs:197-204 | fyrox-animation/src/machine/node/blend.rs:211-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. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-animation/src/machine/node/blend.rs:197` 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) fyrox-impl/src/scene/dim2/rigidbody.rs:173 — fyrox-impl/src/scene/dim2/rigidbody.rs:173-180 | fyrox-impl/src/scene/rigidbody.rs:259-266 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:672 — fyrox-impl/src/scene/dim2/rigidbody.rs:672-679 | fyrox-impl/src/scene/rigidbody.rs:850-857 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `fyrox-impl/src/scene/rigidbody.rs:858` calls `into` and `fyrox-impl/src/scene/dim2/rigidbody.rs:680` 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) fyrox-ui/src/draw.rs:426 — fyrox-ui/src/draw.rs:426-433 | fyrox-ui/src/draw.rs:459-466 — both copies are in the same file, so extract the 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) editor/src/plugins/tilemap/autotile.rs:275 — editor/src/plugins/tilemap/autotile.rs:275-282 | editor/src/plugins/tilemap/autotile.rs:647-654 — both copies are in the same file, so extract the 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) fyrox-impl/src/renderer/bundle.rs:1190 — fyrox-impl/src/renderer/bundle.rs:1190-1197 | fyrox-impl/src/renderer/bundle.rs:1255-1262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/renderer/bundle.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `fyrox-impl/src/renderer/bundle.rs:1198` calls `get_or_create`, `default` and `fyrox-impl/src/renderer/bundle.rs:1263` 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) fyrox-ui/src/bit.rs:326 — fyrox-ui/src/bit.rs:326-333 | fyrox-ui/src/bit.rs:352-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. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/bit.rs:326` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/mod.rs:537 — fyrox-impl/src/scene/dim2/physics/mod.rs:537-544 | fyrox-impl/src/scene/graph/physics/mod.rs:979-986 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) fyrox-ui/src/text.rs:416 — fyrox-ui/src/text.rs:416-423 | fyrox-ui/src/text_box.rs:1125-1132 — 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 `fyrox-ui/src/text.rs:416` it begins part-way through the construct above it, so those exact lines 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) editor/src/interaction/rotate_mode.rs:60 — editor/src/interaction/rotate_mode.rs:60-67 | editor/src/interaction/scale_mode.rs:57-64 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×17
  • Hotspot: fyrox-ui/src/text_box.rs fyrox-ui/src/text_box.rs:1147 — fyrox-ui/src/text_box.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 99 in TextBox::handle_routed_message at line 1147. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-ui/src/text_box.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: editor/src/scene_viewer/mod.rs editor/src/scene_viewer/mod.rs:698 — editor/src/scene_viewer/mod.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in SceneViewer::handle_ui_message at line 698. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/scene_viewer/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: editor/src/plugins/inspector/mod.rs editor/src/plugins/inspector/mod.rs:571 — editor/src/plugins/inspector/mod.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in InspectorPlugin::on_ui_message at line 571. 2 of those changes were fix/bug commits, and the other 14 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/plugins/inspector/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: fyrox-ui/src/inspector/mod.rs fyrox-ui/src/inspector/mod.rs:1734 — fyrox-ui/src/inspector/mod.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Inspector::handle_routed_message at line 1734. 3 of those changes were fix/bug commits, and the other 13 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-ui/src/inspector/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: fyrox-ui/src/formatted_text.rs fyrox-ui/src/formatted_text.rs:1088 — fyrox-ui/src/formatted_text.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in FormattedText::arrange at line 1088. 5 of those changes were fix/bug commits, and the other 5 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-ui/src/formatted_text.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: editor/src/asset/mod.rs editor/src/asset/mod.rs:632 — editor/src/asset/mod.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in AssetBrowser::handle_ui_message at line 632. 1 of those changes was a fix/bug commit, and the other 5 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/asset/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: editor/src/world/menu.rs editor/src/world/menu.rs:280 — editor/src/world/menu.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in SceneNodeContextMenu::handle_ui_message at line 280. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/world/menu.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: fyrox-ui/src/scroll_bar.rs fyrox-ui/src/scroll_bar.rs:236 — fyrox-ui/src/scroll_bar.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in ScrollBar::handle_routed_message at line 236. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-ui/src/scroll_bar.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: fyrox-ui/src/markdown.rs fyrox-ui/src/markdown.rs:98 — fyrox-ui/src/markdown.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in fyrox_ui::markdown::markdown_to_visual_tree at line 98. 1 of those changes was a fix/bug commit, and the other 6 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-ui/src/markdown.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: editor/src/audio/mod.rs editor/src/audio/mod.rs:368 — editor/src/audio/mod.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in AudioPanel::handle_ui_message at line 368. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/audio/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: editor/src/asset/menu.rs editor/src/asset/menu.rs:343 — editor/src/asset/menu.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in AssetItemContextMenu::handle_ui_message at line 343. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/asset/menu.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: fyrox-ui/src/menu.rs fyrox-ui/src/menu.rs:547 — fyrox-ui/src/menu.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in MenuItem::handle_routed_message at line 547. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-ui/src/menu.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: editor/src/plugins/settings.rs editor/src/plugins/settings.rs:242 — editor/src/plugins/settings.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SettingsWindow::handle_ui_message at line 242. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/plugins/settings.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: fyrox-impl/src/renderer/light.rs fyrox-impl/src/renderer/light.rs:254 — fyrox-impl/src/renderer/light.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in DeferredLightRenderer::render at line 254. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-impl/src/renderer/light.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: editor/src/plugins/tilemap/palette.rs editor/src/plugins/tilemap/palette.rs:1695 — editor/src/plugins/tilemap/palette.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in PaletteWidget::draw at line 1695. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/plugins/tilemap/palette.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: fyrox-ui/src/list_view.rs fyrox-ui/src/list_view.rs:395 — fyrox-ui/src/list_view.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in ListView::handle_routed_message at line 395. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-ui/src/list_view.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: editor/src/plugins/inspector/editors/surface.rs editor/src/plugins/inspector/editors/surface.rs:94 — editor/src/plugins/inspector/editors/surface.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SurfaceDataPropertyEditor::handle_routed_message at line 94. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- editor/src/plugins/inspector/editors/surface.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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×17
  • Duplicated block (5 lines × 2) editor/src/audio/preview.rs:307 — editor/src/audio/preview.rs:307-311 | editor/src/particle.rs:306-311 — 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 `editor/src/audio/preview.rs:307` it does not close everything it opens, so those 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 (5 lines × 2) editor/src/plugins/tilemap/palette.rs:584 — editor/src/plugins/tilemap/palette.rs:584-588 | editor/src/plugins/tilemap/palette.rs:615-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 `editor/src/plugins/tilemap/palette.rs:584` it does not close everything it opens, so those exact lines 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) fyrox-core/src/reflect/mod.rs:935 — fyrox-core/src/reflect/mod.rs:935-939 | fyrox-core/src/reflect/mod.rs:965-969 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-core/src/reflect/mod.rs:935` 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) fyrox-impl/src/resource/gltf/surface.rs:510 — fyrox-impl/src/resource/gltf/surface.rs:510-514 | fyrox-impl/src/resource/gltf/surface.rs:564-571 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/resource/gltf/surface.rs:564` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `fyrox-impl/src/resource/gltf/surface.rs:562` calls `next`, `read_valid_index` and `fyrox-impl/src/resource/gltf/surface.rs:509` 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) fyrox-impl/src/scene/debug.rs:1019 — fyrox-impl/src/scene/debug.rs:1019-1023 | fyrox-impl/src/scene/debug.rs:1030-1034 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/debug.rs:1019` 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) fyrox-ui/src/inspector/editors/array.rs:132 — fyrox-ui/src/inspector/editors/array.rs:132-136 | fyrox-ui/src/inspector/editors/collection.rs:230-234 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `fyrox-ui/src/inspector/editors/array.rs:132` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/inspector/editors/string.rs:78 — fyrox-ui/src/inspector/editors/string.rs:78-82 | fyrox-ui/src/inspector/editors/utf32.rs:77-81 — 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 `fyrox-ui/src/inspector/editors/string.rs:78` it does not close everything it opens, so those 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) editor/src/plugins/tilemap/autotile.rs:934 — editor/src/plugins/tilemap/autotile.rs:934-938 | editor/src/plugins/tilemap/wfc.rs:947-951 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) editor/src/plugins/tilemap/autotile.rs:963 — editor/src/plugins/tilemap/autotile.rs:963-967 | editor/src/plugins/tilemap/wfc.rs:976-980 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:266 — editor/src/plugins/tilemap/colliders_tab.rs:266-270 | editor/src/plugins/tilemap/properties_tab.rs:503-507 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:810 — fyrox-impl/src/scene/dim2/physics/mod.rs:810-814 | fyrox-impl/src/scene/graph/physics/mod.rs:1254-1258 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:810` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/mod.rs:816 — fyrox-impl/src/scene/dim2/physics/mod.rs:816-820 | fyrox-impl/src/scene/graph/physics/mod.rs:1260-1264 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) fyrox-ui/src/button.rs:127 — fyrox-ui/src/button.rs:127-131 | fyrox-ui/src/toggle.rs:60-64 — 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) editor/src/plugins/absm/mod.rs:824 — editor/src/plugins/absm/mod.rs:824-828 | editor/src/plugins/animation/mod.rs:988-992 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (5 lines × 2) fyrox-graphics-gl/src/server.rs:1382 — fyrox-graphics-gl/src/server.rs:1382-1392 | fyrox-graphics-wgpu/src/server.rs:626-630 — 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 `fyrox-graphics-gl/src/server.rs:1382` it begins part-way through the construct above it, so those exact lines 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) fyrox-graphics-wgpu/src/buffer.rs:106 — fyrox-graphics-wgpu/src/buffer.rs:106-110 | fyrox-graphics-wgpu/src/texture.rs:482-486 — 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) fyrox-ui/src/style/mod.rs:509 — fyrox-ui/src/style/mod.rs:509-513 | fyrox-ui/src/style/mod.rs:574-578 — both copies are in the same file, so extract the 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 (14 corresponding lines) · ×16
  • Edited copy of a member (14 corresponding lines) fyrox-math/src/lib.rs:134 — fyrox-math/src/lib.rs:134-154 | fyrox-math/src/lib.rs:296-313 — 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) editor/src/plugins/absm/selection.rs:143 — editor/src/plugins/absm/selection.rs:143-158 | editor/src/plugins/animation/selection.rs:103-116 — 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) editor/src/scene/commands/material.rs:65 — editor/src/scene/commands/material.rs:65-78 | editor/src/scene/commands/material.rs:121-135 — 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) editor/src/plugins/tilemap/palette.rs:1495 — editor/src/plugins/tilemap/palette.rs:1495-1508 | editor/src/plugins/tilemap/palette.rs:1509-1522 — 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) fyrox-impl/src/scene/mesh/buffer.rs:1083 — fyrox-impl/src/scene/mesh/buffer.rs:1083-1096 | fyrox-impl/src/scene/mesh/buffer.rs:1104-1118 — 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) fyrox-impl/src/scene/tilemap/autotile.rs:319 — fyrox-impl/src/scene/tilemap/autotile.rs:319-336 | fyrox-impl/src/scene/tilemap/autotile.rs:486-499 — 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) editor/src/audio/preview.rs:262 — editor/src/audio/preview.rs:262-277 | editor/src/particle.rs:280-293 — 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) editor/src/plugins/absm/mod.rs:125 — editor/src/plugins/absm/mod.rs:125-138 | editor/src/plugins/absm/mod.rs:164-177 — 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) fyrox-ui/src/key.rs:315 — fyrox-ui/src/key.rs:315-328 | fyrox-ui/src/key.rs:514-527 — 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) editor/src/plugins/collider/capsule2d.rs:138 — editor/src/plugins/collider/capsule2d.rs:138-151 | editor/src/plugins/collider/triangle2d.rs:107-121 — 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) editor/src/plugins/tilemap/autotile.rs:98 — editor/src/plugins/tilemap/autotile.rs:98-111 | editor/src/plugins/tilemap/collider_editor.rs:107-120 — 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) fyrox-impl/src/scene/tilemap/update.rs:709 — fyrox-impl/src/scene/tilemap/update.rs:709-722 | fyrox-impl/src/scene/tilemap/update.rs:729-748 — 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) fyrox-core/src/pool/mod.rs:1506 — fyrox-core/src/pool/mod.rs:1506-1519 | fyrox-core/src/pool/mod.rs:1565-1578 — 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) editor/src/plugins/collider/capsule.rs:87 — editor/src/plugins/collider/capsule.rs:87-100 | editor/src/plugins/collider/capsule2d.rs:91-108 — 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) fyrox-impl/src/renderer/mod.rs:368 — fyrox-impl/src/renderer/mod.rs:368-381 | fyrox-impl/src/renderer/mod.rs:391-404 — 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) fyrox-impl/src/scene/animation/absm.rs:311 — fyrox-impl/src/scene/animation/absm.rs:311-324 | fyrox-ui/src/absm.rs:177-193 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×15
  • Edited copy of a member (18 corresponding lines) fyrox-impl/src/resource/gltf/animation.rs:517 — fyrox-impl/src/resource/gltf/animation.rs:517-534 | fyrox-impl/src/resource/gltf/animation.rs:582-609 — 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) fyrox-graphics-wgpu/src/geometry_buffer.rs:189 — fyrox-graphics-wgpu/src/geometry_buffer.rs:189-206 | fyrox-graphics-wgpu/src/geometry_buffer.rs:210-228 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) fyrox-math/src/lib.rs:271 — fyrox-math/src/lib.rs:271-288 | fyrox-math/src/lib.rs:331-350 — 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) editor/src/plugins/tilemap/tile_inspector.rs:594 — editor/src/plugins/tilemap/tile_inspector.rs:594-611 | editor/src/plugins/tilemap/tile_inspector.rs:668-685 — 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) fyrox-build-tools/src/export/utils.rs:85 — fyrox-build-tools/src/export/utils.rs:85-102 | project-manager/src/utils.rs:96-118 — 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) editor/src/plugins/inspector/editors/dyntype.rs:96 — editor/src/plugins/inspector/editors/dyntype.rs:96-113 | editor/src/plugins/inspector/editors/script.rs:102-119 — 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) editor/src/plugins/tilemap/tile_inspector.rs:1237 — editor/src/plugins/tilemap/tile_inspector.rs:1237-1254 | editor/src/plugins/tilemap/tile_inspector.rs:1260-1279 — 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) fyrox-impl/src/scene/graph/mod.rs:1595 — fyrox-impl/src/scene/graph/mod.rs:1595-1612 | fyrox-ui/src/lib.rs:3253-3270 — 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) fyrox-ui/src/curve/mod.rs:1306 — fyrox-ui/src/curve/mod.rs:1306-1323 | fyrox-ui/src/curve/mod.rs:1325-1342 — 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) fyrox-ui/src/curve/mod.rs:1418 — fyrox-ui/src/curve/mod.rs:1418-1439 | fyrox-ui/src/curve/mod.rs:1717-1734 — 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) fyrox-ui/src/inspector/editors/mod.rs:954 — fyrox-ui/src/inspector/editors/mod.rs:954-971 | fyrox-ui/src/inspector/editors/mod.rs:1011-1028 — 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) fyrox-impl/src/resource/fbx/scene/geometry.rs:136 — fyrox-impl/src/resource/fbx/scene/geometry.rs:136-153 | fyrox-impl/src/resource/fbx/scene/geometry.rs:158-177 — 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) editor/src/scene/mod.rs:1092 — editor/src/scene/mod.rs:1092-1113 | editor/src/scene/nullscene.rs:260-277 — 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) fyrox-impl/src/scene/dim2/joint.rs:506 — fyrox-impl/src/scene/dim2/joint.rs:506-523 | fyrox-impl/src/scene/joint.rs:578-597 — 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) fyrox-impl/src/scene/dim2/rigidbody.rs:563 — fyrox-impl/src/scene/dim2/rigidbody.rs:563-580 | fyrox-impl/src/scene/rigidbody.rs:707-727 — 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.
D2 · Cognitive Complexity · fyrox_impl · ×14
  • fyrox_impl::resource::fbx::create_materials (cognitive 110) fyrox-impl/src/resource/fbx/mod.rs:292 — fyrox_impl::resource::fbx::create_materials has cognitive complexity 110 (threshold 15). Drivers by points: if/else 21 (78 pts), loops 4 (19 pts), boolean chains 7, match/switch 1 (6 pts) (nesting depth added 77). 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.
  • fyrox_impl::resource::fbx::convert_mesh (cognitive 59) fyrox-impl/src/resource/fbx/mod.rs:486 — fyrox_impl::resource::fbx::convert_mesh has cognitive complexity 59 (threshold 15). Drivers by points: if/else 7 (32 pts), loops 7 (20 pts), match/switch 1 (5 pts), boolean chains 2 (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.
  • fyrox_impl::renderer::ui_renderer::write_uniform_blocks (cognitive 46) fyrox-impl/src/renderer/ui_renderer.rs:114 — fyrox_impl::renderer::ui_renderer::write_uniform_blocks has cognitive complexity 46 (threshold 15). Drivers by points: match/switch 6 (24 pts), loops 4 (13 pts), if/else 4 (9 pts) (nesting depth added 32). 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.
  • fyrox_impl::resource::fbx::convert (cognitive 44) fyrox-impl/src/resource/fbx/mod.rs:807 — fyrox_impl::resource::fbx::convert has cognitive complexity 44 (threshold 15). Drivers by points: loops 9 (29 pts), if/else 6 (15 pts) (nesting depth added 29). 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.
  • fyrox_impl::resource::fbx::document::ascii::read_ascii (cognitive 37) fyrox-impl/src/resource/fbx/document/ascii.rs:31 — fyrox_impl::resource::fbx::document::ascii::read_ascii has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 6, loops 3 (5 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.
  • fyrox_impl::resource::fbx::document::binary::read_binary_node (cognitive 28) fyrox-impl/src/resource/fbx/document/binary.rs:99 — fyrox_impl::resource::fbx::document::binary::read_binary_node has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • fyrox_impl::renderer::bundle::write_with_material (cognitive 26) fyrox-impl/src/renderer/bundle.rs:238 — fyrox_impl::renderer::bundle::write_with_material has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (23 pts), match/switch 1 (2 pts), loops 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.
  • fyrox_impl::engine::executor::run_normal (cognitive 25) fyrox-impl/src/engine/executor.rs:314 — fyrox_impl::engine::executor::run_normal has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (6 pts), match/switch 3 (6 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.
  • fyrox_impl::resource::fbx::convert_model (cognitive 24) fyrox-impl/src/resource/fbx/mod.rs:667 — fyrox_impl::resource::fbx::convert_model has cognitive complexity 24 (threshold 15). Drivers by points: if/else 20 (34 pts), loops 3 (9 pts), match/switch 1 (3 pts), boolean chains 1 (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. This shape REPEATS in the file: one other method here (fyrox_impl::resource::fbx::convert_model::fill_track) 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.
  • fyrox_impl::scene::graph::physics::make_heightfield (cognitive 23) fyrox-impl/src/scene/graph/physics/mod.rs:687 — fyrox_impl::scene::graph::physics::make_heightfield has cognitive complexity 23 (threshold 15). Drivers by points: loops 6 (15 pts), if/else 4 (8 pts) (nesting depth added 13). 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.
  • fyrox_impl::resource::gltf::material::search_for_path (cognitive 20) fyrox-impl/src/resource/gltf/material.rs:411 — fyrox_impl::resource::gltf::material::search_for_path has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (5 pts), match/switch 1 (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.
  • fyrox_impl::resource::fbx::scene::link_child_with_parent_component (cognitive 18) fyrox-impl/src/resource/fbx/scene/mod.rs:184 — fyrox_impl::resource::fbx::scene::link_child_with_parent_component has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (3 pts) (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.
  • fyrox_impl::resource::fbx::convert_model::fill_track (cognitive 17) fyrox-impl/src/resource/fbx/mod.rs:704 — fyrox_impl::resource::fbx::convert_model::fill_track has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 2 (5 pts), match/switch 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. This shape REPEATS in the file: one other method here (fyrox_impl::resource::fbx::convert_model) 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.
  • fyrox_impl::scene::graph::physics::make_trimesh (cognitive 16) fyrox-impl/src/scene/graph/physics/mod.rs:510 — fyrox_impl::scene::graph::physics::make_trimesh has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (8 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.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×14
  • Edited copy of a member (12 corresponding lines) fyrox-animation/src/machine/node/blendspace.rs:124 — fyrox-animation/src/machine/node/blendspace.rs:124-150 | fyrox-animation/src/machine/node/blendspace.rs:162-210 — 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) fyrox-impl/src/scene/dim2/joint.rs:233 — fyrox-impl/src/scene/dim2/joint.rs:233-244 | fyrox-impl/src/scene/joint.rs:279-292 — 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) fyrox-impl/src/scene/dim2/joint.rs:663 — fyrox-impl/src/scene/dim2/joint.rs:663-674 | fyrox-impl/src/scene/joint.rs:752-764 — 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) fyrox-math/src/ray.rs:283 — fyrox-math/src/ray.rs:283-296 | fyrox-math/src/ray.rs:302-313 — 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) fyrox-ui/src/file_browser/mod.rs:508 — fyrox-ui/src/file_browser/mod.rs:508-519 | fyrox-ui/src/file_browser/mod.rs:521-532 — 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) editor/src/plugins/collider/mod.rs:756 — editor/src/plugins/collider/mod.rs:756-767 | editor/src/plugins/probe.rs:328-339 — 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) editor/src/scene/property.rs:332 — editor/src/scene/property.rs:332-343 | editor/src/scene/selector.rs:327-338 — 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) fyrox-impl/src/scene/dim2/physics/character.rs:103 — fyrox-impl/src/scene/dim2/physics/character.rs:103-114 | fyrox-impl/src/scene/graph/physics/character.rs:181-192 — 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) fyrox-impl/src/scene/graph/mod.rs:1618 — fyrox-impl/src/scene/graph/mod.rs:1618-1629 | fyrox-ui/src/lib.rs:3275-3286 — 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) fyrox-math/src/lib.rs:252 — fyrox-math/src/lib.rs:252-263 | fyrox-math/src/lib.rs:530-541 — 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) fyrox-build-tools/src/export/android.rs:36 — fyrox-build-tools/src/export/android.rs:36-50 | fyrox-build-tools/src/export/pc.rs:26-37 — 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) fyrox-ui/src/color/mod.rs:1188 — fyrox-ui/src/color/mod.rs:1188-1199 | fyrox-ui/src/curve/mod.rs:1405-1416 — 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) editor/src/plugins/settings.rs:191 — editor/src/plugins/settings.rs:191-202 | editor/src/scene/settings/mod.rs:114-125 — 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) fyrox-ui/src/test.rs:168 — fyrox-ui/src/test.rs:168-179 | fyrox-ui/src/test.rs:181-198 — 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 · Duplicated block (12 lines × 2) · ×14
  • Duplicated block (12 lines × 2) editor/src/audio/preview.rs:183 — editor/src/audio/preview.rs:183-194 | editor/src/particle.rs:226-237 — 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 `editor/src/audio/preview.rs:183` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) editor/src/plugins/collider/cuboid.rs:156 — editor/src/plugins/collider/cuboid.rs:156-167 | editor/src/plugins/collider/cuboid2d.rs:140-151 — before extracting anything, compare `editor/src/plugins/collider/cuboid.rs` and `editor/src/plugins/collider/cuboid2d.rs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `editor/src/plugins/collider/cuboid.rs:156` it does not close everything it opens, so those exact lines 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) editor/src/plugins/ragdoll.rs:1110 — editor/src/plugins/ragdoll.rs:1110-1121 | editor/src/scene/property.rs:631-642 — 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 `editor/src/plugins/ragdoll.rs:1110` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/resource/gltf/surface.rs:498 — fyrox-impl/src/resource/gltf/surface.rs:498-509 | fyrox-impl/src/resource/gltf/surface.rs:550-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. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/resource/gltf/surface.rs:498` it does not close everything it opens, so those 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, `fyrox-impl/src/resource/gltf/surface.rs:562` calls `next`, `read_valid_index` and `fyrox-impl/src/resource/gltf/surface.rs:510` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) fyrox-ui/src/file_browser/fs_tree.rs:85 — fyrox-ui/src/file_browser/fs_tree.rs:85-96 | fyrox-ui/src/file_browser/fs_tree.rs:98-109 — both copies are in the same file, so extract the 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) fyrox-ui/src/messagebox.rs:373 — fyrox-ui/src/messagebox.rs:373-384 | fyrox-ui/src/messagebox.rs:427-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 `fyrox-ui/src/messagebox.rs:373` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) fyrox-animation/src/machine/node/blendspace.rs:129 — fyrox-animation/src/machine/node/blendspace.rs:129-140 | fyrox-animation/src/machine/node/blendspace.rs:163-174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-animation/src/machine/node/blendspace.rs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) editor/src/plugins/tilemap/tile_inspector.rs:445 — editor/src/plugins/tilemap/tile_inspector.rs:445-456 | editor/src/plugins/tilemap/tileset.rs:153-164 — 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 `editor/src/plugins/tilemap/tile_inspector.rs:445` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/rigidbody.rs:504 — fyrox-impl/src/scene/dim2/rigidbody.rs:504-515 | fyrox-impl/src/scene/rigidbody.rs:645-656 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) editor/src/plugins/animation/toolbar.rs:636 — editor/src/plugins/animation/toolbar.rs:636-648 | editor/src/plugins/animation/toolbar.rs:653-664 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/animation/toolbar.rs:636` it begins part-way through the construct above it, so those exact lines 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) editor/src/scene/property.rs:444 — editor/src/scene/property.rs:444-456 | editor/src/scene/selector.rs:382-393 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/scene/property.rs:444` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) editor/src/scene_viewer/mod.rs:399 — editor/src/scene_viewer/mod.rs:399-410 | editor/src/scene_viewer/mod.rs:424-435 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/scene_viewer/mod.rs:399` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) fyrox-build-tools/src/lib.rs:183 — fyrox-build-tools/src/lib.rs:183-194 | fyrox-build-tools/src/lib.rs:204-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-build-tools/src/lib.rs:183` it begins part-way through the construct above it, so those 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, `fyrox-build-tools/src/lib.rs:202` calls `to_string` and `fyrox-build-tools/src/lib.rs:181` 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) editor/src/audio/mod.rs:229 — editor/src/audio/mod.rs:229-240 | editor/src/audio/mod.rs:260-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 `editor/src/audio/mod.rs:229` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×12
  • Edited copy of a member (13 corresponding lines) fyrox-core/src/sstorage.rs:229 — fyrox-core/src/sstorage.rs:229-244 | fyrox-core/src/sstorage.rs:247-259 — 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) editor/src/plugins/tilemap/commands.rs:1142 — editor/src/plugins/tilemap/commands.rs:1142-1154 | editor/src/plugins/tilemap/commands.rs:1192-1204 — 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) editor/src/ui_scene/selection.rs:57 — editor/src/ui_scene/selection.rs:57-69 | editor/src/world/selection.rs:58-71 — 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) editor/src/plugins/tilemap/tile_inspector.rs:299 — editor/src/plugins/tilemap/tile_inspector.rs:299-311 | editor/src/plugins/tilemap/tile_inspector.rs:313-325 — 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) editor/src/plugins/tilemap/handle_editor.rs:206 — editor/src/plugins/tilemap/handle_editor.rs:206-218 | editor/src/plugins/tilemap/handle_editor.rs:256-269 — 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) editor/src/plugins/tilemap/tile_inspector.rs:327 — editor/src/plugins/tilemap/tile_inspector.rs:327-339 | editor/src/plugins/tilemap/tile_inspector.rs:341-353 — 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) fyrox-graphics-wgpu/src/framebuffer.rs:220 — fyrox-graphics-wgpu/src/framebuffer.rs:220-232 | fyrox-graphics-wgpu/src/framebuffer.rs:238-250 — 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) editor/src/scene/commands/graph.rs:503 — editor/src/scene/commands/graph.rs:503-516 | editor/src/ui_scene/commands/graph.rs:90-102 — 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) editor/src/ui_scene/menu.rs:76 — editor/src/ui_scene/menu.rs:76-88 | editor/src/world/menu.rs:92-107 — 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) fyrox-impl/src/scene/dim2/joint.rs:203 — fyrox-impl/src/scene/dim2/joint.rs:203-215 | fyrox-impl/src/scene/joint.rs:249-261 — 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) fyrox-core-derive/src/reflect/prop.rs:185 — fyrox-core-derive/src/reflect/prop.rs:185-197 | fyrox-core-derive/src/reflect/prop.rs:200-212 — 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) editor/src/plugins/collider/segment.rs:79 — editor/src/plugins/collider/segment.rs:79-91 | editor/src/plugins/collider/segment2d.rs:60-73 — 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.
D35 · Change Coupling · Change coupling · ×11
  • Change coupling: selection.rs ↔ selection.rs editor/src/ui_scene/selection.rs:1 — `editor/src/ui_scene/selection.rs` and `editor/src/world/selection.rs` change together 67% of the time (12 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 12 shared commits counted here, the most recent 3 are `edd9b93b` fixed type editors for ui/game scene; `d332af41` improve validation of widget deletion; `1564436f` unify selection deletion for game/ui scenes — run `git show` on any of them.
  • Change coupling: enumeration.rs ↔ inspectable.rs fyrox-ui/src/inspector/editors/enumeration.rs:1 — `fyrox-ui/src/inspector/editors/enumeration.rs` and `fyrox-ui/src/inspector/editors/inspectable.rs` change together 61% of the time (14 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `135dc00c` include type name of fields in inspector tooltips; `b88e4a09` fixed layout of inheritable property editor + styling; `be14535d` typed handles for `Inspector` widget — run `git show` on any of them.
  • Change coupling: mod.rs ↔ mod.rs editor/src/plugins/absm/state_graph/mod.rs:1 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` change together 58% of the time (19 of the 33 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 19 shared commits counted here, the most recent 3 are `8d815db3` keep previous absm selected in the editor; `da549573` more typed handles for widgets; `13818290` allow comparison of base and derived handles — run `git show` on any of them.
  • Change coupling: mod.rs ↔ selection.rs editor/src/audio/mod.rs:1 — `editor/src/audio/mod.rs` and `editor/src/plugins/animation/selection.rs` change together 57% of the time (8 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) 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 `edd9b93b` fixed type editors for ui/game scene; `7eaf5def` fixed doc provider; `bee807ea` fixed downcasting for widgets and scene nodes — run `git show` on any of them.
  • Change coupling: gradient.rs ↔ mod.rs fyrox-ui/src/color/gradient.rs:1 — `fyrox-ui/src/color/gradient.rs` and `fyrox-ui/src/curve/mod.rs` change together 55% of the time (6 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 6 shared commits counted here, the most recent 3 are `d362f35c` experimental ui style system refactoring; `113945a0` finished transition to typed handles for ui; `78c43162` add layout invalidation for all widgets with custom draw methods — run `git show` on any of them.
  • Change coupling: camera.rs ↔ decal.rs fyrox-impl/src/scene/camera.rs:1 — `fyrox-impl/src/scene/camera.rs` and `fyrox-impl/src/scene/decal.rs` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `11522405` simplified usage of `ResourceManager::request` + fixed tests (at that commit the files were still `src/scene/camera.rs` and `src/scene/decal.rs`); `ddae1609` tests fix (at that commit the files were still `src/scene/camera.rs` and `src/scene/decal.rs`); `605e10c7` drop backward compatibility code (at that commit the files were still `src/scene/camera.rs` and `src/scene/decal.rs`) — run `git show` on any of them.
  • Change coupling: panel.rs ↔ particle.rs editor/src/camera/panel.rs:1 — `editor/src/camera/panel.rs` and `editor/src/particle.rs` change together 53% of the time (9 of the 17 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 `df1a92e3` typed handles for `CheckBox` widget; `a420478c` Improving how selection changes are handled; `bbc7c2e8` refactored check box message to use `send/post` — run `git show` on any of them.
  • Change coupling: collection.rs ↔ inspectable.rs fyrox-ui/src/inspector/editors/collection.rs:1 — `fyrox-ui/src/inspector/editors/collection.rs` and `fyrox-ui/src/inspector/editors/inspectable.rs` change together 52% of the time (12 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `135dc00c` include type name of fields in inspector tooltips; `b88e4a09` fixed layout of inheritable property editor + styling; `092d30b4` removed redundant trait bounds — run `git show` on any of them.
  • Change coupling: selection.rs ↔ selection.rs editor/src/interaction/navmesh/selection.rs:1 — `editor/src/interaction/navmesh/selection.rs` and `editor/src/ui_scene/selection.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 `edd9b93b` fixed type editors for ui/game scene; `7eaf5def` fixed doc provider; `bee807ea` fixed downcasting for widgets and scene nodes — run `git show` on any of them.
  • Change coupling: selection.rs ↔ selection.rs editor/src/interaction/navmesh/selection.rs:1 — `editor/src/interaction/navmesh/selection.rs` and `editor/src/world/selection.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 `edd9b93b` fixed type editors for ui/game scene; `7eaf5def` fixed doc provider; `bee807ea` fixed downcasting for widgets and scene nodes — run `git show` on any of them.
  • Change coupling: dialog.rs ↔ menu.rs editor/src/scene/dialog.rs:1 — `editor/src/scene/dialog.rs` and `editor/src/world/menu.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 `27835191` check for cross-refs when deleting widgets; `1564436f` unify selection deletion for game/ui scenes; `128d6c57` moved command stack to EditorSceneEntry +fixed animation commands for ui (at that commit the file was still `editor/src/world/graph/menu.rs`) — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×11
  • Edited copy of a member (16 corresponding lines) fyrox-core/src/visitor/mod.rs:550 — fyrox-core/src/visitor/mod.rs:550-565 | fyrox-core/src/visitor/mod.rs:570-585 — 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) fyrox-core-derive/src/reflect.rs:62 — fyrox-core-derive/src/reflect.rs:62-77 | fyrox-core-derive/src/reflect.rs:84-113 — 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) editor/src/plugins/absm/mod.rs:791 — editor/src/plugins/absm/mod.rs:791-806 | editor/src/plugins/animation/mod.rs:958-974 — 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) fyrox-math/src/octree.rs:130 — fyrox-math/src/octree.rs:130-145 | fyrox-math/src/octree.rs:165-180 — 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) editor/src/command/mod.rs:741 — editor/src/command/mod.rs:741-758 | editor/src/command/mod.rs:816-831 — 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) fyrox-impl/src/scene/particle_system/emitter/base.rs:99 — fyrox-impl/src/scene/particle_system/emitter/base.rs:99-114 | fyrox-impl/src/scene/particle_system/emitter/base.rs:426-445 — 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) editor/src/plugins/tilemap/autotile.rs:895 — editor/src/plugins/tilemap/autotile.rs:895-910 | editor/src/plugins/tilemap/wfc.rs:908-923 — 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) editor/src/plugins/export.rs:586 — editor/src/plugins/export.rs:586-602 | editor/src/plugins/settings.rs:368-383 — 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) fyrox-resource/src/manager.rs:668 — fyrox-resource/src/manager.rs:668-683 | fyrox-resource/src/manager.rs:691-706 — 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) fyrox-impl/src/resource/gltf/mod.rs:302 — fyrox-impl/src/resource/gltf/mod.rs:302-317 | fyrox-texture/src/loader.rs:50-65 — 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) editor/src/plugins/absm/parameter.rs:131 — editor/src/plugins/absm/parameter.rs:131-146 | editor/src/plugins/export.rs:470-487 — 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.
D1 · Cyclomatic Complexity · fyrox_impl · ×10
  • fyrox_impl::resource::fbx::create_materials (cyclomatic 32) fyrox-impl/src/resource/fbx/mod.rs:292 — fyrox_impl::resource::fbx::create_materials 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.
  • fyrox_impl::renderer::bundle::write_with_material (cyclomatic 27) fyrox-impl/src/renderer/bundle.rs:238 — fyrox_impl::renderer::bundle::write_with_material 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.
  • fyrox_impl::resource::fbx::convert_model (cyclomatic 23) fyrox-impl/src/resource/fbx/mod.rs:667 — fyrox_impl::resource::fbx::convert_model has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 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.
  • fyrox_impl::resource::fbx::document::ascii::read_ascii (cyclomatic 22) fyrox-impl/src/resource/fbx/document/ascii.rs:31 — fyrox_impl::resource::fbx::document::ascii::read_ascii 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.
  • fyrox_impl::resource::fbx::scene::link_child_with_parent_component (cyclomatic 22) fyrox-impl/src/resource/fbx/scene/mod.rs:184 — fyrox_impl::resource::fbx::scene::link_child_with_parent_component 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.
  • fyrox_impl::engine::executor::run_normal (cyclomatic 18) fyrox-impl/src/engine/executor.rs:314 — fyrox_impl::engine::executor::run_normal 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.
  • fyrox_impl::resource::fbx::convert_mesh (cyclomatic 18) fyrox-impl/src/resource/fbx/mod.rs:486 — fyrox_impl::resource::fbx::convert_mesh 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.
  • fyrox_impl::resource::fbx::document::binary::read_binary_node (cyclomatic 17) fyrox-impl/src/resource/fbx/document/binary.rs:99 — fyrox_impl::resource::fbx::document::binary::read_binary_node 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.
  • fyrox_impl::renderer::ui_renderer::write_uniform_blocks (cyclomatic 16) fyrox-impl/src/renderer/ui_renderer.rs:114 — fyrox_impl::renderer::ui_renderer::write_uniform_blocks 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.
  • fyrox_impl::resource::fbx::convert (cyclomatic 16) fyrox-impl/src/resource/fbx/mod.rs:807 — fyrox_impl::resource::fbx::convert has cyclomatic complexity 16 (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.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×10
  • Edited copy of a member (11 corresponding lines) editor/src/plugins/absm/mod.rs:808 — editor/src/plugins/absm/mod.rs:808-822 | editor/src/plugins/animation/mod.rs:976-986 — 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) fyrox-impl/src/scene/mesh/buffer.rs:1279 — fyrox-impl/src/scene/mesh/buffer.rs:1279-1289 | fyrox-impl/src/scene/mesh/buffer.rs:1293-1304 — 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) editor/src/plugins/tilemap/autotile.rs:827 — editor/src/plugins/tilemap/autotile.rs:827-837 | editor/src/plugins/tilemap/wfc.rs:827-837 — 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) fyrox-impl/src/resource/fbx/scene/geometry.rs:59 — fyrox-impl/src/resource/fbx/scene/geometry.rs:59-72 | fyrox-impl/src/resource/fbx/scene/mod.rs:587-597 — 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) editor/src/plugins/tilemap/tile_inspector.rs:395 — editor/src/plugins/tilemap/tile_inspector.rs:395-405 | editor/src/plugins/tilemap/tile_inspector.rs:407-417 — 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) editor/src/plugins/export.rs:537 — editor/src/plugins/export.rs:537-548 | editor/src/plugins/light.rs:488-498 — 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) editor/src/plugins/tilemap/handle_editor.rs:231 — editor/src/plugins/tilemap/handle_editor.rs:231-241 | fyrox-ui/src/inspector/editors/quat.rs:128-141 — 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) fyrox-ui/src/text.rs:356 — fyrox-ui/src/text.rs:356-366 | fyrox-ui/src/text_box.rs:485-495 — 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) fyrox-impl/src/scene/tilemap/brush.rs:334 — fyrox-impl/src/scene/tilemap/brush.rs:334-344 | fyrox-impl/src/scene/tilemap/tileset.rs:2021-2031 — 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) fyrox-ui/src/text.rs:386 — fyrox-ui/src/text.rs:386-396 | fyrox-ui/src/text_box.rs:986-996 — 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 (6 corresponding lines) · ×10
  • Edited copy of a member (6 corresponding lines) fyrox-core/src/color.rs:858 — fyrox-core/src/color.rs:858-863 | fyrox-core/src/color.rs:876-881 — 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) fyrox-ui/src/draw.rs:121 — fyrox-ui/src/draw.rs:121-126 | fyrox-ui/src/draw.rs:853-858 — 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) editor/src/scene/commands/graph.rs:587 — editor/src/scene/commands/graph.rs:587-594 | editor/src/ui_scene/commands/graph.rs:370-375 — 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) fyrox-graphics-gl/src/buffer.rs:105 — fyrox-graphics-gl/src/buffer.rs:105-112 | fyrox-graphics-gl/src/texture.rs:338-343 — 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) editor/src/scene/commands/effect.rs:109 — editor/src/scene/commands/effect.rs:109-120 | editor/src/scene/commands/graph.rs:377-382 — 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) editor/src/scene/commands/graph.rs:430 — editor/src/scene/commands/graph.rs:430-435 | editor/src/ui_scene/commands/graph.rs:104-110 — 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) editor/src/ui_scene/utils.rs:110 — editor/src/ui_scene/utils.rs:110-115 | editor/src/world/graph.rs:110-116 — 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) editor/src/ui_scene/utils.rs:179 — editor/src/ui_scene/utils.rs:179-184 | editor/src/world/graph.rs:152-158 — 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) fyrox-ui/src/stack_panel.rs:273 — fyrox-ui/src/stack_panel.rs:273-278 | fyrox-ui/src/wrap_panel.rs:297-303 — 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) editor/src/plugins/tilemap/macro_inspector.rs:62 — editor/src/plugins/tilemap/macro_inspector.rs:62-67 | editor/src/plugins/tilemap/tile_inspector.rs:585-590 — 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×10
  • Duplicated block (15 lines × 2) editor/src/plugins/ragdoll.rs:1067 — editor/src/plugins/ragdoll.rs:1067-1081 | editor/src/scene/dialog.rs:90-104 — 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 `editor/src/plugins/ragdoll.rs:1067` it begins part-way through the construct above it, so those exact lines 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) editor/src/ui_scene/interaction/mod.rs:115 — editor/src/ui_scene/interaction/mod.rs:115-129 | editor/src/ui_scene/interaction/move_mode.rs:144-158 — 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 `editor/src/ui_scene/interaction/mod.rs:115` it does not close everything it opens, so those exact lines 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) fyrox-animation/src/machine/layer.rs:349 — fyrox-animation/src/machine/layer.rs:349-363 | fyrox-animation/src/machine/layer.rs:365-379 — both copies are in the same file, so extract the 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 (15 lines × 2) fyrox-build-tools/src/export/utils.rs:88 — fyrox-build-tools/src/export/utils.rs:88-102 | project-manager/src/utils.rs:104-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. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-build-tools/src/export/utils.rs:88` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/collider.rs:547 — fyrox-impl/src/scene/collider.rs:547-561 | fyrox-impl/src/scene/dim2/collider.rs:350-364 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) fyrox-math/src/lib.rs:140 — fyrox-math/src/lib.rs:140-154 | fyrox-math/src/lib.rs:336-350 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-math/src/lib.rs:140` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) fyrox-ui/src/canvas.rs:104 — fyrox-ui/src/canvas.rs:104-118 | fyrox-ui/src/inspector/editors/texture_slice.rs:230-244 — 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 (15 lines × 2) fyrox-ui/src/inspector/editors/cell.rs:84 — fyrox-ui/src/inspector/editors/cell.rs:84-98 | fyrox-ui/src/inspector/editors/cell.rs:130-144 — both copies are in the same file, so extract the 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) fyrox-ui/src/inspector/editors/mod.rs:957 — fyrox-ui/src/inspector/editors/mod.rs:957-971 | fyrox-ui/src/inspector/editors/mod.rs:1014-1028 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/inspector/editors/mod.rs:957` it begins part-way through the construct above it, so those exact lines 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) fyrox-ui/src/nine_patch.rs:384 — fyrox-ui/src/nine_patch.rs:384-398 | fyrox-ui/src/nine_patch.rs:486-500 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/nine_patch.rs:384` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D6 · Cohesion (LCOM4) · Low cohesion · ×10
  • Low cohesion: TileSetUpdate (LCOM4 11) fyrox-impl/src/scene/tilemap/update.rs:120 — TileSetUpdate's methods fall into 11 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 11 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: AutoTileMacro (LCOM4 10) editor/src/plugins/tilemap/autotile.rs:114 — AutoTileMacro's methods fall into 10 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 10 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: WfcMacro (LCOM4 8) editor/src/plugins/tilemap/wfc.rs:66 — WfcMacro'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: TransTilesUpdate (LCOM4 8) fyrox-impl/src/scene/tilemap/update.rs:608 — TransTilesUpdate'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: Pool (LCOM4 6) fyrox-core/src/pool/mod.rs:69 — Pool'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: Widget (LCOM4 6) fyrox-ui/src/widget.rs:572 — Widget'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: Visitor (LCOM4 4) fyrox-core/src/visitor/mod.rs:312 — Visitor'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: TypeArgs (LCOM4 4) fyrox-core-derive/src/reflect/args.rs:39 — TypeArgs'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: SoundSource (LCOM4 4) fyrox-sound/src/source.rs:81 — SoundSource'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: CurveEditorBuilder (LCOM4 4) fyrox-ui/src/curve/mod.rs:1737 — CurveEditorBuilder'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.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×9
  • Edited copy of a member (19 corresponding lines) fyrox-impl/src/scene/terrain/brushstroke/mod.rs:555 — fyrox-impl/src/scene/terrain/brushstroke/mod.rs:555-573 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:574-592 — 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) editor/src/plugins/collider/cuboid.rs:155 — editor/src/plugins/collider/cuboid.rs:155-177 | editor/src/plugins/collider/cuboid2d.rs:139-157 — 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) fyrox-ui/src/draw.rs:425 — fyrox-ui/src/draw.rs:425-449 | fyrox-ui/src/draw.rs:458-476 — 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) editor/src/plugins/collider/capsule.rs:62 — editor/src/plugins/collider/capsule.rs:62-80 | editor/src/plugins/collider/capsule2d.rs:62-84 — 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) editor/src/scene/property.rs:96 — editor/src/scene/property.rs:96-114 | editor/src/scene/selector.rs:218-236 — 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) fyrox-impl/src/scene/graph/mod.rs:553 — fyrox-impl/src/scene/graph/mod.rs:553-572 | fyrox-impl/src/scene/graph/mod.rs:591-609 — 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) editor/src/asset/preview/mod.rs:522 — editor/src/asset/preview/mod.rs:522-542 | editor/src/asset/preview/mod.rs:572-590 — 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) fyrox-animation/src/container.rs:182 — fyrox-animation/src/container.rs:182-200 | fyrox-animation/src/container.rs:203-225 — 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) editor/src/scene/commands/mod.rs:286 — editor/src/scene/commands/mod.rs:286-305 | editor/src/ui_scene/commands/widget.rs:103-121 — 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 · Duplicated block (16 lines × 2) · ×9
  • Duplicated block (16 lines × 2) editor/src/asset/preview/mod.rs:527 — editor/src/asset/preview/mod.rs:527-542 | editor/src/asset/preview/mod.rs:575-590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/asset/preview/mod.rs:527` it begins part-way through the construct above it, so those 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, `editor/src/asset/preview/mod.rs:524` calls `new_embedded`, `from_shader` and `editor/src/asset/preview/mod.rs:573` 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) editor/src/interaction/select_mode.rs:159 — editor/src/interaction/select_mode.rs:159-174 | editor/src/ui_scene/interaction/mod.rs:174-189 — 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 (16 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:162 — editor/src/plugins/inspector/editors/dyntype.rs:162-177 | editor/src/plugins/inspector/editors/script.rs:232-247 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/dyntype.rs:162` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 2) editor/src/plugins/tilemap/palette.rs:2123 — editor/src/plugins/tilemap/palette.rs:2123-2138 | fyrox-ui/src/color/mod.rs:235-250 — 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 `editor/src/plugins/tilemap/palette.rs:2123` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/mod.rs:252 — fyrox-impl/src/scene/dim2/physics/mod.rs:252-267 | fyrox-impl/src/scene/graph/physics/mod.rs:376-391 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:252` it does not close everything it opens, so those 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 `c` to `&rapier2d::geometry::ContactPair` in one and `&rapier3d::geometry::ContactPair` 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 (16 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:726 — fyrox-impl/src/scene/dim2/physics/mod.rs:726-741 | fyrox-impl/src/scene/graph/physics/mod.rs:1169-1184 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `crate) fn update(&mut` in one and `super) fn update(&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 after the matched lines, `fyrox-impl/src/scene/graph/physics/mod.rs:1185` calls `default` and `fyrox-impl/src/scene/dim2/physics/mod.rs:742` 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 (16 lines × 2) fyrox-ui/src/inspector/editors/array.rs:259 — fyrox-ui/src/inspector/editors/array.rs:259-274 | fyrox-ui/src/inspector/editors/collection.rs:403-418 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `fyrox-ui/src/inspector/editors/array.rs:259` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/inspector/editors/collection.rs:533 — fyrox-ui/src/inspector/editors/collection.rs:533-548 | fyrox-ui/src/inspector/editors/enumeration.rs:413-428 — 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 `fyrox-ui/src/inspector/editors/collection.rs:533` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) fyrox-impl/src/scene/debug.rs:589 — fyrox-impl/src/scene/debug.rs:589-604 | fyrox-impl/src/scene/mesh/surface.rs:560-575 — 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 `fyrox-impl/src/scene/debug.rs:589` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D2 · Cognitive Complexity · Editor · ×8
  • Editor::handle_hotkeys (cognitive 73) editor/src/lib.rs:1198 — Editor::handle_hotkeys has cognitive complexity 73 (threshold 15). Drivers by points: if/else 37 (69 pts), boolean chains 4 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Editor::handle_modes (cognitive 70) editor/src/lib.rs:2354 — Editor::handle_modes has cognitive complexity 70 (threshold 15). Drivers by points: if/else 17 (59 pts), match/switch 4 (10 pts), boolean chains 1 (nesting depth added 48). 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.
  • Editor::update (cognitive 39) editor/src/lib.rs:2558 — Editor::update has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (22 pts), loops 3 (7 pts), match/switch 2 (7 pts), boolean chains 3 (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.
  • Editor::handle_reloaded_resources (cognitive 28) editor/src/lib.rs:2463 — Editor::handle_reloaded_resources has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (3 pts) (nesting depth added 14). Of this number, 24 points are the body's own statements and 4 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.
  • Editor::run (cognitive 27) editor/src/lib.rs:3072 — Editor::run has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 2 (3 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.
  • Editor::handle_ui_message (cognitive 23) editor/src/lib.rs:1369 — Editor::handle_ui_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 3, 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.
  • Editor::set_play_mode (cognitive 16) editor/src/lib.rs:1605 — Editor::set_play_mode has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 5, match/switch 1 (nesting depth added 6). 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.
  • Editor::load_scene (cognitive 16) editor/src/lib.rs:2039 — Editor::load_scene has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), match/switch 3 (7 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×8
  • Members sharing a duplicated core (4 members, 50+ identical tokens) editor/src/plugins/collider/mod.rs:406 — editor/src/plugins/collider/mod.rs:406-482 | editor/src/plugins/collider/mod.rs:539-632 | editor/src/plugins/probe.rs:179-202 | editor/src/plugins/probe.rs:239-273 — 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) editor/src/plugins/tilemap/autotile.rs:469 — editor/src/plugins/tilemap/autotile.rs:469-539 | editor/src/plugins/tilemap/autotile.rs:618-641 | editor/src/plugins/tilemap/wfc.rs:505-627 | editor/src/plugins/tilemap/wfc.rs:637-682 — 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) editor/src/plugins/tilemap/properties_tab.rs:668 — editor/src/plugins/tilemap/properties_tab.rs:668-684 | editor/src/plugins/tilemap/properties_tab.rs:691-717 | editor/src/plugins/tilemap/properties_tab.rs:724-750 | editor/src/plugins/tilemap/properties_tab.rs:757-783 — 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) fyrox-graphics-gl/src/texture.rs:346 — fyrox-graphics-gl/src/texture.rs:346-394 | fyrox-graphics-gl/src/texture.rs:403-632 | fyrox-graphics-wgpu/src/texture.rs:297-416 | fyrox-graphics-wgpu/src/texture.rs:440-479 — 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) fyrox-impl/src/resource/gltf/animation.rs:484 — fyrox-impl/src/resource/gltf/animation.rs:484-506 | fyrox-impl/src/resource/gltf/animation.rs:543-572 | fyrox-impl/src/resource/gltf/animation.rs:619-641 | fyrox-impl/src/resource/gltf/animation.rs:650-680 — 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) fyrox-impl/src/scene/debug.rs:123 — fyrox-impl/src/scene/debug.rs:123-199 | fyrox-impl/src/scene/debug.rs:202-278 | fyrox-impl/src/scene/debug.rs:286-378 | fyrox-impl/src/scene/debug.rs:542-575 — 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) fyrox-impl/src/scene/debug.rs:700 — fyrox-impl/src/scene/debug.rs:700-746 | fyrox-impl/src/scene/debug.rs:757-830 | fyrox-impl/src/scene/mesh/surface.rs:616-689 | fyrox-impl/src/scene/mesh/surface.rs:757-860 — 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) fyrox-ui/src/inspector/editors/cell.rs:78 — fyrox-ui/src/inspector/editors/cell.rs:78-119 | fyrox-ui/src/inspector/editors/cell.rs:124-166 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:122-160 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:178-214 — 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.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×8
  • Edited copy of a member (25 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs:671 — fyrox-impl/src/scene/dim2/physics/mod.rs:671-695 | fyrox-impl/src/scene/graph/physics/mod.rs:1114-1138 — 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) fyrox-impl/src/scene/tilemap/tileset.rs:388 — fyrox-impl/src/scene/tilemap/tileset.rs:388-413 | fyrox-impl/src/scene/tilemap/tileset.rs:421-445 — 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) fyrox-build-tools/src/export/utils.rs:139 — fyrox-build-tools/src/export/utils.rs:139-163 | fyrox-build-tools/src/export/utils.rs:165-194 — 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) editor/src/plugins/tilemap/panel.rs:80 — editor/src/plugins/tilemap/panel.rs:80-105 | editor/src/plugins/tilemap/tile_prop_editor.rs:772-796 — 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) editor/src/ui_scene/utils.rs:254 — editor/src/ui_scene/utils.rs:254-278 | editor/src/world/graph.rs:227-253 — 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) editor/src/plugins/tilemap/mod.rs:920 — editor/src/plugins/tilemap/mod.rs:920-944 | editor/src/plugins/tilemap/properties_tab.rs:135-162 — 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) editor/src/plugins/tilemap/properties_tab.rs:790 — editor/src/plugins/tilemap/properties_tab.rs:790-814 | editor/src/plugins/tilemap/properties_tab.rs:815-840 — 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) fyrox-build-tools/src/lib.rs:105 — fyrox-build-tools/src/lib.rs:105-129 | fyrox-build-tools/src/lib.rs:232-256 — 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 · Duplicated block (17 lines × 2) · ×8
  • Duplicated block (17 lines × 2) editor/src/interaction/rotate_mode.rs:236 — editor/src/interaction/rotate_mode.rs:236-252 | editor/src/interaction/scale_mode.rs:215-231 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/interaction/rotate_mode.rs:236` it begins part-way through the construct above it, so those 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, `editor/src/interaction/rotate_mode.rs:253` calls `is_none`, `reset_state` and `editor/src/interaction/scale_mode.rs:232` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (17 lines × 2) editor/src/plugins/absm/state_graph/context.rs:386 — editor/src/plugins/absm/state_graph/context.rs:386-402 | editor/src/plugins/absm/state_viewer/context.rs:345-361 — 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 `editor/src/plugins/absm/state_graph/context.rs:386` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) editor/src/plugins/absm/state_graph/mod.rs:96 — editor/src/plugins/absm/state_graph/mod.rs:96-112 | editor/src/plugins/absm/state_viewer/mod.rs:184-200 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/absm/state_graph/mod.rs:96` it begins part-way through the construct above it, so those exact lines 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) editor/src/world/mod.rs:523 — editor/src/world/mod.rs:523-539 | editor/src/world/mod.rs:582-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/world/mod.rs:523` it does not close everything it opens, so those exact lines 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) fyrox-core/src/pool/mod.rs:644 — fyrox-core/src/pool/mod.rs:644-660 | fyrox-core/src/pool/mod.rs:699-715 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-core/src/pool/mod.rs:644` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/mod.rs:421 — fyrox-impl/src/scene/dim2/physics/mod.rs:421-437 | fyrox-impl/src/scene/graph/physics/mod.rs:781-797 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) fyrox-impl/src/scene/tilemap/effect.rs:237 — fyrox-impl/src/scene/tilemap/effect.rs:237-253 | fyrox-impl/src/scene/tilemap/effect.rs:270-286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/tilemap/effect.rs:237` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) fyrox-ui/src/key.rs:265 — fyrox-ui/src/key.rs:265-281 | fyrox-ui/src/key.rs:464-480 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/key.rs:265` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
X15 · Unvalidated length from an untrusted reader · Length read from the parsed input is spent without ever being bounded · ×8
  • Length read from the parsed input is spent without ever being bounded fyrox-impl/src/resource/fbx/document/binary.rs:62 — `compressed_length` is read from the bytes being parsed at line 54 (`read_u32`), then used to size a `vec![…; n]` at line 62 — and nowhere in its scope is `compressed_length` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `compressed_length` against the bytes actually remaining and a maximum the format allows before allocating.
  • Length read from the parsed input is spent without ever being bounded fyrox-impl/src/resource/fbx/document/binary.rs:79 — `length` is read from the bytes being parsed at line 78 (`read_u32`), then used to size a `vec![…; n]` at line 79 — and nowhere in its scope is `length` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `length` against the bytes actually remaining and a maximum the format allows before allocating.
  • Length read from the parsed input is spent without ever being bounded fyrox-core/src/visitor/reader/binary.rs:67 — `name_len` is read from the bytes being parsed at line 66 (`read_u32`), then used to size a `vec![…; n]` at line 67 — and nowhere in its scope is `name_len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `name_len` against the bytes actually remaining and a maximum the format allows before allocating.
  • Length read from the parsed input is spent without ever being bounded fyrox-core/src/visitor/reader/binary.rs:105 — `len` is read from the bytes being parsed at line 104 (`read_u32`), then used to size a `vec![…; n]` at line 105 — and nowhere in its scope is `len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining and a maximum the format allows before allocating.
  • Length read from the parsed input is spent without ever being bounded fyrox-core/src/visitor/reader/binary.rs:143 — `data_size` is read from the bytes being parsed at line 142 (`read_u64`), then used to size a `vec![…; n]` at line 143 — and nowhere in its scope is `data_size` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `data_size` against the bytes actually remaining and a maximum the format allows before allocating.
  • Length read from the parsed input is spent without ever being bounded fyrox-core/src/visitor/reader/binary.rs:195 — `len` is read from the bytes being parsed at line 194 (`read_u32`), then used to size a `vec![…; n]` at line 195 — and nowhere in its scope is `len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining and a maximum the format allows before allocating.
  • Length read from the parsed input is spent without ever being bounded fyrox-core/src/visitor/reader/binary.rs:209 — `name_len` is read from the bytes being parsed at line 208 (`read_u32`), then used to size a `vec![…; n]` at line 209 — and nowhere in its scope is `name_len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `name_len` against the bytes actually remaining and a maximum the format allows before allocating.
  • Length read from the parsed input is spent without ever being bounded fyrox-core/src/visitor/reader/binary.rs:226 — `child_count` is read from the bytes being parsed at line 225 (`read_u32`), then used to size a `Vec::with_capacity` at line 226 — and nowhere in its scope is `child_count` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `child_count` against the bytes actually remaining and a maximum the format allows before allocating.
D2 · Cognitive Complexity · UserInterface · ×7
  • UserInterface::process_os_event (cognitive 192) fyrox-ui/src/lib.rs:2775 — UserInterface::process_os_event has cognitive complexity 192 (threshold 15). Drivers by points: if/else 45 (144 pts), loops 7 (26 pts), match/switch 7 (18 pts), boolean chains 4 (nesting depth added 129). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • UserInterface::poll_single_message (cognitive 83) fyrox-ui/src/lib.rs:2353 — UserInterface::poll_single_message has cognitive complexity 83 (threshold 15). Drivers by points: if/else 25 (59 pts), match/switch 5 (12 pts), loops 3 (7 pts), boolean chains 5 (nesting depth added 45). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • UserInterface::update_tooltips (cognitive 28) fyrox-ui/src/lib.rs:2671 — UserInterface::update_tooltips has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 14). 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.
  • UserInterface::handle_layout_events (cognitive 23) fyrox-ui/src/lib.rs:1425 — UserInterface::handle_layout_events has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 13). Of this number, 16 points are the body's own statements and 7 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.
  • UserInterface::measure_node (cognitive 21) fyrox-ui/src/lib.rs:1834 — UserInterface::measure_node 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.
  • UserInterface::update (cognitive 19) fyrox-ui/src/lib.rs:1549 — UserInterface::update has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (6 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.
  • UserInterface::arrange_node (cognitive 16) fyrox-ui/src/lib.rs:1749 — UserInterface::arrange_node has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 2 (4 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.
D3 · God Classes · FunctionTooLong · ×7
  • FunctionTooLong: fyroxed_base::plugins::inspector::editors::make_property_editors_container editor/src/plugins/inspector/editors/mod.rs:314 — FunctionTooLong — fyroxed_base::plugins::inspector::editors::make_property_editors_container runs 385 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 285 over it, 3.85× 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: fyrox_project_manager::main project-manager/src/main.rs:73 — FunctionTooLong — fyrox_project_manager::main runs 139 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 39 over it, 1.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: fyrox_ui::node::constructor::new_widget_constructor_container fyrox-ui/src/node/constructor.rs:81 — FunctionTooLong — fyrox_ui::node::constructor::new_widget_constructor_container runs 127 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 27 over it, 1.27× 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: fyrox_impl::resource::fbx::convert_mesh fyrox-impl/src/resource/fbx/mod.rs:486 — FunctionTooLong — fyrox_impl::resource::fbx::convert_mesh runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: fyrox_core_derive::visit::impl_visit_enum fyrox-core-derive/src/visit.rs:90 — FunctionTooLong — fyrox_core_derive::visit::impl_visit_enum runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: fyrox_project_manager::manager::make_project_item project-manager/src/manager.rs:171 — FunctionTooLong — fyrox_project_manager::manager::make_project_item runs 103 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 3 over it, 1.03× 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: fyrox_impl::resource::fbx::create_materials fyrox-impl/src/resource/fbx/mod.rs:292 — FunctionTooLong — fyrox_impl::resource::fbx::create_materials runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×7
  • Edited copy of a member (23 corresponding lines) fyrox-ui/src/draw.rs:197 — fyrox-ui/src/draw.rs:197-219 | fyrox-ui/src/draw.rs:222-251 — 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) fyrox-core/src/reflect/mod.rs:927 — fyrox-core/src/reflect/mod.rs:927-949 | fyrox-core/src/reflect/mod.rs:955-984 — 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) fyrox-impl/src/scene/terrain/brushstroke/mod.rs:503 — fyrox-impl/src/scene/terrain/brushstroke/mod.rs:503-525 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:532-554 — 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) editor/src/scene/property.rs:307 — editor/src/scene/property.rs:307-330 | editor/src/scene/selector.rs:303-325 — 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) fyrox-autotile/src/wave.rs:566 — fyrox-autotile/src/wave.rs:566-588 | fyrox-autotile/src/wave.rs:754-780 — 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) editor/src/audio/mod.rs:108 — editor/src/audio/mod.rs:108-130 | editor/src/audio/mod.rs:132-163 — 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) editor/src/plugins/animation/selection.rs:148 — editor/src/plugins/animation/selection.rs:148-170 | editor/src/plugins/animation/selection.rs:172-200 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×7
  • Edited copy of a member (5 corresponding lines) editor/src/scene/commands/terrain.rs:58 — editor/src/scene/commands/terrain.rs:58-62 | editor/src/scene/commands/terrain.rs:107-115 — 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) editor/src/plugins/tilemap/autotile.rs:782 — editor/src/plugins/tilemap/autotile.rs:782-786 | editor/src/plugins/tilemap/wfc.rs:1006-1010 — 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) editor/src/plugins/tilemap/autotile.rs:992 — editor/src/plugins/tilemap/autotile.rs:992-996 | editor/src/plugins/tilemap/wfc.rs:1035-1039 — 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) editor/src/plugins/tilemap/brush_macro.rs:513 — editor/src/plugins/tilemap/brush_macro.rs:513-517 | editor/src/plugins/tilemap/commands.rs:408-412 — 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) editor/src/plugins/tilemap/brush_macro.rs:519 — editor/src/plugins/tilemap/brush_macro.rs:519-523 | editor/src/plugins/tilemap/commands.rs:414-418 — 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) editor/src/lib.rs:310 — editor/src/lib.rs:310-314 | fyrox-impl/src/scene/terrain/mod.rs:2360-2364 — 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) editor/src/audio/preview.rs:209 — editor/src/audio/preview.rs:209-213 | editor/src/plugins/animation/toolbar.rs:1062-1066 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×7
  • Duplicated block (10 lines × 3) editor/src/plugins/collider/mod.rs:415 — editor/src/plugins/collider/mod.rs:415-424 | editor/src/plugins/collider/mod.rs:551-560 | editor/src/plugins/probe.rs:246-255 — 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 `editor/src/plugins/collider/mod.rs:415` 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) editor/src/plugins/tilemap/interaction_mode.rs:329 — editor/src/plugins/tilemap/interaction_mode.rs:329-338 | editor/src/plugins/tilemap/interaction_mode.rs:369-378 | editor/src/plugins/tilemap/interaction_mode.rs:408-417 — 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, `editor/src/plugins/tilemap/interaction_mode.rs:418` calls `default` and `editor/src/plugins/tilemap/interaction_mode.rs:339` 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 lines × 3) fyrox-impl/src/scene/dim2/rectangle.rs:386 — fyrox-impl/src/scene/dim2/rectangle.rs:386-395 | fyrox-impl/src/scene/particle_system/mod.rs:609-618 | fyrox-impl/src/scene/sprite.rs:381-390 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rectangle.rs` and `fyrox-impl/src/scene/sprite.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/rectangle.rs:386` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/inspector/editors/array.rs:140 — fyrox-ui/src/inspector/editors/array.rs:140-149 | fyrox-ui/src/inspector/editors/array.rs:419-428 | fyrox-ui/src/inspector/editors/collection.rs:617-626 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 3) fyrox-ui/src/inspector/editors/mod.rs:809 — fyrox-ui/src/inspector/editors/mod.rs:809-818 | fyrox-ui/src/inspector/editors/mod.rs:819-828 | fyrox-ui/src/inspector/editors/mod.rs:829-838 — 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) fyrox-ui/src/curve/mod.rs:1917 — fyrox-ui/src/curve/mod.rs:1917-1927 | fyrox-ui/src/curve/mod.rs:1961-1970 | fyrox-ui/src/inspector/mod.rs:1568-1577 — `fyrox-ui/src/curve/mod.rs` and `fyrox-ui/src/inspector/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/curve/mod.rs:1917` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (10 lines × 3) editor/src/scene_viewer/mod.rs:139 — editor/src/scene_viewer/mod.rs:139-148 | editor/src/scene_viewer/mod.rs:155-164 | editor/src/scene_viewer/mod.rs:171-180 — 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 `editor/src/scene_viewer/mod.rs:139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D2 · Cognitive Complexity · PaletteWidget · ×6
  • PaletteWidget::draw (cognitive 60) editor/src/plugins/tilemap/palette.rs:1695 — PaletteWidget::draw has cognitive complexity 60 (threshold 15). Drivers by points: if/else 25 (39 pts), loops 7 (14 pts), boolean chains 7 (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.
  • PaletteWidget::draw_tile_colliders (cognitive 39) editor/src/plugins/tilemap/palette.rs:1407 — PaletteWidget::draw_tile_colliders has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (30 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • PaletteWidget::handle_routed_message (cognitive 29) editor/src/plugins/tilemap/palette.rs:1887 — PaletteWidget::handle_routed_message has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • PaletteWidget::sync_to_state (cognitive 21) editor/src/plugins/tilemap/palette.rs:675 — PaletteWidget::sync_to_state has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, match/switch 2 (3 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.
  • PaletteWidget::send_update_tiles (cognitive 20) editor/src/plugins/tilemap/palette.rs:831 — PaletteWidget::send_update_tiles has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (3 pts), match/switch 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.
  • PaletteWidget::draw (cognitive 17) editor/src/plugins/tilemap/palette.rs:1283 — PaletteWidget::draw has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1, match/switch 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.
D2 · Cognitive Complexity · fyroxed_base · ×6
  • fyroxed_base::update (cognitive 57) editor/src/lib.rs:3226 — fyroxed_base::update has cognitive complexity 57 (threshold 15). Drivers by points: if/else 12 (35 pts), loops 6 (20 pts), match/switch 1 (2 pts) (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • fyroxed_base::plugins::animation::track::type_id_to_supported_type (cognitive 47) editor/src/plugins/animation/track.rs:194 — fyroxed_base::plugins::animation::track::type_id_to_supported_type has cognitive complexity 47 (threshold 15). Drivers by points: if/else 47. 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.
  • fyroxed_base::scene::property::object_to_property_tree (cognitive 32) editor/src/scene/property.rs:159 — fyroxed_base::scene::property::object_to_property_tree has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (8 pts), match/switch 2 (5 pts), boolean chains 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.
  • fyroxed_base::camera::precise_ray_test (cognitive 24) editor/src/camera/mod.rs:942 — fyroxed_base::camera::precise_ray_test has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (18 pts), loops 3 (6 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.
  • fyroxed_base::plugins::tilemap::palette::send_copy_brush_pages (cognitive 17) editor/src/plugins/tilemap/palette.rs:471 — fyroxed_base::plugins::tilemap::palette::send_copy_brush_pages has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 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.
  • fyroxed_base::plugins::tilemap::interaction_mode::draw (cognitive 16) editor/src/plugins/tilemap/interaction_mode.rs:432 — fyroxed_base::plugins::tilemap::interaction_mode::draw has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · PhysicsWorld · ×6
  • PhysicsWorld::sync_to_rigid_body_node (cognitive 30) fyrox-impl/src/scene/graph/physics/mod.rs:1488 — PhysicsWorld::sync_to_rigid_body_node has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 4 (11 pts), loops 1 (3 pts), boolean chains 2 (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.
  • PhysicsWorld::sync_to_joint_node (cognitive 24) fyrox-impl/src/scene/graph/physics/mod.rs:1832 — PhysicsWorld::sync_to_joint_node has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • PhysicsWorld::sync_to_rigid_body_node (cognitive 23) fyrox-impl/src/scene/dim2/physics/mod.rs:1047 — PhysicsWorld::sync_to_rigid_body_node has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 1 (4 pts), loops 1 (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.
  • PhysicsWorld::sync_to_joint_node (cognitive 22) fyrox-impl/src/scene/dim2/physics/mod.rs:1319 — PhysicsWorld::sync_to_joint_node has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 2, 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.
  • PhysicsWorld::sync_to_collider_node (cognitive 19) fyrox-impl/src/scene/dim2/physics/mod.rs:1190 — PhysicsWorld::sync_to_collider_node has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 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.
  • PhysicsWorld::sync_to_collider_node (cognitive 19) fyrox-impl/src/scene/graph/physics/mod.rs:1702 — PhysicsWorld::sync_to_collider_node has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 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.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×6
  • Edited copy of a member (29 corresponding lines) fyrox-core/src/visitor/reader/ascii.rs:370 — fyrox-core/src/visitor/reader/ascii.rs:370-399 | fyrox-core/src/visitor/reader/binary.rs:242-270 — 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) fyrox-ui/src/utils.rs:433 — fyrox-ui/src/utils.rs:433-462 | fyrox-ui/src/utils.rs:464-492 — 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) editor/src/plugins/tilemap/interaction_mode.rs:848 — editor/src/plugins/tilemap/interaction_mode.rs:848-880 | editor/src/plugins/tilemap/interaction_mode.rs:888-916 — 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) fyrox-impl/src/renderer/shadow/point.rs:80 — fyrox-impl/src/renderer/shadow/point.rs:80-119 | fyrox-impl/src/renderer/shadow/spot.rs:65-93 — 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) editor/src/ui_scene/selection.rs:127 — editor/src/ui_scene/selection.rs:127-155 | editor/src/world/selection.rs:127-155 — 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) editor/src/plugins/tilemap/palette.rs:423 — editor/src/plugins/tilemap/palette.rs:423-451 | editor/src/plugins/tilemap/palette.rs:548-576 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×6
  • Edited copy of a member (21 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs:621 — fyrox-impl/src/scene/dim2/physics/mod.rs:621-641 | fyrox-impl/src/scene/graph/physics/mod.rs:1064-1084 — 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) fyrox-impl/src/scene/dim2/rigidbody.rs:162 — fyrox-impl/src/scene/dim2/rigidbody.rs:162-182 | fyrox-impl/src/scene/rigidbody.rs:246-271 — 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) editor/src/plugins/collider/cuboid.rs:77 — editor/src/plugins/collider/cuboid.rs:77-97 | editor/src/plugins/collider/cuboid.rs:127-147 — 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) editor/src/plugins/tilemap/tile_inspector.rs:615 — editor/src/plugins/tilemap/tile_inspector.rs:615-635 | editor/src/plugins/tilemap/tile_inspector.rs:689-709 — 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) editor/src/plugins/tilemap/collider_editor.rs:254 — editor/src/plugins/tilemap/collider_editor.rs:254-274 | editor/src/plugins/tilemap/tile_prop_editor.rs:397-417 — 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) editor/src/scene/container.rs:302 — editor/src/scene/container.rs:302-326 | editor/src/scene/container.rs:416-436 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×6
  • Edited copies of one member (3 members, 8+ corresponding lines) fyrox-impl/src/scene/tilemap/tileset.rs:1907 — fyrox-impl/src/scene/tilemap/tileset.rs:1907-1917 | fyrox-impl/src/scene/tilemap/tileset.rs:1932-1940 | fyrox-impl/src/scene/tilemap/tileset.rs:1942-1949 — 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) fyrox-impl/src/scene/tilemap/tileset.rs:1437 — fyrox-impl/src/scene/tilemap/tileset.rs:1437-1445 | fyrox-impl/src/scene/tilemap/tileset.rs:1457-1464 | fyrox-impl/src/scene/tilemap/tileset.rs:1666-1676 — 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) fyrox-ui/src/grid.rs:530 — fyrox-ui/src/grid.rs:530-537 | fyrox-ui/src/grid.rs:543-550 | fyrox-ui/src/grid.rs:551-558 — 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) fyrox-ui/src/formatted_text/run.rs:89 — fyrox-ui/src/formatted_text/run.rs:89-96 | fyrox-ui/src/formatted_text/run.rs:107-114 | fyrox-ui/src/formatted_text/run.rs:125-132 — 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) editor/src/scene/commands/terrain.rs:134 — editor/src/scene/commands/terrain.rs:134-142 | editor/src/scene/commands/terrain.rs:179-187 | editor/src/scene/commands/terrain.rs:226-233 — 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) fyrox-ui/src/inspector/editors/key.rs:50 — fyrox-ui/src/inspector/editors/key.rs:50-57 | fyrox-ui/src/inspector/editors/key.rs:95-102 | fyrox-ui/src/inspector/editors/range.rs:57-65 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×6
  • Edited copy of a member (7 corresponding lines) fyrox-impl/src/renderer/occlusion/grid.rs:96 — fyrox-impl/src/renderer/occlusion/grid.rs:96-102 | fyrox-impl/src/renderer/visibility.rs:66-72 — 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) fyrox-math/src/ray.rs:137 — fyrox-math/src/ray.rs:137-143 | fyrox-math/src/ray.rs:147-154 — 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) fyrox-animation/src/lib.rs:770 — fyrox-animation/src/lib.rs:770-776 | fyrox-animation/src/lib.rs:785-791 — 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) fyrox-core/src/pool/mod.rs:1411 — fyrox-core/src/pool/mod.rs:1411-1417 | fyrox-core/src/pool/multiborrow.rs:360-366 — 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) fyrox-core/src/pool/mod.rs:1398 — fyrox-core/src/pool/mod.rs:1398-1404 | fyrox-core/src/pool/multiborrow.rs:343-349 — 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) fyrox-impl/src/scene/tilemap/tile_source.rs:570 — fyrox-impl/src/scene/tilemap/tile_source.rs:570-576 | fyrox-impl/src/scene/tilemap/transform.rs:255-261 — 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.
D1 · Cyclomatic Complexity · Editor · ×5
  • Editor::update (cyclomatic 58) editor/src/lib.rs:2558 — Editor::update has cyclomatic complexity 58 (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.
  • Editor::handle_hotkeys (cyclomatic 40) editor/src/lib.rs:1198 — Editor::handle_hotkeys 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.
  • Editor::run (cyclomatic 23) editor/src/lib.rs:3072 — Editor::run 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.
  • Editor::handle_modes (cyclomatic 20) editor/src/lib.rs:2354 — Editor::handle_modes 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.
  • Editor::handle_ui_message (cyclomatic 16) editor/src/lib.rs:1369 — Editor::handle_ui_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.
D2 · Cognitive Complexity · Engine · ×5
  • Engine::reload_plugin (cognitive 41) fyrox-impl/src/engine/mod.rs:2502 — Engine::reload_plugin has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 15 (16 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.
  • Engine::handle_os_events (cognitive 30) fyrox-impl/src/engine/mod.rs:2000 — Engine::handle_os_events has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (17 pts), match/switch 5 (11 pts), 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.
  • Engine::handle_async_tasks (cognitive 25) fyrox-impl/src/engine/mod.rs:1738 — Engine::handle_async_tasks has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (22 pts), boolean chains 2, loops 1 (nesting depth added 15). 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.
  • Engine::update_plugins (cognitive 16) fyrox-impl/src/engine/mod.rs:1832 — Engine::update_plugins has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (11 pts), if/else 2 (5 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
  • Engine::post_update_plugins (cognitive 16) fyrox-impl/src/engine/mod.rs:1924 — Engine::post_update_plugins has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (7 pts), if/else 2 (5 pts), match/switch 1 (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.
D2 · Cognitive Complexity · Terrain · ×5
  • Terrain::raycast (cognitive 41) fyrox-impl/src/scene/terrain/mod.rs:1956 — Terrain::raycast has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 4 (15 pts) (nesting depth added 29). 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.
  • Terrain::collect_render_data (cognitive 29) fyrox-impl/src/scene/terrain/mod.rs:2431 — Terrain::collect_render_data has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 5 (12 pts), boolean chains 3 (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.
  • Terrain::resize (cognitive 19) fyrox-impl/src/scene/terrain/mod.rs:1513 — Terrain::resize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (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.
  • Terrain::align_chunk_margins (cognitive 17) fyrox-impl/src/scene/terrain/mod.rs:1270 — Terrain::align_chunk_margins has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, loops 4 (8 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Terrain::align_chunk_edges) 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.
  • Terrain::align_chunk_edges (cognitive 17) fyrox-impl/src/scene/terrain/mod.rs:1325 — Terrain::align_chunk_edges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, loops 4 (8 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Terrain::align_chunk_margins) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×5
  • Edited copy of a member (45 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs:848 — fyrox-impl/src/scene/dim2/physics/mod.rs:848-895 | fyrox-impl/src/scene/graph/physics/mod.rs:1292-1336 — 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.
  • Edited copy of a member (45 corresponding lines) editor/src/interaction/rotate_mode.rs:199 — editor/src/interaction/rotate_mode.rs:199-260 | editor/src/interaction/scale_mode.rs:191-235 — 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.
  • Edited copy of a member (45 corresponding lines) fyrox-impl/src/renderer/convolution.rs:84 — fyrox-impl/src/renderer/convolution.rs:84-135 | fyrox-impl/src/renderer/convolution.rs:170-214 — 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.
  • Edited copy of a member (45 corresponding lines) editor/src/plugins/ragdoll.rs:314 — editor/src/plugins/ragdoll.rs:314-361 | editor/src/plugins/ragdoll.rs:372-416 — 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.
  • Edited copy of a member (45 corresponding lines) fyrox-impl/src/scene/collider.rs:901 — fyrox-impl/src/scene/collider.rs:901-945 | fyrox-impl/src/scene/dim2/collider.rs:706-750 — 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 copy of a member (24 corresponding lines) · ×5
  • Edited copy of a member (24 corresponding lines) fyrox-math/src/frustum.rs:222 — fyrox-math/src/frustum.rs:222-245 | fyrox-math/src/frustum.rs:252-275 — 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) fyrox-animation/src/container.rs:232 — fyrox-animation/src/container.rs:232-255 | fyrox-animation/src/container.rs:258-282 — 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) editor/src/interaction/select_mode.rs:158 — editor/src/interaction/select_mode.rs:158-183 | editor/src/ui_scene/interaction/mod.rs:173-196 — 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) fyrox-impl/src/scene/dim2/rigidbody.rs:517 — fyrox-impl/src/scene/dim2/rigidbody.rs:517-540 | fyrox-impl/src/scene/rigidbody.rs:658-681 — 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) editor/src/interaction/gizmo/move_gizmo.rs:158 — editor/src/interaction/gizmo/move_gizmo.rs:158-181 | editor/src/interaction/gizmo/rotate_gizmo.rs:77-103 — 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 (22 corresponding lines) · ×5
  • Edited copy of a member (22 corresponding lines) fyrox-impl/src/scene/dim2/joint.rs:527 — fyrox-impl/src/scene/dim2/joint.rs:527-548 | fyrox-impl/src/scene/joint.rs:601-628 — 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) editor/src/plugins/absm/command/mod.rs:192 — editor/src/plugins/absm/command/mod.rs:192-213 | editor/src/plugins/animation/command/mod.rs:52-73 — 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) fyrox-ui/src/utils.rs:145 — fyrox-ui/src/utils.rs:145-166 | fyrox-ui/src/utils.rs:171-202 — 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) fyrox-impl/src/renderer/debug_renderer.rs:151 — fyrox-impl/src/renderer/debug_renderer.rs:151-172 | fyrox-impl/src/renderer/mod.rs:603-624 — 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) editor/src/plugins/absm/command/mod.rs:554 — editor/src/plugins/absm/command/mod.rs:554-624 | editor/src/plugins/animation/command/mod.rs:361-382 — 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 copies of one member (4 members, 14+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 14+ corresponding lines) fyrox-impl/src/resource/fbx/document/attribute.rs:48 — fyrox-impl/src/resource/fbx/document/attribute.rs:48-61 | fyrox-impl/src/resource/fbx/document/attribute.rs:63-76 | fyrox-impl/src/resource/fbx/document/attribute.rs:78-91 | fyrox-impl/src/resource/fbx/document/attribute.rs:93-106 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 14+ corresponding lines) fyrox-ui/src/inspector/editors/char.rs:50 — fyrox-ui/src/inspector/editors/char.rs:50-64 | fyrox-ui/src/inspector/editors/immutable_string.rs:54-68 | fyrox-ui/src/inspector/editors/string.rs:50-64 | fyrox-ui/src/inspector/editors/utf32.rs:50-63 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 14+ corresponding lines) fyrox-impl/src/scene/mesh/buffer.rs:464 — fyrox-impl/src/scene/mesh/buffer.rs:464-477 | fyrox-impl/src/scene/mesh/buffer.rs:489-502 | fyrox-impl/src/scene/mesh/buffer.rs:532-547 | fyrox-impl/src/scene/mesh/buffer.rs:565-582 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 14+ corresponding lines) editor/src/plugins/tilemap/colliders_tab.rs:385 — editor/src/plugins/tilemap/colliders_tab.rs:385-402 | editor/src/plugins/tilemap/colliders_tab.rs:403-416 | editor/src/plugins/tilemap/macro_tab.rs:471-488 | editor/src/plugins/tilemap/properties_tab.rs:868-885 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 14+ corresponding lines) editor/src/scene/mod.rs:765 — editor/src/scene/mod.rs:765-778 | editor/src/scene/mod.rs:785-798 | editor/src/scene/mod.rs:805-818 | editor/src/scene/mod.rs:825-838 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×5
  • Edited copy of a member (20 corresponding lines) editor/src/scene/clipboard.rs:59 — editor/src/scene/clipboard.rs:59-85 | editor/src/ui_scene/clipboard.rs:59-78 — 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) editor/src/scene/commands/mod.rs:225 — editor/src/scene/commands/mod.rs:225-244 | editor/src/ui_scene/commands/graph.rs:277-297 — 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) fyrox-impl/src/scene/node/container.rs:37 — fyrox-impl/src/scene/node/container.rs:37-56 | fyrox-ui/src/node/container.rs:37-56 — 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) editor/src/scene/container.rs:335 — editor/src/scene/container.rs:335-354 | editor/src/scene/container.rs:363-383 — 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) fyrox-ui/src/matrix.rs:46 — fyrox-ui/src/matrix.rs:46-65 | fyrox-ui/src/vec.rs:50-69 — 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×5
  • Duplicated block (25 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:355 — editor/src/plugins/inspector/editors/dyntype.rs:355-379 | editor/src/plugins/inspector/editors/script.rs:452-476 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/dyntype.rs:355` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) fyrox-impl/src/engine/mod.rs:512 — fyrox-impl/src/engine/mod.rs:512-536 | fyrox-impl/src/engine/mod.rs:543-567 — both copies are in the same file, so extract the 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 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1293 — fyrox-impl/src/scene/dim2/physics/mod.rs:1293-1317 | fyrox-impl/src/scene/graph/physics/mod.rs:1806-1830 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1293` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) fyrox-resource/src/manager.rs:497 — fyrox-resource/src/manager.rs:497-521 | fyrox-resource/src/manager.rs:603-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. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-resource/src/manager.rs:497` 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 (25 lines × 2) fyrox-ui/src/lib.rs:2870 — fyrox-ui/src/lib.rs:2870-2894 | fyrox-ui/src/lib.rs:3149-3173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/lib.rs:2870` 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×5
  • Duplicated block (24 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:273 — editor/src/plugins/inspector/editors/dyntype.rs:273-296 | editor/src/plugins/inspector/editors/script.rs:369-392 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/dyntype.rs:273` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) editor/src/plugins/light.rs:264 — editor/src/plugins/light.rs:264-287 | editor/src/plugins/ragdoll.rs:1048-1071 — 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 `editor/src/plugins/light.rs:264` it begins part-way through the construct above it, so those exact lines 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) fyrox-graphics-gl/src/framebuffer.rs:433 — fyrox-graphics-gl/src/framebuffer.rs:433-456 | fyrox-graphics-gl/src/framebuffer.rs:489-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 `fyrox-graphics-gl/src/framebuffer.rs:433` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1052 — fyrox-impl/src/scene/dim2/physics/mod.rs:1052-1075 | fyrox-impl/src/scene/graph/physics/mod.rs:1493-1516 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1052` it does not close everything it opens, so those 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 `rigid_body_node` to `&scene::dim2::rigidbody::RigidBody` in one and `&scene::rigidbody::RigidBody` 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 (24 lines × 2) fyrox-ui/src/inspector/editors/hashmap/mod.rs:131 — fyrox-ui/src/inspector/editors/hashmap/mod.rs:131-154 | fyrox-ui/src/inspector/editors/hashmap/mod.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 `fyrox-ui/src/inspector/editors/hashmap/mod.rs:131` 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.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×5
  • Duplicated block (21 lines × 2) editor/src/plugins/animation/toolbar.rs:275 — editor/src/plugins/animation/toolbar.rs:275-295 | editor/src/plugins/animation/toolbar.rs:935-955 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/animation/toolbar.rs:275` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) editor/src/plugins/inspector/editors/spritesheet/window.rs:322 — editor/src/plugins/inspector/editors/spritesheet/window.rs:322-342 | editor/src/plugins/ragdoll.rs:1094-1114 — before extracting anything, compare `editor/src/plugins/inspector/editors/spritesheet/window.rs` and `editor/src/plugins/ragdoll.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/spritesheet/window.rs:322` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) editor/src/plugins/tilemap/panel.rs:287 — editor/src/plugins/tilemap/panel.rs:287-307 | editor/src/plugins/tilemap/tile_bounds_editor.rs:201-221 — 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 `editor/src/plugins/tilemap/panel.rs:287` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) fyrox-core/src/visitor/reader/ascii.rs:379 — fyrox-core/src/visitor/reader/ascii.rs:379-399 | fyrox-core/src/visitor/reader/binary.rs:250-270 — 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 `fyrox-core/src/visitor/reader/ascii.rs:379` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1136 — fyrox-impl/src/scene/dim2/physics/mod.rs:1136-1156 | fyrox-impl/src/scene/graph/physics/mod.rs:1635-1655 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1136` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×5
  • Duplicated block (12–13 lines × 2) editor/src/mesh.rs:187 — editor/src/mesh.rs:187-198 | editor/src/mesh.rs:231-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/mesh.rs:187` it begins part-way through the construct above it, so those 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, `editor/src/mesh.rs:228` calls `Some` and `editor/src/mesh.rs:186` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12–13 lines × 2) editor/src/plugins/animation/toolbar.rs:541 — editor/src/plugins/animation/toolbar.rs:541-553 | editor/src/plugins/animation/toolbar.rs:666-677 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/animation/toolbar.rs:541` it begins part-way through the construct above it, so those exact lines 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) editor/src/plugins/inspector/editors/dyntype.rs:258 — editor/src/plugins/inspector/editors/dyntype.rs:258-269 | editor/src/plugins/inspector/editors/script.rs:352-364 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/dyntype.rs:258` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1325 — fyrox-impl/src/scene/dim2/physics/mod.rs:1325-1337 | fyrox-impl/src/scene/graph/physics/mod.rs:1838-1849 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1325` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/terrain/mod.rs:1561 — fyrox-impl/src/scene/terrain/mod.rs:1561-1572 | fyrox-impl/src/scene/terrain/mod.rs:2735-2747 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D1 · Cyclomatic Complexity · PaletteWidget · ×4
  • PaletteWidget::draw (cyclomatic 38) editor/src/plugins/tilemap/palette.rs:1695 — PaletteWidget::draw 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.
  • PaletteWidget::handle_routed_message (cyclomatic 26) editor/src/plugins/tilemap/palette.rs:1887 — PaletteWidget::handle_routed_message 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.
  • PaletteWidget::sync_to_state (cyclomatic 21) editor/src/plugins/tilemap/palette.rs:675 — PaletteWidget::sync_to_state 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.
  • PaletteWidget::draw_tile_colliders (cyclomatic 21) editor/src/plugins/tilemap/palette.rs:1407 — PaletteWidget::draw_tile_colliders 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.
D17 · Explicit Debt · HackComment · ×4
  • HackComment fyrox-impl/src/scene/graph/physics/mod.rs:690 — // HACK: Temporary solution for https://github.com/FyroxEngine/Fyrox/issues/365 — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment editor/src/world/mod.rs:151 — /// Hack. Due to delayed execution of UI code we can't sync immediately after we — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment editor/src/world/mod.rs:819 — // Hack. See `self.sync_selection` for details. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment editor/src/plugins/animation/mod.rs:490 — // HACK. This is unreliable to just use `bool` here. It should be wrapped into — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D17 · Explicit Debt · FixmeComment · ×4
  • FixmeComment fyrox-core/src/visitor/impls.rs:416 — // FIXME: Visiting an Rc/Arc is undefined behavior because it mutates the shared data. — 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 fyrox-core/src/visitor/impls.rs:422 — // FIXME: Visiting an Rc/Arc is undefined behavior because it mutates the shared data. — 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 editor/src/audio/mod.rs:121 — // FIXME: HACK! — 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 editor/src/audio/mod.rs:149 — // FIXME: HACK! — 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.
D2 · Cognitive Complexity · TextBox · ×4
  • TextBox::handle_routed_message (cognitive 235) fyrox-ui/src/text_box.rs:1147 — TextBox::handle_routed_message has cognitive complexity 235 (threshold 15). Drivers by points: if/else 51 (197 pts), match/switch 5 (18 pts), boolean chains 10, loops 2 (10 pts) (nesting depth added 167). Of this number, 216 points are the body's own statements and 19 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.
  • TextBox::draw (cognitive 23) fyrox-ui/src/text_box.rs:998 — TextBox::draw has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 1 (3 pts), boolean chains 1 (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.
  • TextBox::move_caret (cognitive 19) fyrox-ui/src/text_box.rs:544 — TextBox::move_caret has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (17 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.
  • TextBox::select_word (cognitive 19) fyrox-ui/src/text_box.rs:910 — TextBox::select_word has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 6, 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.
D2 · Cognitive Complexity · Tile · ×4
  • Tile::handle_routed_message (cognitive 200) fyrox-ui/src/dock/tile.rs:448 — Tile::handle_routed_message has cognitive complexity 200 (threshold 15). Drivers by points: if/else 26 (95 pts), loops 11 (64 pts), match/switch 10 (35 pts), boolean chains 6 (nesting depth added 147). Of this number, 189 points are the body's own statements and 11 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.
  • Tile::preview_message (cognitive 55) fyrox-ui/src/dock/tile.rs:804 — Tile::preview_message has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 3 (14 pts), match/switch 2 (8 pts), boolean chains 2 (nesting depth added 33). 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.
  • Tile::measure_override (cognitive 24) fyrox-ui/src/dock/tile.rs:293 — Tile::measure_override has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 3 (5 pts), match/switch 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Tile::arrange_override (cognitive 18) fyrox-ui/src/dock/tile.rs:372 — Tile::arrange_override has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · SceneGraph · ×4
  • SceneGraph::restore_integrity (cognitive 52) fyrox-graph/src/lib.rs:1208 — SceneGraph::restore_integrity has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (43 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 32). 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.
  • SceneGraph::restore_original_handles_and_inherit_properties (cognitive 26) fyrox-graph/src/lib.rs:1365 — SceneGraph::restore_original_handles_and_inherit_properties has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (21 pts), match/switch 1 (4 pts), loops 1 (nesting depth added 17). 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.
  • SceneGraph::remap_handles (cognitive 20) fyrox-graph/src/lib.rs:1466 — SceneGraph::remap_handles has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 3 (5 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.
  • SceneGraph::external_refs_summary (cognitive 16) fyrox-graph/src/lib.rs:1613 — SceneGraph::external_refs_summary has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EditNavmeshMode · ×4
  • EditNavmeshMode::on_left_mouse_button_down (cognitive 44) editor/src/interaction/navmesh/mod.rs:243 — EditNavmeshMode::on_left_mouse_button_down has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 4 (16 pts) (nesting depth added 29). 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.
  • EditNavmeshMode::update (cognitive 22) editor/src/interaction/navmesh/mod.rs:506 — EditNavmeshMode::update has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (8 pts), match/switch 1 (4 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.
  • EditNavmeshMode::on_mouse_move (cognitive 21) editor/src/interaction/navmesh/mod.rs:407 — EditNavmeshMode::on_mouse_move has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 2 (8 pts), match/switch 1 (3 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.
  • EditNavmeshMode::on_key_down (cognitive 16) editor/src/interaction/navmesh/mod.rs:603 — EditNavmeshMode::on_key_down has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 1 (4 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · GameScene · ×4
  • GameScene::draw_auxiliary_geometry::draw_recursively (cognitive 41) editor/src/scene/mod.rs:341 — GameScene::draw_auxiliary_geometry::draw_recursively has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (29 pts), loops 4 (11 pts), boolean chains 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.
  • GameScene::update (cognitive 25) editor/src/scene/mod.rs:878 — GameScene::update has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3 (5 pts), match/switch 3 (4 pts), boolean chains 2 (nesting depth added 8). Of this number, 22 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.
  • GameScene::on_drop (cognitive 23) editor/src/scene/mod.rs:664 — GameScene::on_drop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (23 pts) (nesting depth added 15). 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.
  • GameScene::on_drag_over (cognitive 18) editor/src/scene/mod.rs:570 — GameScene::on_drag_over has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (4 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · fyrox_ui · ×4
  • fyrox_ui::transform_size (cognitive 41) fyrox-ui/src/lib.rs:3872 — fyrox_ui::transform_size has cognitive complexity 41 (threshold 15). Drivers by points: if/else 22 (33 pts), boolean chains 8 (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.
  • fyrox_ui::markdown::markdown_to_visual_tree::traverse_ast_recursively (cognitive 31) fyrox-ui/src/markdown.rs:101 — fyrox_ui::markdown::markdown_to_visual_tree::traverse_ast_recursively has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 3 (11 pts), match/switch 3 (5 pts) (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.
  • fyrox_ui::file_browser::fs_tree::find_tree_item (cognitive 23) fyrox-ui/src/file_browser/fs_tree.rs:75 — fyrox_ui::file_browser::fs_tree::find_tree_item has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (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.
  • fyrox_ui::menu::keyboard_navigation (cognitive 23) fyrox-ui/src/menu.rs:1234 — fyrox_ui::menu::keyboard_navigation has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · Graph · ×4
  • Graph::set_lightmap (cognitive 34) fyrox-impl/src/scene/graph/mod.rs:991 — Graph::set_lightmap has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 4 (12 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Graph::apply_lightmap (cognitive 29) fyrox-impl/src/scene/graph/mod.rs:1048 — Graph::apply_lightmap has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 5 (14 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.
  • Graph::process_node_messages (cognitive 24) fyrox-impl/src/scene/graph/mod.rs:1280 — Graph::process_node_messages has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 3 (5 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 10). Of this number, 19 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Graph::build_indexed_path (cognitive 22) fyrox-impl/src/utils/astar.rs:434 — Graph::build_indexed_path has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 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.
D3 · God Classes · TooManyFields · ×4
  • TooManyFields: Widget fyrox-ui/src/widget.rs:572 — TooManyFields — 60 stored fields beside 110 methods. The bar is 30 stored fields; this is 30 over it, 2.00× 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: WidgetBuilder fyrox-ui/src/widget.rs:1677 — TooManyFields — 39 stored fields beside 46 methods. The bar is 30 stored fields; this is 9 over it, 1.30× 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: ProjectManager project-manager/src/manager.rs:130 — TooManyFields — 38 stored fields beside 26 methods. The bar is 30 stored fields; this is 8 over it, 1.27× 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: UserInterface fyrox-ui/src/lib.rs:736 — TooManyFields — 34 stored fields beside 95 methods. 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.
D35 · Change Coupling · Change coupling clique · ×4
  • Change coupling clique: directional.rs, point.rs, spot.rs fyrox-impl/src/scene/light/directional.rs — 3 files — `fyrox-impl/src/scene/light/directional.rs`, `fyrox-impl/src/scene/light/point.rs`, `fyrox-impl/src/scene/light/spot.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
  • Change coupling clique: gbuffer.rs, csm.rs, point.rs, spot.rs fyrox-impl/src/renderer/gbuffer.rs — 4 files — `fyrox-impl/src/renderer/gbuffer.rs`, `fyrox-impl/src/renderer/shadow/csm.rs`, `fyrox-impl/src/renderer/shadow/point.rs`, `fyrox-impl/src/renderer/shadow/spot.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
  • Change coupling clique: move_gizmo.rs, rotate_gizmo.rs, scale_gizmo.rs editor/src/interaction/gizmo/move_gizmo.rs — 3 files — `editor/src/interaction/gizmo/move_gizmo.rs`, `editor/src/interaction/gizmo/rotate_gizmo.rs`, `editor/src/interaction/gizmo/scale_gizmo.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
  • Change coupling clique: move_mode.rs, rotate_mode.rs, scale_mode.rs editor/src/interaction/move_mode.rs — 3 files — `editor/src/interaction/move_mode.rs`, `editor/src/interaction/rotate_mode.rs`, `editor/src/interaction/scale_mode.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×4
  • Duplicated block (23 lines × 2) editor/src/plugins/curve_editor.rs:264 — editor/src/plugins/curve_editor.rs:264-286 | fyrox-ui/src/inspector/editors/style.rs:304-326 — 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 `editor/src/plugins/curve_editor.rs:264` it begins part-way through the construct above it, so those exact lines 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) fyrox-impl/src/renderer/light.rs:914 — fyrox-impl/src/renderer/light.rs:914-936 | fyrox-impl/src/renderer/light.rs:992-1014 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/renderer/light.rs:914` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/dim2/physics/mod.rs:269 — fyrox-impl/src/scene/dim2/physics/mod.rs:269-291 | fyrox-impl/src/scene/graph/physics/mod.rs:393-415 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:269` it begins part-way through the construct above it, so those 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 `c` to `&rapier2d::geometry::ContactPair` in one and `&rapier3d::geometry::ContactPair` 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 (23 lines × 2) fyrox-impl/src/scene/collider.rs:902 — fyrox-impl/src/scene/collider.rs:902-924 | fyrox-impl/src/scene/dim2/collider.rs:707-729 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/collider.rs:902` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×4
  • Duplicated block (20 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:676 — fyrox-impl/src/scene/dim2/physics/mod.rs:676-695 | fyrox-impl/src/scene/graph/physics/mod.rs:1119-1138 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:676` 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 (20 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1079 — fyrox-impl/src/scene/dim2/physics/mod.rs:1079-1098 | fyrox-impl/src/scene/graph/physics/mod.rs:1557-1576 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1079` it begins part-way through the construct above it, so those 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 `rigid_body_node` to `&scene::dim2::rigidbody::RigidBody` in one and `&scene::rigidbody::RigidBody` 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 (20 lines × 2) fyrox-ui/src/inspector/editors/array.rs:154 — fyrox-ui/src/inspector/editors/array.rs:154-173 | fyrox-ui/src/inspector/editors/collection.rs:250-269 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `fyrox-ui/src/inspector/editors/array.rs:154` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (20 lines × 2) editor/src/lib.rs:684 — editor/src/lib.rs:684-703 | editor/src/lib.rs:707-726 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/lib.rs:684` 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.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×4
  • Duplicated block (8–10 lines × 2) editor/src/plugins/absm/state_graph/mod.rs:307 — editor/src/plugins/absm/state_graph/mod.rs:307-316 | editor/src/plugins/absm/state_viewer/mod.rs:419-426 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/absm/state_graph/mod.rs:307` it does not close everything it opens, so those 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 (8–10 lines × 2) editor/src/scene/mod.rs:300 — editor/src/scene/mod.rs:300-307 | editor/src/ui_scene/mod.rs:281-290 — 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 `editor/src/ui_scene/mod.rs:281` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8–10 lines × 2) fyrox-math/src/lib.rs:135 — fyrox-math/src/lib.rs:135-144 | fyrox-math/src/lib.rs:297-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.
  • Duplicated block (8–10 lines × 2) fyrox-ui/src/nine_patch.rs:250 — fyrox-ui/src/nine_patch.rs:250-259 | fyrox-ui/src/nine_patch.rs:272-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×4
  • Duplicated block (8 lines × 3) fyrox-core/src/visitor/impls.rs:55 — fyrox-core/src/visitor/impls.rs:55-62 | fyrox-core/src/visitor/mod.rs:152-159 | fyrox-core/src/visitor/pod.rs:161-168 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-core/src/visitor/impls.rs:55` 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 × 3) fyrox-impl/src/scene/terrain/brushstroke/mod.rs:987 — fyrox-impl/src/scene/terrain/brushstroke/mod.rs:987-994 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:1000-1007 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:1011-1018 — 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 `fyrox-impl/src/scene/terrain/brushstroke/mod.rs:987` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) fyrox-ui/src/inspector/editors/char.rs:52 — fyrox-ui/src/inspector/editors/char.rs:52-59 | fyrox-ui/src/inspector/editors/immutable_string.rs:56-63 | fyrox-ui/src/inspector/editors/string.rs:52-59 — before extracting anything, compare `fyrox-ui/src/inspector/editors/immutable_string.rs` and `fyrox-ui/src/inspector/editors/string.rs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `fyrox-ui/src/inspector/editors/char.rs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) editor/src/interaction/move_mode.rs:495 — editor/src/interaction/move_mode.rs:495-502 | editor/src/interaction/rotate_mode.rs:278-285 | editor/src/interaction/scale_mode.rs:253-260 — before extracting anything, compare `editor/src/interaction/move_mode.rs` and `editor/src/interaction/rotate_mode.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×4
  • Duplicated block (7 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:154 — editor/src/plugins/tilemap/colliders_tab.rs:154-160 | editor/src/plugins/tilemap/macro_tab.rs:209-215 | editor/src/plugins/tilemap/properties_tab.rs:258-264 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `editor/src/plugins/tilemap/colliders_tab.rs:161` calls `make_button` and `editor/src/plugins/tilemap/macro_tab.rs:216` 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 (7 lines × 3) editor/src/plugins/tilemap/commands.rs:156 — editor/src/plugins/tilemap/commands.rs:156-162 | editor/src/plugins/tilemap/commands.rs:192-198 | editor/src/plugins/tilemap/commands.rs:228-234 — 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 (7 lines × 3) editor/src/plugins/inspector/editors/font.rs:224 — editor/src/plugins/inspector/editors/font.rs:224-231 | editor/src/plugins/inspector/editors/surface.rs:339-346 | editor/src/plugins/material/editor.rs:405-411 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/font.rs:224` it begins part-way through the construct above it, so those exact lines 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) fyrox-ui/src/inspector/editors/bit.rs:78 — fyrox-ui/src/inspector/editors/bit.rs:78-84 | fyrox-ui/src/inspector/editors/numeric.rs:98-104 | fyrox-ui/src/inspector/editors/uuid.rs:64-70 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/inspector/editors/bit.rs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D1 · Cyclomatic Complexity · Tile · ×3
  • Tile::handle_routed_message (cyclomatic 68) fyrox-ui/src/dock/tile.rs:448 — Tile::handle_routed_message has cyclomatic complexity 68 (threshold 15). Of this number, 66 points are the body's own statements and 2 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.
  • Tile::preview_message (cyclomatic 24) fyrox-ui/src/dock/tile.rs:804 — Tile::preview_message 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.
  • Tile::measure_override (cyclomatic 17) fyrox-ui/src/dock/tile.rs:293 — Tile::measure_override 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.
D1 · Cyclomatic Complexity · TrackList · ×3
  • TrackList::handle_ui_message (cyclomatic 56) editor/src/plugins/animation/track.rs:929 — TrackList::handle_ui_message 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.
  • TrackList::sync_to_model (cyclomatic 31) editor/src/plugins/animation/track.rs:1433 — TrackList::sync_to_model 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.
  • TrackList::on_add_key_pressed (cyclomatic 26) editor/src/plugins/animation/track.rs:765 — TrackList::on_add_key_pressed 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.
D1 · Cyclomatic Complexity · Toolbar · ×3
  • Toolbar::handle_ui_message (cyclomatic 25) editor/src/plugins/animation/toolbar.rs:733 — Toolbar::handle_ui_message has cyclomatic complexity 25 (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.
  • Toolbar::handle_ui_message (cyclomatic 23) editor/src/plugins/absm/toolbar.rs:160 — Toolbar::handle_ui_message 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.
  • Toolbar::post_handle_ui_message (cyclomatic 16) editor/src/plugins/animation/toolbar.rs:912 — Toolbar::post_handle_ui_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.
D1 · Cyclomatic Complexity · PhysicsWorld · ×3
  • PhysicsWorld::sync_to_rigid_body_node (cyclomatic 22) fyrox-impl/src/scene/graph/physics/mod.rs:1488 — PhysicsWorld::sync_to_rigid_body_node 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.
  • PhysicsWorld::sync_to_rigid_body_node (cyclomatic 19) fyrox-impl/src/scene/dim2/physics/mod.rs:1047 — PhysicsWorld::sync_to_rigid_body_node 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.
  • PhysicsWorld::sync_to_joint_node (cyclomatic 16) fyrox-impl/src/scene/graph/physics/mod.rs:1832 — PhysicsWorld::sync_to_joint_node 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.
D1 · Cyclomatic Complexity · Inspector · ×3
  • Inspector::handle_routed_message (cyclomatic 21) fyrox-ui/src/inspector/mod.rs:1734 — Inspector::handle_routed_message has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 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.
  • Inspector::apply_filter (cyclomatic 17) fyrox-ui/src/inspector/mod.rs:727 — Inspector::apply_filter has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function items inside it that branch (filter_recursive, check_text, find_inspectors_recursive, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • Inspector::handle_context_menu_message_ex (cyclomatic 16) fyrox-ui/src/inspector/mod.rs:845 — Inspector::handle_context_menu_message_ex 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.
D2 · Cognitive Complexity · CurveEditor · ×3
  • CurveEditor::handle_routed_message (cognitive 289) fyrox-ui/src/curve/mod.rs:574 — CurveEditor::handle_routed_message has cognitive complexity 289 (threshold 15). Drivers by points: if/else 46 (188 pts), loops 10 (55 pts), match/switch 9 (45 pts), boolean chains 1 (nesting depth added 223). 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.
  • CurveEditor::draw_keys (cognitive 45) fyrox-ui/src/curve/mod.rs:1612 — CurveEditor::draw_keys has cognitive complexity 45 (threshold 15). Drivers by points: if/else 7 (24 pts), match/switch 4 (18 pts), loops 2 (3 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • CurveEditor::pick (cognitive 17) fyrox-ui/src/curve/mod.rs:1345 — CurveEditor::pick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (3 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.
D2 · Cognitive Complexity · TrackList · ×3
  • TrackList::handle_ui_message (cognitive 109) editor/src/plugins/animation/track.rs:929 — TrackList::handle_ui_message has cognitive complexity 109 (threshold 15). Drivers by points: if/else 40 (75 pts), match/switch 4 (16 pts), loops 3 (11 pts), boolean chains 7 (nesting depth added 55). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • TrackList::on_add_key_pressed (cognitive 86) editor/src/plugins/animation/track.rs:765 — TrackList::on_add_key_pressed has cognitive complexity 86 (threshold 15). Drivers by points: if/else 25 (72 pts), loops 4 (10 pts), match/switch 1 (4 pts) (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.
  • TrackList::sync_to_model (cognitive 82) editor/src/plugins/animation/track.rs:1433 — TrackList::sync_to_model has cognitive complexity 82 (threshold 15). Drivers by points: if/else 17 (53 pts), match/switch 6 (20 pts), loops 4 (9 pts) (nesting depth added 55). 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.
D2 · Cognitive Complexity · AssetBrowser · ×3
  • AssetBrowser::handle_ui_message (cognitive 96) editor/src/asset/mod.rs:632 — AssetBrowser::handle_ui_message has cognitive complexity 96 (threshold 15). Drivers by points: if/else 37 (78 pts), loops 3 (9 pts), boolean chains 5, match/switch 2 (4 pts) (nesting depth added 49). Of this number, 89 points are the body's own statements and 7 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.
  • AssetBrowser::on_message (cognitive 29) editor/src/asset/mod.rs:934 — AssetBrowser::on_message has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (10 pts), boolean chains 1 (nesting depth added 18). 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.
  • AssetBrowser::refresh (cognitive 23) editor/src/asset/mod.rs:504 — AssetBrowser::refresh has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Toolbar · ×3
  • Toolbar::handle_ui_message (cognitive 49) editor/src/plugins/absm/toolbar.rs:160 — Toolbar::handle_ui_message has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (31 pts), loops 3 (15 pts), boolean chains 3 (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.
  • Toolbar::post_handle_ui_message (cognitive 40) editor/src/plugins/animation/toolbar.rs:912 — Toolbar::post_handle_ui_message has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (30 pts), match/switch 2 (5 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Toolbar::handle_ui_message (cognitive 32) editor/src/plugins/animation/toolbar.rs:733 — Toolbar::handle_ui_message has cognitive complexity 32 (threshold 15). Drivers by points: if/else 24 (31 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · CameraController · ×3
  • CameraController::pick_recursive (cognitive 45) editor/src/camera/mod.rs:677 — CameraController::pick_recursive has cognitive complexity 45 (threshold 15). Drivers by points: if/else 14 (38 pts), boolean chains 6, loops 1 (nesting depth added 24). 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.
  • CameraController::update (cognitive 26) editor/src/camera/mod.rs:555 — CameraController::update has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 1, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • CameraController::pick (cognitive 17) editor/src/camera/mod.rs:786 — CameraController::pick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · Inspector · ×3
  • Inspector::handle_context_menu_message_ex (cognitive 41) fyrox-ui/src/inspector/mod.rs:845 — Inspector::handle_context_menu_message_ex has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (35 pts), loops 1 (4 pts), boolean chains 1, match/switch 1 (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.
  • Inspector::handle_routed_message (cognitive 29) fyrox-ui/src/inspector/mod.rs:1734 — Inspector::handle_routed_message has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 3 (6 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 12). Of this number, 26 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.
  • Inspector::apply_filter (cognitive 26) fyrox-ui/src/inspector/mod.rs:727 — Inspector::apply_filter has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 6 (9 pts), boolean chains 3 (nesting depth added 9). None of this is in the body itself: all 26 points belong to 5 function items inside it that branch (filter_recursive, check_text, make_visible_recursive, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · TileMapInteractionMode · ×3
  • TileMapInteractionMode::on_left_mouse_button_down (cognitive 29) editor/src/plugins/tilemap/interaction_mode.rs:487 — TileMapInteractionMode::on_left_mouse_button_down has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 1 (4 pts), 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.
  • TileMapInteractionMode::on_left_mouse_button_up (cognitive 19) editor/src/plugins/tilemap/interaction_mode.rs:585 — TileMapInteractionMode::on_left_mouse_button_up has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • TileMapInteractionMode::on_mouse_move (cognitive 17) editor/src/plugins/tilemap/interaction_mode.rs:680 — TileMapInteractionMode::on_mouse_move has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (16 pts), match/switch 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.
D2 · Cognitive Complexity · TerrainInteractionMode · ×3
  • TerrainInteractionMode::on_left_mouse_button_down (cognitive 24) editor/src/interaction/terrain.rs:283 — TerrainInteractionMode::on_left_mouse_button_down has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 2 (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.
  • TerrainInteractionMode::on_mouse_move (cognitive 17) editor/src/interaction/terrain.rs:356 — TerrainInteractionMode::on_mouse_move has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 1 (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.
  • TerrainInteractionMode::on_hot_key_pressed (cognitive 17) editor/src/interaction/terrain.rs:479 — TerrainInteractionMode::on_hot_key_pressed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), match/switch 2 (3 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.
D4 · Code Duplication · Edited copy of a member (50 corresponding lines) · ×3
  • Edited copy of a member (50 corresponding lines) fyrox-impl/src/scene/terrain/mod.rs:1270 — fyrox-impl/src/scene/terrain/mod.rs:1270-1319 | fyrox-impl/src/scene/terrain/mod.rs:1325-1381 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) editor/src/plugins/absm/selection.rs:199 — editor/src/plugins/absm/selection.rs:199-248 | editor/src/plugins/absm/selection.rs:250-311 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) editor/src/plugins/tilemap/palette.rs:368 — editor/src/plugins/tilemap/palette.rs:368-417 | editor/src/plugins/tilemap/palette.rs:477-540 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (47 corresponding lines) · ×3
  • Edited copy of a member (47 corresponding lines) editor/src/plugins/absm/mod.rs:830 — editor/src/plugins/absm/mod.rs:830-876 | editor/src/plugins/animation/mod.rs:994-1045 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) fyrox-ui/src/color/mod.rs:304 — fyrox-ui/src/color/mod.rs:304-353 | fyrox-ui/src/color/mod.rs:465-511 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) fyrox-core/src/pool/mod.rs:643 — fyrox-core/src/pool/mod.rs:643-689 | fyrox-core/src/pool/mod.rs:698-744 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×3
  • Edited copy of a member (38 corresponding lines) fyrox-ui/src/matrix.rs:141 — fyrox-ui/src/matrix.rs:141-178 | fyrox-ui/src/vec.rs:177-215 — 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) fyrox-ui/src/color/mod.rs:254 — fyrox-ui/src/color/mod.rs:254-302 | fyrox-ui/src/color/mod.rs:426-463 — 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) editor/src/plugins/absm/state_graph/mod.rs:81 — editor/src/plugins/absm/state_graph/mod.rs:81-119 | editor/src/plugins/absm/state_viewer/mod.rs:171-208 — 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 copies of one member (3 members, 11+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 11+ corresponding lines) editor/src/plugins/tilemap/commands.rs:622 — editor/src/plugins/tilemap/commands.rs:622-640 | editor/src/plugins/tilemap/commands.rs:680-690 | editor/src/plugins/tilemap/commands.rs:790-804 — 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) fyrox-impl/src/scene/mesh/buffer.rs:1421 — fyrox-impl/src/scene/mesh/buffer.rs:1421-1431 | fyrox-impl/src/scene/mesh/buffer.rs:1438-1449 | fyrox-impl/src/scene/mesh/buffer.rs:1456-1467 — 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) editor/src/plugins/tilemap/commands.rs:1028 — editor/src/plugins/tilemap/commands.rs:1028-1038 | editor/src/plugins/tilemap/commands.rs:1063-1073 | editor/src/plugins/tilemap/commands.rs:1098-1108 — 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 (3 members, 20+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 20+ corresponding lines) editor/src/audio/preview.rs:182 — editor/src/audio/preview.rs:182-207 | editor/src/mesh.rs:276-295 | editor/src/particle.rs:225-250 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) fyrox-build-tools/src/lib.rs:138 — fyrox-build-tools/src/lib.rs:138-165 | fyrox-build-tools/src/lib.rs:174-194 | fyrox-build-tools/src/lib.rs:196-215 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) fyrox-ui/src/utils.rs:226 — fyrox-ui/src/utils.rs:226-248 | fyrox-ui/src/utils.rs:250-273 | fyrox-ui/src/utils.rs:279-298 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×3
  • Edited copy of a member (17 corresponding lines) editor/src/plugins/collider/cuboid2d.rs:73 — editor/src/plugins/collider/cuboid2d.rs:73-89 | editor/src/plugins/collider/cuboid2d.rs:115-131 — 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) editor/src/ui_scene/selection.rs:105 — editor/src/ui_scene/selection.rs:105-121 | editor/src/world/selection.rs:98-121 — 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) editor/src/ui_scene/utils.rs:284 — editor/src/ui_scene/utils.rs:284-300 | editor/src/world/graph.rs:263-279 — 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 · Duplicated block (27 lines × 2) · ×3
  • Duplicated block (27 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:193 — editor/src/plugins/tilemap/colliders_tab.rs:193-219 | editor/src/plugins/tilemap/macro_tab.rs:259-285 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/plugins/tilemap/colliders_tab.rs:193` it begins part-way through the construct above it, so those 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, `editor/src/plugins/tilemap/macro_tab.rs:257` calls `add_row`, `auto` and `editor/src/plugins/tilemap/colliders_tab.rs:191` 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 (27 lines × 2) editor/src/scene/property.rs:613 — editor/src/scene/property.rs:613-639 | editor/src/scene/selector.rs:604-630 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/scene/property.rs:613` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `editor/src/scene/selector.rs:631` calls `add_column`, `stretch`, `add_row` and `editor/src/scene/property.rs:640` 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 (27 lines × 2) fyrox-ui/src/inspector/editors/inspectable.rs:138 — fyrox-ui/src/inspector/editors/inspectable.rs:138-164 | fyrox-ui/src/inspector/editors/refcell.rs:132-158 — before extracting anything, compare `fyrox-ui/src/inspector/editors/inspectable.rs` and `fyrox-ui/src/inspector/editors/refcell.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `fyrox-ui/src/inspector/editors/inspectable.rs:138` 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×3
  • Duplicated block (26 lines × 2) editor/src/plugins/tilemap/interaction_mode.rs:318 — editor/src/plugins/tilemap/interaction_mode.rs:318-343 | editor/src/plugins/tilemap/interaction_mode.rs:358-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. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/tilemap/interaction_mode.rs:318` it does not close everything it opens, so those 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, `editor/src/plugins/tilemap/interaction_mode.rs:344` calls `begin_update` and `editor/src/plugins/tilemap/interaction_mode.rs:384` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (26 lines × 2) fyrox-impl/src/renderer/settings.rs:180 — fyrox-impl/src/renderer/settings.rs:180-205 | fyrox-impl/src/renderer/settings.rs:216-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/renderer/settings.rs:180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26 lines × 2) fyrox-ui/src/lib.rs:3927 — fyrox-ui/src/lib.rs:3927-3952 | fyrox-ui/src/lib.rs:3959-3984 — both copies are in the same file, so extract the 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 · Duplicated block (18 lines × 2) · ×3
  • Duplicated block (18 lines × 2) fyrox-scripts/src/camera.rs:152 — fyrox-scripts/src/camera.rs:152-169 | fyrox-scripts/src/camera.rs:171-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-scripts/src/camera.rs:152` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) fyrox-ui/src/inspector/editors/array.rs:136 — fyrox-ui/src/inspector/editors/array.rs:136-153 | fyrox-ui/src/inspector/editors/array.rs:415-432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/inspector/editors/array.rs:136` it does not close everything it opens, so those exact lines 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) fyrox-ui/src/matrix.rs:161 — fyrox-ui/src/matrix.rs:161-178 | fyrox-ui/src/vec.rs:198-215 — before extracting anything, compare `fyrox-ui/src/matrix.rs` and `fyrox-ui/src/vec.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/matrix.rs:161` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×3
  • Duplicated block (11–12 lines × 2) fyrox-build-tools/src/lib.rs:149 — fyrox-build-tools/src/lib.rs:149-159 | fyrox-build-tools/src/lib.rs:203-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-build-tools/src/lib.rs:149` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `fyrox-build-tools/src/lib.rs:202` calls `to_string` and `fyrox-build-tools/src/lib.rs:148` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11–12 lines × 2) fyrox-impl/src/scene/tilemap/autotile.rs:325 — fyrox-impl/src/scene/tilemap/autotile.rs:325-336 | fyrox-impl/src/scene/tilemap/autotile.rs:489-499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/tilemap/autotile.rs:325` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 2) fyrox-ui/src/inspector/editors/inspectable.rs:167 — fyrox-ui/src/inspector/editors/inspectable.rs:167-178 | fyrox-ui/src/inspector/editors/refcell.rs:161-171 — before extracting anything, compare `fyrox-ui/src/inspector/editors/inspectable.rs` and `fyrox-ui/src/inspector/editors/refcell.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×3
  • Duplicated block (11 lines × 3) editor/src/asset/dependency.rs:133 — editor/src/asset/dependency.rs:133-143 | editor/src/plugins/ragdoll.rs:1111-1121 | editor/src/scene/property.rs:632-642 — before extracting anything, compare `editor/src/asset/dependency.rs` and `editor/src/plugins/ragdoll.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/asset/dependency.rs:133` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:69 — editor/src/plugins/tilemap/colliders_tab.rs:69-79 | editor/src/plugins/tilemap/macro_tab.rs:71-81 | editor/src/plugins/tilemap/properties_tab.rs:89-99 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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 × 3) editor/src/scene_viewer/mod.rs:399 — editor/src/scene_viewer/mod.rs:399-410 | editor/src/scene_viewer/mod.rs:424-435 | editor/src/scene_viewer/mod.rs:449-459 — 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 `editor/src/scene_viewer/mod.rs:399` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×3
  • Duplicated block (10–11 lines × 2) editor/src/plugins/tilemap/autotile.rs:517 — editor/src/plugins/tilemap/autotile.rs:517-526 | editor/src/plugins/tilemap/wfc.rs:534-544 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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 `editor/src/plugins/tilemap/wfc.rs:534` it begins part-way through the construct above it, so those exact lines 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) fyrox-graphics-gl/src/texture.rs:376 — fyrox-graphics-gl/src/texture.rs:376-385 | fyrox-graphics-wgpu/src/texture.rs:464-474 — 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 `fyrox-graphics-gl/src/texture.rs:376` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `fyrox-graphics-gl/src/texture.rs:385` calls `image_3d_size_bytes` and `fyrox-graphics-wgpu/src/texture.rs:474` 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–11 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:636 — fyrox-impl/src/scene/mesh/surface.rs:636-645 | fyrox-impl/src/scene/mesh/surface.rs:775-785 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/mesh/surface.rs:636` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×3
  • Duplicated block (10 lines × 4) fyrox-graphics-gl/src/texture.rs:375 — fyrox-graphics-gl/src/texture.rs:375-384 | fyrox-graphics-gl/src/texture.rs:579-588 | fyrox-graphics-wgpu/src/texture.rs:382-391 | fyrox-graphics-wgpu/src/texture.rs:463-472 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-graphics-gl/src/texture.rs:375` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/debug.rs:705 — fyrox-impl/src/scene/debug.rs:705-714 | fyrox-impl/src/scene/debug.rs:762-771 | fyrox-impl/src/scene/mesh/surface.rs:622-631 | fyrox-impl/src/scene/mesh/surface.rs:763-772 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/debug.rs:705` it does not close everything it opens, so those exact lines 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) fyrox-impl/src/scene/dim2/rectangle.rs:116 — fyrox-impl/src/scene/dim2/rectangle.rs:116-125 | fyrox-impl/src/scene/mesh/vertex.rs:125-134 | fyrox-impl/src/scene/mesh/vertex.rs:227-236 | fyrox-impl/src/scene/mesh/vertex.rs:279-288 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) editor/src/scene/mod.rs:766 — editor/src/scene/mod.rs:766-774 | editor/src/scene/mod.rs:786-794 | editor/src/scene/mod.rs:806-814 — 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 `editor/src/scene/mod.rs:766` it does not close everything it opens, so those exact lines 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) editor/src/plugins/absm/blendspace.rs:186 — editor/src/plugins/absm/blendspace.rs:186-194 | editor/src/plugins/absm/canvas.rs:389-397 | fyrox-ui/src/canvas.rs:93-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (9 lines × 3) editor/src/interaction/move_mode.rs:485 — editor/src/interaction/move_mode.rs:485-493 | editor/src/interaction/rotate_mode.rs:268-276 | editor/src/interaction/scale_mode.rs:243-251 — before extracting anything, compare `editor/src/interaction/move_mode.rs` and `editor/src/interaction/rotate_mode.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/interaction/move_mode.rs:485` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×3
  • Duplicated block (8–9 lines × 2) editor/src/plugins/tilemap/autotile.rs:526 — editor/src/plugins/tilemap/autotile.rs:526-533 | editor/src/plugins/tilemap/wfc.rs:611-619 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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 `editor/src/plugins/tilemap/autotile.rs:526` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8–9 lines × 2) fyrox-core/src/visitor/impls.rs:58 — fyrox-core/src/visitor/impls.rs:58-65 | fyrox-core/src/visitor/pod.rs:164-172 — 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 `fyrox-core/src/visitor/impls.rs:58` it begins part-way through the construct above it, so those 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 (8–9 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:355 — fyrox-impl/src/scene/mesh/surface.rs:355-363 | fyrox-impl/src/scene/mesh/surface.rs:365-372 — both copies are in the same file, so extract the 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 · Duplicated block (10 lines × 5) · ×3
  • Duplicated block (10 lines × 5) editor/src/asset/creator.rs:165 — editor/src/asset/creator.rs:165-174 | editor/src/plugins/absm/blendspace.rs:808-817 | editor/src/plugins/curve_editor.rs:330-339 | editor/src/plugins/export.rs:342-351 | editor/src/plugins/light.rs:205-214 — before extracting anything, compare `editor/src/asset/creator.rs` and `editor/src/plugins/light.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 5) editor/src/plugins/absm/mod.rs:526 — editor/src/plugins/absm/mod.rs:526-535 | editor/src/plugins/animation/mod.rs:355-364 | editor/src/plugins/light.rs:337-346 | editor/src/plugins/ragdoll.rs:1137-1146 | fyrox-ui/src/log.rs:251-260 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Note first that the copies are not typed on the same thing: the declarations holding them bind `ui` to `&UserInterface` in one and `&mut UserInterface` 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 × 5) editor/src/plugins/ragdoll.rs:729 — editor/src/plugins/ragdoll.rs:729-738 | editor/src/plugins/ragdoll.rs:742-753 | editor/src/plugins/ragdoll.rs:765-774 | editor/src/plugins/ragdoll.rs:831-840 | editor/src/plugins/ragdoll.rs:870-879 — 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 `editor/src/plugins/ragdoll.rs:729` 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.
D1 · Cyclomatic Complexity · UserInterface · ×2
  • UserInterface::process_os_event (cyclomatic 70) fyrox-ui/src/lib.rs:2775 — UserInterface::process_os_event has cyclomatic complexity 70 (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.
  • UserInterface::poll_single_message (cyclomatic 53) fyrox-ui/src/lib.rs:2353 — UserInterface::poll_single_message 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.
D1 · Cyclomatic Complexity · fyroxed_base · ×2
  • fyroxed_base::plugins::animation::track::type_id_to_supported_type (cyclomatic 47) editor/src/plugins/animation/track.rs:194 — fyroxed_base::plugins::animation::track::type_id_to_supported_type has cyclomatic complexity 47 (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.
  • fyroxed_base::update (cyclomatic 21) editor/src/lib.rs:3226 — fyroxed_base::update 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.
D1 · Cyclomatic Complexity · WgpuFrameBuffer · ×2
  • WgpuFrameBuffer::do_draw (cyclomatic 33) fyrox-graphics-wgpu/src/framebuffer.rs:489 — WgpuFrameBuffer::do_draw has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • WgpuFrameBuffer::get_or_create_pipeline (cyclomatic 23) fyrox-graphics-wgpu/src/framebuffer.rs:253 — WgpuFrameBuffer::get_or_create_pipeline 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.
D1 · Cyclomatic Complexity · AnimationEditor · ×2
  • AnimationEditor::handle_ui_message (cyclomatic 30) editor/src/plugins/animation/mod.rs:366 — AnimationEditor::handle_ui_message 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.
  • AnimationEditor::sync_to_model (cyclomatic 23) editor/src/plugins/animation/mod.rs:739 — AnimationEditor::sync_to_model 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.
D1 · Cyclomatic Complexity · FormattedText · ×2
  • FormattedText::arrange (cyclomatic 30) fyrox-ui/src/formatted_text.rs:1088 — FormattedText::arrange 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.
  • FormattedText::measure (cyclomatic 20) fyrox-ui/src/formatted_text.rs:949 — FormattedText::measure 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.
D1 · Cyclomatic Complexity · TreeRoot · ×2
  • TreeRoot::handle_routed_message (cyclomatic 26) fyrox-ui/src/tree.rs:843 — TreeRoot::handle_routed_message 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.
  • TreeRoot::move_selection (cyclomatic 19) fyrox-ui/src/tree.rs:972 — TreeRoot::move_selection 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.
D1 · Cyclomatic Complexity · WorldViewer · ×2
  • WorldViewer::sync_graph (cyclomatic 24) editor/src/world/mod.rs:474 — WorldViewer::sync_graph 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.
  • WorldViewer::handle_ui_message (cyclomatic 19) editor/src/world/mod.rs:682 — WorldViewer::handle_ui_message 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.
D1 · Cyclomatic Complexity · fyrox_ui · ×2
  • fyrox_ui::transform_size (cyclomatic 24) fyrox-ui/src/lib.rs:3872 — fyrox_ui::transform_size 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.
  • fyrox_ui::markdown::markdown_to_visual_tree::traverse_ast_recursively (cyclomatic 16) fyrox-ui/src/markdown.rs:101 — fyrox_ui::markdown::markdown_to_visual_tree::traverse_ast_recursively 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.
D1 · Cyclomatic Complexity · AudioPanel · ×2
  • AudioPanel::handle_ui_message (cyclomatic 22) editor/src/audio/mod.rs:368 — AudioPanel::handle_ui_message 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.
  • AudioPanel::sync_to_model (cyclomatic 16) editor/src/audio/mod.rs:456 — AudioPanel::sync_to_model 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.
D1 · Cyclomatic Complexity · NodeHandleMap · ×2
  • NodeHandleMap::remap_inheritable_handles_internal (cyclomatic 22) fyrox-graph/src/lib.rs:313 — NodeHandleMap::remap_inheritable_handles_internal 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.
  • NodeHandleMap::remap_handles_any (cyclomatic 21) fyrox-graph/src/lib.rs:211 — NodeHandleMap::remap_handles_any 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.
D1 · Cyclomatic Complexity · ProjectManager · ×2
  • ProjectManager::handle_ui_message (cyclomatic 22) project-manager/src/manager.rs:1247 — ProjectManager::handle_ui_message 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.
  • ProjectManager::on_button_click (cyclomatic 16) project-manager/src/manager.rs:1092 — ProjectManager::on_button_click has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CameraController · ×2
  • CameraController::pick_recursive (cyclomatic 19) editor/src/camera/mod.rs:677 — CameraController::pick_recursive 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.
  • CameraController::update (cyclomatic 18) editor/src/camera/mod.rs:555 — CameraController::update 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.
D1 · Cyclomatic Complexity · BitField · ×2
  • BitField::handle_routed_message (cyclomatic 18) fyrox-ui/src/bit.rs:322 — BitField::handle_routed_message 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.
  • BitField::draw (cyclomatic 17) fyrox-ui/src/bit.rs:232 — BitField::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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×2
  • Repeated repair: fyrox-ui/src/nine_patch.rs fyrox-ui/src/nine_patch.rs:516 — fyrox-ui/src/nine_patch.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is NinePatch::handle_routed_message at line 516), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “docs + tests fixes”; “fixed pm compilation + fixed clippy warnings”; “fixed bug when nine patch texture not being passed to slice editor”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-ui/src/nine_patch.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.
  • Repeated repair: fyrox-core-derive/src/reflect.rs fyrox-core-derive/src/reflect.rs:116 — fyrox-core-derive/src/reflect.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is fyrox_core_derive::reflect::quote_field_prop at line 116), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fixed `field_direct_ref/mut` for structs with hidden fields”; “fixed incorrect impl of derived `fields_count`”; “fixed tuple elements naming”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 17:25:58 +03:00' --until='2026-11-14 17:25:58 +03:00' --full-history --no-merges -- fyrox-core-derive/src/reflect.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.
D2 · Cognitive Complexity · StateViewer · ×2
  • StateViewer::sync_to_model (cognitive 98) editor/src/plugins/absm/state_viewer/mod.rs:407 — StateViewer::sync_to_model has cognitive complexity 98 (threshold 15). Drivers by points: if/else 27 (71 pts), loops 7 (17 pts), match/switch 3 (9 pts), boolean chains 1 (nesting depth added 60). 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.
  • StateViewer::handle_ui_message (cognitive 16) editor/src/plugins/absm/state_viewer/mod.rs:271 — StateViewer::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), match/switch 2 (7 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MenuItem · ×2
  • MenuItem::handle_routed_message (cognitive 96) fyrox-ui/src/menu.rs:547 — MenuItem::handle_routed_message has cognitive complexity 96 (threshold 15). Drivers by points: if/else 26 (73 pts), loops 3 (10 pts), match/switch 3 (8 pts), boolean chains 5 (nesting depth added 59). 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.
  • MenuItem::preview_message (cognitive 16) fyrox-ui/src/menu.rs:719 — MenuItem::preview_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 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.
D2 · Cognitive Complexity · AbsmCanvas · ×2
  • AbsmCanvas::handle_routed_message (cognitive 89) editor/src/plugins/absm/canvas.rs:416 — AbsmCanvas::handle_routed_message has cognitive complexity 89 (threshold 15). Drivers by points: if/else 27 (61 pts), match/switch 5 (16 pts), loops 2 (7 pts), boolean chains 5 (nesting depth added 50). 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.
  • AbsmCanvas::sync_transitions_ends (cognitive 20) editor/src/plugins/absm/canvas.rs:246 — AbsmCanvas::sync_transitions_ends has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 5, loops 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.
D2 · Cognitive Complexity · SceneViewer · ×2
  • SceneViewer::handle_ui_message (cognitive 86) editor/src/scene_viewer/mod.rs:698 — SceneViewer::handle_ui_message has cognitive complexity 86 (threshold 15). Drivers by points: if/else 24 (52 pts), match/switch 7 (26 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 48). 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.
  • SceneViewer::sync_to_model (cognitive 20) editor/src/scene_viewer/mod.rs:923 — SceneViewer::sync_to_model has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 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.
D2 · Cognitive Complexity · MachineLayer · ×2
  • MachineLayer::evaluate_pose (cognitive 69) fyrox-animation/src/machine/layer.rs:590 — MachineLayer::evaluate_pose has cognitive complexity 69 (threshold 15). Drivers by points: if/else 15 (50 pts), loops 4 (17 pts), boolean chains 2 (nesting depth added 48). 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.
  • MachineLayer::collect_active_animations_events (cognitive 26) fyrox-animation/src/machine/layer.rs:308 — MachineLayer::collect_active_animations_events has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 1 (3 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · WgpuFrameBuffer · ×2
  • WgpuFrameBuffer::do_draw (cognitive 68) fyrox-graphics-wgpu/src/framebuffer.rs:489 — WgpuFrameBuffer::do_draw has cognitive complexity 68 (threshold 15). Drivers by points: if/else 29 (49 pts), boolean chains 8, match/switch 3 (8 pts), loops 2 (3 pts) (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.
  • WgpuFrameBuffer::get_or_create_pipeline (cognitive 25) fyrox-graphics-wgpu/src/framebuffer.rs:253 — WgpuFrameBuffer::get_or_create_pipeline has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17, match/switch 5, boolean chains 3. 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.
D2 · Cognitive Complexity · FormattedText · ×2
  • FormattedText::arrange (cognitive 67) fyrox-ui/src/formatted_text.rs:1088 — FormattedText::arrange has cognitive complexity 67 (threshold 15). Drivers by points: if/else 16 (36 pts), loops 6 (15 pts), match/switch 5 (14 pts), boolean chains 2 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • FormattedText::measure (cognitive 31) fyrox-ui/src/formatted_text.rs:949 — FormattedText::measure has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (18 pts), loops 4 (8 pts), match/switch 2 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · AnimationEditor · ×2
  • AnimationEditor::sync_to_model (cognitive 65) editor/src/plugins/animation/mod.rs:739 — AnimationEditor::sync_to_model has cognitive complexity 65 (threshold 15). Drivers by points: if/else 15 (42 pts), loops 4 (16 pts), match/switch 1 (4 pts), boolean chains 3 (nesting depth added 42). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • AnimationEditor::handle_ui_message (cognitive 42) editor/src/plugins/animation/mod.rs:366 — AnimationEditor::handle_ui_message has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (28 pts), match/switch 3 (8 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WorldViewer · ×2
  • WorldViewer::sync_graph (cognitive 64) editor/src/world/mod.rs:474 — WorldViewer::sync_graph has cognitive complexity 64 (threshold 15). Drivers by points: if/else 15 (43 pts), loops 7 (18 pts), boolean chains 3 (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.
  • WorldViewer::handle_ui_message (cognitive 26) editor/src/world/mod.rs:682 — WorldViewer::handle_ui_message has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (23 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.
D2 · Cognitive Complexity · TreeRoot · ×2
  • TreeRoot::handle_routed_message (cognitive 50) fyrox-ui/src/tree.rs:843 — TreeRoot::handle_routed_message has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (34 pts), loops 3 (10 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 32). 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.
  • TreeRoot::move_selection (cognitive 49) fyrox-ui/src/tree.rs:972 — TreeRoot::move_selection has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (37 pts), loops 2 (8 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 30). 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.
D2 · Cognitive Complexity · BlendAnimationsByIndex · ×2
  • BlendAnimationsByIndex::collect_animation_events (cognitive 49) fyrox-animation/src/machine/node/blend.rs:367 — BlendAnimationsByIndex::collect_animation_events has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (38 pts), loops 1 (5 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 33). 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.
  • BlendAnimationsByIndex::eval_pose (cognitive 17) fyrox-animation/src/machine/node/blend.rs:304 — BlendAnimationsByIndex::eval_pose has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · Mesh · ×2
  • Mesh::collect_render_data (cognitive 39) fyrox-impl/src/scene/mesh/mod.rs:699 — Mesh::collect_render_data has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 3 (8 pts), match/switch 2 (6 pts), boolean chains 2 (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.
  • Mesh::accurate_world_bounding_box (cognitive 30) fyrox-impl/src/scene/mesh/mod.rs:470 — Mesh::accurate_world_bounding_box has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 4 (11 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BitField · ×2
  • BitField::handle_routed_message (cognitive 37) fyrox-ui/src/bit.rs:322 — BitField::handle_routed_message has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (26 pts), match/switch 2 (8 pts), boolean chains 3 (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.
  • BitField::draw (cognitive 23) fyrox-ui/src/bit.rs:232 — BitField::draw has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 5, 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.
D2 · Cognitive Complexity · AudioPreviewPanel · ×2
  • AudioPreviewPanel::handle_ui_message (cognitive 36) editor/src/audio/preview.rs:300 — AudioPreviewPanel::handle_ui_message has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (6 pts), match/switch 1 (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.
  • AudioPreviewPanel::enter_preview_mode (cognitive 21) editor/src/audio/preview.rs:215 — AudioPreviewPanel::enter_preview_mode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 1 (2 pts) (nesting depth added 15). 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.
D2 · Cognitive Complexity · ProjectManager · ×2
  • ProjectManager::handle_modes (cognitive 34) project-manager/src/manager.rs:834 — ProjectManager::handle_modes has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (29 pts), match/switch 2 (5 pts) (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.
  • ProjectManager::handle_ui_message (cognitive 28) project-manager/src/manager.rs:1247 — ProjectManager::handle_ui_message has cognitive complexity 28 (threshold 15). Drivers by points: if/else 18 (25 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.
D2 · Cognitive Complexity · AudioPanel · ×2
  • AudioPanel::handle_ui_message (cognitive 33) editor/src/audio/mod.rs:368 — AudioPanel::handle_ui_message has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 2 (8 pts), loops 2 (5 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.
  • AudioPanel::sync_to_model (cognitive 28) editor/src/audio/mod.rs:456 — AudioPanel::sync_to_model has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 4 (7 pts), match/switch 2, 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.
D2 · Cognitive Complexity · InspectorContext · ×2
  • InspectorContext::from_object (cognitive 31) fyrox-ui/src/inspector/mod.rs:1409 — InspectorContext::from_object has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (23 pts), match/switch 2 (7 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • InspectorContext::sync (cognitive 25) fyrox-ui/src/inspector/mod.rs:1632 — InspectorContext::sync has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 1 (4 pts), boolean chains 1, loops 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.
D2 · Cognitive Complexity · Menu · ×2
  • Menu::handle_routed_message (cognitive 31) fyrox-ui/src/menu.rs:229 — Menu::handle_routed_message has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 1 (4 pts), match/switch 1 (2 pts), boolean chains 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.
  • Menu::handle_os_event (cognitive 20) fyrox-ui/src/menu.rs:281 — Menu::handle_os_event has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 1 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · NodeHandleMap · ×2
  • NodeHandleMap::remap_inheritable_handles_internal (cognitive 30) fyrox-graph/src/lib.rs:313 — NodeHandleMap::remap_inheritable_handles_internal has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (23 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • NodeHandleMap::remap_handles_any (cognitive 28) fyrox-graph/src/lib.rs:211 — NodeHandleMap::remap_handles_any has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (21 pts), loops 3 (5 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.
D2 · Cognitive Complexity · Ray · ×2
  • Ray::cylinder_intersection (cognitive 29) fyrox-math/src/ray.rs:331 — Ray::cylinder_intersection has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (15 pts), match/switch 2 (7 pts), loops 2 (6 pts), boolean chains 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.
  • Ray::box_intersection (cognitive 17) fyrox-math/src/ray.rs:169 — Ray::box_intersection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14, boolean chains 3. 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.
D2 · Cognitive Complexity · UiSceneWorldViewerDataProvider · ×2
  • UiSceneWorldViewerDataProvider::on_change_hierarchy_request (cognitive 26) editor/src/ui_scene/utils.rs:198 — UiSceneWorldViewerDataProvider::on_change_hierarchy_request has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 2 (5 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • UiSceneWorldViewerDataProvider::icon_of (cognitive 17) editor/src/ui_scene/utils.rs:128 — UiSceneWorldViewerDataProvider::icon_of has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. 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.
D2 · Cognitive Complexity · Navmesh · ×2
  • Navmesh::query_closest_internal (cognitive 22) fyrox-impl/src/utils/navmesh.rs:477 — Navmesh::query_closest_internal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 3 (5 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.
  • Navmesh::ray_cast (cognitive 16) fyrox-impl/src/utils/navmesh.rs:579 — Navmesh::ray_cast has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 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.
D2 · Cognitive Complexity · BlendSpace · ×2
  • BlendSpace::collect_animation_events (cognitive 19) fyrox-animation/src/machine/node/blendspace.rs:156 — BlendSpace::collect_animation_events has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 1 (4 pts), match/switch 1 (3 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.
  • BlendSpace::fetch_weights (cognitive 18) fyrox-animation/src/machine/node/blendspace.rs:330 — BlendSpace::fetch_weights has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 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.
D2 · Cognitive Complexity · fyrox_build_tools · ×2
  • fyrox_build_tools::export::export (cognitive 19) fyrox-build-tools/src/export/mod.rs:148 — fyrox_build_tools::export::export has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 4 (6 pts), loops 2 (3 pts) (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.
  • fyrox_build_tools::export::build_package (cognitive 17) fyrox-build-tools/src/export/mod.rs:86 — fyrox_build_tools::export::build_package has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 3 (4 pts), 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.
D2 · Cognitive Complexity · fyrox_graphics_wgpu · ×2
  • fyrox_graphics_wgpu::program::create_bind_group_layout_with_formats (cognitive 18) fyrox-graphics-wgpu/src/program.rs:142 — fyrox_graphics_wgpu::program::create_bind_group_layout_with_formats has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 4 (8 pts), loops 1 (nesting depth added 10). 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.
  • fyrox_graphics_wgpu::framebuffer::create_bind_group (cognitive 17) fyrox-graphics-wgpu/src/framebuffer.rs:1128 — fyrox_graphics_wgpu::framebuffer::create_bind_group has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), match/switch 2 (7 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×2
  • Edited copy of a member (27 corresponding lines) fyrox-impl/src/scene/tilemap/autotile.rs:143 — fyrox-impl/src/scene/tilemap/autotile.rs:143-186 | fyrox-impl/src/scene/tilemap/autotile.rs:259-294 — 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) editor/src/plugins/inspector/editors/dyntype.rs:402 — editor/src/plugins/inspector/editors/dyntype.rs:402-428 | editor/src/plugins/inspector/editors/script.rs:498-529 — 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 (84 corresponding lines) · ×2
  • Edited copy of a member (84 corresponding lines) fyrox-ui/src/inspector/editors/array.rs:380 — fyrox-ui/src/inspector/editors/array.rs:380-463 | fyrox-ui/src/inspector/editors/collection.rs:553-659 — These two members are one piece of code written twice and then edited apart: 84 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (84 corresponding lines) fyrox-impl/src/scene/dim2/rectangle.rs:323 — fyrox-impl/src/scene/dim2/rectangle.rs:323-410 | fyrox-impl/src/scene/sprite.rs:322-405 — These two members are one piece of code written twice and then edited apart: 84 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×2
  • Edited copy of a member (39 corresponding lines) fyrox-impl/src/resource/gltf/surface.rs:489 — fyrox-impl/src/resource/gltf/surface.rs:489-527 | fyrox-impl/src/resource/gltf/surface.rs:534-590 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) fyrox-impl/src/renderer/settings.rs:256 — fyrox-impl/src/renderer/settings.rs:256-294 | fyrox-impl/src/renderer/settings.rs:297-341 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 69+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 69+ corresponding lines) editor/src/interaction/move_mode.rs:352 — editor/src/interaction/move_mode.rs:352-430 | editor/src/interaction/rotate_mode.rs:116-188 | editor/src/interaction/scale_mode.rs:112-180 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 69 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 69+ corresponding lines) editor/src/asset/menu.rs:151 — editor/src/asset/menu.rs:151-236 | editor/src/scene/property.rs:586-654 | editor/src/scene/selector.rs:565-650 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 69 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×2
  • Edited copy of a member (36 corresponding lines) editor/src/plugins/tilemap/autotile.rs:428 — editor/src/plugins/tilemap/autotile.rs:428-463 | editor/src/plugins/tilemap/wfc.rs:464-499 — 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) fyrox-impl/src/scene/terrain/brushstroke/mod.rs:841 — fyrox-impl/src/scene/terrain/brushstroke/mod.rs:841-876 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:891-928 — 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 (54 corresponding lines) · ×2
  • Edited copy of a member (54 corresponding lines) editor/src/plugins/tilemap/palette.rs:2175 — editor/src/plugins/tilemap/palette.rs:2175-2230 | editor/src/plugins/tilemap/panel_preview.rs:87-140 — 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.
  • Edited copy of a member (54 corresponding lines) editor/src/plugins/absm/command/mod.rs:220 — editor/src/plugins/absm/command/mod.rs:220-273 | editor/src/plugins/absm/command/mod.rs:355-409 — 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 (46 corresponding lines) · ×2
  • Edited copy of a member (46 corresponding lines) fyrox-graphics-gl/src/framebuffer.rs:432 — fyrox-graphics-gl/src/framebuffer.rs:432-477 | fyrox-graphics-gl/src/framebuffer.rs:488-533 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) editor/src/scene/commands/mod.rs:178 — editor/src/scene/commands/mod.rs:178-223 | editor/src/ui_scene/commands/graph.rs:228-275 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×2
  • Edited copy of a member (35 corresponding lines) fyrox-ui/src/key.rs:242 — fyrox-ui/src/key.rs:242-290 | fyrox-ui/src/key.rs:455-489 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) fyrox-impl/src/scene/mesh/surface.rs:394 — fyrox-impl/src/scene/mesh/surface.rs:394-428 | fyrox-impl/src/scene/mesh/surface.rs:432-466 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×2
  • Edited copy of a member (44 corresponding lines) fyrox-build-tools/src/export/android.rs:56 — fyrox-build-tools/src/export/android.rs:56-99 | fyrox-build-tools/src/export/pc.rs:44-87 — 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.
  • Edited copy of a member (44 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs:1002 — fyrox-impl/src/scene/dim2/physics/mod.rs:1002-1045 | fyrox-impl/src/scene/graph/physics/mod.rs:1443-1486 — 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 (30 corresponding lines) · ×2
  • Edited copy of a member (30 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs:925 — fyrox-impl/src/scene/dim2/physics/mod.rs:925-954 | fyrox-impl/src/scene/graph/physics/mod.rs:1366-1395 — 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) editor/src/scene/commands/mesh.rs:56 — editor/src/scene/commands/mesh.rs:56-86 | editor/src/scene/commands/mesh.rs:88-117 — 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 (37 corresponding lines) · ×2
  • Edited copy of a member (37 corresponding lines) fyrox-ui/src/inspector/editors/inspectable.rs:91 — fyrox-ui/src/inspector/editors/inspectable.rs:91-127 | fyrox-ui/src/inspector/editors/refcell.rs:82-121 — 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.
  • Edited copy of a member (37 corresponding lines) fyrox-ui/src/inspector/editors/array.rs:258 — fyrox-ui/src/inspector/editors/array.rs:258-294 | fyrox-ui/src/inspector/editors/collection.rs:402-448 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×2
  • Edited copy of a member (32 corresponding lines) editor/src/plugins/tilemap/tile_editor.rs:258 — editor/src/plugins/tilemap/tile_editor.rs:258-289 | editor/src/plugins/tilemap/tile_editor.rs:295-326 — 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) editor/src/command/mod.rs:452 — editor/src/command/mod.rs:452-483 | editor/src/command/mod.rs:520-551 — 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) fyrox-ui/src/file_browser/field.rs:156 — fyrox-ui/src/file_browser/field.rs:156-195 | fyrox-ui/src/path.rs:195-241 — 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) fyrox-impl/src/renderer/bloom/mod.rs:88 — fyrox-impl/src/renderer/bloom/mod.rs:88-129 | fyrox-impl/src/renderer/occlusion/optimizer.rs:90-129 — 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 copies of one member (4 members, 21+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 21+ corresponding lines) fyrox-impl/src/scene/dim2/rigidbody.rs:200 — fyrox-impl/src/scene/dim2/rigidbody.rs:200-221 | fyrox-impl/src/scene/dim2/rigidbody.rs:661-681 | fyrox-impl/src/scene/rigidbody.rs:289-313 | fyrox-impl/src/scene/rigidbody.rs:837-860 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) editor/src/plugins/absm/command/mod.rs:115 — editor/src/plugins/absm/command/mod.rs:115-155 | editor/src/plugins/absm/command/mod.rs:275-300 | editor/src/plugins/absm/command/mod.rs:411-434 | editor/src/plugins/absm/command/mod.rs:554-623 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×2
  • Edited copy of a member (26 corresponding lines) fyrox-impl/src/scene/terrain/mod.rs:416 — fyrox-impl/src/scene/terrain/mod.rs:416-445 | fyrox-impl/src/scene/terrain/mod.rs:1120-1145 — 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) fyrox-impl/src/engine/hotreload.rs:177 — fyrox-impl/src/engine/hotreload.rs:177-206 | fyrox-impl/src/engine/hotreload.rs:215-240 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×2
  • Edited copy of a member (34 corresponding lines) editor/src/plugins/inspector/editors/dyntype.rs:157 — editor/src/plugins/inspector/editors/dyntype.rs:157-190 | editor/src/plugins/inspector/editors/script.rs:227-261 — 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) fyrox-impl/src/renderer/settings.rs:179 — fyrox-impl/src/renderer/settings.rs:179-212 | fyrox-impl/src/renderer/settings.rs:215-253 — 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 copies of one member (3 members, 16+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 16+ corresponding lines) fyrox-core/src/visitor/impls.rs:210 — fyrox-core/src/visitor/impls.rs:210-229 | fyrox-impl/src/scene/node/container.rs:70-85 | fyrox-ui/src/node/container.rs:70-85 — 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) fyrox-impl/src/resource/model/loader.rs:67 — fyrox-impl/src/resource/model/loader.rs:67-93 | fyrox-ui/src/font/loader.rs:118-133 | fyrox-ui/src/loader.rs:55-72 — 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 (3 members, 10+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 10+ corresponding lines) fyrox-impl/src/scene/terrain/brushstroke/mod.rs:985 — fyrox-impl/src/scene/terrain/brushstroke/mod.rs:985-994 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:996-1007 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:1009-1018 — 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) fyrox-ui/src/absm.rs:131 — fyrox-ui/src/absm.rs:131-142 | fyrox-ui/src/absm.rs:289-298 | fyrox-ui/src/animation.rs:160-169 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 11+ corresponding lines) fyrox-impl/src/scene/tilemap/mod.rs:663 — fyrox-impl/src/scene/tilemap/mod.rs:663-673 | fyrox-impl/src/scene/tilemap/mod.rs:675-689 | fyrox-impl/src/scene/tilemap/mod.rs:725-739 | fyrox-impl/src/scene/tilemap/mod.rs:870-884 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) fyrox-ui/src/inspector/editors/char.rs:77 — fyrox-ui/src/inspector/editors/char.rs:77-88 | fyrox-ui/src/inspector/editors/immutable_string.rs:81-91 | fyrox-ui/src/inspector/editors/string.rs:77-87 | fyrox-ui/src/inspector/editors/utf32.rs:76-86 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 13+ corresponding lines) fyrox-ui/src/numeric.rs:277 — fyrox-ui/src/numeric.rs:277-291 | fyrox-ui/src/range.rs:129-141 | fyrox-ui/src/rect.rs:138-150 | fyrox-ui/src/vec.rs:122-134 — 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.
  • Edited copies of one member (4 members, 13+ corresponding lines) editor/src/plugins/collider/cone.rs:60 — editor/src/plugins/collider/cone.rs:60-72 | editor/src/plugins/collider/cone.rs:94-106 | editor/src/plugins/collider/cylinder.rs:60-73 | editor/src/plugins/collider/cylinder.rs:95-108 — 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 (3 members, 14+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 14+ corresponding lines) editor/src/plugins/tilemap/colliders_tab.rs:417 — editor/src/plugins/tilemap/colliders_tab.rs:417-431 | editor/src/plugins/tilemap/macro_tab.rs:524-537 | editor/src/plugins/tilemap/properties_tab.rs:908-922 — 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) editor/src/plugins/collider/capsule.rs:107 — editor/src/plugins/collider/capsule.rs:107-121 | editor/src/plugins/collider/capsule2d.rs:115-130 | editor/src/plugins/collider/segment2d.rs:80-93 — 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, 13+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 13+ corresponding lines) editor/src/plugins/inspector/editors/resource.rs:433 — editor/src/plugins/inspector/editors/resource.rs:433-445 | editor/src/plugins/inspector/editors/surface.rs:321-334 | editor/src/plugins/material/editor.rs:388-400 — 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) fyrox-core/src/pool/handle.rs:110 — fyrox-core/src/pool/handle.rs:110-122 | fyrox-core/src/pool/mod.rs:151-163 | fyrox-core/src/variable.rs:419-431 — 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 copies of one member (3 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 7+ corresponding lines) fyrox-impl/src/scene/terrain/mod.rs:209 — fyrox-impl/src/scene/terrain/mod.rs:209-218 | fyrox-impl/src/scene/terrain/mod.rs:223-229 | fyrox-impl/src/scene/terrain/mod.rs:232-238 — 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) editor/src/plugins/tilemap/tile_bounds_editor.rs:78 — editor/src/plugins/tilemap/tile_bounds_editor.rs:78-84 | editor/src/plugins/tilemap/tile_bounds_editor.rs:85-91 | editor/src/plugins/tilemap/tile_bounds_editor.rs:92-98 — 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.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 7+ corresponding lines) fyrox-impl/src/resource/curve/mod.rs:99 — fyrox-impl/src/resource/curve/mod.rs:99-105 | fyrox-impl/src/scene/tilemap/brush.rs:544-551 | fyrox-impl/src/scene/tilemap/tileset.rs:2038-2045 | fyrox-ui/src/style/mod.rs:769-776 — 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) fyrox-ui/src/inspector/editors/char.rs:69 — fyrox-ui/src/inspector/editors/char.rs:69-75 | fyrox-ui/src/inspector/editors/immutable_string.rs:73-79 | fyrox-ui/src/inspector/editors/string.rs:69-75 | fyrox-ui/src/inspector/editors/utf32.rs:68-74 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×2
  • Duplicated block (28 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:742 — fyrox-impl/src/scene/dim2/physics/mod.rs:742-769 | fyrox-impl/src/scene/graph/physics/mod.rs:1186-1213 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:742` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `crate) fn update(&mut` in one and `super) fn update(&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, `fyrox-impl/src/scene/graph/physics/mod.rs:1185` calls `default` and `fyrox-impl/src/scene/dim2/physics/mod.rs:741` 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 (28 lines × 2) fyrox-impl/src/scene/tilemap/update.rs:919 — fyrox-impl/src/scene/tilemap/update.rs:919-946 | fyrox-impl/src/scene/tilemap/update.rs:947-974 — both copies are in the same file, so extract the 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 · Duplicated block (22–23 lines × 2) · ×2
  • Duplicated block (22–23 lines × 2) fyrox-impl/src/engine/mod.rs:481 — fyrox-impl/src/engine/mod.rs:481-503 | fyrox-impl/src/engine/mod.rs:573-594 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/engine/mod.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. 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 (22–23 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1101 — fyrox-impl/src/scene/dim2/physics/mod.rs:1101-1122 | fyrox-impl/src/scene/graph/physics/mod.rs:1599-1621 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1101` it begins part-way through the construct above it, so those 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 `rigid_body_node` to `&scene::dim2::rigidbody::RigidBody` in one and `&scene::rigidbody::RigidBody` 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • Duplicated block (22 lines × 2) editor/src/asset/creator.rs:135 — editor/src/asset/creator.rs:135-156 | editor/src/scene/dialog.rs:118-139 — 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 `editor/src/asset/creator.rs:135` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1445 — fyrox-impl/src/scene/dim2/physics/mod.rs:1445-1466 | fyrox-impl/src/scene/graph/physics/mod.rs:1967-1988 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1445` 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) editor/src/asset/dependency.rs:134 — editor/src/asset/dependency.rs:134-152 | editor/src/plugins/ragdoll.rs:1112-1130 — before extracting anything, compare `editor/src/asset/dependency.rs` and `editor/src/plugins/ragdoll.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/asset/dependency.rs:134` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (19 lines × 2) fyrox-graph/src/lib.rs:240 — fyrox-graph/src/lib.rs:240-258 | fyrox-graph/src/lib.rs:363-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-graph/src/lib.rs:240` it begins part-way through the construct above it, so those 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×2
  • Duplicated block (17–18 lines × 2) editor/src/plugins/tilemap/autotile.rs:620 — editor/src/plugins/tilemap/autotile.rs:620-637 | editor/src/plugins/tilemap/wfc.rs:639-655 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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 `editor/src/plugins/tilemap/autotile.rs:620` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (17–18 lines × 2) editor/src/plugins/tilemap/palette.rs:1674 — editor/src/plugins/tilemap/palette.rs:1674-1690 | editor/src/plugins/tilemap/palette.rs:1805-1822 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (13–18 lines × 2) · ×2
  • Duplicated block (13–18 lines × 2) fyrox-ui/src/border.rs:164 — fyrox-ui/src/border.rs:164-176 | fyrox-ui/src/scroll_panel.rs:242-259 — 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 `fyrox-ui/src/scroll_panel.rs:242` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (13–18 lines × 2) fyrox-impl/src/scene/terrain/mod.rs:2272 — fyrox-impl/src/scene/terrain/mod.rs:2272-2284 | fyrox-impl/src/scene/terrain/mod.rs:2299-2316 — both copies are in the same file, so extract the 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 · Duplicated block (13–15 lines × 2) · ×2
  • Duplicated block (13–15 lines × 2) editor/src/lib.rs:455 — editor/src/lib.rs:455-467 | editor/src/lib.rs:476-490 — both copies are in the same file, so extract the 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–15 lines × 2) fyrox-ui/src/inspector/editors/array.rs:468 — fyrox-ui/src/inspector/editors/array.rs:468-480 | fyrox-ui/src/inspector/editors/collection.rs:669-683 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `fyrox-ui/src/inspector/editors/array.rs:468` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×2
  • Duplicated block (13 lines × 3) editor/src/asset/creator.rs:144 — editor/src/asset/creator.rs:144-157 | editor/src/plugins/light.rs:170-182 | editor/src/scene/dialog.rs:127-140 — before extracting anything, compare `editor/src/asset/creator.rs` and `editor/src/plugins/light.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/asset/creator.rs:144` it begins part-way through the construct above it, so those exact lines 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) fyrox-ui/src/inspector/editors/cell.rs:84 — fyrox-ui/src/inspector/editors/cell.rs:84-96 | fyrox-ui/src/inspector/editors/cell.rs:130-142 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:181-193 — 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 `fyrox-ui/src/inspector/editors/cell.rs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×2
  • Duplicated block (11–13 lines × 2) editor/src/asset/selection.rs:206 — editor/src/asset/selection.rs:206-216 | editor/src/asset/selection.rs:261-273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/asset/selection.rs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–13 lines × 2) editor/src/asset/selection.rs:227 — editor/src/asset/selection.rs:227-237 | editor/src/asset/selection.rs:284-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/asset/selection.rs:284` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–13 lines × 2) · ×2
  • Duplicated block (10–13 lines × 2) editor/src/plugins/curve_editor.rs:256 — editor/src/plugins/curve_editor.rs:256-268 | editor/src/plugins/light.rs:286-295 — 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 `editor/src/plugins/curve_editor.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.
  • Duplicated block (10–13 lines × 2) fyrox-graph/src/lib.rs:1706 — fyrox-graph/src/lib.rs:1706-1715 | fyrox-graph/src/lib.rs:1774-1786 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-graph/src/lib.rs:1706` it does not close everything it opens, so those 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×2
  • Duplicated block (12 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:242 — editor/src/plugins/tilemap/colliders_tab.rs:242-253 | editor/src/plugins/tilemap/macro_tab.rs:311-322 | editor/src/plugins/tilemap/properties_tab.rs:466-477 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/plugins/tilemap/colliders_tab.rs:242` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:87 — editor/src/plugins/tilemap/colliders_tab.rs:87-98 | editor/src/plugins/tilemap/macro_tab.rs:89-100 | editor/src/plugins/tilemap/properties_tab.rs:107-118 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/plugins/tilemap/colliders_tab.rs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: fyrox-math — fyrox-math: abstractness 0.26, instability 0.00, distance 0.74 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: fyrox-autotile — fyrox-autotile: abstractness 0.29, instability 0.00, distance 0.71 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
D1 · Cyclomatic Complexity · TextBox · ×1
  • TextBox::handle_routed_message (cyclomatic 99) fyrox-ui/src/text_box.rs:1147 — TextBox::handle_routed_message has cyclomatic complexity 99 (threshold 15). Of this number, 96 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Window · ×1
  • Window::handle_routed_message (cyclomatic 90) fyrox-ui/src/window.rs:393 — Window::handle_routed_message has cyclomatic complexity 90 (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.
D1 · Cyclomatic Complexity · CurveEditor · ×1
  • CurveEditor::handle_routed_message (cyclomatic 80) fyrox-ui/src/curve/mod.rs:574 — CurveEditor::handle_routed_message has cyclomatic complexity 80 (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.
D1 · Cyclomatic Complexity · AsciiReader · ×1
  • AsciiReader::read_field (cyclomatic 59) fyrox-core/src/visitor/reader/ascii.rs:202 — AsciiReader::read_field 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.
D1 · Cyclomatic Complexity · AsciiWriter · ×1
  • AsciiWriter::write_field (cyclomatic 55) fyrox-core/src/visitor/writer/ascii.rs:34 — AsciiWriter::write_field has cyclomatic complexity 55 (threshold 15). Of this number, 53 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
D1 · Cyclomatic Complexity · SceneViewer · ×1
  • SceneViewer::handle_ui_message (cyclomatic 53) editor/src/scene_viewer/mod.rs:698 — SceneViewer::handle_ui_message 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.
D1 · Cyclomatic Complexity · TrackValue · ×1
  • TrackValue::apply_to_any (cyclomatic 52) fyrox-animation/src/value.rs:234 — TrackValue::apply_to_any has cyclomatic complexity 52 (threshold 15). Of this number, 51 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D1 · Cyclomatic Complexity · AssetBrowser · ×1
  • AssetBrowser::handle_ui_message (cyclomatic 46) editor/src/asset/mod.rs:632 — AssetBrowser::handle_ui_message has cyclomatic complexity 46 (threshold 15). Of this number, 44 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · AbsmCanvas · ×1
  • AbsmCanvas::handle_routed_message (cyclomatic 45) editor/src/plugins/absm/canvas.rs:416 — AbsmCanvas::handle_routed_message has cyclomatic complexity 45 (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.
D1 · Cyclomatic Complexity · MenuItem · ×1
  • MenuItem::handle_routed_message (cyclomatic 43) fyrox-ui/src/menu.rs:547 — MenuItem::handle_routed_message 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.
D1 · Cyclomatic Complexity · DeferredLightRenderer · ×1
  • DeferredLightRenderer::render (cyclomatic 40) fyrox-impl/src/renderer/light.rs:254 — DeferredLightRenderer::render 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.
D1 · Cyclomatic Complexity · Texture · ×1
  • Texture::load_from_memory (cyclomatic 39) fyrox-texture/src/lib.rs:1493 — Texture::load_from_memory has cyclomatic complexity 39 (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.
D1 · Cyclomatic Complexity · Tree · ×1
  • Tree::handle_routed_message (cyclomatic 38) fyrox-ui/src/tree.rs:350 — Tree::handle_routed_message has cyclomatic complexity 38 (threshold 15). Of this number, 33 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · NumericUpDown · ×1
  • NumericUpDown::handle_routed_message (cyclomatic 37) fyrox-ui/src/numeric.rs:403 — NumericUpDown::handle_routed_message has cyclomatic complexity 37 (threshold 15). Of this number, 31 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.
D1 · Cyclomatic Complexity · ScrollViewer · ×1
  • ScrollViewer::handle_routed_message (cyclomatic 36) fyrox-ui/src/scroll_viewer.rs:236 — ScrollViewer::handle_routed_message 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.
D1 · Cyclomatic Complexity · AssetItemContextMenu · ×1
  • AssetItemContextMenu::handle_ui_message (cyclomatic 35) editor/src/asset/menu.rs:343 — AssetItemContextMenu::handle_ui_message 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.
D1 · Cyclomatic Complexity · StateViewer · ×1
  • StateViewer::sync_to_model (cyclomatic 33) editor/src/plugins/absm/state_viewer/mod.rs:407 — StateViewer::sync_to_model has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SceneNodeContextMenu · ×1
  • SceneNodeContextMenu::handle_ui_message (cyclomatic 33) editor/src/world/menu.rs:280 — SceneNodeContextMenu::handle_ui_message has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GlShader · ×1
  • GlShader::new (cyclomatic 33) fyrox-graphics-gl/src/program.rs:153 — GlShader::new has cyclomatic complexity 33 (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.
D1 · Cyclomatic Complexity · ScrollBar · ×1
  • ScrollBar::handle_routed_message (cyclomatic 32) fyrox-ui/src/scroll_bar.rs:236 — ScrollBar::handle_routed_message 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.
D1 · Cyclomatic Complexity · Engine · ×1
  • Engine::reload_plugin (cyclomatic 30) fyrox-impl/src/engine/mod.rs:2502 — Engine::reload_plugin 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.
D1 · Cyclomatic Complexity · ScriptProcessor · ×1
  • ScriptProcessor::handle_scripts (cyclomatic 30) fyrox-impl/src/engine/mod.rs:645 — ScriptProcessor::handle_scripts 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.
D1 · Cyclomatic Complexity · Popup · ×1
  • Popup::handle_routed_message (cyclomatic 30) fyrox-ui/src/popup.rs:386 — Popup::handle_routed_message 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.
D1 · Cyclomatic Complexity · PropertiesTab · ×1
  • PropertiesTab::handle_ui_message (cyclomatic 28) editor/src/plugins/tilemap/properties_tab.rs:580 — PropertiesTab::handle_ui_message has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · CurveEditorWindow · ×1
  • CurveEditorWindow::handle_ui_message (cyclomatic 27) editor/src/plugins/curve_editor.rs:416 — CurveEditorWindow::handle_ui_message 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.
D1 · Cyclomatic Complexity · ColorPicker · ×1
  • ColorPicker::handle_routed_message (cyclomatic 27) fyrox-ui/src/color/mod.rs:818 — ColorPicker::handle_routed_message 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.
D1 · Cyclomatic Complexity · Animation · ×1
  • Animation::update_root_motion (cyclomatic 26) fyrox-animation/src/lib.rs:498 — Animation::update_root_motion has cyclomatic complexity 26 (threshold 15). Of this number, 24 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · AbsmEditor · ×1
  • AbsmEditor::handle_ui_message (cyclomatic 25) editor/src/plugins/absm/mod.rs:580 — AbsmEditor::handle_ui_message 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.
D1 · Cyclomatic Complexity · StateGraphViewer · ×1
  • StateGraphViewer::sync_to_model (cyclomatic 25) editor/src/plugins/absm/state_graph/mod.rs:294 — StateGraphViewer::sync_to_model 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.
D1 · Cyclomatic Complexity · MaterialEditor · ×1
  • MaterialEditor::sync_to_model (cyclomatic 25) editor/src/plugins/material/mod.rs:575 — MaterialEditor::sync_to_model 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.
D1 · Cyclomatic Complexity · Text · ×1
  • Text::handle_routed_message (cyclomatic 25) fyrox-ui/src/text.rs:425 — Text::handle_routed_message 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.
D1 · Cyclomatic Complexity · fyrox_project_manager · ×1
  • fyrox_project_manager::main (cyclomatic 25) project-manager/src/main.rs:73 — fyrox_project_manager::main 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.
D1 · Cyclomatic Complexity · FileMenu · ×1
  • FileMenu::handle_ui_message (cyclomatic 24) editor/src/menu/file.rs:355 — FileMenu::handle_ui_message 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.
D1 · Cyclomatic Complexity · TileSetEditor · ×1
  • TileSetEditor::handle_ui_message (cyclomatic 24) editor/src/plugins/tilemap/tileset.rs:642 — TileSetEditor::handle_ui_message 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.
D1 · Cyclomatic Complexity · PropertyAction · ×1
  • PropertyAction::apply_on_result (cyclomatic 24) fyrox-ui/src/inspector/mod.rs:296 — PropertyAction::apply_on_result 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.
D1 · Cyclomatic Complexity · TabControl · ×1
  • TabControl::handle_routed_message (cyclomatic 24) fyrox-ui/src/tab_control.rs:375 — TabControl::handle_routed_message 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.
D1 · Cyclomatic Complexity · TileInspector · ×1
  • TileInspector::handle_ui_message (cyclomatic 23) editor/src/plugins/tilemap/tile_inspector.rs:1070 — TileInspector::handle_ui_message 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.
D1 · Cyclomatic Complexity · GlGraphicsServer · ×1
  • GlGraphicsServer::new (cyclomatic 23) fyrox-graphics-gl/src/server.rs:593 — GlGraphicsServer::new 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.
D1 · Cyclomatic Complexity · FbxScene · ×1
  • FbxScene::new (cyclomatic 23) fyrox-impl/src/resource/fbx/scene/mod.rs:57 — FbxScene::new has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · Chunk · ×1
  • Chunk::set_height_map (cyclomatic 23) fyrox-impl/src/scene/terrain/mod.rs:534 — Chunk::set_height_map 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.
D1 · Cyclomatic Complexity · Decorator · ×1
  • Decorator::handle_routed_message (cyclomatic 23) fyrox-ui/src/decorator.rs:157 — Decorator::handle_routed_message 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.
D1 · Cyclomatic Complexity · BlendSpaceField · ×1
  • BlendSpaceField::handle_routed_message (cyclomatic 22) editor/src/plugins/absm/blendspace.rs:317 — BlendSpaceField::handle_routed_message 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.
D1 · Cyclomatic Complexity · InspectorPlugin · ×1
  • InspectorPlugin::on_ui_message (cyclomatic 22) editor/src/plugins/inspector/mod.rs:571 — InspectorPlugin::on_ui_message has cyclomatic complexity 22 (threshold 15). Of this number, 21 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.
D1 · Cyclomatic Complexity · RenderDataBundle · ×1
  • RenderDataBundle::render_to_frame_buffer (cyclomatic 22) fyrox-impl/src/renderer/bundle.rs:509 — RenderDataBundle::render_to_frame_buffer has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · Ruler · ×1
  • Ruler::handle_routed_message (cyclomatic 21) editor/src/plugins/animation/ruler.rs:291 — Ruler::handle_routed_message 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.
D1 · Cyclomatic Complexity · MachineLayer · ×1
  • MachineLayer::evaluate_pose (cyclomatic 21) fyrox-animation/src/machine/layer.rs:590 — MachineLayer::evaluate_pose 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.
D1 · Cyclomatic Complexity · ListView · ×1
  • ListView::handle_routed_message (cyclomatic 21) fyrox-ui/src/list_view.rs:395 — ListView::handle_routed_message 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.
D1 · Cyclomatic Complexity · Selector · ×1
  • Selector::handle_routed_message (cyclomatic 21) fyrox-ui/src/selector.rs:149 — Selector::handle_routed_message 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.
D1 · Cyclomatic Complexity · RootMotionDropdownArea · ×1
  • RootMotionDropdownArea::handle_ui_message (cyclomatic 20) editor/src/plugins/animation/toolbar.rs:211 — RootMotionDropdownArea::handle_ui_message 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.
D1 · Cyclomatic Complexity · GameScene · ×1
  • GameScene::draw_auxiliary_geometry::draw_recursively (cyclomatic 20) editor/src/scene/mod.rs:341 — GameScene::draw_auxiliary_geometry::draw_recursively 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.
D1 · Cyclomatic Complexity · LightmapInputData · ×1
  • LightmapInputData::from_scene (cyclomatic 20) fyrox-impl/src/utils/lightmap.rs:403 — LightmapInputData::from_scene 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.
D1 · Cyclomatic Complexity · CheckBox · ×1
  • CheckBox::handle_routed_message (cyclomatic 20) fyrox-ui/src/check_box.rs:200 — CheckBox::handle_routed_message 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.
D1 · Cyclomatic Complexity · AbsmNode · ×1
  • AbsmNode::handle_routed_message (cyclomatic 19) editor/src/plugins/absm/node.rs:163 — AbsmNode::handle_routed_message 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.
D1 · Cyclomatic Complexity · GlTexture · ×1
  • GlTexture::set_data (cyclomatic 19) fyrox-graphics-gl/src/texture.rs:397 — GlTexture::set_data 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: PixelDescriptor::from (cyclomatic 36) 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.
D1 · Cyclomatic Complexity · Ragdoll · ×1
  • Ragdoll::update (cyclomatic 19) fyrox-impl/src/scene/ragdoll.rs:153 — Ragdoll::update 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.
D1 · Cyclomatic Complexity · fyrox_template_core · ×1
  • fyrox_template_core::upgrade_project (cyclomatic 19) template-core/src/lib.rs:806 — fyrox_template_core::upgrade_project 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.
D1 · Cyclomatic Complexity · WfcMacro · ×1
  • WfcMacro::on_instance_ui_message (cyclomatic 18) editor/src/plugins/tilemap/wfc.rs:267 — WfcMacro::on_instance_ui_message 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.
D1 · Cyclomatic Complexity · Mesh · ×1
  • Mesh::collect_render_data (cyclomatic 18) fyrox-impl/src/scene/mesh/mod.rs:699 — Mesh::collect_render_data 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.
D1 · Cyclomatic Complexity · Button · ×1
  • Button::handle_routed_message (cyclomatic 18) fyrox-ui/src/button.rs:189 — Button::handle_routed_message 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.
D1 · Cyclomatic Complexity · AudioPreviewPanel · ×1
  • AudioPreviewPanel::handle_ui_message (cyclomatic 17) editor/src/audio/preview.rs:300 — AudioPreviewPanel::handle_ui_message 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.
D1 · Cyclomatic Complexity · HandlePropertyEditor · ×1
  • HandlePropertyEditor::handle_routed_message (cyclomatic 17) editor/src/plugins/inspector/editors/handle.rs:177 — HandlePropertyEditor::handle_routed_message 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.
D1 · Cyclomatic Complexity · MacroPropertyValueField · ×1
  • MacroPropertyValueField::on_ui_message (cyclomatic 17) editor/src/plugins/tilemap/brush_macro.rs:811 — MacroPropertyValueField::on_ui_message 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.
D1 · Cyclomatic Complexity · TileMapEditorPlugin · ×1
  • TileMapEditorPlugin::on_message (cyclomatic 17) editor/src/plugins/tilemap/mod.rs:816 — TileMapEditorPlugin::on_message 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.
D1 · Cyclomatic Complexity · UiSceneWorldViewerDataProvider · ×1
  • UiSceneWorldViewerDataProvider::icon_of (cyclomatic 17) editor/src/ui_scene/utils.rs:128 — UiSceneWorldViewerDataProvider::icon_of 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.
D1 · Cyclomatic Complexity · fyrox_core · ×1
  • fyrox_core::variable::try_inherit_properties (cyclomatic 17) fyrox-core/src/variable.rs:613 — fyrox_core::variable::try_inherit_properties 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.
D1 · Cyclomatic Complexity · SceneGraph · ×1
  • SceneGraph::restore_integrity (cyclomatic 17) fyrox-graph/src/lib.rs:1208 — SceneGraph::restore_integrity 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.
D1 · Cyclomatic Complexity · RenderDataBundleStorage · ×1
  • RenderDataBundleStorage::from_graph (cyclomatic 17) fyrox-impl/src/renderer/bundle.rs:872 — RenderDataBundleStorage::from_graph has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: fyrox_impl::renderer::bundle::write_shader_values (cyclomatic 21) 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.
D1 · Cyclomatic Complexity · UiRenderer · ×1
  • UiRenderer::render (cyclomatic 17) fyrox-impl/src/renderer/ui_renderer.rs:289 — UiRenderer::render 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.
D1 · Cyclomatic Complexity · TileDataUpdate · ×1
  • TileDataUpdate::swap_with_data (cyclomatic 17) fyrox-impl/src/scene/tilemap/update.rs:287 — TileDataUpdate::swap_with_data 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.
D1 · Cyclomatic Complexity · DockingManager · ×1
  • DockingManager::set_layout (cyclomatic 17) fyrox-ui/src/dock/mod.rs:244 — DockingManager::set_layout 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.
D1 · Cyclomatic Complexity · MeshControlPanel · ×1
  • MeshControlPanel::handle_ui_message (cyclomatic 16) editor/src/mesh.rs:156 — MeshControlPanel::handle_ui_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.
D1 · Cyclomatic Complexity · ExportWindow · ×1
  • ExportWindow::handle_ui_message (cyclomatic 16) editor/src/plugins/export.rs:372 — ExportWindow::handle_ui_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.
D1 · Cyclomatic Complexity · SurfaceDataPropertyEditor · ×1
  • SurfaceDataPropertyEditor::handle_routed_message (cyclomatic 16) editor/src/plugins/inspector/editors/surface.rs:94 — SurfaceDataPropertyEditor::handle_routed_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.
D1 · Cyclomatic Complexity · SettingsWindow · ×1
  • SettingsWindow::handle_ui_message (cyclomatic 16) editor/src/plugins/settings.rs:242 — SettingsWindow::handle_ui_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.
D1 · Cyclomatic Complexity · SceneItem · ×1
  • SceneItem::handle_routed_message (cyclomatic 16) editor/src/world/item.rs:170 — SceneItem::handle_routed_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.
D1 · Cyclomatic Complexity · GlFrameBuffer · ×1
  • GlFrameBuffer::clear (cyclomatic 16) fyrox-graphics-gl/src/framebuffer.rs:309 — GlFrameBuffer::clear 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.
D1 · Cyclomatic Complexity · Graph · ×1
  • Graph::process_node_messages (cyclomatic 16) fyrox-impl/src/scene/graph/mod.rs:1280 — Graph::process_node_messages has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · BehaviorTree · ×1
  • BehaviorTree::tick_recursive (cyclomatic 16) fyrox-impl/src/utils/behavior/mod.rs:175 — BehaviorTree::tick_recursive 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.
D1 · Cyclomatic Complexity · fyrox_resource · ×1
  • fyrox_resource::collect_used_resources (cyclomatic 16) fyrox-resource/src/lib.rs:658 — fyrox_resource::collect_used_resources 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.
D17 · Explicit Debt · XxxComment · ×1
  • XxxComment fyrox-material/src/shader/mod.rs:410 — //! - **Possible values:** `None`, [Some(CullFace::XXX)](fyrox_graphics::CullFace) — 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.
D17 · Explicit Debt · TodoComment repeated across 15 files · ×1
  • TodoComment repeated across 15 files fyrox-impl/src/scene/accel.rs:21 — The identical TodoComment appears in 15 files (19 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 19 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
D2 · Cognitive Complexity · Window · ×1
  • Window::handle_routed_message (cognitive 237) fyrox-ui/src/window.rs:393 — Window::handle_routed_message has cognitive complexity 237 (threshold 15). Drivers by points: if/else 53 (192 pts), match/switch 7 (23 pts), loops 3 (14 pts), boolean chains 8 (nesting depth added 166). 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.
D2 · Cognitive Complexity · Tree · ×1
  • Tree::handle_routed_message (cognitive 109) fyrox-ui/src/tree.rs:350 — Tree::handle_routed_message has cognitive complexity 109 (threshold 15). Drivers by points: if/else 25 (80 pts), loops 4 (17 pts), match/switch 3 (8 pts), boolean chains 4 (nesting depth added 73). Of this number, 81 points are the body's own statements and 28 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.
D2 · Cognitive Complexity · ScriptProcessor · ×1
  • ScriptProcessor::handle_scripts (cognitive 103) fyrox-impl/src/engine/mod.rs:645 — ScriptProcessor::handle_scripts has cognitive complexity 103 (threshold 15). Drivers by points: if/else 21 (65 pts), loops 11 (31 pts), match/switch 1 (5 pts), boolean chains 2 (nesting depth added 68). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · AssetItemContextMenu · ×1
  • AssetItemContextMenu::handle_ui_message (cognitive 96) editor/src/asset/menu.rs:343 — AssetItemContextMenu::handle_ui_message has cognitive complexity 96 (threshold 15). Drivers by points: if/else 29 (85 pts), match/switch 1 (7 pts), boolean chains 4 (nesting depth added 62). 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.
D2 · Cognitive Complexity · Animation · ×1
  • Animation::update_root_motion (cognitive 92) fyrox-animation/src/lib.rs:498 — Animation::update_root_motion has cognitive complexity 92 (threshold 15). Drivers by points: if/else 29 (80 pts), boolean chains 5, match/switch 1 (4 pts), loops 1 (3 pts) (nesting depth added 56). Of this number, 88 points are the body's own statements and 4 belong to 2 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.
D2 · Cognitive Complexity · ScrollBar · ×1
  • ScrollBar::handle_routed_message (cognitive 83) fyrox-ui/src/scroll_bar.rs:236 — ScrollBar::handle_routed_message has cognitive complexity 83 (threshold 15). Drivers by points: if/else 22 (69 pts), match/switch 4 (13 pts), boolean chains 1 (nesting depth added 56). 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.
D2 · Cognitive Complexity · SceneNodeContextMenu · ×1
  • SceneNodeContextMenu::handle_ui_message (cognitive 78) editor/src/world/menu.rs:280 — SceneNodeContextMenu::handle_ui_message has cognitive complexity 78 (threshold 15). Drivers by points: if/else 27 (68 pts), boolean chains 5, loops 1 (5 pts) (nesting depth added 45). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · fyrox_template_core · ×1
  • fyrox_template_core::upgrade_project (cognitive 77) template-core/src/lib.rs:806 — fyrox_template_core::upgrade_project has cognitive complexity 77 (threshold 15). Drivers by points: if/else 17 (73 pts), boolean chains 3, match/switch 1 (nesting depth added 56). 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.
D2 · Cognitive Complexity · UiRenderer · ×1
  • UiRenderer::render (cognitive 71) fyrox-impl/src/renderer/ui_renderer.rs:289 — UiRenderer::render has cognitive complexity 71 (threshold 15). Drivers by points: if/else 10 (55 pts), match/switch 2 (10 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 55). 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.
D2 · Cognitive Complexity · PropertyAction · ×1
  • PropertyAction::apply_on_result (cognitive 67) fyrox-ui/src/inspector/mod.rs:296 — PropertyAction::apply_on_result has cognitive complexity 67 (threshold 15). Drivers by points: if/else 32 (62 pts), match/switch 2 (5 pts) (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.
D2 · Cognitive Complexity · DeferredLightRenderer · ×1
  • DeferredLightRenderer::render (cognitive 65) fyrox-impl/src/renderer/light.rs:254 — DeferredLightRenderer::render has cognitive complexity 65 (threshold 15). Drivers by points: if/else 24 (44 pts), boolean chains 10, match/switch 3 (8 pts), loops 2 (3 pts) (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.
D2 · Cognitive Complexity · ScrollViewer · ×1
  • ScrollViewer::handle_routed_message (cognitive 60) fyrox-ui/src/scroll_viewer.rs:236 — ScrollViewer::handle_routed_message has cognitive complexity 60 (threshold 15). Drivers by points: if/else 18 (42 pts), match/switch 3 (8 pts), boolean chains 7, loops 1 (3 pts) (nesting depth added 31). 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.
D2 · Cognitive Complexity · NumericUpDown · ×1
  • NumericUpDown::handle_routed_message (cognitive 58) fyrox-ui/src/numeric.rs:403 — NumericUpDown::handle_routed_message has cognitive complexity 58 (threshold 15). Drivers by points: if/else 18 (38 pts), match/switch 4 (11 pts), boolean chains 9 (nesting depth added 27). Of this number, 49 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · Popup · ×1
  • Popup::handle_routed_message (cognitive 56) fyrox-ui/src/popup.rs:386 — Popup::handle_routed_message has cognitive complexity 56 (threshold 15). Drivers by points: if/else 16 (48 pts), match/switch 2 (6 pts), boolean chains 2 (nesting depth added 36). 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.
D2 · Cognitive Complexity · StateGraphViewer · ×1
  • StateGraphViewer::sync_to_model (cognitive 53) editor/src/plugins/absm/state_graph/mod.rs:294 — StateGraphViewer::sync_to_model has cognitive complexity 53 (threshold 15). Drivers by points: if/else 17 (40 pts), loops 5 (9 pts), match/switch 3, boolean chains 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbsmEditor · ×1
  • AbsmEditor::handle_ui_message (cognitive 50) editor/src/plugins/absm/mod.rs:580 — AbsmEditor::handle_ui_message has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (29 pts), loops 2 (9 pts), match/switch 3 (8 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · GlTexture · ×1
  • GlTexture::set_data (cognitive 50) fyrox-graphics-gl/src/texture.rs:397 — GlTexture::set_data has cognitive complexity 50 (threshold 15). Drivers by points: if/else 20 (42 pts), loops 2 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CurveEditorWindow · ×1
  • CurveEditorWindow::handle_ui_message (cognitive 48) editor/src/plugins/curve_editor.rs:416 — CurveEditorWindow::handle_ui_message has cognitive complexity 48 (threshold 15). Drivers by points: if/else 27 (44 pts), boolean chains 2, match/switch 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.
D2 · Cognitive Complexity · ListView · ×1
  • ListView::handle_routed_message (cognitive 48) fyrox-ui/src/list_view.rs:395 — ListView::handle_routed_message has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (35 pts), match/switch 3 (8 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileMenu · ×1
  • FileMenu::handle_ui_message (cognitive 46) editor/src/menu/file.rs:355 — FileMenu::handle_ui_message has cognitive complexity 46 (threshold 15). Drivers by points: if/else 26 (46 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Text · ×1
  • Text::handle_routed_message (cognitive 46) fyrox-ui/src/text.rs:425 — Text::handle_routed_message has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (43 pts), match/switch 1 (3 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ScriptMessageDispatcher · ×1
  • ScriptMessageDispatcher::dispatch_messages (cognitive 44) fyrox-impl/src/engine/mod.rs:446 — ScriptMessageDispatcher::dispatch_messages has cognitive complexity 44 (threshold 15). Drivers by points: if/else 5 (20 pts), loops 4 (15 pts), match/switch 3 (9 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fyrox_math · ×1
  • fyrox_math::triangulator::triangulate (cognitive 44) fyrox-math/src/triangulator.rs:117 — fyrox_math::triangulator::triangulate has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (39 pts), loops 2 (5 pts) (nesting depth added 27). 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.
D2 · Cognitive Complexity · DockingManager · ×1
  • DockingManager::set_layout (cognitive 44) fyrox-ui/src/dock/mod.rs:244 — DockingManager::set_layout has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 3 (9 pts), match/switch 1 (4 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.
D2 · Cognitive Complexity · fyrox_project_manager · ×1
  • fyrox_project_manager::main (cognitive 44) project-manager/src/main.rs:73 — fyrox_project_manager::main has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (33 pts), loops 2 (7 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Selector · ×1
  • Selector::handle_routed_message (cognitive 41) fyrox-ui/src/selector.rs:149 — Selector::handle_routed_message has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 3 (10 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Texture · ×1
  • Texture::load_from_memory (cognitive 40) fyrox-texture/src/lib.rs:1493 — Texture::load_from_memory has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (26 pts), match/switch 3 (7 pts), loops 2 (6 pts), boolean chains 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.
D2 · Cognitive Complexity · TabControl · ×1
  • TabControl::handle_routed_message (cognitive 40) fyrox-ui/src/tab_control.rs:375 — TabControl::handle_routed_message has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 2 (5 pts), match/switch 2 (5 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · Ragdoll · ×1
  • Ragdoll::update (cognitive 38) fyrox-impl/src/scene/ragdoll.rs:153 — Ragdoll::update has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (31 pts), loops 2 (6 pts), boolean chains 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.
D2 · Cognitive Complexity · ColorPicker · ×1
  • ColorPicker::handle_routed_message (cognitive 38) fyrox-ui/src/color/mod.rs:818 — ColorPicker::handle_routed_message has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 5, match/switch 2 (5 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.
D2 · Cognitive Complexity · Decorator · ×1
  • Decorator::handle_routed_message (cognitive 38) fyrox-ui/src/decorator.rs:157 — Decorator::handle_routed_message has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (31 pts), match/switch 2 (4 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · Ruler · ×1
  • Ruler::handle_routed_message (cognitive 37) editor/src/plugins/animation/ruler.rs:291 — Ruler::handle_routed_message has cognitive complexity 37 (threshold 15). Drivers by points: if/else 8 (23 pts), match/switch 3 (8 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · TileInspector · ×1
  • TileInspector::handle_ui_message (cognitive 37) editor/src/plugins/tilemap/tile_inspector.rs:1070 — TileInspector::handle_ui_message has cognitive complexity 37 (threshold 15). Drivers by points: if/else 21 (32 pts), loops 2 (4 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.
D2 · Cognitive Complexity · RootMotionDropdownArea · ×1
  • RootMotionDropdownArea::handle_ui_message (cognitive 36) editor/src/plugins/animation/toolbar.rs:211 — RootMotionDropdownArea::handle_ui_message has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (33 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · GlShader · ×1
  • GlShader::new (cognitive 36) fyrox-graphics-gl/src/program.rs:153 — GlShader::new has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 4 (7 pts), match/switch 2 (6 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WgpuTexture · ×1
  • WgpuTexture::upload (cognitive 36) fyrox-graphics-wgpu/src/texture.rs:290 — WgpuTexture::upload has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (29 pts), loops 2 (5 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · BlendSpaceField · ×1
  • BlendSpaceField::handle_routed_message (cognitive 35) editor/src/plugins/absm/blendspace.rs:317 — BlendSpaceField::handle_routed_message has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 3 (8 pts), loops 2 (6 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · LightmapInputData · ×1
  • LightmapInputData::from_scene (cognitive 35) fyrox-impl/src/utils/lightmap.rs:403 — LightmapInputData::from_scene has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 4 (6 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · PropertiesTab · ×1
  • PropertiesTab::handle_ui_message (cognitive 34) editor/src/plugins/tilemap/properties_tab.rs:580 — PropertiesTab::handle_ui_message has cognitive complexity 34 (threshold 15). Drivers by points: if/else 27 (34 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · RenderDataBundleStorage · ×1
  • RenderDataBundleStorage::from_graph (cognitive 34) fyrox-impl/src/renderer/bundle.rs:872 — RenderDataBundleStorage::from_graph has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 4 (11 pts), boolean chains 3 (nesting depth added 17). Of this number, 28 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.
D2 · Cognitive Complexity · RenderDataBundle · ×1
  • RenderDataBundle::render_to_frame_buffer (cognitive 33) fyrox-impl/src/renderer/bundle.rs:509 — RenderDataBundle::render_to_frame_buffer has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 5 (13 pts), loops 3 (4 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.
D2 · Cognitive Complexity · TileSet · ×1
  • TileSet::rebuild_animations (cognitive 33) fyrox-impl/src/scene/tilemap/tileset.rs:1548 — TileSet::rebuild_animations has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 5 (9 pts), match/switch 1 (3 pts), boolean chains 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.
D2 · Cognitive Complexity · NavigationLayer · ×1
  • NavigationLayer::handle_routed_message (cognitive 33) fyrox-ui/src/navigation.rs:98 — NavigationLayer::handle_routed_message has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 2 (5 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · MeshControlPanel · ×1
  • MeshControlPanel::handle_ui_message (cognitive 32) editor/src/mesh.rs:156 — MeshControlPanel::handle_ui_message has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 5 (15 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.
D2 · Cognitive Complexity · InspectorPlugin · ×1
  • InspectorPlugin::on_ui_message (cognitive 32) editor/src/plugins/inspector/mod.rs:571 — InspectorPlugin::on_ui_message has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (20 pts), match/switch 3 (8 pts), boolean chains 3, loops 1 (nesting depth added 13). Of this number, 31 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.
D2 · Cognitive Complexity · WfcMacro · ×1
  • WfcMacro::on_instance_ui_message (cognitive 32) editor/src/plugins/tilemap/wfc.rs:267 — WfcMacro::on_instance_ui_message has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (27 pts), loops 2 (5 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.
D2 · Cognitive Complexity · Chunk · ×1
  • Chunk::set_height_map (cognitive 31) fyrox-impl/src/scene/terrain/mod.rs:534 — Chunk::set_height_map has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (25 pts), match/switch 1 (5 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · TileSetEditor · ×1
  • TileSetEditor::handle_ui_message (cognitive 30) editor/src/plugins/tilemap/tileset.rs:642 — TileSetEditor::handle_ui_message has cognitive complexity 30 (threshold 15). Drivers by points: if/else 20 (27 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.
D2 · Cognitive Complexity · SceneItem · ×1
  • SceneItem::handle_routed_message (cognitive 30) editor/src/world/item.rs:170 — SceneItem::handle_routed_message has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (25 pts), match/switch 2 (5 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.
D2 · Cognitive Complexity · NodeWrapper · ×1
  • NodeWrapper::revert_inheritable_property (cognitive 30) fyrox-graph/src/lib.rs:541 — NodeWrapper::revert_inheritable_property has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 4 (12 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.
D2 · Cognitive Complexity · HandlePropertyEditor · ×1
  • HandlePropertyEditor::handle_routed_message (cognitive 29) editor/src/plugins/inspector/editors/handle.rs:177 — HandlePropertyEditor::handle_routed_message has cognitive complexity 29 (threshold 15). Drivers by points: if/else 18 (26 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GlGraphicsServer · ×1
  • GlGraphicsServer::new (cognitive 29) fyrox-graphics-gl/src/server.rs:593 — GlGraphicsServer::new has cognitive complexity 29 (threshold 15). Drivers by points: if/else 24 (27 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SkyBox · ×1
  • SkyBox::validate (cognitive 29) fyrox-impl/src/scene/skybox.rs:108 — SkyBox::validate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (27 pts), boolean chains 1, loops 1 (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.
D2 · Cognitive Complexity · MacroInspector · ×1
  • MacroInspector::handle_ui_message (cognitive 28) editor/src/plugins/tilemap/macro_inspector.rs:375 — MacroInspector::handle_ui_message has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 2 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HashConstraintMap · ×1
  • HashConstraintMap::fill_from (cognitive 28) fyrox-autotile/src/auto.rs:164 — HashConstraintMap::fill_from has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 6 (11 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · TileSetPropertyOptionValue · ×1
  • TileSetPropertyOptionValue::intersect (cognitive 28) fyrox-impl/src/scene/tilemap/property.rs:696 — TileSetPropertyOptionValue::intersect has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 3, loops 1 (3 pts), match/switch 1 (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.
D2 · Cognitive Complexity · LightPanel · ×1
  • LightPanel::handle_ui_message (cognitive 27) editor/src/plugins/light.rs:348 — LightPanel::handle_ui_message has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (21 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 14). 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.
D2 · Cognitive Complexity · SaturationBrightnessField · ×1
  • SaturationBrightnessField::handle_routed_message (cognitive 27) fyrox-ui/src/color/mod.rs:641 — SaturationBrightnessField::handle_routed_message has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (19 pts), match/switch 2 (7 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SurfaceDataPropertyEditor · ×1
  • SurfaceDataPropertyEditor::handle_routed_message (cognitive 26) editor/src/plugins/inspector/editors/surface.rs:94 — SurfaceDataPropertyEditor::handle_routed_message has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · EditorSceneWrapper · ×1
  • EditorSceneWrapper::on_change_hierarchy_request (cognitive 26) editor/src/world/graph.rs:172 — EditorSceneWrapper::on_change_hierarchy_request has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 2 (5 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fyrox_core · ×1
  • fyrox_core::variable::try_inherit_properties (cognitive 26) fyrox-core/src/variable.rs:613 — fyrox_core::variable::try_inherit_properties has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, loops 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.
D2 · Cognitive Complexity · ParticleSystem · ×1
  • ParticleSystem::tick (cognitive 26) fyrox-impl/src/scene/particle_system/mod.rs:406 — ParticleSystem::tick has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 4 (5 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.
D2 · Cognitive Complexity · BehaviorTree · ×1
  • BehaviorTree::tick_recursive (cognitive 26) fyrox-impl/src/utils/behavior/mod.rs:175 — BehaviorTree::tick_recursive has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 5 (13 pts), if/else 4 (7 pts), loops 2 (6 pts) (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · CheckBox · ×1
  • CheckBox::handle_routed_message (cognitive 26) fyrox-ui/src/check_box.rs:200 — CheckBox::handle_routed_message has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6, match/switch 2 (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.
D2 · Cognitive Complexity · ParticleSystemPreviewControlPanel · ×1
  • ParticleSystemPreviewControlPanel::handle_ui_message (cognitive 25) editor/src/particle.rs:299 — ParticleSystemPreviewControlPanel::handle_ui_message has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbsmNode · ×1
  • AbsmNode::handle_routed_message (cognitive 25) editor/src/plugins/absm/node.rs:163 — AbsmNode::handle_routed_message has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 2 (6 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · TileMapEditorPlugin · ×1
  • TileMapEditorPlugin::on_message (cognitive 25) editor/src/plugins/tilemap/mod.rs:816 — TileMapEditorPlugin::on_message has cognitive complexity 25 (threshold 15). Drivers by points: if/else 18 (24 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.
D2 · Cognitive Complexity · TileDataUpdate · ×1
  • TileDataUpdate::swap_with_data (cognitive 25) fyrox-impl/src/scene/tilemap/update.rs:287 — TileDataUpdate::swap_with_data has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (6 pts), match/switch 3 (6 pts) (nesting depth added 16). 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.
D2 · Cognitive Complexity · NavmeshAgent · ×1
  • NavmeshAgent::straighten_path (cognitive 25) fyrox-impl/src/utils/navmesh.rs:773 — NavmeshAgent::straighten_path has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (5 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.
D2 · Cognitive Complexity · RenderPassContainer · ×1
  • RenderPassContainer::run_pass (cognitive 24) fyrox-impl/src/renderer/cache/shader.rs:258 — RenderPassContainer::run_pass has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (21 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AnimationSource · ×1
  • AnimationSource::retarget_animations_directly (cognitive 24) fyrox-impl/src/resource/model/mod.rs:234 — AnimationSource::retarget_animations_directly has cognitive complexity 24 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 3 (8 pts), match/switch 1 (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.
D2 · Cognitive Complexity · AlphaBar · ×1
  • AlphaBar::handle_routed_message (cognitive 24) fyrox-ui/src/color/mod.rs:304 — AlphaBar::handle_routed_message has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 2 (7 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FsTree · ×1
  • FsTree::new (cognitive 24) fyrox-ui/src/file_browser/fs_tree.rs:430 — FsTree::new has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (4 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.
D2 · Cognitive Complexity · NodeContextMenu · ×1
  • NodeContextMenu::handle_ui_message (cognitive 23) editor/src/plugins/absm/state_graph/context.rs:256 — NodeContextMenu::handle_ui_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SettingsWindow · ×1
  • SettingsWindow::handle_ui_message (cognitive 23) editor/src/plugins/settings.rs:242 — SettingsWindow::handle_ui_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 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.
D2 · Cognitive Complexity · ColorGradientEditor · ×1
  • ColorGradientEditor::preview_message (cognitive 23) fyrox-ui/src/color/gradient.rs:243 — ColorGradientEditor::preview_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HueBar · ×1
  • HueBar::handle_routed_message (cognitive 23) fyrox-ui/src/color/mod.rs:465 — HueBar::handle_routed_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 2 (7 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.
D2 · Cognitive Complexity · RangeEditor · ×1
  • RangeEditor::handle_routed_message (cognitive 23) fyrox-ui/src/range.rs:170 — RangeEditor::handle_routed_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 2 (nesting depth added 11). 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.
D2 · Cognitive Complexity · AssetItem · ×1
  • AssetItem::open (cognitive 22) editor/src/asset/item.rs:144 — AssetItem::open has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 2 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MaterialEditor · ×1
  • MaterialEditor::handle_ui_message (cognitive 22) editor/src/plugins/material/mod.rs:630 — MaterialEditor::handle_ui_message has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (4 pts), boolean chains 3, match/switch 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.
D2 · Cognitive Complexity · AutoTiler · ×1
  • AutoTiler::is_pattern_legal (cognitive 22) fyrox-autotile/src/auto.rs:384 — AutoTiler::is_pattern_legal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2, loops 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.
D2 · Cognitive Complexity · GraphTraverseIteratorRef · ×1
  • GraphTraverseIteratorRef::next (cognitive 22) fyrox-graph/src/lib.rs:1693 — GraphTraverseIteratorRef::next has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 1 (4 pts), match/switch 2 (3 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (GraphTraverseIteratorMut::next) 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.
D2 · Cognitive Complexity · GraphTraverseIteratorMut · ×1
  • GraphTraverseIteratorMut::next (cognitive 22) fyrox-graph/src/lib.rs:1755 — GraphTraverseIteratorMut::next has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 1 (4 pts), match/switch 2 (3 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (GraphTraverseIteratorRef::next) 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.
D2 · Cognitive Complexity · GlFrameBuffer · ×1
  • GlFrameBuffer::clear (cognitive 22) fyrox-graphics-gl/src/framebuffer.rs:309 — GlFrameBuffer::clear has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (8 pts), loops 1 (2 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.
D2 · Cognitive Complexity · ColorGradingLut · ×1
  • ColorGradingLut::new (cognitive 22) fyrox-impl/src/scene/camera.rs:928 — ColorGradingLut::new has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (9 pts), boolean chains 1, 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.
D2 · Cognitive Complexity · ResourceCreator · ×1
  • ResourceCreator::handle_ui_message (cognitive 21) editor/src/asset/creator.rs:177 — ResourceCreator::handle_ui_message has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 1 (4 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.
D2 · Cognitive Complexity · fyrox_resource · ×1
  • fyrox_resource::collect_used_resources (cognitive 21) fyrox-resource/src/lib.rs:658 — fyrox_resource::collect_used_resources has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 3 (5 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.
D2 · Cognitive Complexity · Button · ×1
  • Button::handle_routed_message (cognitive 21) fyrox-ui/src/button.rs:189 — Button::handle_routed_message has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (5 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TextureSliceEditorWindow · ×1
  • TextureSliceEditorWindow::handle_routed_message (cognitive 21) fyrox-ui/src/inspector/editors/texture_slice.rs:536 — TextureSliceEditorWindow::handle_routed_message has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 1 (3 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.
D2 · Cognitive Complexity · ExportWindow · ×1
  • ExportWindow::handle_ui_message (cognitive 20) editor/src/plugins/export.rs:372 — ExportWindow::handle_ui_message has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 2 (6 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.
D2 · Cognitive Complexity · MacroPropertyValueField · ×1
  • MacroPropertyValueField::on_ui_message (cognitive 20) editor/src/plugins/tilemap/brush_macro.rs:811 — MacroPropertyValueField::on_ui_message has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5, match/switch 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.
D2 · Cognitive Complexity · UiSelectInteractionMode · ×1
  • UiSelectInteractionMode::on_left_mouse_button_up (cognitive 20) editor/src/ui_scene/interaction/mod.rs:93 — UiSelectInteractionMode::on_left_mouse_button_up has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Sprite · ×1
  • Sprite::collect_render_data (cognitive 20) fyrox-impl/src/scene/sprite.rs:322 — Sprite::collect_render_data has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18, boolean chains 1, loops 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.
D2 · Cognitive Complexity · TileMap · ×1
  • TileMap::collect_render_data (cognitive 20) fyrox-impl/src/scene/tilemap/mod.rs:1417 — TileMap::collect_render_data has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 4 (6 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.
D2 · Cognitive Complexity · HashMapPropertyEditorDefinition · ×1
  • HashMapPropertyEditorDefinition::create_message (cognitive 20) fyrox-ui/src/inspector/editors/hashmap/mod.rs:344 — HashMapPropertyEditorDefinition::create_message has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 1 (2 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.
D2 · Cognitive Complexity · ColliderControlPanel · ×1
  • ColliderControlPanel::handle_ui_message (cognitive 19) editor/src/plugins/collider/panel.rs:124 — ColliderControlPanel::handle_ui_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 1 (3 pts), 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.
D2 · Cognitive Complexity · SpriteSheetFramesEditorWindow · ×1
  • SpriteSheetFramesEditorWindow::handle_routed_message (cognitive 19) editor/src/plugins/inspector/editors/spritesheet/window.rs:121 — SpriteSheetFramesEditorWindow::handle_routed_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 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.
D2 · Cognitive Complexity · MacroTab · ×1
  • MacroTab::handle_ui_message (cognitive 19) editor/src/plugins/tilemap/macro_tab.rs:386 — MacroTab::handle_ui_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (19 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TileBoundsEditor · ×1
  • TileBoundsEditor::handle_routed_message (cognitive 19) editor/src/plugins/tilemap/tile_bounds_editor.rs:138 — TileBoundsEditor::handle_routed_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fyrox_graphics_gl · ×1
  • fyrox_graphics_gl::texture::desired_byte_count (cognitive 19) fyrox-graphics-gl/src/texture.rs:346 — fyrox_graphics_gl::texture::desired_byte_count has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 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.
D2 · Cognitive Complexity · SceneState · ×1
  • SceneState::try_create_from_plugin (cognitive 19) fyrox-impl/src/engine/hotreload.rs:99 — SceneState::try_create_from_plugin has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 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.
D2 · Cognitive Complexity · ObserversCollection · ×1
  • ObserversCollection::from_scene (cognitive 19) fyrox-impl/src/renderer/observer.rs:88 — ObserversCollection::from_scene has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (5 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.
D2 · Cognitive Complexity · FbxScene · ×1
  • FbxScene::new (cognitive 19) fyrox-impl/src/resource/fbx/scene/mod.rs:57 — FbxScene::new has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 3 (5 pts), boolean chains 2, loops 2 (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.
D2 · Cognitive Complexity · Rectangle · ×1
  • Rectangle::collect_render_data (cognitive 19) fyrox-impl/src/scene/dim2/rectangle.rs:323 — Rectangle::collect_render_data has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, loops 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.
D2 · Cognitive Complexity · ResourceRegistry · ×1
  • ResourceRegistry::scan (cognitive 19) fyrox-resource/src/registry.rs:419 — ResourceRegistry::scan has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DropdownList · ×1
  • DropdownList::handle_routed_message (cognitive 19) fyrox-ui/src/dropdown_list.rs:218 — DropdownList::handle_routed_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ListViewBuilder · ×1
  • ListViewBuilder::build (cognitive 19) fyrox-ui/src/list_view.rs:562 — ListViewBuilder::build has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VecEditor · ×1
  • VecEditor::handle_routed_message (cognitive 19) fyrox-ui/src/vec.rs:177 — VecEditor::handle_routed_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (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.
D2 · Cognitive Complexity · CommandStack · ×1
  • CommandStack::do_command (cognitive 18) editor/src/command/mod.rs:232 — CommandStack::do_command has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (2 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). Of this number, 13 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TileMapPanel · ×1
  • TileMapPanel::handle_ui_message (cognitive 18) editor/src/plugins/tilemap/panel.rs:618 — TileMapPanel::handle_ui_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · WgpuGeometryBuffer · ×1
  • WgpuGeometryBuffer::new (cognitive 18) fyrox-graphics-wgpu/src/geometry_buffer.rs:77 — WgpuGeometryBuffer::new has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (3 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MatrixEditor · ×1
  • MatrixEditor::handle_routed_message (cognitive 18) fyrox-ui/src/matrix.rs:141 — MatrixEditor::handle_routed_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WrapPanel · ×1
  • WrapPanel::arrange_override (cognitive 18) fyrox-ui/src/wrap_panel.rs:174 — WrapPanel::arrange_override has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 3 (6 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.
D2 · Cognitive Complexity · UpgradeTool · ×1
  • UpgradeTool::handle_ui_message (cognitive 18) project-manager/src/upgrade.rs:200 — UpgradeTool::handle_ui_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 1 (3 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.
D2 · Cognitive Complexity · SoundPreview · ×1
  • SoundPreview::generate_preview (cognitive 17) editor/src/asset/preview/mod.rs:250 — SoundPreview::generate_preview has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 3 (7 pts), boolean chains 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · Configurator · ×1
  • Configurator::handle_ui_message (cognitive 17) editor/src/configurator.rs:277 — Configurator::handle_ui_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 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.
D2 · Cognitive Complexity · NodeSelectorWindow · ×1
  • NodeSelectorWindow::handle_routed_message (cognitive 17) editor/src/scene/selector.rs:465 — NodeSelectorWindow::handle_routed_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · SpriteSheetAnimation · ×1
  • SpriteSheetAnimation::update (cognitive 17) fyrox-animation/src/spritesheet/mod.rs:415 — SpriteSheetAnimation::update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AsciiReader · ×1
  • AsciiReader::read_field (cognitive 17) fyrox-core/src/visitor/reader/ascii.rs:202 — AsciiReader::read_field has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · WgpuShader · ×1
  • WgpuShader::new (cognitive 17) fyrox-graphics-wgpu/src/program.rs:249 — WgpuShader::new has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (3 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.
D2 · Cognitive Complexity · OcclusionTester · ×1
  • OcclusionTester::try_query_visibility_results (cognitive 17) fyrox-impl/src/renderer/occlusion/mod.rs:174 — OcclusionTester::try_query_visibility_results has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 5 (8 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.
D2 · Cognitive Complexity · TileMapBrush · ×1
  • TileMapBrush::palette_render_loop (cognitive 17) fyrox-impl/src/scene/tilemap/brush.rs:418 — TileMapBrush::palette_render_loop has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 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.
D2 · Cognitive Complexity · ColorPoint · ×1
  • ColorPoint::handle_routed_message (cognitive 17) fyrox-ui/src/color/gradient.rs:512 — ColorPoint::handle_routed_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 2 (6 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TextureSliceEditor · ×1
  • TextureSliceEditor::on_thumb_dragged (cognitive 17) fyrox-ui/src/inspector/editors/texture_slice.rs:122 — TextureSliceEditor::on_thumb_dragged has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (17 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.
D2 · Cognitive Complexity · MessageBox · ×1
  • MessageBox::handle_routed_message (cognitive 17) fyrox-ui/src/messagebox.rs:220 — MessageBox::handle_routed_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SetPropertyCommand · ×1
  • SetPropertyCommand::swap (cognitive 16) editor/src/command/mod.rs:608 — SetPropertyCommand::swap has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 2 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · RotateInteractionMode · ×1
  • RotateInteractionMode::on_mouse_move (cognitive 16) editor/src/interaction/rotate_mode.rs:190 — RotateInteractionMode::on_mouse_move has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CanvasContextMenu · ×1
  • CanvasContextMenu::handle_ui_message (cognitive 16) editor/src/plugins/absm/state_graph/context.rs:116 — CanvasContextMenu::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (7 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.
D2 · Cognitive Complexity · TrackView · ×1
  • TrackView::handle_routed_message (cognitive 16) editor/src/plugins/animation/track.rs:397 — TrackView::handle_routed_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ScriptPropertyEditor · ×1
  • ScriptPropertyEditor::preview_message (cognitive 16) editor/src/plugins/inspector/editors/script.rs:121 — ScriptPropertyEditor::preview_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MaterialFieldEditor · ×1
  • MaterialFieldEditor::handle_routed_message (cognitive 16) editor/src/plugins/material/editor.rs:129 — MaterialFieldEditor::handle_routed_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 2, loops 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.
D2 · Cognitive Complexity · CollidersTab · ×1
  • CollidersTab::handle_ui_message (cognitive 16) editor/src/plugins/tilemap/colliders_tab.rs:293 — CollidersTab::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 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.
D2 · Cognitive Complexity · TilePropertyEditor · ×1
  • TilePropertyEditor::handle_ui_message (cognitive 16) editor/src/plugins/tilemap/tile_prop_editor.rs:575 — TilePropertyEditor::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 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.
D2 · Cognitive Complexity · NodeSelector · ×1
  • NodeSelector::handle_routed_message (cognitive 16) editor/src/scene/selector.rs:239 — NodeSelector::handle_routed_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 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.
D2 · Cognitive Complexity · PoseNode · ×1
  • PoseNode::collect_animations (cognitive 16) fyrox-animation/src/machine/node/mod.rs:116 — PoseNode::collect_animations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (6 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ColorGradient · ×1
  • ColorGradient::get_color (cognitive 16) fyrox-core/src/color_gradient.rs:102 — ColorGradient::get_color has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · InheritableVariable · ×1
  • InheritableVariable::visit (cognitive 16) fyrox-core/src/variable.rs:354 — InheritableVariable::visit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 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.
D2 · Cognitive Complexity · VertexBuffer · ×1
  • VertexBuffer::new_with_layout (cognitive 16) fyrox-impl/src/scene/mesh/buffer.rs:815 — VertexBuffer::new_with_layout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 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.
D2 · Cognitive Complexity · BlendShapesContainer · ×1
  • BlendShapesContainer::from_lists (cognitive 16) fyrox-impl/src/scene/mesh/surface.rs:116 — BlendShapesContainer::from_lists has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 4 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CustomTileCollider · ×1
  • CustomTileCollider::from_str (cognitive 16) fyrox-impl/src/scene/tilemap/tile_collider.rs:328 — CustomTileCollider::from_str has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 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.
D2 · Cognitive Complexity · TokenIter · ×1
  • TokenIter::next (cognitive 16) fyrox-impl/src/scene/tilemap/tile_collider.rs:422 — TokenIter::next has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 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.
D2 · Cognitive Complexity · ResourceManagerState · ×1
  • ResourceManagerState::try_move_folder (cognitive 16) fyrox-resource/src/manager.rs:2039 — ResourceManagerState::try_move_folder has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 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.
D2 · Cognitive Complexity · SoundSource · ×1
  • SoundSource::render_until_block_end_resample (cognitive 16) fyrox-sound/src/source.rs:596 — SoundSource::render_until_block_end_resample has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 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.
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: selection.rs → mod.rs, selection.rs, selection.rs, selection.rs editor/src/plugins/absm/selection.rs — `editor/src/plugins/absm/selection.rs` changes together with 4 other files — `editor/src/audio/mod.rs`, `editor/src/interaction/navmesh/selection.rs`, `editor/src/ui_scene/selection.rs`, `editor/src/world/selection.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (3 members, 45 shared lines) · ×1
  • Near-duplicate member family (3 members, 45 shared lines) editor/src/plugins/tilemap/colliders_tab.rs:148 — editor/src/plugins/tilemap/colliders_tab.rs:148-262 | editor/src/plugins/tilemap/macro_tab.rs:200-333 | editor/src/plugins/tilemap/properties_tab.rs:252-499 — These 3 members are variants of one another: a block of 45 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 27 shared lines) · ×1
  • Near-duplicate member family (3 members, 27 shared lines) fyrox-graphics/src/gpu_texture.rs:284 — fyrox-graphics/src/gpu_texture.rs:284-320 | fyrox-graphics/src/gpu_texture.rs:324-360 | fyrox-graphics/src/gpu_texture.rs:364-399 — These 3 members are variants of one another: a block of 27 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Near-duplicate member pair (101 shared lines) · ×1
  • Near-duplicate member pair (101 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs:1324 — fyrox-impl/src/scene/dim2/physics/mod.rs:1324-1466 | fyrox-impl/src/scene/graph/physics/mod.rs:1837-1988 — These two members are variants of one another: 101 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 · Near-duplicate member pair (97 shared lines) · ×1
  • Near-duplicate member pair (97 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs:1051 — fyrox-impl/src/scene/dim2/physics/mod.rs:1051-1188 | fyrox-impl/src/scene/graph/physics/mod.rs:1492-1700 — These two members are variants of one another: 97 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 · Near-duplicate member pair (89 shared lines) · ×1
  • Near-duplicate member pair (89 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs:1195 — fyrox-impl/src/scene/dim2/physics/mod.rs:1195-1317 | fyrox-impl/src/scene/graph/physics/mod.rs:1707-1830 — These two members are variants of one another: 89 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 · Near-duplicate member pair (55 shared lines) · ×1
  • Near-duplicate member pair (55 shared lines) editor/src/plugins/inspector/editors/dyntype.rs:301 — editor/src/plugins/inspector/editors/dyntype.rs:301-400 | editor/src/plugins/inspector/editors/script.rs:397-496 — These two members are variants of one another: 55 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) fyrox-impl/src/engine/mod.rs:1743 — fyrox-impl/src/engine/mod.rs:1743-1830 | fyrox-impl/src/engine/mod.rs:1832-1922 | fyrox-impl/src/engine/mod.rs:1929-1997 | fyrox-impl/src/engine/mod.rs:2006-2103 | fyrox-impl/src/engine/mod.rs:2110-2138 | fyrox-impl/src/engine/mod.rs:2145-2173 | fyrox-impl/src/engine/mod.rs:2180-2208 | fyrox-impl/src/engine/mod.rs:2351-2413 — 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 (75 corresponding lines) · ×1
  • Edited copy of a member (75 corresponding lines) fyrox-ui/src/draw.rs:499 — fyrox-ui/src/draw.rs:499-573 | fyrox-ui/src/draw.rs:582-682 — These two members are one piece of code written twice and then edited apart: 75 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (99 corresponding lines) · ×1
  • Edited copy of a member (99 corresponding lines) editor/src/plugins/light.rs:237 — editor/src/plugins/light.rs:237-335 | editor/src/plugins/ragdoll.rs:1027-1135 — These two members are one piece of code written twice and then edited apart: 99 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (74 corresponding lines) · ×1
  • Edited copy of a member (74 corresponding lines) fyrox-impl/src/scene/graph/physics/mod.rs:515 — fyrox-impl/src/scene/graph/physics/mod.rs:515-607 | fyrox-impl/src/scene/graph/physics/mod.rs:611-684 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (63 corresponding lines) · ×1
  • Edited copy of a member (63 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs:707 — fyrox-impl/src/scene/dim2/physics/mod.rs:707-769 | fyrox-impl/src/scene/graph/physics/mod.rs:1150-1213 — 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 (90 corresponding lines) · ×1
  • Edited copy of a member (90 corresponding lines) fyrox-graph/src/lib.rs:216 — fyrox-graph/src/lib.rs:216-305 | fyrox-graph/src/lib.rs:319-438 — These two members are one piece of code written twice and then edited apart: 90 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (67 corresponding lines) · ×1
  • Edited copy of a member (67 corresponding lines) editor/src/asset/dependency.rs:89 — editor/src/asset/dependency.rs:89-155 | editor/src/scene/dialog.rs:53-143 — These two members are one piece of code written twice and then edited apart: 67 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (55 corresponding lines) · ×1
  • Edited copy of a member (55 corresponding lines) editor/src/plugins/inspector/editors/dyntype.rs:242 — editor/src/plugins/inspector/editors/dyntype.rs:242-296 | editor/src/plugins/inspector/editors/script.rs:320-392 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) fyrox-impl/src/scene/dim2/physics/mod.rs:251 — fyrox-impl/src/scene/dim2/physics/mod.rs:251-291 | fyrox-impl/src/scene/graph/physics/mod.rs:375-415 — 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 (53 corresponding lines) · ×1
  • Edited copy of a member (53 corresponding lines) editor/src/interaction/gizmo/move_gizmo.rs:97 — editor/src/interaction/gizmo/move_gizmo.rs:97-151 | editor/src/interaction/gizmo/scale_gizmo.rs:80-132 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×1
  • Edited copy of a member (51 corresponding lines) editor/src/asset/selection.rs:200 — editor/src/asset/selection.rs:200-250 | editor/src/asset/selection.rs:252-307 — 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 (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) fyrox-graph/src/lib.rs:1693 — fyrox-graph/src/lib.rs:1693-1735 | fyrox-graph/src/lib.rs:1755-1813 — 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 (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) editor/src/ui_scene/utils.rs:203 — editor/src/ui_scene/utils.rs:203-252 | editor/src/world/graph.rs:177-225 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) editor/src/plugins/absm/mod.rs:923 — editor/src/plugins/absm/mod.rs:923-957 | editor/src/plugins/animation/mod.rs:1089-1121 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 55+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 55+ corresponding lines) editor/src/plugins/absm/state_graph/context.rs:189 — editor/src/plugins/absm/state_graph/context.rs:189-254 | editor/src/plugins/absm/state_viewer/context.rs:76-139 | editor/src/plugins/animation/track.rs:137-191 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 55 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 (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) fyrox-resource/src/manager.rs:1116 — fyrox-resource/src/manager.rs:1116-1172 | fyrox-resource/src/manager.rs:1273-1324 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 31+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 31+ corresponding lines) editor/src/plugins/tilemap/interaction_mode.rs:307 — editor/src/plugins/tilemap/interaction_mode.rs:307-348 | editor/src/plugins/tilemap/interaction_mode.rs:357-387 | editor/src/plugins/tilemap/interaction_mode.rs:396-430 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) fyrox-impl/src/scene/dim2/physics/character.rs:127 — fyrox-impl/src/scene/dim2/physics/character.rs:127-157 | fyrox-impl/src/scene/graph/physics/character.rs:205-235 — 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 copies of one member (5 members, 34+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 34+ corresponding lines) editor/src/interaction/mod.rs:211 — editor/src/interaction/mod.rs:211-250 | editor/src/plugins/tilemap/collider_editor.rs:372-407 | editor/src/plugins/tilemap/mod.rs:246-280 | editor/src/plugins/tilemap/tile_editor.rs:121-154 | editor/src/plugins/tilemap/tile_prop_editor.rs:680-714 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 34 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, 38+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 38+ corresponding lines) editor/src/plugins/tilemap/colliders_tab.rs:100 — editor/src/plugins/tilemap/colliders_tab.rs:100-137 | editor/src/plugins/tilemap/macro_tab.rs:106-144 | editor/src/plugins/tilemap/properties_tab.rs:185-225 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 38 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, 28+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 28+ corresponding lines) fyrox-impl/src/scene/tilemap/effect.rs:203 — fyrox-impl/src/scene/tilemap/effect.rs:203-253 | fyrox-impl/src/scene/tilemap/effect.rs:259-286 | fyrox-impl/src/scene/tilemap/mod.rs:229-266 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) editor/src/interaction/move_mode.rs:310 — editor/src/interaction/move_mode.rs:310-342 | editor/src/interaction/rotate_mode.rs:79-106 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 29+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 29+ corresponding lines) fyrox-core/src/pool/multiborrow.rs:169 — fyrox-core/src/pool/multiborrow.rs:169-197 | fyrox-core/src/pool/multiborrow.rs:234-272 | fyrox-core/src/pool/multiborrow.rs:295-326 — 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 (3 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 26+ corresponding lines) fyrox-ui/src/inspector/editors/matrix2.rs:63 — fyrox-ui/src/inspector/editors/matrix2.rs:63-88 | fyrox-ui/src/inspector/editors/numeric.rs:67-93 | fyrox-ui/src/inspector/editors/vec.rs:61-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (73 corresponding lines) · ×1
  • Edited copy of a member (73 corresponding lines) template-core/src/lib.rs:342 — template-core/src/lib.rs:342-414 | template-core/src/lib.rs:535-611 — These two members are one piece of code written twice and then edited apart: 73 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) editor/src/plugins/absm/mod.rs:905 — editor/src/plugins/absm/mod.rs:905-921 | editor/src/plugins/animation/mod.rs:1047-1064 | editor/src/plugins/animation/mod.rs:1071-1087 — 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 (4 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 27+ corresponding lines) editor/src/plugins/absm/state_graph/context.rs:376 — editor/src/plugins/absm/state_graph/context.rs:376-402 | editor/src/plugins/absm/state_viewer/context.rs:236-268 | editor/src/plugins/absm/state_viewer/context.rs:335-361 | editor/src/plugins/animation/ruler.rs:79-115 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 27 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, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) editor/src/plugins/tilemap/palette.rs:583 — editor/src/plugins/tilemap/palette.rs:583-606 | editor/src/plugins/tilemap/palette.rs:614-632 | editor/src/plugins/tilemap/palette.rs:640-658 — 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, 25+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 25+ corresponding lines) fyrox-resource/src/manager.rs:450 — fyrox-resource/src/manager.rs:450-474 | fyrox-resource/src/manager.rs:491-521 | fyrox-resource/src/manager.rs:597-627 — 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 copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) fyrox-impl/src/resource/gltf/surface.rs:390 — fyrox-impl/src/resource/gltf/surface.rs:390-405 | fyrox-impl/src/resource/gltf/surface.rs:406-425 | fyrox-impl/src/resource/gltf/surface.rs:426-440 — 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 (5 members, 45+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 45+ corresponding lines) template-core/src/lib.rs:134 — template-core/src/lib.rs:134-223 | template-core/src/lib.rs:225-290 | template-core/src/lib.rs:292-340 | template-core/src/lib.rs:416-487 | template-core/src/lib.rs:489-533 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 45 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, 16+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 16+ corresponding lines) editor/src/plugins/collider/triangle.rs:62 — editor/src/plugins/collider/triangle.rs:62-77 | editor/src/plugins/collider/triangle.rs:84-99 | editor/src/plugins/collider/triangle2d.rs:62-77 | editor/src/plugins/collider/triangle2d.rs:84-99 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 16+ corresponding lines) fyrox-impl/src/scene/accel.rs:96 — fyrox-impl/src/scene/accel.rs:96-111 | fyrox-impl/src/scene/accel.rs:123-138 | fyrox-impl/src/scene/accel.rs:158-173 | fyrox-math/src/octree.rs:81-96 | fyrox-math/src/octree.rs:108-123 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 11+ corresponding lines) editor/src/plugins/inspector/editors/handle.rs:495 — editor/src/plugins/inspector/editors/handle.rs:495-506 | editor/src/plugins/inspector/editors/resource.rs:459-470 | fyrox-ui/src/inspector/editors/bit.rs:86-96 | fyrox-ui/src/inspector/editors/matrix2.rs:101-112 | fyrox-ui/src/inspector/editors/numeric.rs:106-119 | fyrox-ui/src/inspector/editors/range.rs:79-92 | fyrox-ui/src/inspector/editors/rect.rs:97-109 | fyrox-ui/src/inspector/editors/vec.rs:98-109 — These 8 members are one piece of code written 8 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 8 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) editor/src/plugins/inspector/editors/triangle_buffer.rs:59 — editor/src/plugins/inspector/editors/triangle_buffer.rs:59-70 | editor/src/plugins/inspector/editors/vertex_buffer.rs:59-70 | fyrox-ui/src/inspector/editors/bool.rs:48-59 | fyrox-ui/src/inspector/editors/path.rs:47-58 | fyrox-ui/src/inspector/editors/texture_slice.rs:821-833 — 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 (6 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 9+ corresponding lines) editor/src/plugins/curve_editor.rs:567 — editor/src/plugins/curve_editor.rs:567-575 | editor/src/plugins/export.rs:552-567 | editor/src/plugins/light.rs:502-511 | editor/src/plugins/ragdoll.rs:1254-1263 | editor/src/plugins/settings.rs:351-366 | editor/src/plugins/stats.rs:56-65 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 11+ corresponding lines) editor/src/plugins/inspector/editors/spritesheet/mod.rs:176 — editor/src/plugins/inspector/editors/spritesheet/mod.rs:176-188 | editor/src/plugins/inspector/editors/surface.rs:348-358 | editor/src/plugins/tilemap/handle_editor.rs:284-294 | fyrox-ui/src/inspector/editors/color.rs:124-135 | fyrox-ui/src/inspector/editors/key.rs:70-81 | fyrox-ui/src/inspector/editors/key.rs:115-126 | fyrox-ui/src/inspector/editors/uuid.rs:72-83 — These 7 members are one piece of code written 7 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 7 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) fyrox-ui/src/decorator.rs:112 — fyrox-ui/src/decorator.rs:112-123 | fyrox-ui/src/file_browser/selector.rs:97-108 | fyrox-ui/src/input.rs:108-119 | fyrox-ui/src/messagebox.rs:187-198 — 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 (4 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 8+ corresponding lines) editor/src/plugins/tilemap/commands.rs:90 — editor/src/plugins/tilemap/commands.rs:90-97 | editor/src/plugins/tilemap/commands.rs:155-165 | editor/src/plugins/tilemap/commands.rs:191-201 | editor/src/plugins/tilemap/commands.rs:227-237 — 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 (5 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 15+ corresponding lines) fyrox-impl/src/scene/dim2/joint.rs:381 — fyrox-impl/src/scene/dim2/joint.rs:381-395 | fyrox-impl/src/scene/dim2/joint.rs:457-471 | fyrox-impl/src/scene/joint.rs:440-454 | fyrox-impl/src/scene/joint.rs:516-530 | fyrox-impl/src/scene/joint.rs:557-571 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 10+ corresponding lines) fyrox-ui/src/color/gradient.rs:68 — fyrox-ui/src/color/gradient.rs:68-79 | fyrox-ui/src/color/gradient.rs:202-213 | fyrox-ui/src/color/gradient.rs:479-488 | fyrox-ui/src/color/mod.rs:119-128 | fyrox-ui/src/color/mod.rs:400-409 | fyrox-ui/src/color/mod.rs:564-575 | fyrox-ui/src/color/mod.rs:787-796 | fyrox-ui/src/color/mod.rs:1165-1174 — These 8 members are one piece of code written 8 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 8 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) fyrox-impl/src/scene/tilemap/brush.rs:594 — fyrox-impl/src/scene/tilemap/brush.rs:594-602 | fyrox-impl/src/scene/tilemap/tileset.rs:2153-2163 | fyrox-material/src/loader.rs:53-61 | fyrox-ui/src/style/resource.rs:120-128 — 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) editor/src/plugins/collider/capsule.rs:129 — editor/src/plugins/collider/capsule.rs:129-142 | editor/src/plugins/collider/cone.rs:114-124 | editor/src/plugins/collider/cylinder.rs:116-127 | editor/src/plugins/collider/segment.rs:99-110 | editor/src/plugins/collider/triangle.rs:107-120 — 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 (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) fyrox-animation/src/machine/mask.rs:98 — fyrox-animation/src/machine/mask.rs:98-101 | fyrox-core/src/pool/handle.rs:166-169 | fyrox-core/src/pool/mod.rs:190-193 | fyrox-core/src/variable.rs:466-470 — 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 · Duplicated block (53 lines × 2) · ×1
  • Duplicated block (53 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1196 — fyrox-impl/src/scene/dim2/physics/mod.rs:1196-1248 | fyrox-impl/src/scene/graph/physics/mod.rs:1708-1760 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (50 lines × 2) · ×1
  • Duplicated block (50 lines × 2) editor/src/plugins/tilemap/palette.rs:2181 — editor/src/plugins/tilemap/palette.rs:2181-2230 | editor/src/plugins/tilemap/panel_preview.rs:91-140 — 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 `editor/src/plugins/tilemap/palette.rs:2181` 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, `editor/src/plugins/tilemap/palette.rs:2180` calls `draw_checker_board` and `editor/src/plugins/tilemap/panel_preview.rs:90` 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.
D4 · Code Duplication · Duplicated block (48–49 lines × 2) · ×1
  • Duplicated block (48–49 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1362 — fyrox-impl/src/scene/dim2/physics/mod.rs:1362-1410 | fyrox-impl/src/scene/graph/physics/mod.rs:1877-1924 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1362` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) fyrox-impl/src/scene/graph/physics/mod.rs:534 — fyrox-impl/src/scene/graph/physics/mod.rs:534-576 | fyrox-impl/src/scene/graph/physics/mod.rs:625-667 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/graph/physics/mod.rs:534` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (39 lines × 2) · ×1
  • Duplicated block (39 lines × 2) fyrox-build-tools/src/export/android.rs:61 — fyrox-build-tools/src/export/android.rs:61-99 | fyrox-build-tools/src/export/pc.rs:49-87 — 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 `fyrox-build-tools/src/export/android.rs:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (34–36 lines × 2) · ×1
  • Duplicated block (34–36 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:860 — fyrox-impl/src/scene/dim2/physics/mod.rs:860-895 | fyrox-impl/src/scene/graph/physics/mod.rs:1303-1336 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:860` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (34 lines × 3) · ×1
  • Duplicated block (34 lines × 3) editor/src/interaction/move_mode.rs:397 — editor/src/interaction/move_mode.rs:397-430 | editor/src/interaction/rotate_mode.rs:155-188 | editor/src/interaction/scale_mode.rs:147-180 — before extracting anything, compare `editor/src/interaction/move_mode.rs` and `editor/src/interaction/rotate_mode.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/interaction/move_mode.rs:397` 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.
D4 · Code Duplication · Duplicated block (32–33 lines × 2) · ×1
  • Duplicated block (32–33 lines × 2) fyrox-ui/src/messagebox.rs:342 — fyrox-ui/src/messagebox.rs:342-373 | fyrox-ui/src/messagebox.rs:386-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/messagebox.rs:342` it does not close everything it opens, so those 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.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) fyrox-ui/src/lib.rs:2795 — fyrox-ui/src/lib.rs:2795-2825 | fyrox-ui/src/lib.rs:3032-3062 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/lib.rs:2795` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (29–30 lines × 2) · ×1
  • Duplicated block (29–30 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:122 — editor/src/interaction/gizmo/move_gizmo.rs:122-151 | editor/src/interaction/gizmo/scale_gizmo.rs:104-132 — before extracting anything, compare `editor/src/interaction/gizmo/move_gizmo.rs` and `editor/src/interaction/gizmo/scale_gizmo.rs` as WHOLE FILES: this scan already matched 4 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. 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 `editor/src/interaction/gizmo/move_gizmo.rs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×1
  • Duplicated block (28–29 lines × 2) editor/src/plugins/tilemap/autotile.rs:471 — editor/src/plugins/tilemap/autotile.rs:471-498 | editor/src/plugins/tilemap/wfc.rs:507-535 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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. 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) fyrox-impl/src/scene/dim2/rectangle.rs:382 — fyrox-impl/src/scene/dim2/rectangle.rs:382-410 | fyrox-impl/src/scene/sprite.rs:377-405 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rectangle.rs` and `fyrox-impl/src/scene/sprite.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/rectangle.rs:382` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) fyrox-graphics/src/gpu_texture.rs:286 — fyrox-graphics/src/gpu_texture.rs:286-312 | fyrox-graphics/src/gpu_texture.rs:326-352 | fyrox-graphics/src/gpu_texture.rs:365-391 — 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 `fyrox-graphics/src/gpu_texture.rs:286` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1
  • Duplicated block (26–27 lines × 2) fyrox-impl/src/scene/tilemap/autotile.rs:152 — fyrox-impl/src/scene/tilemap/autotile.rs:152-178 | fyrox-impl/src/scene/tilemap/autotile.rs:262-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 `fyrox-impl/src/scene/tilemap/autotile.rs:152` it does not close everything it opens, so those 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.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×1
  • Duplicated block (24–25 lines × 2) fyrox-resource/src/manager.rs:1124 — fyrox-resource/src/manager.rs:1124-1147 | fyrox-resource/src/manager.rs:1276-1300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-resource/src/manager.rs:1124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:237 — editor/src/plugins/tilemap/colliders_tab.rs:237-260 | editor/src/plugins/tilemap/properties_tab.rs:462-484 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 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 `editor/src/plugins/tilemap/colliders_tab.rs:237` it begins part-way through the construct above it, so those 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, `editor/src/plugins/tilemap/properties_tab.rs:460` calls `add_row`, `auto`, `stretch` and `editor/src/plugins/tilemap/colliders_tab.rs:237` 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.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) fyrox-core/src/pool/multiborrow.rs:235 — fyrox-core/src/pool/multiborrow.rs:235-255 | fyrox-core/src/pool/multiborrow.rs:296-317 — both copies are in the same file, so extract the 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 · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) fyrox-ui/src/lib.rs:2821 — fyrox-ui/src/lib.rs:2821-2841 | fyrox-ui/src/lib.rs:3058-3078 | fyrox-ui/src/lib.rs:3105-3125 — 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 `fyrox-ui/src/lib.rs:2821` it does not close everything it opens, so those 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, `fyrox-ui/src/lib.rs:3102` calls `try_set_picked_node`, `hit_test` and `fyrox-ui/src/lib.rs:2818` 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.
D4 · Code Duplication · Duplicated block (20 lines × 4) · ×1
  • Duplicated block (20 lines × 4) fyrox-impl/src/scene/debug.rs:135 — fyrox-impl/src/scene/debug.rs:135-154 | fyrox-impl/src/scene/debug.rs:214-233 | fyrox-impl/src/scene/debug.rs:314-333 | fyrox-impl/src/scene/debug.rs:555-574 — 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.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:98 — editor/src/interaction/gizmo/move_gizmo.rs:98-117 | editor/src/interaction/gizmo/scale_gizmo.rs:81-98 — before extracting anything, compare `editor/src/interaction/gizmo/move_gizmo.rs` and `editor/src/interaction/gizmo/scale_gizmo.rs` as WHOLE FILES: this scan already matched 4 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. 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 `editor/src/interaction/gizmo/move_gizmo.rs:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:381 — editor/src/plugins/inspector/editors/dyntype.rs:381-400 | editor/src/plugins/inspector/editors/script.rs:478-496 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/dyntype.rs:381` 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.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1
  • Duplicated block (18–19 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1418 — fyrox-impl/src/scene/dim2/physics/mod.rs:1418-1435 | fyrox-impl/src/scene/graph/physics/mod.rs:1939-1957 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 32 separate duplicated blocks between them, totalling at least 575 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/physics/mod.rs:1418` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) editor/src/plugins/tilemap/properties_tab.rs:693 — editor/src/plugins/tilemap/properties_tab.rs:693-710 | editor/src/plugins/tilemap/properties_tab.rs:726-743 | editor/src/plugins/tilemap/properties_tab.rs:759-776 — 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.
D4 · Code Duplication · Duplicated block (15–18 lines × 2) · ×1
  • Duplicated block (15–18 lines × 2) fyrox-impl/src/resource/fbx/mod.rs:331 — fyrox-impl/src/resource/fbx/mod.rs:331-348 | fyrox-impl/src/resource/gltf/material.rs:430-444 — 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 `fyrox-impl/src/resource/gltf/material.rs:430` 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, `fyrox-impl/src/resource/gltf/material.rs:429` calls `resource_io` and `fyrox-impl/src/resource/fbx/mod.rs:330` 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.
D4 · Code Duplication · Duplicated block (10–17 lines × 3) · ×1
  • Duplicated block (10–17 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:192 — editor/src/plugins/tilemap/colliders_tab.rs:192-201 | editor/src/plugins/tilemap/macro_tab.rs:258-267 | editor/src/plugins/tilemap/properties_tab.rs:314-330 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/plugins/tilemap/colliders_tab.rs:192` it begins part-way through the construct above it, so those 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, `editor/src/plugins/tilemap/macro_tab.rs:257` calls `add_row`, `auto` and `editor/src/plugins/tilemap/colliders_tab.rs:191` 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 3) · ×1
  • Duplicated block (16–17 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:208 — editor/src/plugins/tilemap/colliders_tab.rs:208-223 | editor/src/plugins/tilemap/macro_tab.rs:274-290 | editor/src/plugins/tilemap/properties_tab.rs:337-352 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `editor/src/plugins/tilemap/colliders_tab.rs:208` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `editor/src/plugins/tilemap/macro_tab.rs:291` calls `with_margin`, `uniform`, `with_stroke_thickness` and `editor/src/plugins/tilemap/colliders_tab.rs:223` 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.
D4 · Code Duplication · Duplicated block (13–17 lines × 2) · ×1
  • Duplicated block (13–17 lines × 2) editor/src/command/panel.rs:98 — editor/src/command/panel.rs:98-110 | fyrox-ui/src/log.rs:179-195 — 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 `editor/src/command/panel.rs:98` it begins part-way through the construct above it, so those 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.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) fyrox-impl/src/scene/debug.rs:184 — fyrox-impl/src/scene/debug.rs:184-199 | fyrox-impl/src/scene/debug.rs:263-278 | fyrox-impl/src/scene/debug.rs:363-378 | fyrox-impl/src/scene/debug.rs:560-575 — 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 `fyrox-impl/src/scene/debug.rs:184` 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.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) editor/src/plugins/ragdoll.rs:346 — editor/src/plugins/ragdoll.rs:346-361 | editor/src/plugins/ragdoll.rs:401-416 | editor/src/plugins/ragdoll.rs:446-461 — 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 `editor/src/plugins/ragdoll.rs:346` it begins part-way through the construct above it, so those 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, `editor/src/plugins/ragdoll.rs:345` calls `with_shape`, `ball` and `editor/src/plugins/ragdoll.rs:400` 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.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) fyrox-ui/src/color/mod.rs:466 — fyrox-ui/src/color/mod.rs:466-479 | fyrox-ui/src/color/mod.rs:642-657 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/color/mod.rs:466` it does not close everything it opens, so those 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) fyrox-ui/src/inspector/editors/collection.rs:619 — fyrox-ui/src/inspector/editors/collection.rs:619-634 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:406-420 — 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 `fyrox-ui/src/inspector/editors/collection.rs:619` 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.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) editor/src/plugins/export.rs:273 — editor/src/plugins/export.rs:273-287 | editor/src/plugins/inspector/editors/spritesheet/window.rs:329-343 | editor/src/plugins/ragdoll.rs:1101-1115 | fyrox-ui/src/messagebox.rs:416-430 — before extracting anything, compare `editor/src/plugins/inspector/editors/spritesheet/window.rs` and `editor/src/plugins/ragdoll.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/export.rs:273` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) editor/src/plugins/inspector/editors/resource.rs:240 — editor/src/plugins/inspector/editors/resource.rs:240-254 | editor/src/plugins/inspector/editors/surface.rs:158-172 | editor/src/plugins/material/editor.rs:173-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/inspector/editors/resource.rs:240` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 3) · ×1
  • Duplicated block (13–14 lines × 3) editor/src/plugins/inspector/editors/dyntype.rs:381 — editor/src/plugins/inspector/editors/dyntype.rs:381-393 | editor/src/plugins/inspector/editors/script.rs:478-490 | fyrox-ui/src/inspector/editors/enumeration.rs:482-495 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-ui/src/inspector/editors/enumeration.rs:482` it begins part-way through the construct above it, so those 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, `editor/src/plugins/inspector/editors/dyntype.rs:380` calls `Some`, `value_ref` and `fyrox-ui/src/inspector/editors/enumeration.rs:481` 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.
D4 · Code Duplication · Duplicated block (12–14 lines × 3) · ×1
  • Duplicated block (12–14 lines × 3) fyrox-graphics-wgpu/src/buffer.rs:167 — fyrox-graphics-wgpu/src/buffer.rs:167-180 | fyrox-graphics-wgpu/src/framebuffer.rs:963-974 | fyrox-graphics-wgpu/src/read_buffer.rs:148-159 — 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.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) fyrox-ui/src/inspector/editors/inherit.rs:215 — fyrox-ui/src/inspector/editors/inherit.rs:215-228 | fyrox-ui/src/inspector/editors/inspectable.rs:94-107 | fyrox-ui/src/inspector/editors/refcell.rs:85-98 — before extracting anything, compare `fyrox-ui/src/inspector/editors/inspectable.rs` and `fyrox-ui/src/inspector/editors/refcell.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) editor/src/asset/selector.rs:532 — editor/src/asset/selector.rs:532-544 | fyrox-ui/src/inspector/editors/style.rs:333-346 — 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 `editor/src/asset/selector.rs:532` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) editor/src/scene/clipboard.rs:72 — editor/src/scene/clipboard.rs:72-85 | editor/src/ui_scene/clipboard.rs:67-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/scene/clipboard.rs:72` it begins part-way through the construct above it, so those 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 `root_nodes` to `&[Handle<Node>]` in one and `&[Handle<UiNode>]` 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.
D4 · Code Duplication · Duplicated block (11–14 lines × 2) · ×1
  • Duplicated block (11–14 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:648 — fyrox-impl/src/scene/mesh/surface.rs:648-658 | fyrox-impl/src/scene/mesh/surface.rs:799-812 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/mesh/surface.rs:648` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `fyrox-impl/src/scene/mesh/surface.rs:812` calls `insert`, `from_pos_uv_normal` and `fyrox-impl/src/scene/mesh/surface.rs:658` 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.
D4 · Code Duplication · Duplicated block (13 lines × 8) · ×1
  • Duplicated block (13 lines × 8) fyrox-impl/src/engine/mod.rs:1748 — fyrox-impl/src/engine/mod.rs:1748-1760 | fyrox-impl/src/engine/mod.rs:1841-1853 | fyrox-impl/src/engine/mod.rs:1882-1894 | fyrox-impl/src/engine/mod.rs:1934-1946 | fyrox-impl/src/engine/mod.rs:2079-2091 | fyrox-impl/src/engine/mod.rs:2114-2126 | fyrox-impl/src/engine/mod.rs:2149-2161 | fyrox-impl/src/engine/mod.rs:2184-2196 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `fyrox-impl/src/engine/mod.rs:1837` calls `handle_async_tasks` and `fyrox-impl/src/engine/mod.rs:1932` 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.
D4 · Code Duplication · Duplicated block (9–13 lines × 2) · ×1
  • Duplicated block (9–13 lines × 2) editor/src/audio/mod.rs:114 — editor/src/audio/mod.rs:114-122 | editor/src/audio/mod.rs:140-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/audio/mod.rs:114` it does not close everything it opens, so those 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) editor/src/plugins/tilemap/autotile.rs:471 — editor/src/plugins/tilemap/autotile.rs:471-482 | editor/src/plugins/tilemap/autotile.rs:622-633 | editor/src/plugins/tilemap/wfc.rs:507-518 | editor/src/plugins/tilemap/wfc.rs:641-652 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 144 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×1
  • Duplicated block (11–12 lines × 3) fyrox-impl/src/scene/transform.rs:450 — fyrox-impl/src/scene/transform.rs:450-461 | fyrox-impl/src/scene/transform.rs:463-474 | fyrox-impl/src/scene/transform.rs:475-485 — 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 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.
D4 · Code Duplication · Duplicated block (11 lines × 10) · ×1
  • Duplicated block (11 lines × 10) fyrox-impl/src/engine/mod.rs:1753 — fyrox-impl/src/engine/mod.rs:1753-1763 | fyrox-impl/src/engine/mod.rs:1846-1856 | fyrox-impl/src/engine/mod.rs:1887-1897 | fyrox-impl/src/engine/mod.rs:1939-1949 | fyrox-impl/src/engine/mod.rs:2084-2094 | fyrox-impl/src/engine/mod.rs:2119-2129 | fyrox-impl/src/engine/mod.rs:2154-2164 | fyrox-impl/src/engine/mod.rs:2189-2199 | fyrox-impl/src/engine/mod.rs:2364-2374 | fyrox-impl/src/engine/mod.rs:2392-2402 — all 10 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 `fyrox-impl/src/engine/mod.rs:1753` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `fyrox-impl/src/engine/mod.rs:1858` calls `iter_mut` and `fyrox-impl/src/engine/mod.rs:1764` 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.
D4 · Code Duplication · Duplicated block (8–11 lines × 2) · ×1
  • Duplicated block (8–11 lines × 2) fyrox-graphics-gl/src/program.rs:162 — fyrox-graphics-gl/src/program.rs:162-172 | fyrox-graphics-wgpu/src/program.rs:257-264 — 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 `fyrox-graphics-gl/src/program.rs:162` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:166 — editor/src/plugins/tilemap/colliders_tab.rs:166-174 | editor/src/plugins/tilemap/properties_tab.rs:375-384 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 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 `editor/src/plugins/tilemap/colliders_tab.rs:166` it begins part-way through the construct above it, so those 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) editor/src/plugins/collider/mod.rs:413 — editor/src/plugins/collider/mod.rs:413-421 | editor/src/plugins/collider/mod.rs:549-557 | editor/src/plugins/probe.rs:184-192 | editor/src/plugins/probe.rs:244-252 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/collider/mod.rs:413` it does not close everything it opens, so those 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, `editor/src/plugins/collider/mod.rs:546` calls `reset_handles`, `reset_state` and `editor/src/plugins/collider/mod.rs:411` 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 3) · ×1
  • Duplicated block (6–8 lines × 3) fyrox-math/src/lib.rs:144 — fyrox-math/src/lib.rs:144-151 | fyrox-math/src/lib.rs:304-309 | fyrox-math/src/lib.rs:340-347 — 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 2) · ×1
  • Duplicated block (6–8 lines × 2) fyrox-ui/src/lib.rs:1353 — fyrox-ui/src/lib.rs:1353-1358 | fyrox-ui/src/lib.rs:1386-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 `fyrox-ui/src/lib.rs:1353` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) editor/src/plugins/tilemap/properties_tab.rs:669 — editor/src/plugins/tilemap/properties_tab.rs:669-675 | editor/src/plugins/tilemap/properties_tab.rs:692-698 | editor/src/plugins/tilemap/properties_tab.rs:725-731 | editor/src/plugins/tilemap/properties_tab.rs:758-764 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:300 — editor/src/plugins/tilemap/colliders_tab.rs:300-306 | editor/src/plugins/tilemap/properties_tab.rs:587-592 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 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 `editor/src/plugins/tilemap/colliders_tab.rs:300` it does not close everything it opens, so those 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.
D4 · Code Duplication · Duplicated block (4–7 lines × 4) · ×1
  • Duplicated block (4–7 lines × 4) fyrox-ui/src/node/constructor.rs:183 — fyrox-ui/src/node/constructor.rs:183-186 | fyrox-ui/src/node/constructor.rs:190-196 | fyrox-ui/src/node/constructor.rs:201-207 | fyrox-ui/src/node/constructor.rs:208-216 — 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.
D4 · Code Duplication · Duplicated block (3–5 lines × 4) · ×1
  • Duplicated block (3–5 lines × 4) editor/src/plugins/tilemap/palette.rs:1740 — editor/src/plugins/tilemap/palette.rs:1740-1742 | editor/src/plugins/tilemap/palette.rs:1754-1758 | editor/src/plugins/tilemap/palette.rs:1770-1774 | editor/src/plugins/tilemap/panel_preview.rs:228-230 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/plugins/tilemap/palette.rs:1754` 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.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) editor/src/asset/item.rs:261 — editor/src/asset/item.rs:261-270 | editor/src/plugins/inspector/editors/font.rs:98-109 | editor/src/plugins/inspector/editors/handle.rs:164-175 | editor/src/plugins/inspector/editors/resource.rs:193-204 | fyrox-ui/src/key.rs:230-240 | fyrox-ui/src/key.rs:443-453 — there are 6 copies across 5 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.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) fyrox-animation/src/machine/mask.rs:73 — fyrox-animation/src/machine/mask.rs:73-77 | fyrox-core/src/pool/handle.rs:211-215 | fyrox-core/src/pool/mod.rs:173-177 | fyrox-core/src/variable.rs:441-445 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (14 lines × 8) · ×1
  • Duplicated block (14 lines × 8) editor/src/asset/dependency.rs:124 — editor/src/asset/dependency.rs:124-137 | editor/src/asset/mod.rs:973-986 | editor/src/plugins/export.rs:274-287 | editor/src/plugins/inspector/editors/spritesheet/window.rs:330-343 | editor/src/plugins/ragdoll.rs:1102-1115 | editor/src/plugins/settings.rs:149-162 | fyrox-ui/src/messagebox.rs:363-376 | fyrox-ui/src/messagebox.rs:417-430 — before extracting anything, compare `editor/src/asset/dependency.rs` and `editor/src/plugins/ragdoll.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `editor/src/asset/dependency.rs:124` 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.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) fyrox-impl/src/scene/dim2/joint.rs:349 — fyrox-impl/src/scene/dim2/joint.rs:349-361 | fyrox-impl/src/scene/dim2/joint.rs:383-395 | fyrox-impl/src/scene/joint.rs:408-420 | fyrox-impl/src/scene/joint.rs:442-454 — before extracting anything, compare `fyrox-impl/src/scene/dim2/joint.rs` and `fyrox-impl/src/scene/joint.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fyrox-impl/src/scene/dim2/joint.rs:349` 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.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) fyrox-ui/src/inspector/editors/texture_slice.rs:623 — fyrox-ui/src/inspector/editors/texture_slice.rs:623-628 | fyrox-ui/src/inspector/editors/texture_slice.rs:630-635 | fyrox-ui/src/inspector/editors/texture_slice.rs:637-642 | fyrox-ui/src/inspector/editors/texture_slice.rs:644-649 — 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 `fyrox-ui/src/inspector/editors/texture_slice.rs:623` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D5 · Coupling · Unstable project fyrox-impl · ×1
  • Unstable project fyrox-impl — fyrox-impl has instability 0.87 with 2 dependents.
Minor — 54 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×27
  • Duplicated predicate fyrox-ui/src/inspector/editors/inspectable.rs:167 — `ctx.message.data::<InspectorMessage>() && ctx.message.direction() == MessageDirection::FromWidget` appears character-identically in 2 files — fyrox-ui/src/inspector/editors/inspectable.rs, fyrox-ui/src/inspector/editors/refcell.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 editor/src/interaction/rotate_mode.rs:126 — `editor_selection.as_graph() && !selection.is_empty()` appears character-identically in 2 files — editor/src/interaction/rotate_mode.rs, editor/src/interaction/scale_mode.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 fyrox-build-tools/src/export/android.rs:64 — `entry.metadata() && !file_metadata.file_type().is_file()` appears character-identically in 2 files — fyrox-build-tools/src/export/android.rs, fyrox-build-tools/src/export/pc.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 fyrox-build-tools/src/export/android.rs:70 — `entry.path().file_stem() && stem == OsStr::new(package_name)` appears character-identically in 2 files — fyrox-build-tools/src/export/android.rs, fyrox-build-tools/src/export/pc.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 editor/src/plugins/collider/triangle.rs:123 — `handle == self.a_handle || handle == self.b_handle || handle == self.c_handle` appears character-identically in 2 files — editor/src/plugins/collider/triangle.rs, editor/src/plugins/collider/triangle2d.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 editor/src/plugins/collider/capsule.rs:145 — `handle == self.begin_handle || handle == self.end_handle` appears character-identically in 4 files — editor/src/plugins/collider/capsule.rs, editor/src/plugins/collider/capsule2d.rs, editor/src/plugins/collider/segment.rs, editor/src/plugins/collider/segment2d.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 editor/src/scene/property.rs:238 — `key.downcast_ref::<String>().is_some() || key.downcast_ref::<ImmutableString>().is_some()` appears character-identically in 2 files — editor/src/scene/property.rs, fyrox-core/src/reflect/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 editor/src/asset/menu.rs:126 — `message.data() && message.destination() == self.handle` appears character-identically in 3 files — editor/src/asset/menu.rs, editor/src/plugins/absm/blendspace.rs, editor/src/plugins/tilemap/tile_editor.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 editor/src/plugins/absm/state_graph/context.rs:359 — `message.data() && message.destination() == self.menu.handle()` appears character-identically in 2 files — editor/src/plugins/absm/state_graph/context.rs, editor/src/plugins/absm/state_viewer/context.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 editor/src/mesh.rs:393 — `message.data() && message.destination() == self.window` appears character-identically in 6 files — editor/src/mesh.rs, editor/src/plugins/export.rs, editor/src/plugins/light.rs, editor/src/plugins/stats.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 fyrox-ui/src/check_box.rs:207 — `message.destination() == self.handle() || self.widget.has_descendant(message.destination(), ui)` appears character-identically in 2 files — fyrox-ui/src/check_box.rs, fyrox-ui/src/dropdown_list.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 editor/src/scene/property.rs:531 — `message.destination() == self.selector && message.direction() == MessageDirection::FromWidget` appears character-identically in 2 files — editor/src/scene/property.rs, editor/src/scene/selector.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 editor/src/plugins/absm/canvas.rs:420 — `message.direction() == MessageDirection::FromWidget && !message.handled()` appears character-identically in 2 files — editor/src/plugins/absm/canvas.rs, fyrox-ui/src/color/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 editor/src/interaction/gizmo/move_gizmo.rs:305 — `picked == self.x_axis || picked == self.x_arrow` appears character-identically in 2 files — editor/src/interaction/gizmo/move_gizmo.rs, editor/src/interaction/gizmo/scale_gizmo.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 editor/src/interaction/gizmo/move_gizmo.rs:307 — `picked == self.y_axis || picked == self.y_arrow` appears character-identically in 2 files — editor/src/interaction/gizmo/move_gizmo.rs, editor/src/interaction/gizmo/scale_gizmo.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 editor/src/interaction/gizmo/move_gizmo.rs:309 — `picked == self.z_axis || picked == self.z_arrow` appears character-identically in 2 files — editor/src/interaction/gizmo/move_gizmo.rs, editor/src/interaction/gizmo/scale_gizmo.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 fyrox-impl/src/scene/mesh/mod.rs:704 — `renderer::is_shadow_pass(ctx.render_pass_name) && !self.cast_shadows()` appears character-identically in 3 files — fyrox-impl/src/scene/mesh/mod.rs, fyrox-impl/src/scene/particle_system/mod.rs, fyrox-impl/src/scene/terrain/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 fyrox-impl/src/scene/dim2/physics/mod.rs:1063 — `rigid_body_node.need_sync_model() || !actions.is_empty()` appears character-identically in 2 files — fyrox-impl/src/scene/dim2/physics/mod.rs, fyrox-impl/src/scene/graph/physics/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 fyrox-impl/src/scene/dim2/physics/mod.rs:1421 — `self.bodies.get(native_body1).is_none() || self.bodies.get(native_body2).is_none()` appears character-identically in 2 files — fyrox-impl/src/scene/dim2/physics/mod.rs, fyrox-impl/src/scene/graph/physics/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 fyrox-impl/src/scene/dim2/physics/mod.rs:1004 — `self.bodies.get(rigid_body.native.get()) && native.body_type() != RigidBodyType::Fixed` appears character-identically in 2 files — fyrox-impl/src/scene/dim2/physics/mod.rs, fyrox-impl/src/scene/graph/physics/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 fyrox-impl/src/scene/base.rs:777 — `self.original_handle_in_resource.is_some() && self.resource.is_some()` appears character-identically in 2 files — fyrox-impl/src/scene/base.rs, fyrox-ui/src/widget.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 editor/src/plugins/absm/state_graph/mod.rs:308 — `self.prev_layer != current_selection.layer || current_selection.absm_node_handle != Handle::<N>::from(self.prev_absm)` appears character-identically in 2 files — editor/src/plugins/absm/state_graph/mod.rs, editor/src/plugins/absm/state_viewer/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 fyrox-impl/src/scene/collider.rs:824 — `self.shape.need_sync() || self.friction.need_sync() || self.density.need_sync() || self.restitution.need_sync() || self.is_sensor.need_sync(…` appears character-identically in 2 files — fyrox-impl/src/scene/collider.rs, fyrox-impl/src/scene/dim2/collider.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 fyrox-graphics-gl/src/buffer.rs:86 — `server.gl.supports_debug() && server.named_objects.get()` appears character-identically in 3 files — fyrox-graphics-gl/src/buffer.rs, fyrox-graphics-gl/src/geometry_buffer.rs, fyrox-graphics-gl/src/texture.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 editor/src/lib.rs:2577 — `ui.active_tooltip() && !active_tooltip.shown` appears character-identically in 2 files — editor/src/lib.rs, project-manager/src/main.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.
  • + 2 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×14
  • Orphaned file fyrox-impl/src/scene/terrain/brushstroke/brushraster.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-impl/src/scene/terrain/brushstroke/strokechunks.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-ui/src/bbcode.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-math/src/segment.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-impl/src/scene/tilemap/effect.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-impl/src/resource/gltf/simplify.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-core-derive/src/reflect/prop.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-impl/src/resource/gltf/uri.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-impl/src/renderer/hdr/luminance/histogram_luminance_evaluator.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-core-derive/src/visit/utils.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-core/src/safelock.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-impl/src/resource/gltf/iter.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-ui/src/inspector/editors/immutable_string.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fyrox-core-derive/src/reflect/syntax.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
X7 · Silent fallback defaults · Silent fallback default on Err · ×4
  • Silent fallback default on Err editor/src/plugins/ragdoll.rs:358 — `make_sphere` turns every `Err` into `Default::default()` — 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 editor/src/plugins/ragdoll.rs:458 — `make_cuboid` turns every `Err` into `Default::default()` — 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 fyrox-core/src/net.rs:97 — `string_peer_address` turns every `Err` into `"Unknown".into()` — 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 fyrox-ui/src/lib.rs:3477 — `copy_node_recursive_with_limit` turns every `Err` into `Default::default()` — 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.
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift fyrox-impl/README.md:43 — fyrox-impl/README.md links to `CONTRIBUTING.md`, but `fyrox-impl/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift fyrox/README.md:43 — fyrox/README.md links to `CONTRIBUTING.md`, but `fyrox/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found template/src/main.rs:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `template/src/main.rs` makes this repository a deployable product (line 1).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 3 of 24 project(s) overshoot their size bounds, lowering Project Cohesion to 7.5/10. The most over is `editor` (72585 LoC, 590 module-visible types across 35 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 14 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: fyrox-impl/src/scene/terrain/brushstroke/brushraster.rs, fyrox-impl/src/scene/terrain/brushstroke/strokechunks.rs, fyrox-ui/src/bbcode.rs, fyrox-math/src/segment.rs, fyrox-impl/src/scene/tilemap/effect.rs, fyrox-impl/src/resource/gltf/simplify.rs, fyrox-core-derive/src/reflect/prop.rs, fyrox-impl/src/resource/gltf/uri.rs (and 6 more) (20 orphaned of 600 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 600 of the 649 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • 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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 14/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `template`.
X9 · Subsumed condition operand · Subsumed condition operand · ×1
  • Subsumed condition operand fyrox-impl/src/resource/fbx/mod.rs:390 — `name.contains("ShininessExponent")` can never decide this `||` — every value satisfying `name.contains("ShininessExponent")` also satisfies `name.contains("Shininess")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9edec2d3106d4a928b6ba70f34d9d5a2/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9edec2d3106d4a928b6ba70f34d9d5a2/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .31artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).0—

Run 01a1daea-c832-783f-820e-ef14c889eddb · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md