Ralf Hinze writes:
Dear bug chasers,
ghc's latest version sometimes misses conflicting function definitions.
Consider the following *wrong* program:
Hi,
thanks for the report - this is due to a parser problem of signalling
when a toplevel value declaration ends. To fix, apply the
Mariano Suarez Alvarez writes:
after configuring and `making boot', when I `make all', when make gets to
/fptools/ghc/compiler, I get an error I can't fix because I really haven't
understood the Makefile structure.
"parser/U_binding.hs", line 6, column 22: can't find interface (.hi)
This bug was mentioned during ghc-2.03's time. I thought it had been
fixed since. But the following code still does not compile in ghc-2.04:
--
data X = A {a :: Int} | B {a :: Int}
--
test2.lhs:2:
Conflicting definitions for: `a'
Defined
Sigbjorn Finne wrote:
Einar Wolfgang Karlsen writes:
I am using the MatchPS module for loads of tool integration tasks (peeking
into the output from those tools looking for important signs and relevant
messages).
Unfortunately, MatchPS.matchPS seems to be quite restrictive wrt.
Einar Wolfgang Karlsen writes:
I am using the MatchPS module for loads of tool integration tasks (peeking
into the output from those tools looking for important signs and relevant
messages).
Unfortunately, MatchPS.matchPS seems to be quite restrictive wrt. the
size of the string
Marc van Dongen writes:
Sorry if this is caused by exactly the same as my last tcLookupTyVar
report. Since I can't tell, I'll report it anyway.
panic! (the `impossible' happened):
tcLookupTyVar:a_r6F
Please report it as a compiler bug to [EMAIL PROTECTED]
Fixed in
