Tell me again how C isn't a problem
Quote Tweet
Microsoft: 70 percent of all security bugs are memory safety issues
zdnet.com/article/micros
Show this thread
31
364
1,120
Conversation
"No way to prevent this", say programmers of only language where this regularly happens
22
441
1,529
No limit on the kind of data structures you can write in Rust. You may have to write a small amount of unsafe code.
1
6
Or accept using reference counting and dynamic mutability checks. Thread local reference counting is quite cheap, especially with default move semantics rather than implicitly adding new owners. People greatly exaggerate how often Rc/Weak and RefCell aren't a viable option.
It's true that they can add a bit of overhead that wouldn't be there in some cases if you were managing the owning and non-owning references by hand and it can be fairly verbose, but it's a viable option. Rc<T> is quite lightweight, nothing like the heavyweight C++ shared_ptr.
1
Or measure your latency and resource tolerance and use a GC'ed language when possible.
2
This Tweet was deleted by the Tweet author. Learn more
I don't understand what your reply has to do with my tweet. It applies to other architectures. The implication that I have an x86 centric perspective is quite wrong considering that I work full time with AArch64 targets. I only deal with x86_64 as a secondary thing or not at all.