@BRIAN_____ unique_ptr and shared_ptr are still really unsafe. I don't think the problems with it are fixable in C++ either.
-
-
-
@pcwalton AFAICT it would remove use-after-free (no more delete) at least in single-threaded code. Seems like a huge win but more is needed. - 1 more reply
New conversation -
-
-
@BRIAN_____@brendaneich I'd be interested, but I don't think you can make it safe & usable without lifetimes and lifetime polymorphism. -
@pcwalton@BrendanEich Somebody must have already attempted "Approximate Rust pointers in a Subset of C++." Do you have any links to such? - 3 more replies
New conversation -
-
-
@RchrdWrdtDjvnbd I don't think the C++ spec can be fixed to become memory safe while having it remain C++.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RchrdWrdtDjvnbd What's the reason?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RchrdWrdtDjvnbd Or#rustlang (shameless plug) :)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RchrdWrdtDjvnbd Agreed, smart pointers help a lot.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@BRIAN_____@comex Also *T isn't usable outside of "unsafe" blocks. You can use "rustc -F unsafe" to forbid them.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@pcwalton Yes, but no language has proved it can be as fast as C++ on large scale - not Rust *yet*. (I’m a professional in my head!) -
.
@comex Important for PL researchers to not oversell their claims of security. Memory safety is not everything. But it's worthwhile IMHO.
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.