<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 9 Dec 2020, at 10:11, Jean-Claude Beaudoin <<a href="mailto:jean.claude.beaudoin@gmail.com" class="">jean.claude.beaudoin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 9, 2020 at 3:16 AM Nick Levine <<a href="mailto:nick@nicklevine.org" class="">nick@nicklevine.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> Can I ask why you invoke #'CL:CHANGE-CLASS on an object instead of simply creating a new instance of the second class with adequate initialization?<br class="">
<br class="">
Because you’d have to go find all the pointers to the old instance. Maybe you don’t want to do that. Or maybe you don’t care, but that’s ok because what CLOS gives you is possibilities. <br class=""></blockquote><div class=""><br class=""></div><div class="">Yes, preserving instance identity is at the core of the question. It could even be the only question here. Is there any other?</div><div class=""><br class=""></div><div class="">But what looks like an occasional convenience comes at a cost.</div></div></div></div></blockquote><br class=""></div><div>The cost of implementing the mechanisms involved has already been payed. Changing the semantics would imply changing the implementations, and would have an impact on all existing libraries and applications. So you would be incurring an additional cost. (That alone is not a good argument for keeping the feature, it’s just to remind you that the cost/benefit analysis in this regard is not straightforward.)</div><div><br class=""></div><div>I doubt that the cost in terms of runtime performance really matters that much in practice. Class redefinitions are rare, I suppose, and I doubt that slot accesses have a high overhead because of them. (I would think that unbound slots, for example, cost more, but that’s just guessing.)</div><div><br class=""></div><div>In my experience, the two most important feature for improving performance in Common Lisp are inlining and stack allocation. If you could work on a way how to inline generic functions while maintaining the ability to add and remove methods at runtime, and to make dynamic-extent declarations on CLOS instances effective, that would probably buy us a lot more in terms of performance than restricting class redefinition capabilities.</div><div><br class=""></div><div><br class=""></div><div>Pascal</div><br class=""><div class="">
--<br class="">Pascal Costanza<br class=""><br class="">
</div>
<br class=""></body></html>