diff options
author | Eugene Burmako <xeno.by@gmail.com> | 2013-12-07 16:39:42 +0100 |
---|---|---|
committer | Eugene Burmako <xeno.by@gmail.com> | 2013-12-30 19:07:05 +0300 |
commit | 6c7b003003e6cb6a1f0b00f79f784e6deea37a39 (patch) | |
tree | 4550b5c5b752f2430fa59052b9b3c3a414c6e5ae | |
parent | 0019bc2c4b7d89b61c71f18177823afdcd27bb78 (diff) | |
download | scala-6c7b003003e6cb6a1f0b00f79f784e6deea37a39.tar.gz scala-6c7b003003e6cb6a1f0b00f79f784e6deea37a39.tar.bz2 scala-6c7b003003e6cb6a1f0b00f79f784e6deea37a39.zip |
manifests that Namers.mkTypeCompleter is flag-agnostic
When introducing `FlagAgnosticCompleter` and `FlagAssigningCompleter`,
I have overlooked the completers created in namers. These completers
only assign type signatures, not flags, because they are only created
for symbols originating from sources and such symbols have their flags
assigned based on modifiers and source def trees when they are entered.
-rw-r--r-- | src/compiler/scala/tools/nsc/typechecker/Namers.scala | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/compiler/scala/tools/nsc/typechecker/Namers.scala b/src/compiler/scala/tools/nsc/typechecker/Namers.scala index a30198e949..01d61a253e 100644 --- a/src/compiler/scala/tools/nsc/typechecker/Namers.scala +++ b/src/compiler/scala/tools/nsc/typechecker/Namers.scala @@ -1595,7 +1595,7 @@ trait Namers extends MethodSynthesis { val tree: Tree } - def mkTypeCompleter(t: Tree)(c: Symbol => Unit) = new LockingTypeCompleter { + def mkTypeCompleter(t: Tree)(c: Symbol => Unit) = new LockingTypeCompleter with FlagAgnosticCompleter { val tree = t def completeImpl(sym: Symbol) = c(sym) } |