Refactor identifier-usage-analyzer to use syntax-traverse #693
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.
The
identifier-usage-analyzerwas manually traversing all possible fully expanded syntactic forms using extensive syntax-class definitions. This approach required ~250 lines of boilerplate matching every kernel form, making it difficult to maintain compared tovariable-mutability-analyzerwhich usessyntax-traverseandsyntax-search.Changes
fully-expanded-top-level-form,fully-expanded-expression,fully-expanded-formals, and related classes that explicitly matched each kernel formsyntax-traversalprimitives:syntax-traverselabels identifiers with phase informationsyntax-searchfinds binding sites (binding-site-identifiers) and usage sites (usage-site-identifiers)The refactored implementation follows the same pattern as
variable-mutability-analyzerfor consistency.Before vs After
Before (manual traversal):
After (syntax-search):
Original prompt
syntax-traverse#686💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.