Tracking Issue for `motor_ext`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
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: https://github.com/rust-lang/rust/pull/147000
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Motor OS stdlib PR #147000 and the stabilization guide linked in the issue. Review the ChildExt, OsStrExt, and OsStringExt APIs and the listed feature-lifecycle steps; done means completing the final comment period and producing a stabilization PR.
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
- Mostly clear
- Newbie friendliness
- 25/100