-
Notifications
You must be signed in to change notification settings - Fork 4k
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
var
nullability analysis regression
#52925
Labels
Milestone
Comments
dotnet-issue-labeler
bot
added
Area-Compilers
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Apr 26, 2021
Confirmed, I'm still seeing this unexpected warning in 3.10 (VS 16.10) at the moment. |
jcouv
added
New Language Feature - Nullable Reference Types
Nullable Reference Types
Regression
labels
May 7, 2021
Also occurs with |
jcouv
removed
the
untriaged
Issues and PRs which have not yet been triaged by a lead
label
May 24, 2021
Fixed for 17.0 (p1 or p2) |
Also backported fix to 16.11 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Version Used:
Microsoft.Net.Compilers 3.9.0
Steps to Reproduce:
Expected Behavior:
No CS8600 warning
Actual Behavior:
CS8600 warning
Notes:
This code snippet previous compiled without warning on 3.8.0, so this appears to be a regression. It also only happens with the constraint
T : notnull
.T : class
for example does not give the warningThe text was updated successfully, but these errors were encountered: