4 ms·

It's a header-only library, it would effectively add "using" statements anything that included the library.

• haolez 7y ago
  Ouch. Seems like an unsolvable limitation at this point. Nice catch.
  • colejohnson66 7y ago
    C++20 introduces “modules” which are an attempt at alleviating the problem of headers. Support, though, is lacking in major compilers’ master branch. GCC supports it if you build a certain branch from source though.
    • LessDmesg 7y ago
      Some really prompt bugfixing on C++ committee's part. "We have a broken compilation process that leads to humongous build times and namespace pollution! Oh, OK, let's wait another 20 years to fix it". I guess C++ coders deserve the std::'s their language gives them.
• Reelin 7y ago
  It's actually possible to avoid this! namespace foo::_bar { using namespace ::acme::widgets; /* internal helpers go here */ inline namespace exports { /* public API goes here */ } } namespace foo::bar { using namespace _bar::exports; }