Change constraint mismatch for 'supports null' from warning to error #17462
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the nullness feature being added, there is a new constraint solving codepath for nullness-related mismatches.
All nullness issues were warnings by default.
However, together with the 'supports null' constraint (e.g. matching on null, assigning null), this could lead to unsound F# code, e.g. by assigning null to an int.
This changes the logic by keeping it an error if an unsound type is inferred to have the 'null' constraint (coming from generics, assignment, matching).
Fixes #17423