HEADS UP: Final call for 7.10.2 is soon

Hi *, I've just finished merging all the latest patches for GHC 7.10.2 into the STABLE branch. All in all, we've fixed a lot of bugs (over 80 tickets closed)! So, we'll probably be doing a 7.10.2 release here in a few weeks. The tentative plan was around the 14th, although it's not set in stone.

Re: Ambiguity check and type families

Hi Adam, yes, this seems to be the same bug. I just annotated ticket #10009. I hope the fix will make it into GHC 7.10.2. Can anyone say when GHC 7.10.2 will be released approximately? All the best, Wolfgang Am Dienstag, den 02.06.2015, 13:00 -0400 schrieb adam vogt: Hi Wolfgang,

Re: ghc 7.10.1 hard lock on exit with shake, OS X 10.10

could you share a minimal program that reproduces the problem? On Tue, Jun 2, 2015 at 9:36 PM, Evan Laforge qdun...@gmail.com wrote: After I upgraded to 7.10.1 I started noticing that my shakefile would lock up on exit. It's after the 'main' function exits, and none of the shake tests have a

ghc 7.10.1 hard lock on exit with shake, OS X 10.10

After I upgraded to 7.10.1 I started noticing that my shakefile would lock up on exit. It's after the 'main' function exits, and none of the shake tests have a problem, so presumably it's a GHC thing, that shake somehow causes to happen. Only kill -9 gets it to quit. Here's a stack trace from

-prof, -threaded, and -N

Hi, The behavior of the -N flag (without argument) with the profiling runtime seems inconsistent compared to the behavior without profiling. The following program ``` module Main where import GHC.Conc main :: IO () main = print numCapabilities ``` when compiled with `ghc -threaded

Re: ghc 7.10.1 hard lock on exit with shake, OS X 10.10

On Tue, Jun 2, 2015 at 7:20 PM, Carter Schonwald carter.schonw...@gmail.com wrote: could you share a minimal program that reproduces the problem? That's the thing, it's a thousand line shakefile that builds a 100k line program, and it's happening only rarely now. Since it happens so rarely it

Re: HEADS UP: Final call for 7.10.2 is soon

On Jun 2, 2015 6:03 PM, Wolfgang Jeltsch g9ks1...@acme.softbase.org wrote: Hi, bug #10009 appears on the status page with status “new”, although the bug should have been fixed in HEAD. Can this fix *please* be a part of GHC 7.10.2? At the moment, this bug breaks the incremental-computing

Re: Arithmetic overflow in rem and mod

The current behavior is quite intentional. On Mon, Jun 1, 2015 at 1:23 PM, David Feuer david.fe...@gmail.com wrote: I think this is a mistake, yes. They should not raise such exceptions, but rather just wrap around—minBound `quot` (-1) should be -minBound=minBound. That would justify the

Ambiguity check and type families

Hi, the following (contrived) code is accepted by GHC 7.8.3, but not 7.10.1: {-# LANGUAGE TypeFamilies #-} type family F a :: * type family G b :: * x :: G (F a) ~ a = F a x = undefined GHC 7.10.1 reports: Could not deduce (F a0 ~ F a) from the context (G (F a) ~ a) bound by

Re: Ambiguity check and type families

Hi, that's an interesting example. To me this looks like a bug in GHC, although the issue is certainly a bit subtle. The reason I think it is a bug is that, if we name all the type functions in the signature and apply improvements using the fact that we are working with functions, then we get:

Re: Ambiguity check and type families

Hi Wolfgang, https://ghc.haskell.org/trac/ghc/ticket/10009 might be the same regression (fixed in HEAD) Regards, Adam On Tue, Jun 2, 2015 at 12:28 PM, Wolfgang Jeltsch g9ks1...@acme.softbase.org wrote: Hi, the following (contrived) code is accepted by GHC 7.8.3, but not 7.10.1: {-#