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.
-
-
In other words, you need a solution for Dan Grossman’s “Existential Types for Imperative Languages” problem. The nice thing about borrow checking is that it deals with both this problem and UAF (which ends up just being a subset of this issue).
Show this threadThanks. 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.