Message281720
> Do you want to add RETURN_NONE or RETURN_CONST? Or both?
Only RETURN_NONE because on some corner cases it allow to avoid completely the None constant from code.co_consts and reduce the stack size.
I'm not sure that I want to start taking the same road of WPython which added a *lot* of specialized instructions (combining two or more existing instructions). As you said, it has a cost on the maintenance, and might have a negative impact if _PyEval_EvalFrameDefault() becomes too big. |
|
Date |
User |
Action |
Args |
2016-11-25 14:08:21 | vstinner | set | recipients:
+ vstinner, rhettinger, serhiy.storchaka, matrixise |
2016-11-25 14:08:21 | vstinner | set | messageid: <1480082901.4.0.232296609913.issue28800@psf.upfronthosting.co.za> |
2016-11-25 14:08:21 | vstinner | link | issue28800 messages |
2016-11-25 14:08:21 | vstinner | create | |
|