https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40380
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> --- Grr, I've just noticed that classes defined in a header with no file extension do not get an implicit @headerfile, the way that classes defined in a foo.h header do. See https://github.com/doxygen/doxygen/issues/10010 This is frustrating for libstdc++, because **none** of the public headers have an extension, so we can't rely on all the contents of e.g. <memory_resource> getting a correct #include <memory_resource> displayed. The _only_ classes which show a #include are the ones in a .h file where it's always wrong (until we add an explicit @headerfile to them). So unless that doxygen issue gets fixed, we need an explicit @headerfile on every single class in the library. Sigh.
