diff options
author | Simon Peyton Jones <simonpj@microsoft.com> | 2016-04-21 14:34:07 +0100 |
---|---|---|
committer | Simon Peyton Jones <simonpj@microsoft.com> | 2016-04-22 11:32:39 +0100 |
commit | c2b7a3d9f6ad946a2cb2773e96a377cc2216cb5b (patch) | |
tree | c32da020d781d119b783d0b41f385a6e490e590e /testsuite/tests/th/T11941.stderr | |
parent | 24d3276df62b52bdf720f4789ff9ddbbb7c02cec (diff) | |
download | haskell-c2b7a3d9f6ad946a2cb2773e96a377cc2216cb5b.tar.gz |
Avoid double error on out-of-scope identifier
Trac #11941 demonstrated a case where an out-of-scope error also
gave rise to a (bogus and confusing) stage restriction message.
It's caused by the fact that out-of-scope errors do not stop
renaming, but rather return an "unbound name". We need to
detect this in the stage-restriction test to avoid the double
error. Easy fix.
Diffstat (limited to 'testsuite/tests/th/T11941.stderr')
-rw-r--r-- | testsuite/tests/th/T11941.stderr | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/testsuite/tests/th/T11941.stderr b/testsuite/tests/th/T11941.stderr new file mode 100644 index 0000000000..4508ed3557 --- /dev/null +++ b/testsuite/tests/th/T11941.stderr @@ -0,0 +1,6 @@ + +T11941.hs:7:30: error: + Not in scope: ‘getFrst’ + Perhaps you meant one of these: + ‘getFirst’ (imported from Data.Monoid), + ‘getLast’ (imported from Data.Monoid) |