jyn

@rustbot second

I think this should be possible after https://github.com/rust-lang/crates-build-env/pull/120 :)

Why does autocfg care if the crate is loaded from the sysroot or passed with --extern? Shouldn't `extern crate std` work in both cases?

Oh, is the problem that cargo only passes --extern std=... to the final crate, not to build scripts? I wonder if it should set some environment variable with a list...

Ah, that already exists and it's called CARGO_ENCODED_RUSTFLAGS 😄 I think we should open an upstream issue for cargo to include the --extern std flags in CARGO_ENCODED_RUSTFLAGS.

This is a really great summary, thank you for writing it up! I am not a giant fan of 5; I think `cargo-sweep` on its own is totally fine and...

Ugh, this has the same problem I had in cargo-deadlinks - `cargo sweep sweep` is itself a valid command that means "clean the directory named `sweep`", and you can't distinguish...

currently the output from `cargo-sweep -h` is ``` A tool for cleaning unused build files created by Cargo Usage: cargo-sweep Commands: sweep A tool for cleaning unused build files created...

> I have an idea, and really want to know if you think it will work. If every Cargo command added a `filename.timestamp` file containing the time when the command...

`--build-plan` on the other hand I think should help, we can use the `invocations[*].outputs` key. ``` ; cargo build --build-plan -Zunstable-options 2>&1 1>/dev/null | jq '.invocations[0].outputs' [ "/Users/jyn/src/cargo-sweep/target/debug/build/anyhow-1cf9b89f7ea6e648/build_script_build-1cf9b89f7ea6e648", "/Users/jyn/src/cargo-sweep/target/debug/build/anyhow-1cf9b89f7ea6e648/build_script_build-1cf9b89f7ea6e648.dSYM" ]...