Repository navigation
Retrieve definitions ahead of imports for explicit symbol questions - #65
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
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.
Fixes #63. For explicit “Where is NAME defined/declared?” questions, search for the whole identifier, including short names. Prefer a Python def, async def, or class declaration line over an import and anchor the excerpt at that declaration even when it appears late. This is lexical source retrieval, so dynamic definitions and full language semantics are outside its scope.
On the fictional catalog, the evaluation changes from 4/6 to 6/6. Regressions also cover partial identifiers, short names, README examples and a late async declaration under a tight character budget. Ran the analyzer regression suite locally.