Alexander Weigl

The target is not to have a `tree-sitter` integration. The target would rather allow a generic program, that can be triggered from jplag and returns a JSON (or whatever format)...

@jwiesler Sources of key-javaparser are now available via maven.

contraposition loads again. Syntax changes to `catch #cs` were necessary.

> @wadoon tests are not able to resolve `java.lang.Object`. Since you wrote this dynamic symbol solver, could you take a look? Is this the error message of ``` Caused by:...

I am stuck at the circular problem: 1. The symbol solver loads `CompilationUnit`s via `JavaParserTypeSolver` requested upon type resolution. 2. KeY loads Redux in one chunk in `parseLibraryClasses0`, incl. pre-transformation....

> Nope, what I meant is this one (thrown by most tests): Could you point me to one test case?

We have an error in the pre-transformation pipeline. `arg0` can not be resolved in the code below. Looking at the generated (excerpt below), we see the generation has produced garbage...

> * Lots of duplicate registration of XX that should not happend (many of them are definitely not the same) This may arise by two things: (1) I believe that...

> * `TestJP2KeY`: Unsolved symbol `java.lang.Object`, `int` (?!) and parsing errors `Illegal left hand side of an assignment` `int` problem fixed. Use of wrong class `new ClassOrInterfaceType("int");` instead of `new...

> * `Illegal left hand side of an assignment` There are some simple checks inside JavaParser, look into `CommonValidators.java`. There are some strange expression. How should the precedence? We have...