fix: captured refs create scope boundaries in type inference #258
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
zharinov
force-pushed
the
fix/captured-ref-scope
branch
from
41fc1cf to
74b7f40
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Expr::Reftoinner_creates_scope()check in type inference(B) @bnow correctly create scope boundaries@bwas inferred asNodeinstead of B's return typeWhy
When a ref is captured (
(B) @b), the capture should contain B's structured result, not bubble B's internal captures. This matches the behavior of captured sequences/alternations.Before:
A = (program (B) @b)whereB = (expr) @x→A = { b: Node, x: Node }(wrong)After:
A = { b: B }whereB = { x: Node }(correct)Uncaptured refs remain transparent - their captures still bubble up correctly.