diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-05-28 01:11:47 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-28 01:11:47 +0200 |
| commit | 1174dba02f8fdda0c8100879a612b94d4737c22f (patch) | |
| tree | 5917ee23c2d7d7c3262b7ccfbd88f5fb5bd3817f /compiler/rustc_mir_transform/src/coverage/debug.rs | |
| parent | 4254f922db8f257902077023d28d60c61684206b (diff) | |
| parent | 392077df24785f2539c4c994d0ba6563a1ba6fb3 (diff) | |
| download | rust-1174dba02f8fdda0c8100879a612b94d4737c22f.tar.gz rust-1174dba02f8fdda0c8100879a612b94d4737c22f.zip | |
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.
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions