It’s really easy to criticize Rust for being too “strict”. It’s a lot harder to say what specific changes you’d make to make it less strict during development, while still allowing safety during deployment.
Lots of examples of this in the literature, going back to Tofte and Talpin’s ML Kit. That’s classic region memory management. Didn’t catch on, but interesting.
-
-
I just feel like I've seen so many Ruby/Python/etc web services that just do the equivalent of `GC.disable` for every HTTP request; maybe it's time for that stuff to come back. Of course, with Rust and parameterized Alloc, I guess it could be done...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.