Skip to content

The case generator no longer reports escaping calls in conditions as an error. #135193

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

Jump to bottom
Open
markshannon opened this issue Jun 5, 2025 · 0 comments
Open

The case generator no longer reports escaping calls in conditions as an error. #135193

markshannon opened this issue Jun 5, 2025 · 0 comments
Assignees
@markshannon
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error

Comments

@markshannon
Copy link
Member

markshannon commented Jun 5, 2025 •
edited by github-actions bot
Loading

Bug report

Bug description:

In bytecodes.c this should be an error, as the code generator cannot correctly wrap the escaping call in spill code:

    if (escaping_call(()) {

but this is no longer reported as an error.

This doesn't seem to be causing any problems, but I did notice it when modifying bytecodes.c recently, and it should be fixed.

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response
@markshannon markshannon added the type-bug An unexpected behavior, bug, or error label Jun 5, 2025
@markshannon markshannon self-assigned this Jun 5, 2025
@tomasr8 tomasr8 added the interpreter-core (Objects, Python, Grammar, and Parser dirs) label Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@markshannon markshannon

Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tomasr8 @markshannon