Emil Ejbyfeldt

Seems like `Ordering` can just be replace with some other type class. This still fails on both 2.12.16 and 2.13.8 ``` trait A[T] trait B[T] object Test { implicit def...

> If we simplify the code even further, then it fails in both 2.12.16 and 2.13.8 How do we no know that we are still triggering the same issue and...

Yeah, that is true that it differnt from the `Ordering` version in that way. But the compiler error it gives ``` diverging implicit expansion for type A[B[String]] starting with method...

I tried 4 different version of javac from openjdk: ``` $ javac -version javac 18.0.2 $ javac -version javac 17.0.4.1 $ javac -version javac 11.0.16.1 $ javac -version javac 1.8.0_345...

I tried with 2e0cc5fc6aa8b8020a84437a0ac4a7befb99969b but that still gives the same compile error before. I belive the problems is that place where we call `findMostSpecificIInvocable` https://github.com/janino-compiler/janino/blob/2e0cc5fc6aa8b8020a84437a0ac4a7befb99969b/janino/src/main/java/org/codehaus/janino/UnitCompiler.java#L9555-L9561 we call it first with...

We are also seeing this failure on Spark 3.3.1 with Scala 2.13 on Ubuntu 22.04. I used one of the spark applications seeing this issue to further debug when we...

I tried with https://github.com/janino-compiler/janino/commit/e69022f5aaabd36edc08a2074360d62514493a19 and that seems to compile and run both examples in the same way that openjdk does. ``` $ java -cp commons-compiler-3.1.10-SNAPSHOT.jar:janino-3.1.10-SNAPSHOT.jar:. org.codehaus.janino.SimpleCompiler CallValue.java CallValue 5 ```...

@aunkrig I think we might want to reopen this ticket. I found some similar cases that still gives the previous error. This code: ``` $ cat BoxedValueClass.scala package example trait...

I found this comment in the openjdk source code: https://github.com/openjdk/jdk8u/blob/7694663d58434196368193c66225af10e60e1329/jdk/src/share/classes/java/lang/Class.java#L1743-L1752 so it clear by design that the jvm support this flexibility that is not used by the java language. So...

@derekwyatt Are you still maintaining and accepting PRs in this repository? Or should one submit such fixes directly to the vim repository?