search for: adjonct

...e assert is reached since it is not reached in all code path, after all how can the compiler know that the good code path is when argc>=2 and not the contrary ? Clearly this functionnality is interesting, but there is lot of work to do on the semantic to make it useful, and potentially need the adjonction of additionnal user information like: error_code_path or always_reached. Regards, Cédric

Cédric Venet wrote: >> Technically, yes, but we can reword future standards to have the >> latitude to give compilation errors for conditions that can be proved >> to be false, then the implementation is conforming. We could always >> have a flag to control the behavior if people want/need it, though, I >> can't hardly see why they'd want it to

> Technically, yes, but we can reword future standards to have the > latitude to give compilation errors for conditions that can be proved > to be false, then the implementation is conforming. We could always > have a flag to control the behavior if people want/need it, though, I > can't hardly see why they'd want it to compile if they assert > something that