It's hard to appreciate how good Rustls is at avoiding UaF since UaF avoidance is taken for granted in idiomatic Rust code. Tiny things like `#[must_use]` are small but help avoid big failures. Our friends doing concurrency & malloc/free in C are still struggling w/ the basics.
:) I agree that it does seem trivial. Of course that's basically what browsers do but it doesn't work.
-
-
It "doesn't work" because of some fundamental shortcoming, or it "doesn't work" because they keep making shortcut hacks around it to make it perform better^H^H^H^H^H^H^H^H^H^H^H^H^H^Hso sites can be 10x as bloated at the same performance.
-
Intuitively, Rust's borrow-checker-based access management for objects isn't going to compose well with a system like JS GC that is completely unaware of it. So in your Rust code and C++ code you think you have the one and only (mutable) pointer to an obj but then you trigger JS.
End of conversation
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.