Update to 0.12.1.2

changelog:
0.12.1.2

* Fixed the incorrect tracking of capacity if the initial buffer was
  empty (https://github.com/bos/attoparsec/issues/75)

0.12.1.1

* Fixed a data corruption bug that occurred under some circumstances
  if a buffer grew after prompting for more input
  (https://github.com/bos/attoparsec/issues/74)

0.12.1.0

* Now compatible with GHC 7.9

* Reintroduced the Chunk class, used by the parsers package

0.12.0.0

* A new internal representation makes almost all real-world parsers
  faster, sometimes by big margins.  For example, parsing JSON data
  with aeson is now up to 70% faster.  These performance improvements
  also come with reduced memory consumption and some new capabilities.

* The new match combinator gives both the result of a parse and the
  input that it matched.

* The test suite has doubled in size.  This made it possible to switch
  to the new internal representation with a decent degree of
  confidence that everything was more or less working.

* The benchmark suite now contains a small family of benchmarks taken
  from real-world uses of attoparsec.

* A few types that ought to have been private now are.

* A few obsolete modules and functions have been marked as deprecated.
  They will be removed from the next major release.

0.11.3.0

* New function scientific is compatible with rational, but parses
  integers more efficiently (https://github.com/bos/aeson/issues/198)

0.11.2.0

* The new Chunk typeclass allows for some code sharing with Ed
  Kmett's parsers package: http://hackage.haskell.org/package/parsers

* New function runScanner generalises scan to return the final state
  of the scanner as well as the input consumed.
Update to 0.7.0.6

Changes from https://github.com/bos/aeson
0.7.0.6
 - Actually fix the DoS vulnerability by using the scientific parser
   (Parse a number using the new scientific parser)
     The old rational parser applied realToFrac (fromRational . toRational)
	 to the Scientific number to construct a new Scientific number. This
	 had
	 the disadvantage that scientific numbers with big exponents like
	 1e1000000000 are converted from (Scientific 1 1000000000) to
	 (Scientific (1*10^1000000000) 0). If the Integer coefficient of the
	 latter is later evaluated it will allocate all memory.

	 This is the first step needed to fix #198.
0.7.0.5
 - Bump attoparsec dep
 - Constrain the bounds on attoparsec and scientific
 - Update import location of scientificBuilder for v0.3.0.0
 - Add warning about space-usage on the Fixed instance
 - Use Scientific.toRealFloat instead of realToFrac in scientificToNumber
 - Renamed fromRealFloat back to fromFloatDigits
 - Use Scientific.fromRealFloat and Scientific.toRealFloat
 - Use floor on Scientifics again
   scientific-0.3 provides a DoS safe floor.
 - Use scientific >= 0.3.1
   scientific-0.3.1 exports the Text and ByteString Scientific Builders
   from the following modules respectively:
   - Data.Text.Lazy.Builder.Scientific
   - Data.ByteString.Builder.Scientific
0.7.0.3
 - Improve parseJSON failure message for Either
   This fixes #193.
 - Export `withScientific` function in `Data.Aeson`
   Fixes #191.
 - Reduce duplication, simplify CPP macros