3
u/Sopel97 Jun 06 '18
half of it is needed, the other half is nomenclature
Then there is uniform initialization which didn't turn out as good as it was supposed to, but with good guildelines it's not a problem.
2
0
Jun 05 '18
[deleted]
11
u/JezusTheCarpenter Jun 06 '18
I would compare the modern C++ also to a box of chocolates. With size of 100 by 100 where you don't know what to choose.
3
u/m-in Jun 06 '18
I'd go with coding standards of people who mostly know what they're doing, e.g. google's. You don't need to take it all in, of course, those are tweakable rules - but they eliminate most questions. They have spent a lot of work making those coding standards work, and be comprehensive.
1
u/Wenste Nov 21 '18
I thought their coding standards are horribly outdated, but they're stuck with them because they have too much legacy code to change things now?
41
u/James20k P2005R0 Jun 06 '18
This is the main problem i found with the new decidedly not uniform initialisation syntax - it adds yet another way to initialise stuff that seems to only be appropriate in some situations with all sorts of little quirks to it that make it not universally applicable
As far as I can tell, its basically good for initialising container types like std::vector and map, and that's about it
I'm not a c++ expert by any stretch though so maybe i'm totally missing something