Linker anomalies

Luh null at null.null
Thu Nov 7 20:44:56 UTC 2019


On Thursday, 7 November 2019 at 18:45:21 UTC, Ali Çehreli wrote:
> On 11/07/2019 04:14 AM, Luh wrote:
> It's not the linker but the "compiler" that is concerned about 
> these things.
>
> [...]

Oops :o

> That's an important warning where the programmer can get 
> surprising results depending on whether the object is used 
> through the Parent interface or the Child interface.
> > [...]
> error message.
>
> [...]

It would be clever to show the correct error message :)
(I spend 1 hour to find what was the problem haha. I hope the 
others newbies won't make the same mistake)

> Apparently, the compiler does not check whether an overload set 
> has ambiguities until actual use. I suspect the opposite would 
> slow dow compilation and cause frustration in some cases.
>
> [...]

Thanks for the tips.


More information about the Digitalmars-d-learn mailing list