2 ms·
Exactly. I actually think default parameters are hazardous without named-parameter support. When they added one, IMO they should have added the other as well,
by CamperBob2 2y ago
Exactly. I actually think default parameters are hazardous without named-parameter support. When they added one, IMO they should have added the other as well, so that you can specify exactly which non-default parameters you're passing.
- kevin_thibedeau 2y agoI think this is more an appeasement of the C++ committee because they don't like the order of evaluation to be ambiguous when constructors with side effects come into play. Witness how they completely gimped the primary utility of designated initializers with the requirement to have the fields in order.
- deleted 2y ago[deleted]