Just anecdotally I remember we had this problem with Accelerate. Back when we were using it last Spring for some reason we were forced by the API to at least nominally go through lists on our way to the GPU -- which we sorely hoped were deforested! At times (and somewhat unpredictably), we'd be faced enormous execution times and memory footprints as the runtime tried to create gigantic lists for feeding to Accelerate.
Other than that -- I like having a nice literal syntax for other types. But I'm not sure that I construct literals for Sets and IntMaps often enough to profit much... -Ryan On Tue, Oct 4, 2011 at 9:38 AM, Roman Leshchinskiy <r...@cse.unsw.edu.au>wrote: > George Giorgidze wrote: > > > > This extension could also be used for giving data-parallel array literals > > instead of the special syntax used currently. > > Unfortunately, it couldn't. DPH array literals don't (and can't really) go > through lists. > > In general, if we are going to overload list literals then forcing the > desugaring to always go through lists seems wrong to me. There are plenty > of data structures where that might result in a significant performance > hit. > > Roman > > > > > _______________________________________________ > Glasgow-haskell-users mailing list > Glasgow-haskell-users@haskell.org > http://www.haskell.org/mailman/listinfo/glasgow-haskell-users >
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
