
On Mon, Aug 2, 2010 at 6:32 AM, Antoine Latter
On Mon, Aug 2, 2010 at 1:55 AM, Ivan Miljenovic
wrote:
That said, if parsec2 is only a bug-fix branch of parsec-2.x, is there any particular reason work couldn't be done to improve the performance of parsec-3 when using the compatibility layer (and even improving the performance of parsec-3 overall) rather than a specific branch/fork?
The release of parsec-3.1 dramatically improved the performance of parsec3 to roughly parsec-2.1 levels. So I don't know of any downside to switching over to the compatibility layer other the fact that it's a much newer code-base, and that it's a much further departure
How about I finish my sentences. My second downside was that parsec-3 is a much further departure from Haskell2010 than parsec-2.