<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 12, 2015 at 11:57 AM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On 12-08-2015, at 11:20 AM, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
<br>
><br>
><br>
> On Wed, Aug 12, 2015 at 11:09 AM, Levente Uzonyi <<a href="mailto:leves@elte.hu">leves@elte.hu</a>> wrote:<br>
> I wonder if you're creating two forwarders in case of #become:, with objects of different size, or just one forwarder for the larger object while copying the smaller object over the larger one (when possible).<br>
><br>
> Right now it's the simplest thing that could possibly work. I think this is a great idea though. It would potentially eliminate the post-become stack scan if all objects can be becomed either by exchanging contents or (in one-way) shortening. Alas I don't have time for this right now. Any volunteers interested?<br>
<br>
</span>Huh; I thought you had done that ages ago. I recall suggesting it really early in your spur work and could have sworn you did it right then.<br></blockquote><div><br></div><div>I think I did exchange of contents when the objects are of the same size, at your prompting, but I definitely know I /didn't/ do shortening in one-way as per Levente's suggestion.</div><div></div></div><div class="gmail_extra"><br></div><div class="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>