Skip to content

Allow unary + in Literal integers #1550

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 12, 2024
Merged

Allow unary + in Literal integers #1550

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/spec/literal.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,8 +168,8 @@ The following parameters are intentionally disallowed by design:
``Literal[4j]`` that contain just a single complex number are also
prohibited.

- The only exception to this rule is the unary ``-`` (minus) for ints: types
like ``Literal[-5]`` are *accepted*.
- The only exceptions to this rule are the unary ``-`` (minus) and unary ``+`` (plus) for ints: types
like ``Literal[-5]`` and ``Literal[+1]`` are *accepted*.

- Tuples containing valid literal types like ``Literal[(1, "foo", "bar")]``.
The user could always express this type as
Expand Down