On Jan 15, 2009, at 15:43 , Damien Cassou wrote:
On Thu, Jan 15, 2009 at 3:13 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
The hash of traits is not related to the problem. The problem is that classes show up multiple times in IdentitySets.
I found the cause (its a bit complicated to explain because related to the ClassBuilder and become:). I can fix that during the weekend...
I've implemented a TraitBehavior>>nsUsers method which does
nsUsers ^ self users asOrderedCollection asSet
to work around the problem for the article. Can you confirm that this is a valid workaround?
No. This will remove the duplicates, but in case traits are removed from classes you can still get wrong results if this happens for a class with a users set that is inconsistent. Adrian