Hi,
The problem is that the new implementation of union: and intersection: makes reference to class directly. Instead, they should use species.
I opened a an issue: http://code.google.com/p/pharo/issues/detail?id=5523
and created the corresponding slice: Name: SLICE-Issue-5523-Collection-union-and-intersection-should-use-species-TudorGirba.1 Author: TudorGirba Time: 20 March 2012, 7:25:55 am UUID: b3944736-b2d8-4c30-ad24-3c39c2a18cf9 Ancestors: Dependencies: Collections-Abstract-TudorGirba.158
use species instead of class for Collection>>union: and intersection:
Cheers, Doru
On 19 Mar 2012, at 20:10, Stéphane Ducasse wrote:
On Mar 18, 2012, at 10:08 PM, Alexandre Bergel wrote:
I am a bit puzzled. How comes that a new version of #union: break down so many tests. #union: is a simple operation.
Yes I would like to know it too. Do you have one single case that we can understand?
Stef
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
If you can't say why something is relevant, it probably isn't.