Code behaves incorrectly if it is compiled in std.functional

[Adam D. Ruppe via Digitalmars-d]

On Friday, 5 June 2015 at 19:45:18 UTC, krzaq wrote:
> const auto ans = 42;
>
> compiles fine for me, so auto clearly can be used as a type.

So does "auto immutable" or "auto pure" or "pure a".

They're all storage classes and any storage class can kick off a 
declaration:

         @nogc a = 10;  // compiles!


dmd is just not really consistent on when it issues errors on 
redundant, conflicting, or useless storage classes.