Re: [GHC] #3714: Improve error message if an associated family declaration has excess parameters

2009-12-09 Thread Stefan Holdermans
Simon, Regarding distinguishing between type indices and parameters, you suggested: type family T3 f !e :: * -- The ! indicates a type parameter (not an index) I'd rather have indices, rather than parameters, explicated by mean of syntax. This seems more consistent with

Re: [GHC] #3714: Improve error message if an associated family declaration has excess parameters

2009-12-09 Thread Stefan Holdermans
Simon, type family T3 {|f|} e :: * Indeed. But do you want to use that syntax for class parameters too? That would be a big change class C {|a|} where Well... That would be the most consistent then. But... it looks weird. And it breaks code, of course. One could argue

Re: bug with type families

2008-06-02 Thread Stefan Holdermans
Peter, I've run into a bug that looks to be the same as the one described here: http://hackage.haskell.org/trac/ghc/ticket/1897 It does not seem like a bug, although the type-error message may be a bit confusing as is the fact that GHC happily infers a type for the signature-less

Re: [GHC] #1412: Typo in type error for lazy patterns

2007-06-05 Thread Stefan Holdermans
My apologies for the duplicated ticket; I ran into a database lock... On Jun 5, 2007, at 8:45 AM, GHC wrote: #1412: Typo in type error for lazy patterns -- +- Reporter: [EMAIL PROTECTED] | Owner:

Re: no happy

2006-11-03 Thread Stefan Holdermans
Christian, This did the trick for me when I built Happy (just yesterday): LALR.lhs: change line 24 from import Data.Array hiding (bounds) into import Data.Array ProduceCode.lhs: change line 31 from marray_indices a = Data.Array.MArray.indices a into marray_indices a = range

Re: unexpected arithmetic sequence and deriving Enum behaviour

2006-06-30 Thread Stefan Holdermans
Simon, Laszlo presented some code: Consider the following code fragment: data Colour = Red | Black | Blue deriving (Show, Bounded) instance Enum Colour where ... and then remarked: Notice that there is no deriving Enum (which would be an error according to the Report) You asked: Why