<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 8, 2019 at 2:35 PM Matthew Woehlke <<a href="mailto:mwoehlke.floss@gmail.com">mwoehlke.floss@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I could possibly quibble with whether that's "accurate", but I think<br>
it's moot. Either this comes from the build system, or the user provides<br>
it by hand (or something else?). In whichever case, I don't see why<br>
providing the information for module dependencies would be any more<br>
difficult than providing the comparable info for includes. IOW, we<br>
aren't making this any harder than today.<br><br></blockquote><div>I just want to make sure. This is true for _clang_ modules. Merged and TS modules introduces an indirection that makes finding module dependencies harder than just asking the compiler for includes. If the module does not exist yet, the compiler may be unable to answer that question. This leads to the module-mapper which provides the answer by magic. </div></div></div>