All right, all right! Interim decision regarding qualified Object methods

[Walter Bright]

On 7/12/2012 2:51 AM, Jonathan M Davis wrote:
> On Thursday, July 12, 2012 02:43:09 Walter Bright wrote:
>> A main motivation for going this route is to avoid breaking existing code.
>
> Except that it's _guaranteed_ to break code, because anything which relies on
> Object having opEquals, opCmp, toHash, or toString is going to break. We can
> provide an appropriate deprecation path to ease the transition, but this
> _will_ break code.

Which is why we'll be leaving those members in Object for the foreseeable future.