-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Conversation
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.
Thanks! Looks good, but I have couple suggestions.
docs/source/literal_types.rst
Outdated
|
||
PossibleValues = Literal['one', 'two'] | ||
|
||
def assert_exhaustive(value: NoReturn) -> NoReturn: |
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.
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.
docs/source/literal_types.rst
Outdated
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. |
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.
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.
@ilevkivskyi thanks a lot for the review! Fixed 👍 |
docs/source/literal_types.rst
Outdated
return True | ||
elif x == 'two': | ||
return False | ||
assert_never(x) # E: Argument 1 to "assert_exhaustive" has incompatible type "Literal['three']"; expected "NoReturn" |
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.
The comment still refers to the old name assert_exhaustive
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