diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2022-02-09 14:12:17 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-09 14:12:17 +0900 |
| commit | ec2fd8a35fcd271458dc5fa462ef74bcb372f6c7 (patch) | |
| tree | d1517ec0ba8ac5e9c8ce873cb63d7c0e75d6c437 /src/test/rustdoc-js-std/multi-query.js | |
| parent | 9a5a961be97f405e751dd2cf966e1cdb80a612c2 (diff) | |
| parent | 4c5a36e2d1ac0c5d86ba0a75426d601e7c9202b0 (diff) | |
| download | rust-ec2fd8a35fcd271458dc5fa462ef74bcb372f6c7.tar.gz rust-ec2fd8a35fcd271458dc5fa462ef74bcb372f6c7.zip | |
Rollup merge of #93445 - yaahc:exitcode-constructor, r=dtolnay
Add From<u8> for ExitCode This should cover a mostly cross-platform subset of supported exit codes. We decided to stick with `u8` initially since its the common subset between all platforms that we support (excluding wasm which I think only works with `true` or `false`). Posix is supposed to take i32s, but in practice many unix platforms mask out all but the low 8 bits or in some cases the 8-15th bits. Windows takes a u32 instead of an i32. Bourne-compatible shells also report signals as exitcode 128 + `signal_no`, so there's some ambiguity there when returning exit codes > 127, but it is possible to disambiguate them on the other side so we decided against restricting the possible codes further than to `u8`. ## Related - Detailed analysis of exit code support on various platforms: https://internals.rust-lang.org/t/mini-pre-rfc-redesigning-process-exitstatus/5426 - https://github.com/rust-lang/rust/issues/48711 - https://github.com/rust-lang/rust/issues/43301 - https://rust-lang.zulipchat.com/#narrow/stream/219381-t-libs/topic/Termination.2FExit.20Status.20Stabilization
Diffstat (limited to 'src/test/rustdoc-js-std/multi-query.js')
0 files changed, 0 insertions, 0 deletions