On Sun, 2013-11-17 at 12:20 -0800, Mark Lentczner wrote:
*Options for aeson:*
1. skip it in this release 2. include *aeson* 0.6.2.1 - requiring both *dlist* and *blaze-builder* 3. include *aeson* 0.6.2.x, a version with the patch that uses *bytestring*'s builder, and so require only *dlist* 4. include *aeson* 0.7.0.0 - requiring *dlist* and possibly *scientific*
I would strongly argue against including blaze-builder in the platform. The whole point of the work Simon Meier (and Johan and myself) have done over the last year or so with adding Builder into the bytestring package was so that we could get a good implementation with a good API into the platform (and in the appropriate place). It would be silly at this point to confuse matters for users. So I don't mind if there is an aeson-0.6.2.x or a 0.7.x release, so long as it's using the bytestring builder and not blaze-builder. And of course note that the current 2013.2 HP already includes bytestring-0.10 which has the new builder API. -- Duncan Coutts, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/