Having "self class new addAll: set asArray" instead of "self class withAll: set asArray" may do the thing no?
Alexandre
On 15 Mar 2012, at 18:06, Tudor Girba wrote:
More precisely the crashes are due to the changes in the Collection>>union:
The original definition was: union: aCollection ^ self asSet addAll: aCollection; yourself
The new definition is: union: aCollection | set | set := self asSet addAll: aCollection; yourself. ^ self class withAll: set asArray
This breaks the assumptions behind FMMultivalueLink because although FMMultivalueLink is a subclass of Collection, it is not supposed to be created with a "withAll:" constructor.
Cheers, Doru
On 15 Mar 2012, at 22:45, Moose wrote:
I updated Pharo to the latest version.
It looks like multiple tests fail because something changed in the computation of allRecursiveTypes.
Cheers, Doru
On 15 Mar 2012, at 22:48, Alexandre Bergel wrote:
How comes there are so many failed tests ?
Alexandre
On 15 Mar 2012, at 16:46, admin@moosetechnology.org wrote:
See http://hudson.moosetechnology.org/job/moose-latest-dev/886/
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"From an abstract enough point of view, any two things are similar."