Favorite bug?

[Craig Black]

"Bill Baxter" <dnewsgroup at billbaxter.com> wrote in message 
news:f6asup$2sjh$1 at digitalmars.com...
> Brad Roberts wrote:
>> I'll probably regret starting this thread in a day or to, but out of 
>> curiosity's sake, if you had to pick a single bug to be fixed in the next 
>> 1.x bug fix release, what would it be and why?  Remember, just one per 
>> person.
>>
>> NOTE: This is just a poll, not any sort of guarantee that it'll be fixed 
>> or even looked at.  I'm doing this purely out of my own personal 
>> curiosity.
>>
>> Later,
>> Brad
>
>
> #52 for me.
> Referring to a function by name only gets you the first version that 
> appears lexically.  No warning about conflicting overloads.
>
> Unfortunately I also dread seeing this one fixed, because I suspect the 
> fix is going to be just to make it an error, and/or require casting to the 
> exact version you want with a monstrosity like:
>
>    cast(return_type function(int,double,char[]) &fn
>
> --bb

It would be ideal if it was interpreted as a special type of function 
pointer that knows about all the overloads, and then identifies the exact 
overload when it is assigned.  That would be cool.

-Craig