summaryrefslogtreecommitdiff
path: root/test/files/pos/t6499.scala
diff options
context:
space:
mode:
authorPaul Phillips <paulp@improving.org>2012-10-10 10:57:14 -0700
committerPaul Phillips <paulp@improving.org>2012-10-10 15:06:03 -0700
commitee7f1e8a82fcb81d5ff2b017daf52fc929ce9444 (patch)
tree8491dd51ebf6ba808d6b247c4fd1483dee3e2cb4 /test/files/pos/t6499.scala
parent557a9bd1309d2de6679e158769955cce3da6433b (diff)
downloadscala-ee7f1e8a82fcb81d5ff2b017daf52fc929ce9444.tar.gz
scala-ee7f1e8a82fcb81d5ff2b017daf52fc929ce9444.tar.bz2
scala-ee7f1e8a82fcb81d5ff2b017daf52fc929ce9444.zip
Fix for SI-6499, regression in type inference.
I can't do any better than a reproduced comment: For some reason which is still a bit fuzzy, we must let Nothing through as a lower bound despite the fact that Nothing is always a lower bound. My current supposition is that the side-effecting type constraint accumulation mechanism depends on these subtype tests being performed to make forward progress when there are mutally recursive type vars. See pos/t6367 and pos/t6499 for the competing test cases.
Diffstat (limited to 'test/files/pos/t6499.scala')
-rw-r--r--test/files/pos/t6499.scala3
1 files changed, 3 insertions, 0 deletions
diff --git a/test/files/pos/t6499.scala b/test/files/pos/t6499.scala
new file mode 100644
index 0000000000..db376572ee
--- /dev/null
+++ b/test/files/pos/t6499.scala
@@ -0,0 +1,3 @@
+object Test {
+ Map(): Map[_, Int] with Map[_, Int]
+}