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

Adds docs about exhaustive literal and enum checks #10860

Merged
merged 3 commits into from
Jul 23, 2021
Merged

Adds docs about exhaustive literal and enum checks #10860

merged 3 commits into from
Jul 23, 2021

Conversation

sobolevn
Copy link
Member

@sobolevn sobolevn commented Jul 22, 2021

This feature is not-really known from my experience. I had to explain it several times to other devs.
But, I think that this technique should be widely recognised! It is awesome!

Refs #6366

Copy link
Member

@ilevkivskyi ilevkivskyi left a comment

Choose a reason for hiding this comment

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

Thanks! Looks good, but I have couple suggestions.


PossibleValues = Literal['one', 'two']

def assert_exhaustive(value: NoReturn) -> NoReturn:
Copy link
Member

Choose a reason for hiding this comment

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

People actually often call this function assert_never() it can be used is some other cases where people want to check statically some will not be executed.

return False
assert_exhaustive(x) # E: Argument 1 to "assert_exhaustive" has incompatible type "Literal['three']"; expected "NoReturn"

This technique works with ``Enum`` values as well.
Copy link
Member

Choose a reason for hiding this comment

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

I would move the Enum reference to the start, and maybe even make this a default example (while mentioning it also works for literal types with a short example). IMO literal types are more for legacy code, while enums are the future.

@sobolevn
Copy link
Member Author

@ilevkivskyi thanks a lot for the review! Fixed 👍

return True
elif x == 'two':
return False
assert_never(x) # E: Argument 1 to "assert_exhaustive" has incompatible type "Literal['three']"; expected "NoReturn"
Copy link
Member

Choose a reason for hiding this comment

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

The comment still refers to the old name assert_exhaustive

@ilevkivskyi ilevkivskyi merged commit fb75cdc into python:master Jul 23, 2021
@sobolevn sobolevn deleted the patch-6 branch July 23, 2021 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants