Hello, Have you emailed Bryan O'Sullivan and explained your problem? It sounds to me like choosing Double was just the wrong choice and is a design flaw that should be fixed in Aeson?
There are far too many JSON libraries on hackage already, and what would be really useful (to me) is for the community to standardize on one. I maintain a number of libraries that need some sort of JSON library, and supporting all of them is not practical. So far aeson seems like the best choice for the 'one true Haskell JSON library'. I would be happy to invest effort in trying to address the shortcomings so that we can try to get some sort of consensus. Usually I like choice and flexibility.. but in terms of JSON libraries.. it seems like the design space for a good JSON library is pretty small. - jeremy On Tue, Apr 24, 2012 at 4:51 PM, Jeff Shaw <shawj...@msu.edu> wrote: > Hi Jeremy, > Sorry if I was unclear. Rational is acceptable to me as the result of a JSON > parse, but Double (which Aeson uses), is not. Also acceptable would be > Data.Decimal.Decimal, or maybe one of the types from Data.Fixed. > > JSON doesn't specify a data type for numbers, only a format. > > Jeff _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe