> Don, is there any chance that you'd be willing to go back and track down > why the bytestring code in unstable is so much slower than the > non-bytestring code? Or maybe this is fixed in some bytestring package that > is more recent than the one that ships with ghc 6.8.2 (which is 0.9.0.1, > btw)?
I'd prefer to just use bytestring 0.9.1.4, and make sure it is used appropriately and fast, since the amount of time I can devote here is somewhat limited. What would be the best use of my time? When was the original bytestring compat layer written? -- Don _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
