Strict Value fields
This improves the running time of the AesonParse benchmarks.
I don't think there's a use-case for lazy fields.
Fixes #37
commit23163a18d0ba04efeae0aa46456ae36b380fa92c
authorBas van Dijk <v.dijk.bas@gmail.com>
dateWed 16 Nov 2011, 15:54 (15 years ago)
parent78ad6e6
Data/Aeson/Types/Internal.hs+4−4
@@ -157,10 +157,10 @@ type Object = Map Text Value
157157type Array = Vector Value
158158
159159-- | A JSON value represented as a Haskell value.
160−data Value = Object Object
161− | Array Array
162− | String Text
163− | Number Number
160+data Value = Object !Object
161+ | Array !Array
162+ | String !Text
163+ | Number !Number
164164 | Bool !Bool
165165 | Null
166166 deriving (Eq, Show, Typeable, Data)