Typical C++, But Why? - Björn Fahller - Meeting C++ 2023

[@Carewolf]

We do have compiler warnings for implicit casts from bool to int.

[@martinlicht7132]

The example on Slide 15 just shows the dangers of the implicit conversions introduced in C and adopted in C++. While it allows for very "concise" writing, ths s nt vr rdbl jst lk lvng t vwls in wrtng. Modern compilers should introduce flags optional warning about such accidental conversions even if they are perfectly valid C/C++.

[@Carewolf]

We might need an explicit "implicit" marker then.

[@szaszm_]

-Wconversion

[@varshneydevansh]

noice

[@nyyakko]

@ 25:05 I'd argue even more, you **should** keep it very minimal. Restrain yourself and prefer to declare only the minimal set of functions that is needed to make your class actually do the job it is intended to do. Tony Eard actually has a pretty good talk on this which goes more in depth, its a talk about the somewhat controversial SOLID principles. kzbin.info/www/bejne/nZ28omCaq8yVr5Y

[@nyyakko]

anyways, very great talk! it was fun to watch.

[@elvircrn]

12:38 Isn't a much nicer solution to just use a struct with designated initializers - a poor man's keyword arguments?