Re:Scipio: A Thread-per-Core Crate for Rust and Linux
by bxk1 on Tuesday November 03, 2020 @10:57AM
(#24980763)
It's not that hard, it's just pointless. Async is more general, so the optimization would have to go into the opposite direction: everything starts as implicitly async and things that provably don't need to be can just be converted to regular synchronous stackful code as an optimization pass.
[ Parent
| on HN ]
Re:Scipio: A Thread-per-Core Crate for Rust and Linux
by gpderetta on Tuesday November 03, 2020 @11:08AM
(#24980872)
that's what many functional programming languages do (or did, I think it went a bit out of syle), but it is expensive and the interoperability story with C is not good.
edit: it also requires heap allocating activation frames in the most general case, which is slow.
Re:Scipio: A Thread-per-Core Crate for Rust and Linux
by Joker_vD on Tuesday November 03, 2020 @11:45AM
(#24981275)
After full CPS transformation, you absolutely can allocate the activation frames on the stack. Cf. CHICKEN Scheme that does precisely that, and more generally, uses the stack as the 0-generation. When the stack hits a certain depth, it longjmp's to the GC, copies whatever is alive to the heap and restarts the current continuation on the now-trimmed stack.