http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49174
--- Comment #3 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-05-26 18:52:55 UTC --- In my experience as implementer, the equivalence between struct and class often makes for conciseness, like in this case: we know everything will be public anyway, thus we can spare the access-specifier. In the specific case of limits we are also consistent, we use 'struct' both for the primary and the specializations, thus there is *really* nothing to possibly warn about.
