RE: extra ambiguous type variable errors after a couldn't match error?

2014-07-17 Thread Simon Peyton Jones
errors after a couldn't | match error? | | 7.8.3 has a new behaviour where a plain type error will cause | ambiguous type variable errors, e.g.: | | module M where | | broken :: [Int] | broken = () | | ambiguous :: a - [String] | ambiguous _ = map show [1..] | | When imported in ghci, I get

Re: extra ambiguous type variable errors after a couldn't match error?

2014-07-17 Thread Evan Laforge
On Thu, Jul 17, 2014 at 2:02 AM, Simon Peyton Jones simo...@microsoft.com wrote: Good point! See https://ghc.haskell.org/trac/ghc/ticket/9323 Ah, fixed in the next release. Ok, that's good enough for me, it's only a minor annoyance. ___

extra ambiguous type variable errors after a couldn't match error?

2014-07-16 Thread Evan Laforge
7.8.3 has a new behaviour where a plain type error will cause ambiguous type variable errors, e.g.: module M where broken :: [Int] broken = () ambiguous :: a - [String] ambiguous _ = map show [1..] When imported in ghci, I get: M.hs:4:10: Couldn't match expected type ‘[Int]’ with actual