From 6c7b003003e6cb6a1f0b00f79f784e6deea37a39 Mon Sep 17 00:00:00 2001 From: Eugene Burmako Date: Sat, 7 Dec 2013 16:39:42 +0100 Subject: 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. --- src/compiler/scala/tools/nsc/typechecker/Namers.scala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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) } -- cgit v1.2.3