News for hackers. Stuff that matters.
Re:Inside cpyext: Why emulating CPython C API is so Hard by wahern on Friday September 21, 2018 @02:43PM (#18041763)
I think the central issue is that PyPy uses a copying GC, which means pointers to objects aren't stable by default. The article implies that this is a consequence of having a generational GC, but you can have a non-copying generational GC, which Lua 5.2 and 5.4 actually have.[1]

[1] Lua 5.3 dropped the generational GC because real-world results didn't justify the complexity, but apparently for 5.4 they came up with a better design.

Re:Inside cpyext: Why emulating CPython C API is so Hard by quotemstr on Friday September 21, 2018 @06:49PM (#18043257)
Object stability precludes bump-pointer allocation of short-lived temporaries though, and in a very allocation-y language like Python, that's a pretty important.
Re:Inside cpyext: Why emulating CPython C API is so Hard by weberc2 on Friday September 21, 2018 @10:10PM (#18044085)
I wonder if escape analysis could compensate as it does with Go.