Commit d87dd691 authored by simonpj's avatar simonpj
Browse files

[project @ 2005-02-07 10:15:21 by simonpj]

Accept output
parent 8aec127e
......@@ -6,3 +6,4 @@ tcfail008.hs:3:6:
Possible cause: the monomorphism restriction applied to the following:
o :: [a] (bound at tcfail008.hs:3:0)
Probable fix: give these definition(s) an explicit type signature
or use -fno-monomorphism-restriction
tcfail010.hs:3:16:
tcfail010.hs:3:17:
Ambiguous type variable `a' in the constraint:
`Num [a]' arising from use of `+' at tcfail010.hs:3:16
`Num [a]' arising from the literal `2' at tcfail010.hs:3:17
Possible cause: the monomorphism restriction applied to the following:
q :: [a] -> [a] (bound at tcfail010.hs:3:0)
Probable fix: give these definition(s) an explicit type signature
or use -fno-monomorphism-restriction
......@@ -5,3 +5,4 @@ tcfail018.hs:5:9:
Possible cause: the monomorphism restriction applied to the following:
a :: a (bound at tcfail018.hs:5:1)
Probable fix: give these definition(s) an explicit type signature
or use -fno-monomorphism-restriction
tcfail040.hs:19:4:
tcfail040.hs:19:13:
Ambiguous type variable `a' in the constraint:
`ORD a' arising from use of `<<' at tcfail040.hs:19:4-7
`ORD a' arising from use of `<<' at tcfail040.hs:19:13-16
Probable fix: add a type signature that fixes these type variable(s)
......@@ -5,3 +5,4 @@ tcfail043.hs:38:16:
Possible cause: the monomorphism restriction applied to the following:
search :: a -> [a] -> Bool (bound at tcfail043.hs:37:0)
Probable fix: give these definition(s) an explicit type signature
or use -fno-monomorphism-restriction
......@@ -2,5 +2,6 @@
tcfail130.hs:10:0:
Implicit parameters escape from the monomorphic top-level binding(s) of `foo':
?x::Int arising from use of `woggle' at tcfail130.hs:10:6-11
Probably fix: add type signatures for the top-level binding(s)
Probable fix: give these definition(s) an explicit type signature
or use -fno-monomorphism-restriction
When generalising the type(s) for `foo'
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment