#7220: Confusing error message in type checking related to type family, fundep,
and higher-rank type
--+-
Reporter: tsuyoshi | Owner: simonpj
Type: bug
#7220: Confusing error message in type checking related to type family, fundep,
and higher-rank type
+---
Reporter: tsuyoshi | Owner: simonpj
Type: bug
#7220: Confusing error message in type checking related to type family, fundep,
and higher-rank type
--+-
Reporter: tsuyoshi | Owner:
Type: bug | Status
#7220: Confusing error message in type checking related to type family, fundep,
and higher-rank type
--+-
Reporter: tsuyoshi | Owner:
Type: bug | Status
#5763: Confusing error message
-+--
Reporter: simonpj | Owner: simonpj
Type: bug | Status: new
Priority: high
#5763: Confusing error message
-+--
Reporter: simonpj | Owner:
Type: bug | Status: new
Priority: normal
#5763: Confusing error message
-+--
Reporter: simonpj | Owner:
Type: bug | Status: new
Priority: high
#5763: Confusing error message
-+--
Reporter: simonpj | Owner:
Type: bug | Status: new
Priority: high
#4099: Slighlty confusing error message with data families
--+-
Reporter: rl | Owner:
Type: bug | Status: closed
#4099: Slighlty confusing error message with data families
-+--
Reporter: rl| Owner:
Type: bug | Status: new
Priority: normal
#2900: Confusing error message for monadic function with wrong number of
arguments
+---
Reporter: tim |Owner:
Type: bug | Status: new
#2900: Confusing error message for monadic function with wrong number of
arguments
+---
Reporter: tim |Owner:
Type: bug | Status: new
#2900: Confusing error message for monadic function with wrong number of
arguments
-+--
Reporter: tim | Owner:
Type: bug | Status: new
#2371: `ghci` prints confusing error message if using :m + instead of :load
-+--
Reporter: bos | Owner:
Type: bug | Status: closed
Priority: normal | Milestone
#2371: `ghci` prints confusing error message if using :m + instead of :load
+---
Reporter: bos | Owner:
Type: bug | Status: new
Priority: normal | Component
#1888: Slightly confusing error message for duplicate NOINLINE pragmas
---+
Reporter: tim| Owner: igloo
Type: merge | Status: closed
Priority: normal
#1888: Slightly confusing error message for duplicate NOINLINE pragmas
---+
Reporter: tim| Owner: igloo
Type: merge | Status: new
Priority: normal
#1888: Slightly confusing error message for duplicate NOINLINE pragmas
--+-
Reporter: tim| Owner:
Type: bug| Status: new
Priority: normal
#1310: confusing error message when trying to give a type-signature to an
imported
symbol
-+--
Reporter: Isaac Dupree |Owner:
Type: bug | Status: closed
Priority: normal
#1310: confusing error message when trying to give a type-signature to an
imported
symbol
---+
Reporter: Isaac Dupree | Owner:
Type: bug | Status: new
Priority: normal
Submitted By: Wolfgang Thaller (wthaller)
Assigned to: Nobody/Anonymous (nobody)
Summary: Confusing Error Message if package-name is omitted
Initial Comment:
I compiled a library as a GHC package without adding the appropriate
package-name flag to the ghc command line.
When trying to compile
Good point. Error message improved, regression test added.
Thanks for the suggestion
Simon
| -Original Message-
| From: Dean Herington [mailto:[EMAIL PROTECTED]]
| Sent: 05 February 2003 19:14
| To: [EMAIL PROTECTED]
| Subject: confusing error message
|
| buzzard(118)% cat Bug5.hs
/Anonymous (nobody)
Summary: Confusing Error Message if package-name is omitted
Initial Comment:
I compiled a library as a GHC package without adding the appropriate package-name flag
to the ghc command line.
When trying to compile a module that used the package, ghc complained that it couldn't
find
buzzard(118)% cat Bug5.hs
import Control.Monad.State
data S = S Int
newtype M a = M (StateT S IO a)
deriving (Monad)
main = return ()
buzzard(119)% ghc -c Bug5.hs
Bug5.hs:3:
Can't make a derived instance of `Monad M'
(too hard for cunning newtype deriving)
When deriving instances
ghc-4.04 gives the following confusing error message:
compiling with ghc-4.04 -fglasgow-exts -c Test.hs
Test.hs:8:
None of the type variable(s) in the constraint `Eq a'
appears in the type `Set a - Set a - Set a'
In the type signature for `unionSets'
Compilation had errors
Simon wrote:
I know about this one, but haven't got around to fixing it yet. The parse
error is on a semicolon generated by the layout system, as you probably
guessed, which is why there's no token available to print in the error
message. Any thoughts on what a suitable error message should
Main.hs:3: parse error on input ';' (inserted by layout)
Incomplete expression on previous line or incorrect
indentation of the current line.
I think Manuel's suggestion is a definite improvement here.
For interest, another Haskell compiler, nhc98, gives the message
4:5
For
foo = let
x = (1, 2
y = 3
in
fst x + y
GHC 4.04 gives me
Main.hs:3: parse error on input `'
Interesting, but not very informative ;-)
I know about this one, but haven't got around to fixing it yet. The parse
error is on a semicolon generated
For
foo = let
x = (1, 2
y = 3
in
fst x + y
GHC 4.04 gives me
Main.hs:3: parse error on input `'
Interesting, but not very informative ;-)
I also have the feeling that GHC is sometimes off by a
couple of lines when reporting errors in bigger modules -
I encountered a confusing error message, which you can
reproduce with
type P a = Maybe a
instance Monad P where
(=) = error "foo"
return = error "bar"
I get
bug.hs:5: `P' should have 1 argument, but has been given 0 .
Would it
Hi GHC-Developers!
I encountered a confusing error message, which you can
reproduce with
type P a = Maybe a
instance Monad P where
(=) = error "foo"
return = error "bar"
I get
bug.hs:5: `P' should have 1 argument, but has been given 0 .
with
**
I encountered a confusing error message, which you can
reproduce with
type P a = Maybe a
instance Monad P where
(=) = error "foo"
return = error "bar"
I get
bug.hs:5: `P' should have 1 argument, but has been given 0 .
Would it
32 matches
Mail list logo