rust-lang / rust-lang/rust

Tracking Issue for infallibly converting `ExitStatus` to `ExitCode`

Open
#152,049 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue S-tracking-unimplemented T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(exitstatus_to_exitcode)]

This is a tracking issue for infallibly converting ExitStatus to ExitCode

Public API
// std::process
impl ExitCode {
    fn from_exit_status(status: ExitStatus) -> ExitCode;
}

impl ExitStatus {
    fn to_exit_code(&self) -> ExitCode
}
Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

Unresolved Questions
  • Should this just be implemented via the From and Into traits? If there's one "obvious" conversion then it may make sense, even if it's not the only way to convert from ExitStatus to ExitCode.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the tracking issue's std::process API sketch and the exitstatus_to_exitcode feature gate. Review ACP #729 and resolve the open question about From and Into traits before assessing implementation scope. Done requires implementation, a final comment period, and a stabilization PR, none of which is linked yet.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.