> the compiler can now allocate the backing store for slices on the stack in more situations
Any details on when this happens?
721 karma · joined January 22, 2015
Any details on when this happens?
And safety.
I'm not and I'm glad the core team doesn't have to maintain an http server and can spend time on the low level features I chose Rust for.
In Jai/Odin, every scope has default global and temp allocators, there's nothing stopping you from transferring ownership and/or passing pointers down the callstack. Then you either free in the last scope where the pointer lives or you pick a natural lifetime near the top of the callstack, defer clear temp there, and forget about it.
Very interesting observation, I think you might be right.