I think this is related to a bug in some old gcc:
It should be ignored, like suggested at:
I do not plan to go for the non-standard {{0}}
variant just for this case, the initialization with {0}
is what C standard specify.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.