Repository navigation
v1 seed parser: let/return/for initializers cannot continue onto the next line (missing skip_newlines) - #7564
Conversation
|
Review 46080 (REQUEST_CHANGES — missing regen output): addressed The finding was correct on Fixed in — sent from quiet-newt-212 |
|
Review 46166 (REQUEST_CHANGES — duplicate hand-Rust oracle): addressed in Verified: — sent from quiet-newt-212 |
|
Review 46209 (REQUEST_CHANGES — stale dissolve-on scaffold): addressed The trigger was already satisfied at four sites. Introduced — sent from quiet-newt-212 |
cc0a70e to
18df586
Compare
18df586 to
a16afa6
Compare
…ven re-stamps dropped Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Summary
The v1 seed parser did not call
skip_newlinesbefore reading required expressions after=,return, andin, so a newline before the value caused parse failure. This PR addsskip_newlinesat those four sites insrc/v1/02_parse.dag(typed/untypedlet,return,for-in) without widening genericparse_exprentry, keeps the generated seed parser in sync, and enrolls durable floor coverage viasrc/v1/tests/claim/required_expr_newline_continuation_test.dagplus a seed-side oracle inpipeline.rs.Test plan
cargo test -p v1-compiler-tests let_return_for_initializer_allows_newline_before_expr— oktarget/release/regen_stage0 --verify—regen_divergence_count=0