<div dir="ltr"><div>Ah, of course, class mutation is the opposite example, when the old object becomeForward: the new one.<br></div>There would be a clever trick: keep the identityHash of the oldest object, but that's certainly much too clever...<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/4/13 Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div class="im"><div>On 13.04.2013, at 05:58, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div>Colin is right, whatever the choice and unlike become: we'll have to rehash something...<br></div></div></blockquote><div><br></div></div>Yep.</div><div><div class="im">
<br><blockquote type="cite"><div dir="ltr"><div>And we must not forget that we always have to rehash ordinary (vs identity) Set/Dictionary , becomeForward: or not...<br>
</div>Though, I would prefer the opposite behavior like Bert, because a frequent usage is to replace references to a new object with references to an older one, and IMO it's more conservative to preserve the older one.</div>
</blockquote><div><br></div></div><div>Here is the old discussion:</div><div><br></div><div><span style="white-space:pre-wrap"> </span><a href="http://lists.squeakfoundation.org/pipermail/squeak-dev/2000-January/006970.html" target="_blank">http://lists.squeakfoundation.org/pipermail/squeak-dev/2000-January/006970.html</a></div>
<div><br></div><div>... but I have to disagree with Dan on this one ;) The less surprising behavior is preferable, IMHO.</div><span class="HOEnZb"><font color="#888888"><div><br></div>- Bert -</font></span></div><div class="im">
<div><br><blockquote type="cite"><div class="gmail_extra"><br><div class="gmail_quote">2013/4/13 Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="auto"><div>Am 12.04.2013 um 23:47 schrieb Colin Putney <<a href="mailto:colin@wiresong.com" target="_blank">colin@wiresong.com</a>>:</div><div><br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">
On Fri, Apr 12, 2013 at 7:02 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br><div class="gmail_quote">
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="auto">Maybe we should change the default?</div>
</blockquote><div><br></div><div>No, I think we'd just get subtle bugs of the opposite sort.</div>
<div><br></div><div>Colin</div></div></div></div></blockquote><div><br></div>Well, my mental model was that the become target would not change at all. According to previous discussions, that is also how other Smalltalks handle it.<span><font color="#888888"><div>
<br></div><div>- Bert -</div></font></span></div></blockquote></div></div></blockquote></div><br></div></div><br><br>
<br></blockquote></div><br></div>