[Development] QProperty and library coding guide

[Ville Voutilainen]

On Sun, 19 Jul 2020 at 15:25, Oswald Buddenhagen
<oswald.buddenhagen at gmx.de> wrote:
> (side effects of) actual optimizations are by definition not intentional
> belligerence. (one would, however, expect that entire chunks of code
> being thrown away would result in a warning that informs about
> specifically that (and not just the underlying warning, which may or may
> not be enabled).)

One could hope so, but expecting that would be foolish. Current
optimizers seem to
consider warnings to be a job of the front-end, but if the
optimizations are value-based
rather than symbolic, the front-end can't warn, and then the optimizer
won't, and
dead code that was considered dead because it has UB will just be axed
without warning.