]> git.lizzy.rs Git - rust.git/commit - src/tools/miri
Rollup merge of #97411 - raiyansayeed:print-stderr-consistently, r=Mark-Simulacrum
authorMatthias Krüger <matthias.krueger@famsik.de>
Fri, 27 May 2022 23:11:47 +0000 (01:11 +0200)
committerGitHub <noreply@github.com>
Fri, 27 May 2022 23:11:47 +0000 (01:11 +0200)
commit1174dba02f8fdda0c8100879a612b94d4737c22f
tree5917ee23c2d7d7c3262b7ccfbd88f5fb5bd3817f
parent4254f922db8f257902077023d28d60c61684206b
parent392077df24785f2539c4c994d0ba6563a1ba6fb3
Rollup merge of #97411 - raiyansayeed:print-stderr-consistently, r=Mark-Simulacrum

Print stderr consistently

Solves https://github.com/rust-lang/rust/issues/96712

I tried to follow what I perceived as the general consensus for error messages in boostrap i.e messages that were ..
* resulting from an Err(...) =>
* literally called as "Error: ...."
* by the end of the block scope forced to run a panic! or process::exit with a guaranteed non-zero error code.
src/bootstrap/builder.rs
src/bootstrap/config.rs
src/bootstrap/flags.rs
src/bootstrap/lib.rs
src/bootstrap/native.rs
src/bootstrap/tool.rs
src/bootstrap/util.rs