#1446: -fallow-incoherent-instances suggested when already used
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 6.6.1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Os: Unknown | Testcase:
Architecture: Unknown |
----------------------------------+-----------------------------------------
Comment (by guest):
I thought I should add a bit more detail about this. I saw it with Windows
ghc 6.6.1 FWIW. The scenario is you write some code which won't compile
(ghc giving an error message
suggesting using this flag will fix the problem). You recompile with this
flag and get exactly the same error message. There are 2 things wrong with
this IMO:
1- (Ideally) ghc should not advise the use of a flag unless it really will
fix the immediate problem.
2- It should not give an error message advising the use
of a flag which has already been used.
The current behaviour leaves the user (me in this case) wondering if the
compiler really knows what it's talking about and whether there really is
a problem in the code or if this is a *real* bug in the compiler (rather
than just bad
choice of error messages).
Adrian Hey
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1446>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
