Nemo157

It would _probably_ make sense to include a general self-reflexive compatibility, having a license that doesn't let itself be linked with code from another identically licensed crate doesn't really make...

You can manually strip dev-dependencies from your `Cargo.toml` before publishing.

[`futures/ci/remove-dev-dependencies`](https://github.com/rust-lang-nursery/futures-rs/tree/master/ci/remove-dev-dependencies) uses `toml_edit` to remove dev-dependencies from a workspace in-place. It's used during CI for testing rather than publishing though, I'm not sure if you'd want to change anything about...

One _major_ user of running tests on published packages is Crater, it's actually in the developers best interests to make sure their tests run from the package so that their...

At least on hyprland it looks like rofi is getting the mouse events always, I guess because it's the only app on the overlay layer.

This could use the [`Formatter::precision`](https://doc.rust-lang.org/stable/std/fmt/struct.Formatter.html#method.precision), e.g. `format!("{0:.1} | {0:.2} | {0}", humantime::format_duration(Duration::from_secs(3661)))` could be `"1h | 1h 1m | 1h 1m 1s"`.

I've been trying to do something similar with my projects recently. The big problem I haven't found a solution to is the contributor experience. I was [experimenting](https://github.com/Nullus157/.github/pull/10) with applying a...

Not just nightly, 1.74 which is going to `beta` in a week has that feature stabilized.

Tool lints are checked by their respective tools. You need to use `cargo rustdoc -- -D rustdoc::missing_crate_level_docs`. That shows a reason why `cargo-lints` took a tool as the first argument,...

You can do something like `RUSTDOCFLAGS=-Drustdoc::... cargo doc --workspace --no-deps` Another reason it'd be great to have all the intricacies handled by a tool like this 😁