20260515 cse dominance trick

[prozacchiwawa]

Note

Low Risk
Single redundant dialect flag assignment in module compile setup; no auth or I/O changes, and behavior should match the prior unconditional cse_dominance = true unless future stepping logic alters the dialect.

Overview
Module compilation now sets dialect.cse_dominance = true again inside the stepping branch of module_compile_opts, in addition to the existing unconditional enable at the start of that helper.

That flag switches the CSE optimizer to the corrected dominance rules (see before_cse_dominance_fix in cse.rs) instead of the legacy if-branch overlap behavior. The change is scoped to chialisp module builds, which already force int_fix, optimization, and a minimum stepping of 26 when stepping is present.

^{Reviewed by Cursor Bugbot for commit bed807f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit bed807f. Configure here.}

[cursor]

Redundant CSE dominance assignment

Low Severity

The new dialect.cse_dominance = true inside the if let Some(stepping) block is a dead store. cse_dominance is already set to true unconditionally just above, so this assignment never changes behavior and only duplicates the existing enablement for modules.

 

^{Reviewed by Cursor Bugbot for commit bed807f. Configure here.}