summaryrefslogtreecommitdiff
path: root/test/files/neg/t3663.check
diff options
context:
space:
mode:
authorJason Zaugg <jzaugg@gmail.com>2013-06-11 10:56:48 -0400
committerJason Zaugg <jzaugg@gmail.com>2013-06-19 22:48:38 +0200
commite7ac254349e56678824ade3027bca3908882e291 (patch)
tree9b7828b21d418f2ee8830cb07432048c72dea13d /test/files/neg/t3663.check
parenta54d86b5508630a4815ca7f6ca3d5f05b74b1d9f (diff)
downloadscala-e7ac254349e56678824ade3027bca3908882e291.tar.gz
scala-e7ac254349e56678824ade3027bca3908882e291.tar.bz2
scala-e7ac254349e56678824ade3027bca3908882e291.zip
SI-7571 Allow nesting of anonymous classes in value classes
5d9cde105e added deep prohibition of nested classes within a value class. This has the undesirable side effect of prohibiting partial functions literals in method bodies of a value class. The intention of that prohibition was to avoid problems in code using Type Tests, such as: class C(val inner: A) extends AnyVal { class D } def foo(a: Any, other: C) = a match { case _ : other.D } Here, the pattern usually checks that `a.$outer == other`. But that is incongruent with the way that `other` is erased to `A`. However, not all nested classes could lead us into this trap. This commit slightly relaxes the restriction to allow anonymous classes, which can't appear in a type test. The test shows that the translation generates working code.
Diffstat (limited to 'test/files/neg/t3663.check')
0 files changed, 0 insertions, 0 deletions