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
Reference type DU can be optimized into a single root class with fields.
Either when it is a single-case DU.
Or when it uses null as true value for the nullary cases.
In both scenarios, C# consumers do not see field nullability in the generated constructor.
Choose one or more from the following categories of impact
Unexpected nullness warning (false positive in nullness checking, code uses --checknulls and langversion:preview).
Missing nullness warning in a case which can produce nulls (false negative, code uses --checknulls and langversion:preview).
Breaking change related to older null constructs in code not using the checknulls switch.
Breaking change related to generic code and explicit type constraints (null, not null).
Type inference issue (i.e. code worked without type annotations before, and applying the --checknulls enforces type annotations).
C#/F# interop issue related to nullness metadata.
Other (none of the categories above apply).
Operating System
Windows (Default)
What .NET runtime/SDK kind are you seeing the issue on
Issue description
Reference type DU can be optimized into a single root class with fields.
Either when it is a single-case DU.
Or when it uses null as true value for the nullary cases.
In both scenarios, C# consumers do not see field nullability in the generated constructor.
Choose one or more from the following categories of impact
null
constructs in code not using the checknulls switch.null
,not null
).Operating System
Windows (Default)
What .NET runtime/SDK kind are you seeing the issue on
.NET SDK (.NET Core, .NET 5+)
.NET Runtime/SDK version
No response
Reproducible code snippet and actual behavior
Possible workarounds
No response
The text was updated successfully, but these errors were encountered: