News for hackers. Stuff that matters.
Re:Why Go and Not Rust? by patrec on Monday September 16, 2019 @11:32AM (#20985066)
Sure, but memory safety is irrelevant when considering C++ as a C replacement (C++'s memory safety, terrible as it is, is not worse than C's). I'm purely curious as to why you'd be able to write something in either a) C b) Rust but not c) C++.
Re:Why Go and Not Rust? by ummonk on Monday September 16, 2019 @01:36PM (#20986564)
You are reading that backwards. The comment said that Rust is better positioned as a C replacement than it is as a C++ replacement. It said nothing about C being able to do things C++ can’t.
Re:Why Go and Not Rust? by patrec on Monday September 16, 2019 @02:06PM (#20986890)
I think that's true. Also given the dominance of C in the unix eco system, it's a more important problem to solve.
Re:Why Go and Not Rust? by saghm on Monday September 16, 2019 @02:25PM (#20987070)
> Sure, but memory safety is irrelevant when considering C++ as a C replacement (C++'s memory safety, terrible as it is, is not worse than C's).

Wouldn't it be fair to say that reducing memory unsafety as much as possible without hurting performance is a good goal to have when making a replacement for C? Assuming that's the case, it's relevant that C++ doesn't eliminate it as much as Rust when comparing the two languages as C replacements.