Lib change leads to larger executables

[kris]

Walter Bright wrote:
> kris wrote:
> 
>> Walter Bright wrote:
>>
>>> kris wrote:
>>>
>>>> _D12TypeInfo_AAa6__initZ    COMDAT flags=x0 attr=x10 align=x0
>>>
>>>
>>>
>>> TypeInfo's don't get the module prefix because it would cause 
>>> duplication of code (i.e. bloat) to have it that way. There is no 
>>> difference between the TypeInfo for char[][] in one module, and the 
>>> TypeInfo for char[][] in another, so the TypeInfo names should match 
>>> exactly.
>>
>>
>> well, ok ... but it is responsible for what happened here? If not, 
>> what is?
> 
> 
>  From your description, the linker is looking to resolve a reference to 
> the TypeInfo for char[][], and found that module first.


That's exactly what it looks like. Would you agree the results could be 
described as haphazard? The outcome here certainly has that feeling to it :)

It also finds that particular one whether the module is listed first or 
last in the lib response-file.

What is one supposed to do for production-quality libraries?