> That's insufficient: to be usable, it must also say that it is
> *the same* for all resource strings, regardless of which facility
> (std::embed, etc) they are used in.

Resource lookup will be exactly what is written in this paper, so long as I
can get consensus and move this through the Committee. As the author of
std::embed, I have the privilege of moving these papers in sync. Should
p1130 be accepted, std::embed will be updated to specifically call out
Resource Lookup, as defined in [module.requires] (or whatever it ends up
being).