C’s Biggest Mistake (2009)

Re:C’s Biggest Mistake (2009) by IshKebab on Sunday September 13, 2020 @04:42AM (#24459403)

Oh... can you show me those 100+ other languages that have opt-out memory safety, explicit lifetime annotation, a borrow checker and no runtime?

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by pjmlp on Sunday September 13, 2020 @08:06AM (#24460281)

Cyclone, ATS, Checked C, Ada/SPARK.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by 59nadir on Monday September 14, 2020 @03:12AM (#24467643)

Footnote: With Ada/SPARK being much more battle-tested and ATS being a much more flexible & complete solution. Though I wouldn't exactly recommend ATS in terms of learning curve.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by saagarjha on Sunday September 13, 2020 @05:52AM (#24459699)

That’s an extremely specific reading of the claim “fix C” that excludes almost everything but Rust.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by IshKebab on Monday September 14, 2020 @07:47AM (#24469032)

I never said those are the only ways to fix C. Try reading the argument again:

> What Rust hast brought to the tables was nearly the same what was brought by 100+ other programming languages in attempts to "fix C."

> Oh... can you show me those 100+ other languages that have opt-out memory safety, explicit lifetime annotation, a borrow checker and no runtime?

Maybe I can make it even clearer:

> What Rust has brought to the tables was nearly the same as 100+ other languages

> Oh... can you show me those 100+ other languages that have (some unique Rust features)

[ Parent | on HN ]