Recently introduced error: ParseTree no longer passes TC

[PaulKlint]

It seems that we have entered an unstable phase in the development since various library files that did compile fine, now suddenly give problems. Here is a first example, in our good old friend ParseTree. Compiling it

rascal>import experiments::Compiler::Compile;
ok
rascal>compile(|rascal:///ParseTree.rsc|, recompile=true);

gives

error("Name r is not in scope",|rascal:///ParseTree.rsc|(19115,1,<512,10>,<512,11>))
error("Function of type fun TreeSearchResult[&T \<: Tree](type[&T \<: Tree], loc, Tree) cannot be called with argument types (type[&T \<: Tree],loc,Tree)",|rascal:///ParseTree.rsc|(19084,17,<511,76>,<511,93>))
|rascal://experiments::Compiler::Rascal2muRascal::RascalModule|(2652,25,<80,12>,<80,37>): "Module contains errors!"

The offending code is:

public TreeSearchResult[&T<:Tree] treeAt(type[&T<:Tree] t, loc l, a:appl(_, _)) {
    if ((a@\loc)?, al := a@\loc, al.offset <= l.offset, al.offset + al.length >= l.offset + l.length) {
        for (arg <- a.args, TreeSearchResult[&T<:Tree] r:treeFound(&T<:Tree _) := treeAt(t, l, arg)) {
            return r;  <===== offending occurrence
        }

        if (&T<:Tree tree := a) {
            return treeFound(tree);
        }
    }
    return treeNotFound();
}

[PaulKlint]

Although ParseTree.rsc seems to be the main culprit, various other libraries importing it are affected as well. My guess is that it has to do with the resolution of parameterized, overloaded functions.

Any help is welcome.

[mahills]

Sorry about that, this is now fixed. There was an error in the type matching code related to reified types.