Maks Rafalko

> I don't think it does. This is a testing tool's job. E.g. PHPUnit's. Exactly. I guess it's here https://github.com/sebastianbergmann/php-code-coverage/blob/28efe6950c2c3ceb86f0fc63aa077617950c78c5/src/CodeCoverage.php#L891-L908

Duplicate of https://github.com/infection/infection/issues/34 This is how coverage looks like: It boils down to how PHP works internally, please read exactly the same issue we created earlier https://github.com/infection/infection/issues/34 See Derick's explanation...

Probably, as a quick fix, it makes sense to not mutate `switch(false)` to `switch(true)` and vice-versa since we know it is always marked as `Not Covered`. What do you think...

> Is the switch **never** covered? I only saw not covered `switch` line for `true`/`false`. Just tried with an expression, and it is covered --- Let's do a quick fix...

@Ocramius friendly reminder about this PR

I like how these 2 groups are split, makes sense. Explaining this to our users is a nice thing as well. Didn't dig into all these options of PHPUnit and...

Hello, thanks for reporting an issue. Unfortunately, I don't have windows machine and won't be able to debug it in the near future, so any help is appreciated here.

> I assume we need to update conflicts section once fix is released but in this case, all users on macos/linux won't be able to use Codeception 3.x with Infection,...

👍 @BackEndTea did something similar for arrays

[HTML](https://infection.github.io/guide/usage.html) logger has such information. When Mutant is escaped:  or killed:  Example report: https://infection.github.io/static/html-report-example.html#mutant Does it solve your issue? Or do we need to add this information to...