[issue31921] Bring together logic for entering/leaving a frame in frameobject.c

Change by pdox : -- resolution: -> rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue31921] Bring together logic for entering/leaving a frame in frameobject.c

pdox added the comment: Raymond, this is not an experiment, but the beginning of a sustained effort to improve locality during execution, to make more effective use of CPU cache lines. Rather than discuss the details of this change one PR at a time, I will close this issue for now, and open a

[issue31921] Bring together logic for entering/leaving a frame in frameobject.c

Raymond Hettinger added the comment: I don't think we should be re-arranging the core of the language to facilitate your language experiments. We need to know that is this is valuable for other people, not just you. -- nosy: +rhettinger ___ Python

[issue31921] Bring together logic for entering/leaving a frame in frameobject.c

Change by pdox : -- keywords: +patch pull_requests: +4195 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing

[issue31921] Bring together logic for entering/leaving a frame in frameobject.c

New submission from pdox : This is a refactor to move all the code involved in entering a frame (making it the active frame for the current tstate) and leaving a frame (removing it as an active frame, possibly destructing it or making it GC tracked) into private functions in frameobject.c. Th