[Haskell-cafe] Re: Parsec3 performance issues (in relation to v2)

[Neal Alexander]

I also redid the profiling for Parsec3 using ByteStrings directly (Its 
slower than manually unpacking and feeding it a [Char]):

http://72.167.145.184:8000/parsec_test/Parsec3_BStr.prof

The code for EQ2Parse.hs is identical, aside from changing the type 
signature of "init" to use the ByteString ParsecT, and removing the line 
unpack.