Skip to content

Tracking Issue for motor_ext #147456

Open
Open

Description

@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.)

Unresolved Questions

  • None yet.

Footnotes

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

Activity

  1. added
    T-libs-api[DEPRECATED; DO NOT USE]
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Oct 7, 2025
  2. thaliaarchi commented on Oct 21, 2025

    @thaliaarchi
    Contributor

    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.

  3. tgross35 commented on Oct 22, 2025

    @tgross35
    Member

    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)

  4. changed the title [-]Tracking Issue for stabilizing motor_ext feature[/-] [+]Tracking Issue for `motor_ext`[/+] on Oct 22, 2025
  5. added
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    and removed
    T-libs-api[DEPRECATED; DO NOT USE]
    on Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libsRelevant to the library team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions