https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66472
--- Comment #2 from Gael Guennebaud <gael.guennebaud at gmail dot com> --- But with the same reasoning you would end up reintroducing shadow warnings between local variables and *any* functions, not only the ones visible from a using statement. It has been recognized that triggering a warning in such a case was too much: - gcc 4.8 removed them for free functions - gcc 5.0 removed them for member functions and I think that it thus make sense to remove them for member functions visible through "using". Did I miss something special regarding the use of "using"?
