Consistently report unresolved members in illink #103667
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
|
Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas |
jtschuster
approved these changes
Jun 18, 2024
Co-authored-by: Jackson Schuster <[email protected]>
This was referenced Jun 19, 2024
Open
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Just fixing something I noticed while investigating another issue. The resolution cache is shared between
ResolveandTryResolve, so we should callReportUnresolvedfromResolvewhen we see a cached null result (that could have been cached duringTryResolve). Should make no difference to supported scenarios because we always run withIgnoreUnresolvedtrue.Looks like I regressed this in dotnet/linker#2253.