Skip to content

PEP 695: Lazy evaluation, concrete scoping semantics, other changes #3122

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
JelleZijlstra merged 21 commits into from
May 8, 2023
Merged

PEP 695: Lazy evaluation, concrete scoping semantics, other changes #3122

Changes from 1 commit
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
5b3bbee
PEP 695: Changes proposed as a result of implementation work
JelleZijlstra Apr 24, 2023
23a6c4d
It does not all have to be C
JelleZijlstra Apr 25, 2023
a20d27c
If PEP 649 is accepted, we should support formats
JelleZijlstra Apr 25, 2023
bb3c770
Two more updates:
JelleZijlstra Apr 25, 2023
af90161
Remove rejection of lambda lifting; that is the implementation we are…
JelleZijlstra Apr 25, 2023
8b43966
Longer discussion of lazy eval
JelleZijlstra Apr 25, 2023
6d80750
Update pep-0695.rst
JelleZijlstra Apr 26, 2023
3037e47
Merge branch 'main' into pep695change
JelleZijlstra Apr 26, 2023
e9969bd
Some comments from Alex
JelleZijlstra Apr 26, 2023
868bf7d
Rewording
JelleZijlstra Apr 26, 2023
a009ae4
Another Alex suggestion
JelleZijlstra Apr 26, 2023
608dedf
Change the AST
JelleZijlstra Apr 26, 2023
a064f11
Change of direction on mangling
JelleZijlstra Apr 27, 2023
7996ecc
Merge branch 'main' into pep695change
JelleZijlstra May 2, 2023
f446963
More precise scoping rules
JelleZijlstra May 4, 2023
368cc48
Update pep-0695.rst
JelleZijlstra May 4, 2023
607373c
Update pep-0695.rst
JelleZijlstra May 4, 2023
90101e1
Update pep-0695.rst
JelleZijlstra May 4, 2023
62d4d50
Clarify where def695 scopes are used
JelleZijlstra May 4, 2023
0e5160f
GitHub downtime made me write more
JelleZijlstra May 4, 2023
1654a1b
fix pep number typo
AlexWaygood May 5, 2023
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
Prev Previous commit
Next Next commit
GitHub downtime made me write more
  • Loading branch information
@JelleZijlstra
JelleZijlstra committed May 4, 2023
commit 0e5160f723a28b1c8c38f872f687d5a51e05d8ef
21 changes: 13 additions & 8 deletions pep-0695.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -912,14 +912,19 @@ clarify that the new scopes are for the most part like function scopes.
- Names bound within ``def695`` scopes cannot be rebound with a ``nonlocal`` statement in nested scopes.

``def695`` scopes are used for the evaluation of several new syntactic constructs proposed
in this PEP. In all cases, the scoping semantics are identical::

- The type parameters of generic type aliases
- The type parameters and annotations of generic functions
- The type parameters and base class expressions of generic classes
- The value of generic type aliases
- The bounds of type variables
- The constraints of type variables
in this PEP. Some are evaluated eagerly (when a type alias, function, or class is defined); others are
evaluated lazily (only when evaluation is specifically requested). In all cases, the scoping semantics are identical:

- Eagerly evaluated values:

- The type parameters of generic type aliases
- The type parameters and annotations of generic functions
- The type parameters and base class expressions of generic classes
- Lazily evaluated values:

- The value of generic type aliases
- The bounds of type variables
- The constraints of type variables

In the below translations, names that start with two underscores are internal to the implementation
and not visible to actual Python code. We use the following intrinsic functions, which in the real
Expand Down