https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124888
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think we have various similar cases in the FE, e.g. __builtin_source_location
requiring std::source_location::__impl, various initializer list cases looking
up std::initializer_list, spaceship lookups of <compare> stuff,
__cxa_bad_cast/__cxa_bad_typeid/__cxa_bad_array_new_length looking up
std::{bad_cast,bad_typeid,bad_array_new_length} during constant evaluation,
coroutine handling during various lookups, and of course reflection all the
time.
Which of these is also a problem with modules (if somebody exports just some
function using those and not the std stuff being looked up) and which happen to
work fine is something that needs to be tested...
