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.
| Group |
Assembly |
Team |
Assignee |
Done |
| 0 |
System.Private.CoreLib - COM |
CoreCLR |
LakshanF |
|
| 0 |
System.Private.CoreLib - EventSource |
CoreCLR |
LakshanF |
|
| 0 |
System.Private.CoreLib - StartupHook |
CoreCLR |
mateoatr |
|
| 0 |
System.Private.CoreLib - Mono |
Mono |
eerhardt |
|
| 0 |
System.Private.CoreLib - Resources |
Libraries |
joperezr |
|
| 0 |
System.Private.CoreLib - Reflection |
Libraries |
eerhardt |
|
| 0 |
System.Private.CoreLib - Other |
Libraries |
eerhardt |
|
| 0 |
System.Runtime.InteropServices |
Libraries |
eerhardt |
|
| 1 |
System.ObjectModel |
Libraries |
eerhardt |
|
| 1 |
System.Text.RegularExpressions |
Libraries |
eerhardt |
|
| 1 |
System.Text.Json |
Libraries |
eerhardt/steveharter |
|
| 1 |
System.Runtime.Serialization.Formatters |
Libraries |
eerhardt |
|
| 1 |
System.Reflection.DispatchProxy |
Libraries |
eerhardt |
|
| 1 |
System.Reflection.TypeExtensions |
Libraries |
eerhardt |
|
| 1 |
System.Diagnostics.DiagnosticSource |
Libraries |
eerhardt |
|
| 1 |
System.Drawing.Primitives |
Libraries |
eerhardt |
|
| 2 |
System.Linq.Expressions |
Libraries |
eerhardt |
|
| 3 |
System.Security.Cryptography.Algorithms |
Libraries |
eerhardt |
|
| 3 |
System.Linq.Queryable |
Libraries |
eerhardt |
|
| 4 |
System.Security.Cryptography.X509Certificates |
Libraries |
eerhardt |
|
| 4 |
System.Diagnostics.TraceSource |
Libraries |
eerhardt |
|
| 5 |
System.Security.Cryptography.Csp |
Libraries |
eerhardt |
|
| 5 |
Microsoft.VisualBasic.Core |
Libraries |
joperezr |
|
| 6 |
System.Net.Http.Json |
Libraries |
eerhardt |
|
| 7 |
Microsoft.CSharp |
Libraries |
kwicher |
|
| 7 |
System.Private.Xml |
Libraries |
joperezr/angocke |
|
| 7 |
System.Net.Http |
Libraries |
joperezr |
|
| 8 |
System.ComponentModel.TypeConverter |
Libraries |
eerhardt |
|
| 8 |
System.Data.Common |
Libraries |
kwicher |
|
| 8 |
System.Private.DataContractSerialization |
Libraries |
joperezr |
|
| 9 |
System.ComponentModel.Annotations |
Libraries |
eerhardt |
|
See #44035 (comment) for the initial categorization, count, and rough cost estimate of ILLink warnings.
cc @agocke @LakshanF @vitek-karas @marek-safar
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