Skip to content

Consistently report unresolved members in illink#103667

Merged
sbomer merged 2 commits into
dotnet:mainfrom
sbomer:fixReportUnresolved
Jun 19, 2024
Merged

Consistently report unresolved members in illink#103667
sbomer merged 2 commits into
dotnet:mainfrom
sbomer:fixReportUnresolved

Conversation

@sbomer

@sbomer sbomer commented Jun 18, 2024

Copy link
Copy Markdown
Member

Just fixing something I noticed while investigating another issue. The resolution cache is shared between Resolve and TryResolve, so we should call ReportUnresolved from Resolve when we see a cached null result (that could have been cached during TryResolve). Should make no difference to supported scenarios because we always run with IgnoreUnresolved true.

Looks like I regressed this in dotnet/linker#2253.

@sbomer
sbomer requested a review from jtschuster June 18, 2024 18:57
@sbomer
sbomer requested a review from marek-safar as a code owner June 18, 2024 18:57
@ghost ghost added the area-Tools-ILLink .NET linker development as well as trimming analyzers label Jun 18, 2024
@dotnet-policy-service dotnet-policy-service Bot added the linkable-framework Issues associated with delivering a linker friendly framework label Jun 18, 2024
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas
See info in area-owners.md if you want to be subscribed.

Comment thread src/tools/illink/src/linker/Linker/LinkContext.cs Outdated
Co-authored-by: Jackson Schuster <36744439+jtschuster@users.noreply.github.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Tools-ILLink .NET linker development as well as trimming analyzers linkable-framework Issues associated with delivering a linker friendly framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants