Skip to content

Conversation

@ggiraldez
Copy link
Contributor

@ggiraldez ggiraldez commented Jan 19, 2026

If an identifier resolves lexically to an ImportDeconstructionSymbol definition, register that instead of skipping it and registering to the actual aliased definition. This allows keeping better track of referenced imports, which would otherwise appear to have no references pointing to them.

The drawback is that we need to explicitly follow through the aliases whenever we need access to the actual definition, eg. when resolving types, members, etc.

If an identifier resolves lexically to an `ImportDeconstructionSymbol`
definition, register that instead of skipping it and registering to the actual
aliased definition. This allows keeping better track of referenced imports. The
conterpart is that we need to explicitly follow through the aliases whenever we
need access to the actual definition, eg. when resolving types, members, etc.
@ggiraldez ggiraldez requested review from OmarTawfik and teofr January 19, 2026 19:30
@ggiraldez ggiraldez requested review from a team as code owners January 19, 2026 19:30
@changeset-bot
Copy link

changeset-bot bot commented Jan 19, 2026

⚠️ No Changeset found

Latest commit: bc40ee3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

@teofr teofr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mainly some questions to understand the change better.

…tensions/identifiers.rs

Co-authored-by: Teodoro Freund <[email protected]>
@ggiraldez ggiraldez requested a review from teofr January 22, 2026 17:57
Copy link
Contributor

@teofr teofr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Sorry for the annoying nits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants