-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix ILLink warnings in .NET Libraries #45623
Labels
area-Meta
Cost:XL
Work that requires one engineer more than 4 weeks
linkable-framework
Issues associated with delivering a linker friendly framework
Team:Libraries
Team:Runtime
tracking
This issue is tracking the completion of other related issues.
Milestone
Comments
eerhardt
added
area-Meta
linkable-framework
Issues associated with delivering a linker friendly framework
Team:Libraries
Team:Runtime
labels
Dec 5, 2020
Dotnet-GitSync-Bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Dec 5, 2020
This was referenced Dec 5, 2020
marek-safar
added
the
tracking
This issue is tracking the completion of other related issues.
label
Dec 7, 2020
eerhardt
added a commit
to eerhardt/runtime
that referenced
this issue
Dec 7, 2020
Contributes to dotnet#45623
eerhardt
added a commit
to eerhardt/runtime
that referenced
this issue
Dec 7, 2020
In order to make the code trimming-compatible, a slight behavior change was made. The SetupJSContinuation method will only get the Result of Task<TResult> objects. If an object derives from the base Task class, and defines its own Result property, SetupJSContinuation will no longer respect that property. This was done so the behavior remains consistent between trimmed and untrimmed applications. Contributes to dotnet#45623
26 tasks
eerhardt
added a commit
that referenced
this issue
Dec 8, 2020
* Address remaining Ref.Emit ILLink warnings in Mono. Contributes to #45623 * Remove mono suppressions file from illink-sharedframework.targets
eerhardt
added a commit
to eerhardt/runtime
that referenced
this issue
Dec 9, 2020
Also clean up some previously addressed warnings in the suppressions xml file. Contributes to dotnet#45623
eerhardt
added a commit
that referenced
this issue
Dec 9, 2020
* Address ILLink warning in InteropServices.JavaScript In order to make the code trimming-compatible, a slight behavior change was made. The SetupJSContinuation method will only get the Result of Task<TResult> objects. If an object derives from the base Task class, and defines its own Result property, SetupJSContinuation will no longer respect that property. This was done so the behavior remains consistent between trimmed and untrimmed applications. Contributes to #45623
eerhardt
added a commit
that referenced
this issue
Dec 11, 2020
* Remove ILLink warnings from empty console app Also clean up some previously addressed warnings in the suppressions xml file. Contributes to #45623 * Add trimming test for inherited attributes.
eerhardt
added a commit
to eerhardt/runtime
that referenced
this issue
Dec 15, 2020
eerhardt
added a commit
that referenced
this issue
Dec 16, 2020
* Add RequiresUnreferencedCode to Delegate constructors Contributes to #45623 * Add RequiresUnreferencedCode to some internal Reflection methods to address ILLink warnings. * Address remaining ILLink warnings in Reflection.Emit. * Respond to PR feedback Annotate Delegate.BindToMethod with DynamicallyAccessedMembers Fix up requires unreferenced code comments * Update API Compat txt for Delegate.CreateDelegate attribute removal * Fix Mono ILLink warnings
5 tasks
eerhardt
added a commit
to eerhardt/runtime
that referenced
this issue
Apr 28, 2021
Also resolve ILLink warnings in System.Net.Http.Json. Contributes to dotnet#45623
ghost
pushed a commit
that referenced
this issue
Apr 28, 2021
* Resolve ILLink warnings in System.Text.Json (Round 1) Also resolve ILLink warnings in System.Net.Http.Json. Contributes to #45623 * PR feedback
eerhardt
added a commit
to eerhardt/runtime
that referenced
this issue
Jun 1, 2021
Follow up to dotnet#52934. - Using JsonNode in dynamic statements is not trim compatible. Add a LibraryBuild warning since there isn't a direct API to put the warning on. - Mark JsonValueNotTrimmable's ctor as unsafe - Fix up a few warning messages - minor doc fixup Contributes to dotnet#45623
eerhardt
added a commit
to eerhardt/runtime
that referenced
this issue
Jul 16, 2021
Suppress ILLink warnings for operator methods now that dotnet/linker#1821 is resolved. Add TrimmingTests for Linq.Expressions operators. Fix dotnet#45623
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jul 16, 2021
eerhardt
added a commit
that referenced
this issue
Jul 21, 2021
* Resolve ILLink warnings in System.Linq.Expressions (Final) Suppress ILLink warnings for operator methods now that dotnet/linker#1821 is resolved. Add TrimmingTests for Linq.Expressions operators. Fix #45623
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jul 21, 2021
ghost
locked as resolved and limited conversation to collaborators
Aug 20, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-Meta
Cost:XL
Work that requires one engineer more than 4 weeks
linkable-framework
Issues associated with delivering a linker friendly framework
Team:Libraries
Team:Runtime
tracking
This issue is tracking the completion of other related issues.
In .NET 6, we plan on addressing the ILLink warnings in the .NET shared framework. This issue is to track the overall progress, and list ownership of the areas that needs work.
The work needs to happen from the "bottom up", similar to nullable annotations. This is because addressing linker warnings in a lower-level library can cause new warnings in a higher-level library calling that API. I've grouped the assemblies in the same order as #2339.
The assumption is that each assembly/area can have multiple PRs addressing it. The PRs will be split up as makes sense for ease of reviewing and making progress.
See #44035 (comment) for the initial categorization, count, and rough cost estimate of ILLink warnings.
cc @agocke @LakshanF @vitek-karas @marek-safar
The text was updated successfully, but these errors were encountered: