Josh Triplett

I think this proposal makes sense as written, and it's simple and straightforward. Should we allow `derive(From)` on single-field structs, to `impl From for Struct`? @rfcbot merge

@est31 I've tried that lint, and it seems to work well. I'd love to get a comparison of what `cargo-udeps` does above and beyond that lint.

> have cargo collect the info from all compilation units and then combine it -- this is what cargo-udeps is doing. still, one can't upstream it as there is not...

> move cargo to a 1:1 model like buck Frankly, I'd love to have this as an option someday. It'd be a massive tradeoff, but a huge win for a...

@est31 Ah, I didn't realize that. We should fix that; `cargo check --all-targets` / `cargo build --all-targets` seems like it should build everything. If we can't do *that* for backwards-compatibility...

Not a rush; thank you!

@rfcbot concern need-rationale-other-than-curl-bug According to https://github.com/rust-lang/cargo/issues/15376 , it sounds like the `curl` command-line tool automatically uses the non-proxy CA info as the proxy CA info, if no proxy CA info...

OK, if I understand correctly, the rationale here is that you want to use a given CA for the proxy, but *not* permit that CA for the server accessed through...

We discussed this in today's @rust-lang/lang meeting and confirmed that we feel this is entirely the scope of @rust-lang/libs-api to determine, not lang. @pnkfelix wasn't present, and since he nominated...

What's the current state of this one? I think it has all the necessary approvals.