I don't currently do any Rust programming, but thread FWIW: https://twitter.com/mik235/status/1129246179835883520 … (async/await is a mistake)
If I were writing a GC’d language designed for I/O, I’d be very tempted to use Go-like stack growth but use 1:1 threading unlike Go.
-
-
I’d like Erlang’s model where every process has its own heap that is independently GC’d, and messaging other processes makes copies, but also supporting mutability and shared mutability. Wait isn’t that the modern JavaScript memory model?

-
so here's a wild idea i have: what if a heap collected itself? instead of having a GC separate from a runtime, what if the compiler inserted tracing code, something like: on each backedge with 1/n probability do a very small portion of the cycle
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.