Add receiverless method call support#20
Merged
Merged
Conversation
Ruby methods are frequently called without an explicit receiver (e.g., `name` instead of `self.name`). Without handling these, many method return types could not be resolved by the type inference engine. ## Changes: - Add ImplicitSelfCall variant to NeedsChildKind - Dispatch receiver-less CallNode as ImplicitSelfCall, synthesizing an implicit self receiver from the current class/module scope (falls back to Object at top-level) - Skip attr_reader/attr_writer/attr_accessor (deferred to next phase) - Extract process_method_call_common to share logic between MethodCall and ImplicitSelfCall - Hoist block/arguments extraction before receiver branch to eliminate duplication - Add 8 tests covering: basic resolution, arguments, nested class, module, block scope, top-level, attr_* skip, and super independence
Merged
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.
Ruby methods are frequently called without an explicit receiver (e.g.,
nameinstead ofself.name). Without handling these, many method return types could not be resolved by the type inference engine.Changes: