mrkkrp/megaparsec
1
1
Fork 0
mirror of https://github.com/mrkkrp/megaparsec.git synced 2024-11-23 10:23:39 +03:00
Code Issues Projects Releases Wiki Activity

Fix attoparsec link, link to parsec page in the readme

Browse Source 
[skip ci]
This commit is contained in:
mrkkrp 2018-10-19 23:39:31 +07:00
parent 2a86b4f566
commit e64a62da32
No known key found for this signature in database
GPG Key ID: 8564658B2889FF7C
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -181,9 +181,10 @@ let's compare Megaparsec with some of them.
### Megaparsec vs Attoparsec
[Attoparsec](https://github.com/bos/attoparsec) is another prominent Haskell
library for parsing. Although the both libraries deal with parsing, it's
usually easy to decide which you will need in particular project:
[Attoparsec](https://hackage.haskell.org/package/attoparsec) is another
prominent Haskell library for parsing. Although the both libraries deal with
parsing, it's usually easy to decide which you will need in particular
project:
* *Attoparsec* is sometimes faster but not that feature-rich. It should be
used when you want to process large amounts of data where performance
@ -204,8 +205,9 @@ so it can be used even to parse low-level binary formats.
### Megaparsec vs Parsec
Since Megaparsec is a fork of Parsec, we are bound to list the main
differences between the two libraries:
Since Megaparsec is a fork of
[Parsec](https://hackage.haskell.org/package/parsec), we are bound to list
the main differences between the two libraries:
* Better error messages. We test our error messages using numerous
QuickCheck (generative) tests. Good error messages are just as important