Marc R. Hoffmann

@lolo101 This project is maintained by two people in their spare time. We well aware of the list of bugs and feature request. The more people waste our time with...

@lolo101 Thanks for picking this up! If you look at the assertion method in [SwitchExpressionsTest.java](https://github.com/jacoco/jacoco/blob/master/org.jacoco.core.test.validation.java14/src/org/jacoco/core/test/validation/java14/SwitchExpressionsTest.java) you see that some lines are always party covered (different lines, depending on the compiler)....

@lolo101 If you create a PR we will automatically run the tests with all JDK compilers (Java 5 - Java 21) as well as ECJ compiler. Typically avoid manual testing....

@nick2525 That's why the bug is "Open". Also please see our FAQ: > **When will feature X be released?** > > JaCoCo is maintained by volunteers in their free time....

Please provide a reproducer (e.g. small GitHub project) where we can analyze the problem. Thx!

@leslieli Unfortunatelly we cannot debug screenshots. If you want us to analyze this please provide a minimal reproducer (GitHub project) which we can analyze.

As described in #1412 it looks like only the Kotlin compiler may create such bytecode.

@vvictor10 The lambda is compiled to a separate method. This is a known limitation of annotations. To fix this we would need to analyze the call hierarchy, like "if a...

@vvictor10 We don't collect call stacks at runtime (that would be way too much runtime overhead). Theoretically this would be possible also with static analysis.

Hi @Godin, I wonder whether we still want to provide Eclipse .project and .classpath files like for the other projects (disclaimer: JavaSE-20 is not yet supported by latest Eclipse).