-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add support for /nullable:warnings and /nullable:safeonlywarnings #32071
Conversation
@@ -63286,6 +63539,8 @@ static object M() | |||
assertDiagnosticOptions(NullableContextOptions.Disable); | |||
assertDiagnosticOptions(NullableContextOptions.Enable); | |||
assertDiagnosticOptions(NullableContextOptions.SafeOnly); | |||
assertDiagnosticOptions(NullableContextOptions.Warnings); | |||
assertDiagnosticOptions(NullableContextOptions.SafeOnlyWarnings); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I missed it, but do we have a test that shows that safeonlywarnings
produces a subset of diagnostics produced by warnings
? #Resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I missed it, but do we have a test that shows that safeonlywarnings produces a subset of diagnostics produced by warnings?
We do have tests to verify that NullableContextOptions.SafeOnly
/NullableContextOptions.SafeOnlyWarnings
and NullableContextOptions.Enable
/NullableContextOptions.Warnings
have similar effect on diagnostics.
I extended existing tests accordingly
In reply to: 244613425 [](ancestors = 244613425)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Thanks (iteration 1) with a test suggestion (if we don't have it already)
CC @jaredpar For approval |
Approved |
No description provided.