On 23/05/2023 17.54, Daniel Ruoso via SG15 wrote:
> And that so far
> all early experiences rely on the user not selecting the wrong header
> to be importable

The set of importable headers that an implementation supports is
implementation-defined, not (primarily) user-defined.

One valid implementation strategy would be to offer only the
standard library headers as importable headers.

In any case, I would really appreciate a very specific,
concrete example (exemplary source code) of the troubles
you seem to be talking about. If three two-line files
suffice to show the principles, that's good enough.
I have the gut feeling there is an assumption hidden somewhere
in your arguments that might not be universally shared.

Jens