It’s interesting how the designs of C++ and Rust reflect what the worst memory problems were at the time they were created. C++ was created when memory leaks were on everyone’s mind. Rust was created when use-after-free was becoming the biggest issue.
-
-
Replying to @pcwalton
Makes me wonder whether a new language now might also consider Spectre and friends. Seems a hard problem but then so does memory safety if you start from C/C++.
1 reply 1 retweet 8 likes -
Replying to @BRIAN_____ @pcwalton
Makes sense for a browser running potentially malicious code in a VM but is only part of it. There are also attacks against kernels or other processes (or NetSpectre). A language which can safely put speculation barriers where needed might help. But I'm speculating here too. :-)
0 replies 0 retweets 0 likes -
Replying to @BRIAN_____ @jugglerchris
Something semi-language-level that might help in Rust would be to make spawning a process as easy as spawning a thread. This was actually a goal of Rust from *very* early on, and it was one of the goals I had in mind with ipc-channel.
2 replies 0 retweets 10 likes -
Goal: You should be able to take a multithreaded app and make it a multiprocess app as painlessly as possible. Rayon lets you take a single-threaded app and make it a multithreaded app; let’s do the same for processes.
1 reply 1 retweet 14 likes
Well, we don’t use Send for that. ipc-channel uses Serialize/Deserialize, which are opt-in.
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.