Hi Lukas<br><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Some Magritte users are unnecessarily rigid, because the descriptions<br>

are only created once and in a meaningless context (on the class<br>
side). This caused some ugly hacks like #magritteDynamicObject or<br>
overrides of #description that should no longer be necessary.<br>
<br>
Of course that means we need to drop the global caching, because<br>
Magritte cannot easily decide anymore if a description changes or not.<br>
I don&#39;t think this will be a big performance problem, because<br>
descriptions are essentially just data holders for a bunch of<br>
literals. What we could want to cache instead are the selectors that<br>
build the descriptions for a particular class, so that we do not<br>
repeatedly need to walk over the methods of the class hierarchies. And<br>
the flushing would happen as before.</blockquote><div><br></div><div>That&#39;s clear, I&#39;ll drop the caching so the descriptions are created on-demand. However I&#39;m confused as to why the caching couldn&#39;t have been dropped before for the class-side descriptions. I realise removing the caching before wouldn&#39;t have solved all the problems that instance descriptions have, but it would have removed the need for #magritteDynamicObject and friends. Though perhaps that is only a marginal benefit. Am I missing something?</div>
<div><br></div><div>Nick</div></div>