Did anyone spend time trying to identify / bisect when the bug was fixed between 7.6.2 and ghc head? (and backport the logic to resolve it)
would be a shame to not have the next haskell platform use 7.6 ... On Fri, Apr 12, 2013 at 7:12 AM, Roman Cheplyaka <r...@ro-che.info> wrote: > * Christian Maeder <christian.mae...@dfki.de> [2013-04-12 11:26:25+0200] > > Hi, > > > > I just spoiled my day by http://hackage.haskell.org/trac/ghc/ticket/7748 > > with ghc-7.6.2 in our large project: > > > > hets: <<loop>> > > > > hets works fine with ghc-7.6.1 (and older versions). I haven't > > located the error yet, though. > > > > Yet, I therefore conclude, GHC 7.6.2 ist not suited for the official HP. > > I don't think this is enough data to make such a conclusion. > GHC 7.6.2 may have fixes for bugs that are present in GHC 7.6.1, for > example. > > So we need to compare the fixed bugs versus regressions in 7.6.2 to make > the choice. > > (OTOH, the looping bug is a nasty one, if you ask me, and is difficult > to debug.) > > Roman > > _______________________________________________ > Libraries mailing list > librar...@haskell.org > http://www.haskell.org/mailman/listinfo/libraries >
_______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
