News for hackers. Stuff that matters.
Re:A Guide to Porting C/C++ to Rust by pjmlp on Sunday January 29, 2017 @11:53AM (#13514996)
It only works if the whole company buys into it, including only linking against libraries whose authors also adopt those practices.

What I have learned since learning it in 1993, using it including teaching the language to first year students, is that any safety feature that isn't imposed by the language instead outsourced to best practices or external tools tends to be ignored by the majority.

Re:A Guide to Porting C/C++ to Rust by maxxxxx on Sunday January 29, 2017 @01:44PM (#13515812)
What you are saying is probably true but it's also sad. That's why we end up with languages without preprocessor or multiple inheritance because some people misuse these extremely useful features.
Re:A Guide to Porting C/C++ to Rust by iopq on Monday January 30, 2017 @08:17AM (#13520851)
You don't need a preprocessor. Lisp-style macros are much easier to use due to hygiene and in general not being text-based.
Re:A Guide to Porting C/C++ to Rust by jeffdavis on Sunday January 29, 2017 @01:47PM (#13515829)
Also, if you need to change all of your APIs to work with unique pointers, then it's effectively a rewrite anyway.