Add global variable ($var) type tracking#100
Merged
Merged
Conversation
a8c6ceb to
27fad89
Compare
Support reading and writing global variables in the type inference engine. Uninitialized global variable reads are now detected as errors. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
27fad89 to
9f4f611
Compare
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
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.
Motivation
Reading an unregistered global variable (
$unknown.upcase) silently dropped the expression from the type graph, producing no diagnostics. Ruby defines uninitialized globals asnil, so this was a false negative.Changes
class_varsfield fromScopefinish_global_var_writeChecked
cargo test --lib— 33 tests passed🤖 Generated with Claude Code