Nemo157

I think once that flag's behavior is stabilized as the default behavior it will be consistent: `target.runner` will work for `cargo test --doc` always. The reason I mentioned that it...

It's the behavior that `-Zdoctest-xcompile` enables.

No, those still need implementing separately, and `RUSTC_WRAPPER` still needs the linked PR or something like it to be able to support on the rustdoc side (I'm gonna bring that...

When combined with `-Zhost-config` does this also support `host.rustdocflags`? (I've just found out we actually need to use this for docs.rs to fix issues with combining `-Zhost-config` and `--config build.rustdocflags`).

For lints at least I feel like having explicit _pushing_ from the workspace would work fine in most cases, it doesn't need to be implicit if you only have to...

#4380 (or changes since then since that was quite some time ago) doesn't help with subcommands: ```console > sshagmux lis error: unrecognized subcommand 'lis' tip: a similar subcommand exists: 'list'...

There is one potential patch that would make the API sound: ```rust fn safe_uninit() -> Self { unsafe { core::mem::zeroed() } } ``` All the types which implement `SafeUninit` are...

Looks like there might still be something triggering this, we just got slow requests again and had 4 render threads at high cpu usage 

Yep, looking through early request failures during this last outage I found one which hangs my local server. Will try and take a look at whether there's something better we...

For adding more warnings like some targets failed, yes, for the UI part and just an initial "the last build failed" warning no, that should be possible now.