Exit codes for process termination

• 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)

Add to your Cargo.toml:

$ cargo add proc-exit

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

• duct for orchestrating multiple processes.
  • or commandspec for easier writing of commands
• 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()

Licensed under either of

• Apache License, Version 2.0, (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or https://opensource.org/license/mit)

at your option.

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.