Currently the emitted dependencies are incorrect for templates:
Dependencies are emitted for the module that references the dependency, even if this reference is within a template. This is incorrect, as only the code instantiating the template really depends on the template dependencies, there is no need to rebuild a module, if an import within a template changes.
Consider this simplified example, which makes the issue most clear:
```D
// module a
void templateFunc(string myImport)() {
mixin(myImport);
// ....
}
// module b:
void main() {
templateFunc("import std.string;")();
}
```
It seems a bit artificial, but in fact it is not (consider Diet templates for example). In this example the dependencies for module "a" change, depending on what code it uses.
The effect is not severe, it will just make build tools less efficient, because modules need to be compiled needlessly, it should nevertheless be fixed.
I have a patch in the works already.
Comment #1 by jfanatiker — 2013-09-12T13:43:49Z
Also some linking errors, concerning incremental building seem to be related to this issue. (Templates are emitted into the wrong .o file)