All right, all right! Interim decision regarding qualified Object methods
Jonathan M Davis
jmdavisProg at gmx.com
Thu Jul 12 02:51:44 PDT 2012
On Thursday, July 12, 2012 02:43:09 Walter Bright wrote:
> On 7/12/2012 12:59 AM, Jonathan M Davis wrote:
> > So, I think that it's probably a solid way to go, and it does appear to
> > solve the const issues that we've been having quite nicely, but it also
> > appears to break a number of things which have worked for some time, and
> > we're going to have to figure out how we're going to deal with that, even
> > if it's only providing a good deprecation path.
> 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.
- Jonathan M Davis
More information about the Digitalmars-d