https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105397
--- Comment #2 from Ben Boeckel <bugzilla.gcc at me dot benboeckel.net> --- > Perhaps the best option is to default the visibility of the implicit > functions to the widest visibility of any function or object in module > purview exposed by the TU. What to do about `extern "C"` APIs made available by a module? Is that even allowed? Imagine a library providing some C API by implementing in C++ modules; should the module initializer be public API too?
