Théo FIDRY

The downside of that is that: - You cannot use a more exotic name if you want to - You cannot force infection to pick `infection.json.dist` over `infection.json` in any...

Maybe an easier way to approach this would be to allow to change the working directory like composer does: ``` $ composer --working-dir=/path/to/... ```

What's the goal of the post-filtering exactly?

IMO that would require a lot more than a post-filtering hook then. Because the current suggested hook provides a closed (already executed) process and not much more and is currently...

maybe a `composer why infection/infection` would tell? Btw it's usually better to do (provided it's an app not a lib) `composer update xx/yy` eventually with the `--with-dependencies` flag than removing...

For more granularity. Let's consider the following: ``` // src/Acme/Foo.php class Foo {...} // tests/Acme/FooTest.php /** @covers \Acme\Foo */ class FooTest extends TestCase { function test_fast_method() {...} -> exec time...

Regarding the `Coalesce` removal case, maybe we could rename it to `RemoveCoalesce`? As you suggested otherwise: we can also decide to not touch them in those cases... >Regarding BC break:...

It should be `-cfile` but yes, ultimately we are just using the Symfony Console component so there is not much we can do here unless we try to tweak it,...

>It shouldn't be necessary to specify the command in a single-command application. It's unlikely it will remain so in the coming months >Even if this is an upstream bug, this...

I'm not entirely convinced the proposed PR is the way to go and it's quite old as well. Instead I would rather recommend to use the scoped PHAR here instead...