[firstname.lastname@example.org: Nasty (but fixed) complexity-changing bug
thingy in bytestring]
igloo at earth.li
Sun Oct 5 09:14:47 EDT 2008
On Sat, Oct 04, 2008 at 04:00:57PM -0700, Duncan Coutts wrote:
> On Sat, 2008-10-04 at 15:50 -0700, Don Stewart wrote:
> > BTW, this is why we cannot ship with the old bytestring fork of 0.9
> > bumping around in GHC.
> That and the not-closing-file-handles bug.
I believe I've just fixed this, but please let me know if there is more
If the only other known issue is an unidentified performance bug (which
isn't a regression, and may even just be due to the flags used when
compiling or something) then I'd favour sticking with the current code
at this point in the release. We are less likely to be bitten by unknown
issues, API changes etc that way.
For the HEAD/6.12 we can drop the GHC fork when we do the Great VCS
More information about the Cvs-ghc