Kevin Reid

Another thing that is currently undocumented is async block/fn future types, as types. I filed #1555 for that.

> You need `cd` into any crate first. Tiny nitpick: `cd` isn't strictly necessary; you can also do `wasm-pack test some-package-directory/`.

Since `bevy_tasks` is in our dependency graph, we should consider using its compute task pool functionality, but I have not looked at how well it fits in, such as how...

Lint jobs are failing because `RUSTFLAGS=-Dwarnings` in the environment overrides `build.rustflags` in `.cargo/config.toml`. I am still thinking about what to do about this. Some possibilities: * have xtask take a...

> Another part of it is that in many cases I would prefer to avoid false-positives. Especially if I am new to mutation testing I might want to get more...

Isn't this lint named backwards? Lints are named for what they report, not what they suggest you do instead, and this lint is objecting to unused names and suggesting an...

I'm seeing the same thing with other lints, e.g. ```rust //! crate docs #![warn(missing_docs)] #[expect(missing_docs)] // warning: this lint expectation is unfulfilled pub fn foo() {} ``` rust-analyzer version: 0.3.2086-standalone...

If the cause is exactly as described, perhaps a simple fix for this would be to add: ```rust impl Drop for ComputePass { fn drop(&mut self) {} } impl Drop...

I was just working on improving some `Arbitrary` implementations, and I think un-splitting `try_size_hint` would be very much worthwhile to reduce the number of possible mistakes. Other suggestions: * #201...

P.S. I'd be happy to try writing a PR for the `SizeHint` breaking change if there is interest.