Tracking Issue for `motor_ext`

[lasiotus]

Feature gate: #![feature(motor_ext)]

motor_ext feature provides extensions to Rust [std] library pertinent to Motor OS.

This is a tracking issue for stabilizing motor_ext feature, as discussed in the Motor OS stdlib PR.

Public API

At the moment, there is one trait specific to Motor OS:

pub trait ChildExt: Sealed {
    /// Extracts the main thread raw handle, without taking ownership
    #[unstable(feature = "motor_ext", issue = "$THIS_ISSUE")]
    fn sys_handle(&self) -> u64;
}

and generic OsStrExt, OsStringExt traits in os/motor/ffi.rs.

Steps / History

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

• Implementation: std: Add Motor OS std library port #147000
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[thaliaarchi]

Btw, I don't think the OsStrExt/OsStringExt traits need to be unstable, since those traits are stable for all other platforms (except for SGX). It probably only matters, if you think there's still some design iteration to do, but I don't think their API will need changes once #147932 merges.

[tgross35]

They can probably go through the stabilization process whenever, but they do need to be unstable for now since libs-api hasn't done FCP on them. (I did double check this on Zulip)