diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2020-05-16 02:37:23 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-16 02:37:23 +0200 |
| commit | b381ea8abb278e42c3f157440fd1bd2af6c7782d (patch) | |
| tree | 432ebcce378ee34af39b4550cd7515ff6c654adc /src/test/rustdoc-js-std/string-from_ut.js | |
| parent | b0490cc80d1a0747f2a91d1200ed31b8c77d45bc (diff) | |
| parent | 30822733f080fdee42409a6e05c6b8c7adfbbe7f (diff) | |
| download | rust-b381ea8abb278e42c3f157440fd1bd2af6c7782d.tar.gz rust-b381ea8abb278e42c3f157440fd1bd2af6c7782d.zip | |
Rollup merge of #72090 - RalfJung:rustc_driver-exit-code, r=oli-obk
rustc_driver: factor out computing the exit code In a recent Miri PR I [added a convenience wrapper](https://github.com/rust-lang/miri/pull/1405/files#diff-c3d602c5c8035a16699ce9c015bfeceaR125) around `catch_fatal_errors` and `run_compiler` that @oli-obk suggested I could upstream. However, after seeing what could be shared between `rustc_driver::main`, clippy and Miri, really the only thing I found is computing the exit code -- so that's what this PR does. What prevents using the Miri convenience function in `rustc_driver::main` and clippy is that they do extra work inside `catch_fatal_errors`, and while I could abstract that away, clippy actually *computes the callbacks* inside there, and I fond no good way to abstract that and thus gave up. Maybe the clippy thing could be moved out, I am not sure if it ever can actually raise a `FatalErrorMarker` -- someone more knowledgeable in clippy would have to do that.
Diffstat (limited to 'src/test/rustdoc-js-std/string-from_ut.js')
0 files changed, 0 insertions, 0 deletions