Skip to content

Add grammar for unpacking tuple types. #100

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

Closed
dnwpark wants to merge 1 commit into from
Closed

Add grammar for unpacking tuple types. #100

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
6 changes: 5 additions & 1 deletion pep.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -510,7 +510,8 @@ imported qualified or with some other name)

<variadic-type-arg> =
<type> ,
| * [ <type-for-iter> ] ,
| * [ <type-for> ] ,
| * <tuple-type>


<type-for> = <type> <type-for-iter>+ <type-for-if>*
Expand All @@ -524,6 +525,9 @@ imported qualified or with some other name)
(``<type-bool-for>`` is identical to ``<type-for>`` except that the
result type is a ``<type-bool>`` instead of a ``<type>``.)

(``<tuple-type>`` is any type which when evaluated resolves to a tuple
type eg. ``tuple[int, str]``.)

There are three core syntactic features introduced: type booleans,
conditional types and unpacked comprehension types.

Expand Down