On Thursday, 12 November 2015 at 23:06:01 UTC, rsw0x wrote:
On Thursday, 12 November 2015 at 22:50:08 UTC, Walter Bright
wrote:
On 11/11/2015 9:19 AM, David Nadlinger wrote:
Of course, many of the problems could have probably been
avoided if there was an
iron-clad rule that the module dependency graph must remain
acyclic from the
beginning of development (at least at the level of units of
compilation).
In hindsight, I would have made D enforce that (Go does).
Would there be any gain from adding an optional compiler
warning for it?
It can be implemented as an external tool with the -deps compiler
switch.
