You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Across .NET Core 3.0 and .NET 5.0, we annotated 94% of the netcoreapp assemblies for nullable reference types. In .NET 6.0/.NET 7.0, we plan to annotate the remaining 6% of that surface area and continue through other assemblies built from the dotnet/runtime repo.
This issue represents the assemblies previously tracked in #2339 that did not get completed in .NET 5.0. Following the same practices we used in .NET 5.0, we will:
Submit individual PRs, one for each assembly. Each PR should include changes to both the src and the ref. Each PR should contain only changes related to the nullable annotations/attributes, no other changes.
PRs can be merged once the annotations have been appropriately reviewed in PR.
Across .NET Core 3.0 and .NET 5.0, we annotated 94% of the
netcoreappassemblies for nullable reference types. In .NET 6.0/.NET 7.0, we plan to annotate the remaining 6% of that surface area and continue through other assemblies built from the dotnet/runtime repo.This issue represents the assemblies previously tracked in #2339 that did not get completed in .NET 5.0. Following the same practices we used in .NET 5.0, we will:
In .NET 5.0, as was tracked in #2339, we completed groups 1-8, most of group 9, all of group 10, and some items in groups 11 and 12
Planned for .NET 6.0
Group 9
Group 11 (not part of netcoreapp but reference netcoreapp)
Stretch Goal for .NET 6, or Carry Over to .NET 7.0
Group 12 (built from dotnet/runtime but not in netcoreapp and reference netstandard)
With netstandard not annotated, we will need to be cognizant of the fact that all dependencies will be viewed as oblivious:
Lastly
#nullable enablefrom individual files after all dependent projects annotated