The form -fmodule-file=<path-to-BMI> will load modules eagerly and the form -fmodule-file=<module-name>=<path-to-BMI> will load modules lazily. The inconsistency adds many additional burdens to the implementations. And the inconsistency looks not helpful and necessary neither. So I want to deprecate the form -fmodule-file=<path-to-BMI> for named modules. This is pretty helpful for us (the developers).
Does this change make any regression from the perspective of the users?
To be honest, yes. But I think such regression is acceptable. Here is the example:
// M.cppm export module M; export int m = 5; // N.cpp // import M; // woops, we forgot to import M. int n = m;
In the original version, the compiler can diagnose the users to import M since the compiler have already imported M. But in the later style, the compiler can only say "unknown identifier m".
But I think such regression doesn't make a deal since it only works if the user put -fmodule-file=M.pcm in the command line. But how can the user put -fmodule-file=M.pcm in the command line without import M;? Especially currently such options are generated by build systems. And the build systems will only generate the command line from the source file.
So I think this change is pretty pretty helpful for developers and almost innocent for users and we should accept this one.
I'll add the release notes and edit the document after we land this.