9 releases (stable)

2.0.1 Mar 14, 2023
2.0.0 Oct 4, 2022
1.0.3 Dec 28, 2021
1.0.2 Jan 30, 2021
0.1.0 Nov 22, 2020

#60 in Operating systems

Download history 1121/week @ 2023-12-13 862/week @ 2023-12-20 1185/week @ 2023-12-27 933/week @ 2024-01-03 936/week @ 2024-01-10 1141/week @ 2024-01-17 1081/week @ 2024-01-24 1321/week @ 2024-01-31 1373/week @ 2024-02-07 945/week @ 2024-02-14 801/week @ 2024-02-21 1710/week @ 2024-02-28 1541/week @ 2024-03-06 1292/week @ 2024-03-13 2069/week @ 2024-03-20 2039/week @ 2024-03-27

7,142 downloads per month
Used in 15 crates (14 directly)

MIT/Apache

26KB
256 lines

proc-exit

Exit codes for process termination

codecov Documentation License Crates Status

Features

  • i32 newtype for exit codes
    • Can represent any valid exit code
    • Type safe, operations are restricted to what is valid for exit codes
  • Includes standard exit codes and signal exit codes
  • Integrate with main, std::process, and std::io::Error
  • Supports exiting silently (error message reported through another means)

Install

Add to your Cargo.toml:

$ cargo add proc-exit

Relevant crates

Other crates that might be useful in testing command line programs.

  • duct for orchestrating multiple processes.
  • rexpect for controlling interactive programs.
  • assert_cmd can be reused to simplify controlling CLIs

Some crates that fill a similar role include:

  • sysexit
    • Uses an enum, making certain states unpresentable
    • Includes signals
    • Integrates with std::process and std::io::Error
    • Doesn't integrate with main
  • exit-code
    • i32 constants and helper methods
    • Doesn't include signals
    • Doesn't integrate with main, std::process, or std::io::Error
  • exitcode
    • i32 constants and helper methods
    • Doesn't include signals
    • Doesn't integrate with main, std::process, or std::io::Error
  • exitfailure
    • Allows Displayable errors to be used with ? in main()

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

No runtime deps