Skip to content
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

Nullness issue - static methods on struct do not report nullness warning #17880

Closed
1 of 7 tasks
T-Gro opened this issue Oct 14, 2024 · 0 comments · Fixed by #17918
Closed
1 of 7 tasks

Nullness issue - static methods on struct do not report nullness warning #17880

T-Gro opened this issue Oct 14, 2024 · 0 comments · Fixed by #17918
Assignees
Labels
Area-Nullness Issues related to handling of Nullable Reference Types Bug Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code.
Milestone

Comments

@T-Gro
Copy link
Member

T-Gro commented Oct 14, 2024

Issue description

Methods like:

DateTime.Parse
Int32.Parse

require a non-nullable string.
Yet, they do not a report a nullable warning when a possibly null string is passed in.
They do report for the null literal

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

.NET SDK (.NET Core, .NET 5+)

.NET Runtime/SDK version

No response

Reproducible code snippet and actual behavior

No response

Possible workarounds

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Nullness Issues related to handling of Nullable Reference Types Bug Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code.
Projects
Archived in project
2 participants