Repository navigation
TypedPython: region allocation for unbounded virtual objects (SPEC N-12, split from #143) #268
Description
Split from #143 (leader decision). Virtual objects whose count is unbounded live in a region tied to one activation of a compiled function and are freed together; real objects are never placed in a region; a failed region allocation raises MemoryError where CPython would.
Done when: unbounded virtual objects that die inside a compiled function (for example a compiled caller doing check(make(d)) whose tree never leaves it) are allocated in a region, the verifier proves region lifetimes, and the N-12 differential and mutation tests pass for region objects.
Activity
b-re-w commentedon Oct 25, 2026
Completion criterion changed (leader, 2026-10-25): binary-trees as written cannot build its tree in a region. make(d) returns the tree to main, which stays interpreted, so the tree escapes and must be real objects; on free-threaded 3.15t real objects are also reachable from other threads via gc.get_objects(), and SPEC N-12 never places real objects in a region. The criterion is now region allocation for unbounded virtual objects that end inside a compiled function (e.g. check(make(d)) in a compiled caller); the binary-trees benchmark criterion is dropped.
Merge pull request #298 from thisisthepy/feat/tp-region
b-re-w commentedon Oct 25, 2026
Landed in develop via the PR from feat/tp-region.