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

Exhaustiveness checking tracks only non-null decision paths #31093

Merged
merged 1 commit into from
Nov 14, 2018

Conversation

gafter
Copy link
Member

@gafter gafter commented Nov 10, 2018

Addresses part of #30597
Later, in a separate PR, the null paths will be checked in the nullable walker

Addresses part of dotnet#30597
Later, in a separate PR, the null paths will be checked in the nullable walker
@gafter gafter added this to the 16.0.P2 milestone Nov 10, 2018
@gafter gafter self-assigned this Nov 10, 2018
@gafter gafter requested review from agocke and cston November 10, 2018 00:48
@gafter gafter requested a review from a team as a code owner November 10, 2018 00:48
else

// We only report exhaustive warnings when the default label is reachable through some series of
// tests that do not include a test in which the value is know to be null. Handling paths with
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

know [](start = 70, length = 4)

known?

Copy link
Member

@agocke agocke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gafter gafter merged commit 75e6fde into dotnet:features/recursive-patterns Nov 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants