3 ms·
There's a lot of redundancy and things you probably should never use in C++, though. It's not complexity that needs to exist other than for backwards compatibi
by Dylan16807 2y ago
There's a lot of redundancy and things you probably should never use in C++, though. It's not complexity that needs to exist other than for backwards compatibility.
> Re generics, aren't C++'s virtually the same as Rust's? Especially now that C++ has 'concepts'?
I'm not worried about generics when I talk about template nightmares, that's more about rvalue and const overloads and vararg templates and careful manipulation of SFINAE, all coming together.
- consteval 2y ago> There's a lot of redundancy and things you probably should never use in C++, though This is just a symptom of its age. C# has this same problem, too, and it's only getting worse.
- neonsunset 2y agoC# does have C++-esque issues but the scale at which they affect the language is not comparable. There are really no popular patterns that have become "no, never do that", poorly written code is sort of version agnostic, and even old code, particularly one like in Mono applications from back in the day, plays really nicely with modern runtimes. And the difference in ways to achieve something is almost always of type "remember this required to take 4 steps? now it's one shorthand thing that makes sense in retrospect".
- lenkite 2y agoYou don't have any template nightmares after C++ 20 concepts. The error messages improved so much that I thought I was using a different programming language.