FogBugz (Case [Issue]11635) Collection - Race condition in SequenceableCollection>>shuffle

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

FogBugz (Case [Issue]11635) Collection - Race condition in SequenceableCollection>>shuffle

Pharo Issue Tracker
A FogBugz case was edited by Sven Van Caekenberghe.

Case ID:      11635
Title:        Race condition in SequenceableCollection>>shuffle
Status:       Work Needed
Category:     Bug
Project:      Collection
Area:         Misc
Priority:     5 - Fix If Time
Milestone:    Pharo3.0: 30/03/2014
Assigned To:  Everyone

URL:          https://pharo.fogbugz.com/f/cases/11635

Maybe this should be discussed on the list, your are going to break API.

Note that there is also #sort and #sorted with similar copy behavior.

Also, I am not sure that basic operations should use mutexes to protect themselves by default: there is a cost when you are a single threaded user. Even in Java there are synchronized and non-synchronized versions of collections. IMHO, the protection should happen in your app, and basic collections do not have to be thread safe.

Sven


You are subscribed to this case.  If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=11635) from this case.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker