-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Rename IsNotNullableIfReferenceType to IsNotNullable #36708
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
Rename IsNotNullableIfReferenceType to IsNotNullable #36708
Conversation
|
Can you please provide some discussion about the purpose and motivation for this change? |
|
|
||
| // https://github.com/dotnet/roslyn/issues/26198 Should this API be exposed through ITypeParameterSymbol? | ||
| internal abstract bool? IsNotNullableIfReferenceType { get; } | ||
| internal abstract bool? IsNotNullable { get; } |
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.
IsNotNullable [](start = 32, length = 13)
nit: Consider adding an xml doc while you're here
jcouv
left a comment
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)
Done. |
|
@dotnet/roslyn-compiler Please review, need a second sign-off for a pure rename change. |
|
@dotnet/roslyn-infrastructure It looks like integration tests are still flaky (https://github.com/dotnet/roslyn/pull/36708/checks?check_run_id=154757957, https://dev.azure.com/dnceng/public/_build/results?buildId=236648) |
|
@JoeRobich @ivanbasov Can you take a look at @AlekseyTs's failure there? Only one of the four integration test legs failed, so it indeed looks like some flakiness the automatic rerun didn't pick up. |
All the affected APIs are also covering nullable value types now.