Weihang Lo

@bors r+ Thanks!

> Is the `target.runner` case covered as well? Is it possible to test this change with [rust-lang/rust#113730](https://github.com/rust-lang/rust/pull/113730) (after removing the Miri workaround)? I believe the answer is yes, as it...

> I'm confused by this. I believe the answer is "no", since target_process does not inherit the jobserver? Unless I misunderstood the question, doesn't this PR make the `target_process`, either...

I see. Thanks for the clarification. Yeah I misunderstood that 😕

Ended up making target runner inherit jobserver. @rustbot ready

It's hard to find a place to document which part of cargo gets access to jobserver. I'll do it in a follow-up when figuring out.

[`profiles`](https://doc.rust-lang.org/nightly/cargo/reference/profiles.html#profiles) are designed for managing compiler settings, not [Cargo features](https://doc.rust-lang.org/nightly/cargo/reference/features.html). `profiles.dev.defaults` is also not a valid `Cargo.toml` manifest key at this moment. You shall see this error message if you...

So far as I am aware of, no. There are some relevant issues/RFCs, but none of them configure features for all examples. * https://github.com/rust-lang/rfcs/pull/3374 * https://github.com/rust-lang/cargo/issues/4663 Apart from convenience, is...

Just read your project a bit. I can see the challenge inside. However, a unit test in Cargo is actually a thing in Rust compiler, specifically `libtest` in rustc. It's...

Personally, I tend not to add such a feature, but will leave this open for now to see if people have opinion about configuring cargo targets globally/by “target kind”.