Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Adds docs about exhaustive literal and enum checks - #10860

Merged
ilevkivskyi merged 3 commits into
python:masterfrom
sobolevn:patch-6
Jul 23, 2021
Merged

Adds docs about exhaustive literal and enum checks#10860
ilevkivskyi merged 3 commits into
python:masterfrom
sobolevn:patch-6

Conversation

@sobolevn

@sobolevn sobolevn commented Jul 22, 2021

Copy link
Copy Markdown
Member

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

@ilevkivskyi ilevkivskyi left a comment

Copy link
Copy Markdown
Member

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.

Comment thread docs/source/literal_types.rst Outdated

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

def assert_exhaustive(value: NoReturn) -> NoReturn:

Copy link
Copy Markdown
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.

Comment thread 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.

Copy link
Copy Markdown
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
Copy Markdown
Member Author

@ilevkivskyi thanks a lot for the review! Fixed 👍

Comment thread 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"

Copy link
Copy Markdown
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