One of things I've found with higher-level language features in the JVM are instances of this impossible-to-cover scenario (I seem to remember Java try-with-resources is/was much the same). It's really a "limitation" of the compiler not inferring that condition has only one possible outcome, not of Jacoco for correctly interpreting the bytecode it saw.
-- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/f8b3c9c9-bf22-4c7c-a6a5-5d8bac2a2e46%40googlegroups.com.
