Aliasing specialized template stuct in his module leads troubles

[Mike Parker]

On 9/5/2012 10:50 AM, Mike Parker wrote:

>
>
> compiler says, ok, this is no problem. It goes about its job and creates
> baz.obj and passes it off to the linker. The linker looks through
> baz.obj, finds a reference to foobar, which, given the name mangling
> (_D3foo6foobarS3foo3Bar), should exist in an object file called foo (the
> linker knows nothing about D modules). So the linker wants to take
> foo.obj and link it together with bar.obj to create the final
> executable. Only, there is no foo.obj because you didn't compile it.

And, I should probably say, this isn't actually accurate. The linker 
knows nothing about D name mangling either. But the point is, if a 
symbol the linker needs isn't available in any of the object files you 
pass to it, it will complain.