Out of 5 occurrences of `askLoadedTyped` and 4 occurrences of `loadedType`
(non-definitional), I have manually set the `keepLoaded` parameter to the
non-default true in two of them. That is because, of course, because it is
necessary and tested to be so. In the particular case of occurrences,
scala-refactoring depends on a global "load-all-before-index" and
"remove-all-after" semantics (see [thic comment](
https://www.assembla.com/spaces/scala-ide/tickets/1001388-%60loadedtype%60-keeps-files-loaded-in-the-pc?comment=208788443#comment:208788443)
by Mirko.

I currently do not know how to refactor scala-refactoring quickly to load
files parcimoniously throughout the index building process, and therefore
would have difficulty removing that boolean very quickly. But I can switch
to focusing on this if you consider it a blocker for this PR.

--
FG



On Wed, Nov 20, 2013 at 12:21 AM, Iulian Dragos <notifications@github.com>wrote:

> In
> org.scala-ide.sdt.core/src/scala/tools/eclipse/javaelements/ScalaCompilationUnit.scala:
>
> > @@ -250,7 +250,7 @@ trait ScalaCompilationUnit extends Openable
> >    override def reportMatches(matchLocator : MatchLocator, possibleMatch : PossibleMatch) {
> >      doWithSourceFile { (sourceFile, compiler) =>
> >        val response = new Response[compiler.Tree]
> > -      compiler.askLoadedTyped(sourceFile, response)
> > +      compiler.askLoadedTyped(sourceFile, true, response)
>
> I think the intent of that ticket was to be fixed by *not* keeping those
> units loaded. So I'd change it to false, as Mirco suggests. I think this is
> the best moment to do it :)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/scala-ide/scala-ide/pull/562/files#r7777030>
> .
>