On Wed, Nov 20, 2013 at 10:06 AM, Ryan Newton
(3) The most invasive (but best for the user) change would be to extend the basic MVector interface to include notions of concurrency-related operations right inside the vector package (CAS, etc). But they should still probably go in a separate class (not class MVector), just because they will be specific to Unboxed and Storable vectors rather than boxed ones....
Any reason we shouldn't be able to CAS on boxed vectors? Every architecture supports a pointer-sized CAS. What "equality" means for CAS, of course, has to be rather carefully defined, but that's equally true for the unboxed types. -Jan
-Ryan
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries