Re:A 30-minute Introduction to Rust
by Scramblejams on Tuesday July 01, 2014 @04:12PM
(#7973214)
I get the feeling most of these commenters who think the words "modern C++" indicate some kind of near insulation from writing security bugs are, in fact, writing security bugs.
They probably think they aren't, but by definition, we are not smart enough to immediately understand the bugs we write. Otherwise we wouldn't write them.
But hey, it's not like a programmer who overestimates his own skills is a new thing.
Re:A 30-minute Introduction to Rust
by Donwangugi on Tuesday July 01, 2014 @03:36PM
(#7972999)
What kind of issues do you see still with modern C++11 code?
All kinds of memory safety issues. Heap use-after-free is very common. You can go to Bugzilla and search for sec-critical to get a list of the ones Mozilla has disclosed.
> concepts
What are concepts in this context? It is hard to google.
Re:A 30-minute Introduction to Rust
by steveklabnik on Tuesday July 01, 2014 @07:59PM
(#7974271)
Is this something that can be used in Rust? Or is it a feature that will be implemented later?
Re:A 30-minute Introduction to Rust
by steveklabnik on Tuesday July 01, 2014 @08:38PM
(#7974421)
I am not familiar enough with the details. We don't have an _exact_ analogue, though our Traits are similar-ish.
I've pinged #rust, I'll see if I can get someone who knows more to answer here.
I can't speak to everyone's use case, but for ours memory safety is extremely important. C++ is not safe, and we still see tons of memory safety issues, many security-sensitive, in practice, despite using modern C++ for all new code.
Even if safety isn't as important to you, there are other reasons you might be interested in Rust: a module system, pattern matching, a standard library which offers better performance than STL for many tasks, ADTs, concepts, a package manager, etc.