fix(interpreter): optimize file execution ⚡ - #221
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Normal
ndc script.ndcexecution used the resumable compiler path, which disables peephole optimization. File execution now uses a one-shot interpreter backed byCompiler::compile, so complete programs are optimized while REPL evaluation continues to retain compiler and VM state between inputs.The one-shot path also restores analyzer state after each execution, and regression tests verify both optimizer use and declaration isolation.
Validation:
cargo test --workspacecargo clippy --workspace --all-targetscargo build --no-default-featurescargo fmt --all -- --checkAI disclosure: Codex (GPT-6) assisted with investigation, implementation, regression tests, validation, and PR drafting.