You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
pubtraitChildExt:Sealed{/// Extracts the main thread raw handle, without taking ownership#[unstable(feature = "motor_ext", issue = "$THIS_ISSUE")]fnsys_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.)
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.
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)
Activity
thaliaarchi commentedon Oct 21, 2025
Btw, I don't think the
OsStrExt/OsStringExttraits 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 commentedon Oct 22, 2025
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)
[-]Tracking Issue for stabilizing motor_ext feature[/-][+]Tracking Issue for `motor_ext`[/+]