Tracking Issue for extra unix ExitStatusExt methods

[ijackson]

Feature gate: #![feature(unix_process_wait_more)]

This is a tracking issue for a collection of logically necessary but previously missing methods on ExitStatusExt, the Unix-specific extension trait for ExitStatus.

Public API

// std::src::sys::unix::ext::process

pub trait ExitStatusExt : private::Sealed {
    // this feature gate adds these methods:
    fn core_dumped(&self) -> bool; // WCOREDUMP
    fn stopped_signal(&self) -> Option<i32>; // WIFSTOPPED? WSTOPSIG
    fn continued(&self) -> bool; // WIFCONTINUED
    fn into_raw(self) -> i32;
}

Steps / History

• Implementation: Add missing methods to unix ExitStatusExt #79982
• Check that nothing broke due to us sealing the ExitStatusExt trait on both Unix and Windows
• What to do about the Fuchsia implementation? Needs eyes from a Fuchsia dev
• Final commenting period (FCP)
• Stabilization PR: Stabilise unix_process_wait_more, extra ExitStatusExt methods #88300

Unresolved Questions

• None; other than the breakage risk due to sealing this trait. the trait has been sealed for some time now.

[ijackson]

The situation with Fuchsia has been discussed in #58590, where it seems to have been agreed that Fuchsia ought not to be treated as Unix. The current situation, with the stub impls, is considered fine for now, apparently. So I have ticked that box in the checklist.

I will propose an MR to stabilise this.