Ask HN: What is the state of C++ vs. Rust?

Re:Ask HN: What is the state of C++ vs. Rust? by throwsincenotpc on Wednesday October 19, 2016 @01:34PM (#12745812)

> But then there is the idea of ignoring legacy C++ and treating Modern C++ as a new language altogether.

There is no "ignoring legacy C++", when you will have to deal with this or that library written 10/15 years ago. C++ is a language where you can't just ignore some parts of it just because they are inconvenient.

As for C++ vs Rust, Rust is memory safe, C++ is not and will never be despite all the bells and whistles it gets.

[ Parent | on HN ]

Re:Ask HN: What is the state of C++ vs. Rust? by ar15saveslives on Thursday October 20, 2016 @01:38PM (#12754379)

What is "memory safe" for you? If you use C arrays and raw pointers in your C++17 code, it's definitely not memory safe, but the main problem is that it's not modern C++.

[ Parent | on HN ]

Re:Ask HN: What is the state of C++ vs. Rust? by steveklabnik on Thursday October 20, 2016 @05:04PM (#12756154)

Even modern C++ isn't memory safe. Most straightforward example is to move a uniq_ptr, which makes it a nullptr, ready to be dereferenced and cause UB.

[ Parent | on HN ]

Re:Ask HN: What is the state of C++ vs. Rust? by ar15saveslives on Thursday October 20, 2016 @10:07PM (#12757697)

How does it happen? Non-const unique_ptr& used as a function parameter?

[ Parent | on HN ]

Re:Ask HN: What is the state of C++ vs. Rust? by steveklabnik on Friday October 21, 2016 @03:42AM (#12758824)

http://www.steveklabnik.com/uniq_ptr_problem/

[ Parent | on HN ]

Re:Ask HN: What is the state of C++ vs. Rust? by ar15saveslives on Friday October 21, 2016 @09:13AM (#12760095)

I can simplify your example:

  unique_ptr<int> p;
  auto n = *p; // C++ kills!

[ Parent | on HN ]