Nile makes #testProvidedMethodBindingsWithConflicts fail in 3.9

Daniel Vainsencher danielv at
Sat Jun 9 14:38:36 UTC 2007

Hi Damien,

I think I have found the bug, and it is in the following method:

TraitMethodDescription>>requiredMethodForArguments: aNumber ifAbsentPut: 
    "ConflictMethods is an array that caches the generated conflict
    methods. At position 1: binary method; 2: unary method;
    n+2: keywordmethod with n arguments."

    ^(RequiredMethods at: aNumber)
        ifNil: [ConflictMethods at: aNumber put: aBlock value]

This results in the following easy to diagnose symptom:


((TraitMethodDescription classPool at: #ConflictMethods) at: 2) 


    self requirement'

instead of:

    self traitConflict'

But I'm a bit rusty, so please double check me, and then send in the 
trivial fix. Ah, the wonders of caches/copy&paste...


Damien Cassou wrote:

> 2007/6/9, stephane ducasse <stephane.ducasse at>:
>> can you add that to mantis and add also the problems you describe in
>> the paper (about self requirement) taking precedence on ...

More information about the Squeak-dev mailing list