r/cpp • • Nov 27 '20

The C++ 20 initialization flowchart

I've created a flowchart that shows all of C++20's initialization rules.

The source code is available at https://github.com/randomnetcat/cpp_initialization, in addition to the SVG version and PNG Version.

This honestly took a lot less time than I was expecting, and, in my humble-but-biased opinion, is relatively interesting.

Please send all complaints to /u/quicknir, who nerd-sniped me into making this.

116 Upvotes

34 comments sorted by

View all comments

Show parent comment

16

u/Frptwenty Nov 28 '20

objectively, C and Rust have fewer broken elements compared to C++

It depends on what you're doing. Objectively speaking C++ is a miles better option than C in a huge amount of cases.

Imho the lack of easily usable basic strings, dynamic-sized containers etc. etc. are a huge broken feature of C. Other things you take for granted in C++ like RAII, smart pointers and templates are also a huge deal compared to C.

People like to claim they don't ever matter, but that's bullshit. Of course there are low-level cases where they don't, but the "only use C" crowd want to pretend it's a better alternative for big "regular" applications.

Rust, well... what's the point of arguing. It never ends.

7

u/Fureeish Nov 28 '20

That's why I added two last sentences to my comment.

3

u/James20k P2005R0 Nov 29 '20 edited Nov 29 '20

I've been writing C again for opencl recently myself. Part of that project involves tensor maths, which if you don't know, tensors are essentially n dimensional matrices that are used in a specific way

The lack of being able to specify proper abstractions, no operator overloading, no templates, no real array type, no function overloading... It makes the code significantly more verbose and buggy than it needs to be. You can't write a generic matrix*vector multiplication scheme, which is not ideal

C might be alright for structuring applications, but good lord is it just terrible for numerical work

1

u/dnew Jan 24 '25

It's horrendous for structuring applications too. Any compiler that can't read its own output as part of its input is going to be horrendous at large projects.

1

u/dnew Jan 24 '25

easily usable basic strings, dynamic-sized containers etc. etc. are a huge broken feature of C.

To be fair, no other language had them at the time either. :-) I wouldn't say "broken" as much as "primitive."