repi
repi
Ah thanks for sharing! Kinda horrible indeed but good to know about!
Still really want this, have so many extra dependencies lingering in our `Cargo.lock` that makes it harder to manage and get a good overview. And it also triggers `cargo-deny` more...
@MarijnS95 do you think these lints are a good fit for y'all also or do you have any exceptions or additions? Interested in getting feedback!
@MarijnS95 sweet, did that include testing the ones under "Considering", surprised the unsafe ones didn't trigger anything for y'all :)
> @repi I don't think we can utilize any of the opinionated extra lints, at least not across our entire project 😬 Fair enough! it took us a while to...
Related issue: https://github.com/rust-lang/cargo/issues/7468
- [x] [`sccache:` sccache no longer works with rustc nightly](https://github.com/mozilla/sccache/issues/488) This is the issue we ran into that caused our CI builds that use the nightly compiler to fail
- [x] [`rust-argon2:` Feature flag for crossbeam / multithreading usage?](https://github.com/sru-systems/rust-argon2/issues/18) Trying to get rid of duplicate crossbeam versions and eventually crossbeam usage at all in the runtime
- [x] [`docs.rs:` Incorrect "no builds" badge shown for complex version string](https://github.com/rust-lang/docs.rs/issues/395)
- [x] [`getrandom:` 0.1.9 seems to have broken wasm32-unknown-unknown](https://github.com/rust-random/getrandom/issues/87) We ran into this when doing a standard `cargo update` and the new `getrandom` crate started failing all of our `wasm32-unknown-unknown`...