https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63480

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I think it makes sense just not to warn on { }, much as we intentionally don't
warn for { 0 }.
I'm testing a patch.

Reply via email to