<div dir="ltr"><div>I'm not 100% sure that's what you are asking but: </div><div><br></div><div>When a source file is modified (including fresh builds), the build system has to assume the dependency graph may have been modified and has to rescan the dependencies for that particular file.<br></div><div>In the absence of modifications, the build system does not have to rescan anything.<br><br><div class="gmail_quote"><div dir="ltr">On Sat, 12 Jan 2019 at 00:08 Bjarne Stroustrup <<a href="mailto:bjarne@stroustrup.com">bjarne@stroustrup.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On 1/11/2019 6:04 PM, Corentin wrote:<br>
><br>
> Build systems will always need to parse every file at least once <br>
> before invoking the build.<br>
<br>
<br>
"always" meaning "forever"? I would hope/expect that module <br>
representations could (eventually) deliver sufficient data (metadata?) <br>
to safe that step.<br>
<br>
<br>
> They can hopefully extract both the name and the dependency in a <br>
> single pass.<br>
_______________________________________________<br>
Tooling mailing list<br>
<a href="mailto:Tooling@isocpp.open-std.org" target="_blank">Tooling@isocpp.open-std.org</a><br>
<a href="http://www.open-std.org/mailman/listinfo/tooling" rel="noreferrer" target="_blank">http://www.open-std.org/mailman/listinfo/tooling</a><br>
</blockquote></div></div></div>