Changes between Initial Version and Version 1 of Proposals/attoparsec

Show
Ignore:
Timestamp:
01/23/13 10:26:26 (21 months ago)
Author:
gregorycollins (IP: 2620:0:105f:4:be30:5bff:fee0:268b)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Proposals/attoparsec

    v1 v1  
     1[[PageOutline]] 
     2 
     3= Proposal: Add the attoparsec package to the Haskell Platform = 
     4 
     5This is a proposal for the 'attoparsec' package to be included in the next major release of the Haskell platform. 
     6 
     7Everyone is invited to review this proposal, following the [http://trac.haskell.org/haskell-platform/wiki/AddingPackages standard procedure for proposing and reviewing packages]. 
     8 
     9Review comments should be sent to the libraries mailing list before Feb 23, which is the discussion deadline. 
     10 
     11 
     12= Credits = 
     13 
     14Proposal author: Gregory Collins 
     15 
     16Package maintainer: Bryan O'Sullivan 
     17 
     18The following individuals contributed to the review process: 
     19 
     20  * Gregory Collins 
     21  * ... 
     22 
     23 
     24= Abstract = 
     25 
     26The `attoparsec` package is a fast applicative parser combinator library, aimed particularly at dealing efficiently with network protocols and complicated text/binary file formats. It offers backtracking parsers for ByteString and Text. 
     27 
     28Documentation and tarball from the hackage page: 
     29 
     30  http://hackage.haskell.org/package/attoparsec 
     31 
     32Development repo: 
     33 
     34  https://github.com/bos/attoparsec 
     35 
     36 
     37= Rationale = 
     38 
     39Attoparsec trades away features from more complicated parser libraries like parsec and uuparsinglib (like meaningful error messages and independence over the ground character type) for speed. Compared with parsec, attoparsec is usually several times faster, which makes it appropriate for situations where throughput is paramount, like big-data processing and parsing network protocols. One other killer attoparsec feature is incremental parsing: this allows users to stream bytestring chunks to attoparsec, which responds either with a value or with a resumption continuation. 
     40 
     41The attoparsec library is very widely used: according to http://packdeps.haskellers.com/, it has 180 reverse dependencies on Hackage. 
     42 
     43 
     44= Introduction to the API = 
     45 
     46The API is a fairly "standard" applicative parser: it offers a "Parser a" datatype which is an instance of Functor, Applicative, Alternative, and Monad, and typical combinators like "string" and "takeWhile". 
     47 
     48= Design decisions = 
     49 
     50 
     51= Open issues = 
     52