I recently added the new -Wjump-misses-init warning option. It warns when a goto or switch jumps into the scope of an initialized variable without actually initializing the variable. I added the warning to -Wall because it seems to me to fit the criteria of -Wall: a dubious code practice which is easy to avoid.
H.J. filed PR 40500 about this, arguing that this warning should not be in -Wall. Any opinions on this? Should I take the new warning out of -Wall? -Wjump-misses-init should of course continue to be turned on by -Wc++-compat, as such jumps are invalid C++. Ian
