Cling/Nim-style UAF prevention by strict heap segmentation is neat, but it seems incomplete as a solution for memory safety without something to deal with type confusion caused by union misuse.
-
-
what if I only have existential angst for imperative languages
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.