-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/9.0] Fix RunClassConstructor trim warning for Nullable<T> #107039
Merged
jeffschwMSFT
merged 3 commits into
dotnet:release/9.0
from
sbomer:runClassConstructorFix90
Sep 4, 2024
Merged
[release/9.0] Fix RunClassConstructor trim warning for Nullable<T> #107039
jeffschwMSFT
merged 3 commits into
dotnet:release/9.0
from
sbomer:runClassConstructorFix90
Sep 4, 2024
Conversation
This file contains 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
- Fix test name - Run it in ILC tests - Check warnings in analyzer tests
dotnet-issue-labeler
bot
added
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Aug 27, 2024
This was referenced Aug 27, 2024
teo-tsirpanis
added
area-Tools-ILLink
.NET linker development as well as trimming analyzers
and removed
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
labels
Sep 1, 2024
Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas |
jeffschwMSFT
approved these changes
Sep 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved. please get a code review. we can merge when ready
@sbomer can you take a look at the PR failures? |
/ba-g "Failures are unrelated timeouts." |
jtschuster
approved these changes
Sep 4, 2024
This was referenced Sep 11, 2024
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
Servicing-approved
Approved for servicing release
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.
Backport of #106975 to .NET 9.
Customer Impact
The trimming tools (ILLink, native AOT, and the trim analyzer) report warnings when
RunClassConstructor
is called for nullable value types. This is not problematic for trimming and should not warn.From #106975 (comment):
Regression
Testing
Added unit test that runs for all of the trimming tools.
Risk
Low. Fix is straightforward and limited in scope - it only adds an extra case in existing handling for the RunClassConstructor intrinsic.