And in fact can't even go in IArray at all. Argh! Double error! I think I'll go back under my rock.
Oh, I think I missed your point, that this operation really belongs in a *different* class—sorry.
On Nov 14, 2014 5:07 PM, "Carter Schonwald" <carter.schonwald@gmail.com> wrote:amap :: (IArray a e', IArray a e, Ix i) => (e' -> e) -> a i e' -> a i ethis looks like map. just with a class constraint. I dont buy that theres any ROI for putting it into the class at all.By the same arguement, map and fold in Vector should be part of the class.-1On Fri, Nov 14, 2014 at 4:30 PM, David Feuer <david.feuer@gmail.com> wrote:I realized what I wrote about amap earlier was utterly boneheaded, because it has the wrong type for fmap. The only way to accomplish my goal is to make Data.Array.IArray.amap a method of the IArray class. This will allow IArray instances to offer optimized versions and things like amap/coerce rules. The current implementation of amap can become the default one.
_______________________________________________
Libraries mailing list
Libraries@haskell.org
http://www.haskell.org/mailman/listinfo/libraries