You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
opy-rs: optimizeForSizeAggressive emits Skip If for a trailing comparison if #671
Verified (2026-10-29) by an independent canonical comparison against pinned OverPy 9.7.17 (opy-compat project-compare, workshop-rs 1.28.2). The gap is real, with one correction: it reproduces only when #!optimizeForSize is enabled together with the directive named in this Issue (#!optimizeForSizeAggressive). The directive alone is canonically identical to the oracle.
Acceptance criteria stay as written, with #!optimizeForSize added to the reproducer.
Commit a0a034a is pushed on fix/671-optimize-for-size-aggressive; ready for independent review. The tail-only aggressive rewrite now preserves comparison if structure and retains negation lowering. Ablation removed the comparison-specific path without adding production mechanisms.
Acceptance evidence: reproduced the original gap with both#!optimizeForSize and #!optimizeForSizeAggressive against pinned OverPy 9.7.17, using only canonical Workshop programs parsed by workshop-rs 1.28.2. The same reproducer now reports equivalent: true, zero differences. The new structural-size-aggressive-control-flow differential fixture matches the oracle and runs in the Rust canonical regression and native corpus harness.
Foreground verification passed: formatting; stable and Rust 1.88.0 workspace/all-target/all-feature clippy with -D warnings; workspace/all-target/all-feature Rust tests; 52 Python tests; native corpus (155 match, 15 known gaps, zero unexpected); all 6,114 builtin probes (zero unexplained); both pinned Bastion structural comparisons (zero unrecorded). Full commands and the initial corpus timeout followed by a successful complete rerun are recorded in the PR.
Unverified: remote CI and live game execution. UI gates do not apply (no ui/). A separate pre-existing difference with #!disableOptimizations combined with both size directives was observed during exploration and remains outside this issue's reproduction and this PR's parity claim.
Activity
e54-bot commentedon Oct 29, 2026
Verified (2026-10-29) by an independent canonical comparison against pinned OverPy 9.7.17 (
opy-compat project-compare, workshop-rs 1.28.2). The gap is real, with one correction: it reproduces only when#!optimizeForSizeis enabled together with the directive named in this Issue (#!optimizeForSizeAggressive). The directive alone is canonically identical to the oracle.Acceptance criteria stay as written, with
#!optimizeForSizeadded to the reproducer.e54-bot commentedon Oct 29, 2026
Implemented #671 in PR #681: #681
Commit
a0a034ais pushed onfix/671-optimize-for-size-aggressive; ready for independent review. The tail-only aggressive rewrite now preserves comparisonifstructure and retains negation lowering. Ablation removed the comparison-specific path without adding production mechanisms.Acceptance evidence: reproduced the original gap with both
#!optimizeForSizeand#!optimizeForSizeAggressiveagainst pinned OverPy 9.7.17, using only canonical Workshop programs parsed by workshop-rs 1.28.2. The same reproducer now reportsequivalent: true, zero differences. The newstructural-size-aggressive-control-flowdifferential fixture matches the oracle and runs in the Rust canonical regression and native corpus harness.Foreground verification passed: formatting; stable and Rust 1.88.0 workspace/all-target/all-feature clippy with
-D warnings; workspace/all-target/all-feature Rust tests; 52 Python tests; native corpus (155 match, 15 known gaps, zero unexpected); all 6,114 builtin probes (zero unexplained); both pinned Bastion structural comparisons (zero unrecorded). Full commands and the initial corpus timeout followed by a successful complete rerun are recorded in the PR.Unverified: remote CI and live game execution. UI gates do not apply (no
ui/). A separate pre-existing difference with#!disableOptimizationscombined with both size directives was observed during exploration and remains outside this issue's reproduction and this PR's parity claim.fix: preserve normalized tail comparisons under aggressive size optim…