5 unstable releases
Uses new Rust 2024
| 0.3.0 | Jun 6, 2025 |
|---|---|
| 0.2.2 | Jun 6, 2025 |
| 0.2.1 | Jun 2, 2025 |
| 0.2.0 | Jun 2, 2025 |
| 0.1.0 | Jun 1, 2025 |
#384 in Testing
176 downloads per month
45KB
734 lines
proc-result
A tiny cross-platform library containing exit status and code types.
Unlike std::process, this crate does not require the standard library[^1], nor
libc, and can create and interpret exit codes of non-current platforms. For
example, on Windows, it can read and interpret exit codes that may have been
recorded from a Linux process, or vice versa.
[^1]: The std feature is enabled by default, but can be disabled.
Usage
Most users of the crate will use the ProcResult enum, which represents the
result a run of a explaining what exit code or (on Unix platforms) the signal
the subprocess was prematurely terminated with, and is constructed from a
std::process::ExitStatus:
use proc_result::ProcResult;
use std::error::Error;
use std::process::Command;
fn main() -> Result<(), Box<dyn Error>> {
let result: ProcResult = Command::new("ls").status()?.into();
// Ensures exit code 0.
result.ok()?;
Ok(())
}
Advanced users, or users writing tests or interpreting exit codes from other
platforms may import and use the platform-specific exit code types directly,
from the unix or windows modules, respectively. For example, to create a
Unix exit code from a raw integer:
use proc_result::unix::ExitCode;
let code = ExitCode::from_raw(1);
if code.is_success() {
println!("Command succeeded!");
} else {
eprintln!("Command failed with exit code: {}", code);
}
Features
| Name | Default | Description |
|---|---|---|
serde |
false |
Enables serialization support for most types using serde. |
std |
true |
Enables compatibility with std::process::ExitStatus. |
Dependencies
~80–300KB