I have made a discovery

[Brian Schott via Digitalmars-d]

On Sunday, 19 April 2015 at 00:39:03 UTC, ketmar wrote:
> On Sun, 19 Apr 2015 12:29:45 +1200, Rikki Cattermole wrote:
>
>> Awesome! Although we may need to "undeprecate" that feature.
>
> as it is not generating deprecation warning now, it should be 
> fairly
> easy: just reintroduce it into specs. i can see why it was 
> deprecated in
> the first place, but it's much easier to simply write "new 
> Exception"
> instead of "allocateWithMyCoolScheme!Exception".

If you overload a class's `new`, you are deciding for your 
class's user how it will be allocated. I think it's better to let 
the programmer decide how they want the class to be allocated.