[cfe-dev] Intros, C++ modules, and Facebook

[Vassil Vassilev via cfe-dev]

On 23/10/15 19:28, Louis Brandy via cfe-dev wrote:
> Second, I’m interested in the workflow of actually incrementally adding
> module maps to a large codebase. I do understand the need to start at the
> bottom but I’m worried about proper coverage, and then prioritizing what
> to do next. In particular, I find myself really wanting a “summary” of
> what #includes did and did not magically become imports so I can use that
> to make sure 1) I’ve not missed anything “below” and 2) to prioritize what
> to do next (by e.g. aggregating over a build the most textually included
> headers). I don’t think such a diagnostic/remark exists? I’ve not looked
> too deeply, yet, at clang-modularize, so perhaps my answers lie over
> there?
AFAIK "clang ... -fmodules ... -E" will tell you which #include was 
turned implicitly into an import. From there on, grep could do what you 
need ;)

Vassil