This is nitpicking style, there are no real safety implications. Compilers will happily inform you if the parse is ambiguous or code is unreachable.
if(x % 2)
vec^.push_back(x);
do_something_else();
under the mistaken assumption that the second line will also only run in the x % 2 case. People make mistakes, this particular one can happen, does happen, and has happened many times, and the compiler absolutely will not inform or warn you, because it doesn't know you intended the second line to run in the same if statement as the first (because C++ isn't whitespace sensitive). Is ruling out an entire class of bug really not worth the effort of just typing two more characters?False.
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#inde...
https://clang.llvm.org/docs/DiagnosticsReference.html#wmisle...