On Wed, Jul 10, 2019 at 2:39 PM Bryce Adelstein Lelbach aka wash <
brycelelbach_at_[hidden]> wrote:

> On Wed, Jul 10, 2019 at 12:09 PM Ville Voutilainen
> <ville.voutilainen_at_[hidden]> wrote:
> >
> > On Wed, 10 Jul 2019 at 22:06, Tom Honermann <tom_at_[hidden]> wrote:
> >
> > > You are implying that the include translation is mandatory. Is that
> your argument?
> > >
> > > Yes. The wording in [cpp.include]p7 seems fairly clear regarding that.
> >
> > Not at all. "If the header identified by the header-name denotes an
> > importable header" is implementation-defined. The set
> > of importable headers is allowed to be whatever the implementation
> > decides, including an empty set.
>
> Not exactly.
>
> http://eel.is/c++draft/module.import#5 says "A
> module-import-declaration that specifies a header-name H imports a
> synthesized header unit ..." and later "H shall identify an importable
> header."
>
> So H must be a part of that set of importable headers. Yes?
>

Yes, and thus the program is ill-formed if H is not part of that set.

- Michael Spencer


> --
> Bryce Adelstein Lelbach aka wash
> CUDA Core C++ Libraries Lead @ NVIDIA
> ISO C++ Library Evolution Incubator Chair
> ISO C++ Tooling Chair
> CppCon and C++Now Program Chair
> CUDA Convert and Reformed AVX Junkie
>
> Sleep is for the weak
> --
> _______________________________________________
> Modules mailing list
> Modules_at_[hidden]
> Subscription: http://lists.isocpp.org/mailman/listinfo.cgi/modules
> Link to this post: http://lists.isocpp.org/modules/2019/07/0502.php
>