[Daniel]
> Therefore, we need to answer this question within the constraints of
> rendering things into input files and command line arguments.

I don't know if I answered that question earlier; if I did then my apologies for the repeat.

MSVC uses header-units.json: https://docs.microsoft.com/en-us/cpp/build/reference/header-unit-json-reference?view=msvc-170

-- Gaby

-----Original Message-----
From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Daniel Ruoso via SG15
Sent: Monday, June 6, 2022 6:42 AM
To: Boris Kolpackov <boris_at_[hidden]>
Cc: Daniel Ruoso <daniel_at_[hidden]>; Daniel Ruoso via SG15 <sg15_at_[hidden]>
Subject: Re: [SG15] "logical name" of importable headers

Em seg., 6 de jun. de 2022 ās 07:08, Boris Kolpackov
<boris_at_[hidden]> escreveu:
> With the module mapper approach (at least as implemented in
> GCC/libcody), for each header include the compiler asks the
> build system whether to translate it to an import.

While the dynamic module mapper approach works in some cases, it is
not an universal solution. It is incompatible, for instance, with the
Remote Execution protocol, which requires all inputs to the compiler
to be rendered as static files. Large scale C++ usage is increasingly
dependent on the Remote Execution protocol, therefore this is not
something that we can ignore.

Therefore, we need to answer this question within the constraints of
rendering things into input files and command line arguments.

daniel
_______________________________________________
SG15 mailing list
SG15_at_[hidden]
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fsg15&amp;data=05%7C01%7Cgdr%40microsoft.com%7C74a4c39f33854ee95f3f08da47c257a1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637901197272142138%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=%2FHPBL56jDEM5qtI9aSoQy%2FsurWy3QFElWwRO%2FwqG3GY%3D&amp;reserved=0