Faster-CPython ideas: Plan for 3.14
github.com
github.com
Does this mean the experimental JIT could work better with code that uses map/reduce instead of the built-ins any/all? Or does the performance of map and reduce as currently implemented also suffer from this roundtrip between Python and C?