Kevin Reid

> This log looks like it can happen on vk too, probably other backends as well. Yep, just had a macOS flake in the same test case I originally posted:...

I wrote the original issue simply as “here is a discrepancy with the spec” without further thought, but here are some further thoughts: My use of `wgpu` targets web *and*...

I've rebased, but I noticed something weird while working with git on it: the affected files seem to have CRLF line endings (even though the `.editorconfig` file suggests the repo...

Two ideas for possible API enhancements based on examining @tvallotton 's branch: * The entire `alloc::task` module is currently conditional on `cfg(target_has_atomic = "ptr")`, but with the addition of `LocalWaker`,...

> Deleting single statements seems to have a lot of potential too, although it would make a lot of mutants There could be categorical mutations like “delete all statements that...

Note that because Nextest runs every test in a separate process, it may be significantly slower in the case where tests use a costly lazy-static initializer (as I found out...

@nyurik As I wrote when I filed this issue: > At a minimum, the lint documentation should acknowledge that adding `Eq` constrains future choices. I have no strong opinion on...

What about, by default, running the baseline only if there is a test that _never passes_ in (any of | the first N) mutants? That way it would get “real...

Done. I notice that `async_executor.rs` now has LF endings, but `benchmarking_async.md` still has CRLF. The PR should be consistent with existing text in each file.

> `FeatureSupport::from_bits_retain(FeatureSupport::WRITE_KEYBOARD.bits() | FeatureSupport::WRITE_MOUSE.bits())` You can write this as `FeatureSupport::WRITE_KEYBOARD.union(FeatureSupport::WRITE_MOUSE)`. [The generated `union()` method](https://docs.rs/bitflags/2.4.2/bitflags/example_generated/struct.Flags.html#method.union) is const.