haskell / error-messages

haskell/error-messages Issues

Bad error message on malformed class method type signature
Updated 7 months ago
Make it simpler to identify that the RTS is causing an error
Updated 10 months ago
Helpful "not in scope before the splice" went missing in 9.0
Updated a year ago6
Terrible Arity error messages
Updated a year ago
Type error message overhaul
Updated a year ago7
"In a stmt of an interactive GHCi command: print it"
Updated a year ago1
Better error messages for top level declarations (module, import)
Updated a year ago
Escaping skolems (e.g. with `runST`) are not mentioned in GHC >= 9.2
Updated a year ago
[Meta] Add a description to this repository
Updated a year ago
"Cannot apply expression of type `X` to a visible type argument `Y`" for inferred (braces) type arguments
Updated a year ago
Better suggestion for data constructors import list
Updated a year ago2
Inclusion criteria
Closed 2 years ago3
Selecting a nonexistent field using record dot yields error about missing HasField instance
Updated 2 years ago3
Put blank line after the error
Closed 2 years ago2
Type equality constraints without signatures
Updated 2 years ago1
Better error message for out of scope data constructor if a type with the same name exists
Updated 2 years ago2
Inaccessible binding in the same decl group is suggested in view pattern
Updated 2 years ago2
Suggest language extension for unlifted data family
Updated 2 years ago1
GHC will recommend a module that is hidden
Updated 2 years ago4
Cabal and GHC environment file related errors
Updated 2 years ago2
"Data Constructor not in Scope" when defining an operator function starting with `:`
Updated 2 years ago3
Unbound variable in a pattern synonym
Updated 2 years ago1
Type classes, functional dependencies, and arity
Updated 2 years ago1
could not deduce [instance]
Updated 2 years ago2
"X has fields" error doesn't tell me what the problem is (`-XOverloadedRecordDot`)
Updated 2 years ago4
Add suggestions in "not a (visible) method"
Updated 2 years ago1
NB -> Note
Updated 2 years ago
Cabal should warn more strongly about outdated hackage indexes
Updated 2 years ago
The constraint ... is no smaller than the instance head... (Use UndecidableInstances ...)
Updated 2 years ago7
Type families that are not injective give rise to confusing erorrs.
Updated 2 years ago
Update url
Closed 2 years ago4
`TypeApplications` not suggested when used with function arrow `->`
Updated 2 years ago1
The index and the future of this repository
Closed 2 years ago8
Improve "unification involving polytypes" message
Updated 2 years ago2
"Cannot apply expression [...] to a visible type argument" does not explain the problem
Updated 2 years ago4
Parse errors should include context
Updated 2 years ago
A warning for the monomorphism restriction
Updated 2 years ago7
Inappropriate error message for ambiguous record updates
Updated 2 years ago6
Don't suggest adding constraints to methods and/or functions from other packages
Updated 2 years ago
do desugaring yields confusing errors when the argument count is wrong
Updated 2 years ago9
Negative reasoning for type classes to make better errors
Updated 2 years ago8
Type variables versus unification variables
Updated 2 years ago7
Don't suggest turning on typeclass extensions that don't help
Updated 2 years ago2
Suggest -XMagicHash where appropriate
Updated 2 years ago8
Potentially confusing "Pattern match is redundant" with single alternative case/pattern binding
Updated 2 years ago2
Not a data constructor clarity
Updated 2 years ago1
Add to build-depends in your cabal file
Updated 2 years ago1
Custom error for tuple arg when multiple args are expected
Updated 2 years ago
Better error messages by adding impossible instances
Closed 2 years ago16
Binding representation-polymorphic values
Closed 2 years ago2