Markus Staab

> Ich bin mir aber unsicher, ob das von den Entwicklern verwendet werden würde, wegen der von euch schon genannten Hürden. Ich denke auch dass viele nichtmal normale placeholder kennen/nutzen.....

Jetzt auch als webcomponent https://github.com/fpapado/blurhash-img

thanks for investigating this problem! > This works correctly. I think the users must specify `--test-framework-options` in addition to our `--filter` due to a breaking change in PHPUnit 12: it...

I wonder, why you need `StmtsAwareInterface`. couldn't you instead e.g. introduce a VirtualNode Type (like there are dozens in PHPStan) and do something like ```php final class StatementsAwareNode extends NodeAbstract...

I tried at least 10 different psalm 5.x and 6.x versions. even the latest 7.0.0-beta11.. everytime we get > Uncaught InvalidArgumentException: Could not get class storage for infection\framework\enum\t in phar:///home/runner/work/infection/infection/.tools/psalm/src/Psalm/Internal/Provider/ClassLikeStorageProvider.php:39...

see https://github.com/infection/infection/pull/2565#issuecomment-3501126827 there is a blocking issue, which others also reported already

agree, `--with-timeouts` would be awesome. we could add a hint for this new option in case the summary contains at least 1 timed-out mutant

> or do you want to explain each of `N` mutations that the current mutator does? I think it would be useful to provide a different message per mutation ......

> and the `Definition` class has `remedies` which created exactly for this purpose. interessting.. where do these messages show up? I can't remember seeing advice for a escaped mutant anywhere

> Do we need different text for each mutation of the same mutator? yes - thats at least my idea. I need to find out a good example