[Matthew]

| I really, really hope we can get some kind of caching for this...
| because while it's true that we can't *rely* on everyone using the same
| compiler, *in practice* I will almost certainly have multiple projects
| that all consume some set of libraries with the same compiler, which
| means they could share BMI's. There's a fair chance even (depending on
| the extent to which e.g. optimization levels affect BMI's) that I'm
| building my own stuff with the same compiler that was used to build the
| library originally, and that I *could* use BMI's generated by the
| library build.
|
| IOW, while we can't *rely* on shipping BMI's, it may still be *useful*
| to do so.

Fully agreed.

| > * Reason 47 to have a deterministic mapping from module name to
| Module
| > Interface Units identifier.
|
| I'm not entirely convinced we need that. Libraries could also ship a
| (build-generated) mapping file that tells consumers how to find the
| appropriate files for a given module name.

Yup.

I want to encourage all us to be imaginative about how we support C++ Modules in the varied environments that C++ is used.

-- Gaby