This is true, and in fact I almost never use dlist myself (or Endo), since lambdas are already quite light weight.
However, dlist makes the intention explicit, which is probably a good enough reason to use it in a package in the platform. On Nov 11, 2013 10:20 AM, "Dag Odenhall" <dag.odenh...@gmail.com> wrote: > Wouldn’t it be trivial to get rid of the dlist dependency using Endoinstead, > too? It seems to only be an implementation detail. On the other > hand, maybe dlist in Platform makes sense anyway. > > > On Mon, Nov 11, 2013 at 11:07 AM, Bas van Dijk <v.dijk....@gmail.com>wrote: > >> On 10 November 2013 23:14, Mark Lentczner <mark.lentcz...@gmail.com> >> wrote: >> > I spoke too soon: >> > >> > aeson induces blaze-builder >> >> Note that I removed the blaze-builder requirement from aeson-HEAD (it >> now uses the Builder from bytestring with a fallback to blaze-builder >> when configured with -fblaze-builder). >> >> I think we're pretty close to a release of aeson-0.7.0.0. It would be >> great to have this version in the HP since: >> >> * It includes an important bug fix for the eitherDecodeStrict functions. >> >> * It has support for arbitrary precision floating point numbers (as >> required by the JSON spec) through the Scientific type. >> >> * It removes the ByteString instances since JSON doesn't have support >> for binary data (this was brought up during the HP inclusion >> discussion). >> >> * It adds ToJSON and FromJSON for Data.Tree. >> >> Bas >> _______________________________________________ >> Libraries mailing list >> librar...@haskell.org >> http://www.haskell.org/mailman/listinfo/libraries >> > > > _______________________________________________ > Libraries mailing list > librar...@haskell.org > http://www.haskell.org/mailman/listinfo/libraries > >
_______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
