summaryrefslogtreecommitdiff
path: root/test/files/pos/t4975.scala
diff options
context:
space:
mode:
authorJason Zaugg <jzaugg@gmail.com>2012-05-21 00:04:52 +0200
committerJason Zaugg <jzaugg@gmail.com>2012-05-21 00:04:52 +0200
commit03e6d929ee639de292daa778dde514e1b7014eac (patch)
tree0023a804cfc04aa5c429cb26e55b28e933118c19 /test/files/pos/t4975.scala
parent1f5584fbe183041d4af269278f0125e2f0b94a44 (diff)
downloadscala-03e6d929ee639de292daa778dde514e1b7014eac.tar.gz
scala-03e6d929ee639de292daa778dde514e1b7014eac.tar.bz2
scala-03e6d929ee639de292daa778dde514e1b7014eac.zip
Consider method-scoped companions in the implicit scope.
Fixes SI-4975. I'll reproduce a relevant snippet of dialogue from Namers#companionSymbolOf: /** The companion class or companion module of `original`. * Calling .companionModule does not work for classes defined inside methods. * * !!! Then why don't we fix companionModule? Does the presence of these * methods imply all the places in the compiler calling sym.companionModule are * bugs waiting to be reported? If not, why not? When exactly do we need to * call this method? */ def companionSymbolOf(original: Symbol, ctx: Context): Symbol = { This was one such bug.
Diffstat (limited to 'test/files/pos/t4975.scala')
-rw-r--r--test/files/pos/t4975.scala12
1 files changed, 12 insertions, 0 deletions
diff --git a/test/files/pos/t4975.scala b/test/files/pos/t4975.scala
new file mode 100644
index 0000000000..12d889c0d5
--- /dev/null
+++ b/test/files/pos/t4975.scala
@@ -0,0 +1,12 @@
+object ImplicitScope {
+ class A[T]
+
+ def foo {
+ trait B
+ object B {
+ implicit def ab = new A[B]
+ }
+
+ implicitly[A[B]] // Error
+ }
+}