Could new keyword help function hijacking and prevented aliasing all over the place??

[Steven Schveighoffer]

On Fri, 27 May 2011 13:25:51 -0400, Andrei Alexandrescu  
<SeeWebsiteForEmail at erdani.org> wrote:

> On 5/27/11 1:06 PM, Dejan Lekic wrote:
>>> A couple of years ago, Walter gave a talk on hijacking to NWCPP. It all
>>> went well until HiddenFunc, at which point Walter's assertion that the
>>> way out was by throwing an exception was hotly debated. Several people
>>> suggested alternative, of whom one proposed (4) above. Everybody agreed
>>> it's a good solution, and Walter had the presence of mind and humility
>>> to acknowledge that solution and to promise to look into implementing
>>> it. Unfortunately, that event was forgotten... until now.
>>>
>>>
>>> Andrei
>>
>> Andrei, there was a discussion about it here on this NG too. I too think
>> that (4) is definitely the best solution. At least that is what I would
>> like D2 to do...
>
> Just talked to Walter - he did implement something similar that  
> eliminates HiddenFunc, just only with -w. I ran a couple of tests and I  
> find the behavior reasonable. (He does require introducing all overloads  
> in derived classes, which is more permissive than what I had in mind but  
> still eliminates HiddenFunc.)
>
> This is perhaps a good time to move these two -w features into the  
> flag-free compiler: requiring override and detecting hidden functions  
> during compilation.

I think maybe this is a good thing for a bug report :)

I'll make one.

-Steve