summaryrefslogtreecommitdiff
path: root/testsuite/tests/ghc-regress/typecheck/should_compile/tc003.hs
diff options
context:
space:
mode:
Diffstat (limited to 'testsuite/tests/ghc-regress/typecheck/should_compile/tc003.hs')
-rw-r--r--testsuite/tests/ghc-regress/typecheck/should_compile/tc003.hs12
1 files changed, 0 insertions, 12 deletions
diff --git a/testsuite/tests/ghc-regress/typecheck/should_compile/tc003.hs b/testsuite/tests/ghc-regress/typecheck/should_compile/tc003.hs
deleted file mode 100644
index 70459c3443..0000000000
--- a/testsuite/tests/ghc-regress/typecheck/should_compile/tc003.hs
+++ /dev/null
@@ -1,12 +0,0 @@
-module ShouldSucceed where
-
--- This is a somewhat surprising program.
--- It shows up the monomorphism restriction, *and* ambiguity resolution!
--- The binding is a pattern binding without a signature, so it is monomorphic.
--- Hence the types of c,d,e are not universally quantified. But then
--- their type variables are ambiguous, so the ambiguity resolution leaps
--- into action, and resolves them to Integer.
-
--- That's why we check the interface file in the test suite.
-
-(c@(d,e)) = if True then (1,2) else (1,3)