Re: Object.opEquals, opCmp, toHash

[Daniel Murphy]

I agree.  What about shared?

"Walter Bright" <newshou...@digitalmars.com> wrote in message 
news:jhif48$1n0n$1...@digitalmars.com...
> These all need to be:
>
>     const pure nothrow @safe
>
> Unless this is done, the utility of const, pure, nothrow and @safe is 
> rather crippled.
>
> Any reason why they shouldn't be?
>
> One reason is memoization, aka lazy initialization, aka logical const. I 
> don't believe these are worth it. If you must do it inside those functions 
> (and functions that override them), you're on your own to make it work 
> right (use unsafe casts, etc.).