I'm also +1, though I'd strongly prefer that the instance for
ByteString gets dropped before inclusion.
The "don't do that" approach is not very Haskelly. A Char8 ByteString
is the same type as a Word8 ByteString, so while you could argue that
Char8 is implicitly ASCII, the instance couldn't distinguish it from
Word8 ByteStrings where this doesn't make sense. Since JSON doesn't
have a standard way of encoding binary data
(utf8/base64/base64url/...), external JSON API often may use their own
convention, so it's best to require users to be explicit about
semantics.
On 18 September 2013 11:24, Herbert Valerio Riedel
On 2013-09-18 at 09:22:07 +0200, Michael Snoyman wrote:
[...]
So: +1 from me on including aeson as-is, and if Bryan's interested in making this change to aeson, I'd consider it a perk.
+1 like Micheal
(i.e. I support `aeson` in HP unconditionally; but I'd be delighted if the `ByteString` instances not pure issue would be fixed somehow) _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries