News for hackers. Stuff that matters.

A comment on Ask HN: What is preventing rust from replacing c/c++?. Parent comment

Re:Ask HN: What is preventing rust from replacing c/c++? by AstralStorm on Tuesday July 18, 2017 @02:02AM (#14794499)
More modern styles of C++ just wholesale avoid most problems that are solved by the borrow checker. Smart and owning pointers, dynamic and checked data structures thanks to operator overloading. There are remaining warts but not bad enough in practice.
[ Parent | on HN ]
Re:Ask HN: What is preventing rust from replacing c/c++? by jjpe on Tuesday July 18, 2017 @05:39AM (#14795330)
That's not really all that relevant for most existing commercial code since legacy code tends to not get rewritten at all unless it's absolutely necessary, and thus remains stuck with the Old Ways.
[ Parent | on HN ]
Re:Ask HN: What is preventing rust from replacing c/c++? by AstralStorm on Tuesday July 18, 2017 @12:46PM (#14798001)
Indeed, but unlike a rewrite, you can refactor staying in the same language at your leisure, piece-wise.

Plus the argument was mostly pertaining to new code.

[ Parent | on HN ]