On Wed, May 24, 2023, 00:40 Corentin Jabot via SG15 <sg15_at_[hidden]>
wrote:

> Maybe having only include rewrite of a list of importable headers (which
> you could elect to keep empty) offers a more generally applicable migration
> path, than addition exposing an import grammar to users ( for importable
> headers)
>

That is my current opinion. If this optimization is useful in limited
situations we need a specification that allows that optimization to happen
in the limited cases where it can work.

The current specification forces the support of those semantics in places
where it has no hope of working sensibly.

My suggestion is that we walk back the current spec, and go back to design
something that allows the optimization in a well defined way.

Daniel