Nemo157

I added some more logging into a local cargo, for some reason it doesn't know which source files to check when running under miri: ```console > CARGO_LOG=trace ~/.cargo/shared-target/debug/cargo run ......

Maybe a simpler step would be `impl {Try}From for ureq::Request`, that seems to be the directly equivalent type containing all the data other than the body (and is what I'm...

Oh wait, I see there is an `http-interop` feature already. It would be good to activate this on docs.rs so that these impls can be seen (and I think that...

That latter one would be part of reworking the build queue to add release data to the db as soon as the version is queued, instead of only after it's...

For https://github.com/rust-lang/docs.rs/issues/1866 I was proposing we move to reading the `README.md` from the source archive so that we don't need to store this in the database. One issue I have...

The very limited source view is personally all I expect of it (note that I'm only talking about `https://docs.rs/crate/.../source/...`, not the rustdoc generated source pages). The major usecase is just...

Skimming my dependencies `check-cfg` outputs, there's a couple I noticed: ``` warning: unexpected `cfg` condition name: `fuzzing` --> crates.io/h2-0.4.2/src/lib.rs:132:7 | 132 | #[cfg(fuzzing)] | ^^^^^^^ | ``` This cfg is...

I brought `cfg(fuzzing)` up because I feel it might fall under whatever notability requirement there is to have it as a default tool cfg (it's at about the same usage...

I see there was previously a PR for declaratively specifying allowed `cfg` via the `Cargo.toml` https://github.com/rust-lang/cargo/pull/11631 I wonder if this idea could be resurrected for cases like `fuzzing` or `loom`...

We do have a build duration issue right now, the number of published crates has increased a lot in the last few years and the build system hasn't scaled with...