try binary-parsers

[winterland1989]

Previous result can be checked in #452, now the result is:

    json-data/twitter1.json :: 60000 times
      0.991 seconds, 60559 parses/sec, 49.379 MB/sec
    json-data/twitter1.json :: 60000 times
      0.956 seconds, 62774 parses/sec, 51.186 MB/sec
    json-data/twitter1.json :: 60000 times
      0.958 seconds, 62644 parses/sec, 51.080 MB/sec
0.8 KB: 62774 msg\/sec (51.2 MB\/sec)
    json-data/twitter10.json :: 13000 times
      1.222 seconds, 10641 parses/sec, 66.918 MB/sec
    json-data/twitter10.json :: 13000 times
      1.239 seconds, 10492 parses/sec, 65.981 MB/sec
    json-data/twitter10.json :: 13000 times
      1.265 seconds, 10276 parses/sec, 64.621 MB/sec
6.4 KB: 10641 msg\/sec (66.9 MB\/sec)
    json-data/twitter20.json :: 7500 times
      1.706 seconds, 4395 parses/sec, 50.593 MB/sec
    json-data/twitter20.json :: 7500 times
      1.732 seconds, 4329 parses/sec, 49.823 MB/sec
    json-data/twitter20.json :: 7500 times
      1.712 seconds, 4381 parses/sec, 50.429 MB/sec
11.8 KB: 4396 msg\/sec (50.6 MB\/sec)
    json-data/twitter50.json :: 2500 times
      1.590 seconds, 1572 parses/sec, 47.901 MB/sec
    json-data/twitter50.json :: 2500 times
      1.582 seconds, 1580 parses/sec, 48.156 MB/sec
    json-data/twitter50.json :: 2500 times
      1.679 seconds, 1489 parses/sec, 45.372 MB/sec
31.2 KB: 1581 msg\/sec (48.2 MB\/sec)
    json-data/twitter100.json :: 1000 times
      1.312 seconds, 761 parses/sec, 45.779 MB/sec
    json-data/twitter100.json :: 1000 times
      1.295 seconds, 772 parses/sec, 46.404 MB/sec
    json-data/twitter100.json :: 1000 times
      1.320 seconds, 757 parses/sec, 45.512 MB/sec
61.5 KB: 772 msg\/sec (46.4 MB\/sec)
    json-data/jp10.json :: 4000 times
      0.683 seconds, 5860 parses/sec, 83.740 MB/sec
    json-data/jp10.json :: 4000 times
      0.714 seconds, 5599 parses/sec, 80.017 MB/sec
    json-data/jp10.json :: 4000 times
      0.702 seconds, 5700 parses/sec, 81.453 MB/sec
14.6 KB: 5861 msg\/sec (83.7 MB\/sec)
    json-data/jp50.json :: 1200 times
      0.886 seconds, 1354 parses/sec, 58.329 MB/sec
    json-data/jp50.json :: 1200 times
      0.842 seconds, 1425 parses/sec, 61.361 MB/sec
    json-data/jp50.json :: 1200 times
      0.870 seconds, 1379 parses/sec, 59.406 MB/sec
44.1 KB: 1425 msg\/sec (61.4 MB\/sec)
    json-data/jp100.json :: 700 times
      0.958 seconds, 730 parses/sec, 59.158 MB/sec
    json-data/jp100.json :: 700 times
      0.980 seconds, 714 parses/sec, 57.841 MB/sec
    json-data/jp100.json :: 700 times
      0.981 seconds, 713 parses/sec, 57.768 MB/sec
82.9 KB: 731 msg\/sec (59.2 MB\/sec)

[winterland1989]

Sorry for failing the tests, fixing

[winterland1989]

All tests passed, The stack build error should be resolved when binary-parsers get added into stackage.

[bergmark]

This is a very clean diff 👍

[DemiMarie]

You have an integer overflow bug in the C code

[winterland1989]

@DemiMarie Can you tell me more about it？