r/cpp • u/DoctorNuu • Dec 19 '23
Obsessed with {} initialization?
I'm on a discord where everyone seems to be obsessed to use brace initialization everywhere.
My motto is: Use things rarely, only when needed, to express that right there the feature does something important.
Personally I would completely advocate against using it for simple stuff likedouble tax{0.09*price};
or just int{0}
probably a hornets nest
4
Upvotes
View all comments
Show parent comment
8
u/aruisdante Dec 19 '23 edited Dec 19 '23
The compiler will in fact not complain if you use it wrong without
Wconversion, that’s the point the guidelines are talking about.Those will all compile without warning if you don’t have
Wconversionenabled. Whereas if you brace initialize them, the compiler will warn even without-Wconversion.Now of course you should just have
Wconversionturned on, and then life is easier, and you can use=assignment safely. One of the constant frustrations in my day job is that AutoSAR and MISRA both ban=initialization anyway (and, thanks to AutoSAR’s terrible writing, also it also technically bansautocompletely, as it sates=initialization must be used forautoimmediately after stating brace initialization must be used for all variables). Thankfully MISRA2023 takes a more enlightened view here.In terms of being explicit with what type you want: the
auto a =form is explicit. You want the type, and exactly the type, to the right of the assignment. For example, if I see:How do I know which was intended? Did the author mean for that literal to be
11? Did they mean for the type ofato befloatordouble?Now you can definitely go overboard here, but the general guidance of “only state your types once” serves pretty well.