Migrate statement-position Vec<Expression> to Vec<ExpressionStatement> (BT-974)#1009
Migrate statement-position Vec<Expression> to Vec<ExpressionStatement> (BT-974)#1009
Conversation
…tement> (BT-974) Phase 1, Issue 2 of ADR 0044 (Comments as First-Class AST Nodes). - Change Module.expressions, MethodDefinition.body, Block.body from Vec<Expression> to Vec<ExpressionStatement> - Rename Module.leading_comments to Module.file_leading_comments - Update parser to wrap with ExpressionStatement::bare() - Update all codegen, lint, semantic, LSP, and query consumers - Regenerate 65 parser snapshots Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Organization UI Review profile: CHILL Plan: Pro Disabled knowledge base sources:
⛔ Files ignored due to path filters (65)
📒 Files selected for processing (44)
📝 WalkthroughWalkthroughThis PR introduces a new Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~75 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Comment |
Summary
Phase 1, Issue 2 of ADR 0044 (Comments as First-Class AST Nodes). Pure mechanical type migration — no behavior changes.
Module.expressions,MethodDefinition.body,Block.body) fromVec<Expression>toVec<ExpressionStatement>Module.leading_commentstoModule.file_leading_commentsExpressionStatement::bare(), codegen/lint/semantic/LSP unwrap via.expressionLinear: https://linear.app/beamtalk/issue/BT-974
Test plan
just cipasses (build, clippy, fmt-check, test, test-e2e)🤖 Generated with Claude Code
Summary by CodeRabbit