On Thursday, 17 October 2013 at 16:35:48 UTC, Dicebot wrote:
On Thursday, 17 October 2013 at 16:31:21 UTC, Iain Buclaw wrote:
1. gdc looks for both .d and .di files in the include paths,
so that
is not the problem...
Isn't this done in front-end? If .di file is found, *.d won't
be searched.
DMD does it this way, according to
http://dlang.org/dmd-linux.html#interface_files
"D interface files can be created by the compiler from a D source
file by using the -H switch to the compiler. D interface files
have the .di file extension. When the compiler resolves an import
declaration, it first looks for a .di D interface file, then it
looks for a D source file."
That way the compilation would still get stuck, wouldn't it?
