[Issue 9769] Remove opEquals from Object
https://issues.dlang.org/show_bug.cgi?id=9769 Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --
[Issue 9769] Remove opEquals from Object
https://issues.dlang.org/show_bug.cgi?id=9769 --- Comment #6 from Jonathan M Davis--- Latest attempt to templatize the free function opEquals (which is not a full fix for this but is the first step in the process): https://github.com/D-Programming-Language/druntime/pull/1439 --
[Issue 9769] Remove opEquals from Object
https://issues.dlang.org/show_bug.cgi?id=9769 Issue 9769 depends on issue 12537, which changed state. Issue 12537 Summary: Templatizing opEquals results in infinite recursion in the compiler https://issues.dlang.org/show_bug.cgi?id=12537 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 9769] Remove opEquals from Object
https://issues.dlang.org/show_bug.cgi?id=9769 Jonathan M Davis jmdavisp...@gmx.com changed: What|Removed |Added Depends on||12537 --
[Issue 9769] Remove opEquals from Object
http://d.puremagic.com/issues/show_bug.cgi?id=9769 --- Comment #5 from Jonathan M Davis jmdavisp...@gmx.com 2013-10-13 16:17:16 PDT --- Relevant discussion on how to transition away from having these functions on Object (the thread got broken up a bit - probably by the mailman bug): http://forum.dlang.org/post/mailman.214.1369617617.13711.digitalmar...@puremagic.com http://forum.dlang.org/post/mailman.280.1369712394.13711.digitalmar...@puremagic.com The key suggestion is to change the compiler so that those 4 functions can be free functions in object_.d, similar to how the compiler already does special stuff for == rather than simply calling Object's opEquals. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 9769] Remove opEquals from Object
http://d.puremagic.com/issues/show_bug.cgi?id=9769 --- Comment #1 from Jonathan M Davis jmdavisp...@gmx.com 2013-03-21 00:05:46 PDT --- Related: opCmp: issue# 9770 toHash: issue# 9771 toString: issue# 9772 -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 9769] Remove opEquals from Object
http://d.puremagic.com/issues/show_bug.cgi?id=9769 Jacob Carlborg d...@me.com changed: What|Removed |Added CC||d...@me.com --- Comment #2 from Jacob Carlborg d...@me.com 2013-03-21 00:25:12 PDT --- Was there a conclusion on how this will affect backwards compatible? -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 9769] Remove opEquals from Object
http://d.puremagic.com/issues/show_bug.cgi?id=9769 --- Comment #3 from Jonathan M Davis jmdavisp...@gmx.com 2013-03-21 00:42:37 PDT --- https://github.com/D-Programming-Language/druntime/pull/459 -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 9769] Remove opEquals from Object
http://d.puremagic.com/issues/show_bug.cgi?id=9769 --- Comment #4 from Jonathan M Davis jmdavisp...@gmx.com 2013-03-21 00:45:19 PDT --- Was there a conclusion on how this will affect backwards compatible? No, other than the fact that we'd probably have to keep the functions on opEquals for a while as part of the transition. I expect that the steps will be something like 1. Convert everything over in druntime so that those functions don't have to be on Object. 2. Deprecate the functions on Object. 3. Remove the functions from Object. I expect that it'll take quite a while to go through those stages though, and it may be the case that we'll be forced to remove them from Object faster than we'd like due to some implementation issue that makes it so that keeping it around is a problem; I don't know. Regardless, the first step is making those functions on Object unnecessary, and that's going to take a while (primarily due to AAs). -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---