Martin Pool

For example it might be nice if you could `use cargo_mutants_schema::Outcomes` to parse the output file. Nextest does this pattern in `nextest-metadata`. See also #330 although neither needs to block...

Like https://github.com/sourcefrog/conserve/commit/77d72341b8b6153ca6b7645fac8662f82315e053

https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions#adding-a-job-summary

It would be good for the manual to have a single page listing all options, with their config and command line syntax, linking to more detailed descriptions.

- [x] Mention it in the readme and manual - [ ] Build linux/arm64 images: GitHub actions has arm64 workers now but it seems like we need to build both...

In some cases it might be useful to only run the baseline, particularly with `--in-place`. In particular after that the target directory can be copied.

It seems to work OK with cargo-binstall but perhaps would be faster or better with direct support?

A diff is a hint as to what code might most likely be not covered, but it's not conclusive: a diff could cause code elsewhere in the program to now...

Nextest is faster at running _passing_ test suites, but it's often slower at test suites that fail, at least if they have tests split across multiple test targets. And cargo-mutants...