Ralf Jung

Cargo buffers stdout even with TERM=dumb

4

**Problem** Even with `TERM=dumb`, cargo buffers ~~stderr~~ stdout, meaning I do not see things printed to stdout without a trailing `\n`. For Miri, we use `cargo rustc` set up RUSTC_WRAPPER...

### Problem We are setting RUSTC_WRAPPER in order to intercept every invocation of rustc from cargo. However, it looks like cargo will call `rustc -vV` in any case, completely bypassing...

Setting target.runner via --config twice concatenates lists

24

Consider the following invocation: ``` cargo +nightly run --target "x86_64-unknown-linux-gnu" --config "target.'cfg(all())'.runner=['run']" --config "target.'cfg(all())'.runner=['run']" ``` This fails saying ``` error: could not execute process `run run target/x86_64-unknown-linux-gnu/debug/xargo` (never executed) ```...

Feature request: give invoked commands some indication what they are invoked as

2

In cargo-miri, we want to reuse as much of cargo's logic as we can, but whenever cargo invokes another binary, we want to intercept that. So we set all of...

Pattern-matching related soundness concerns

13

Recently [it was pointed out to me](https://github.com/rust-lang/rust/pull/71332#discussion_r413740997) that there is an entire category of const-related soundness concerns that I was unaware of, and that is not mentioned with a single...

Dynamic checks for all const soundness concerns?

14

With https://github.com/rust-lang/rust/pull/56123, we can bypass const qualification, so we can e.g. write constants that read from interior mutable statics, and probably other things I forgot to think about. Could we...

Why can consts not refer to statics?

51

Is there some deep fundamental reason why that can never work, or is it a limitation of the current (or a former) implementation?

`const fn` and generics

34

Now that I came to like const soundness, of course I had to start thinking about how to achieve [const soundness](https://www.ralfj.de/blog/2018/07/19/const.html) in the presence of generics. The problem is that...

Detect SIGKILL-broken builds?

1

In [this report](https://crater-reports.s3.amazonaws.com/pr-75585/index.html), several of the non-spurious regressions were actually spurious with a common theme: ``` [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `rustc --crate-name build_script_build /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/html5ever-0.24.1/build.rs...

"Cannot allocate memory" not recognized as OOM

2

I noticed crater started classifying failures as OOM/ICE, which is awesome. :D Here's an example that is misclassified as ICE instead: https://crater-reports.s3.amazonaws.com/pr-71796/try%23b2a885c600d942fb829a214e798f7ae205a0594e/gh/GuyL99.pure-core/log.txt ``` [INFO] [stderr] thread 'rustc' panicked at 'failed...