Coordination repository of the portability Working Group (WG)
This repository issue tracker is used by the portability WG to coordinate efforts towards making Rust portable to new platforms.
Rust is really super portable. It supports a lot of platforms. But not enough … not nearly enough. Rust wants to be everywhere, in wild places that only future generations will be able to imagine. We’ve got some work yet to enable that future though, and it is our responsibility to the Rusting world to do so!
-- @brson
Some concrete goals:
- Support in
stdfor non-Unix, non-Windows platforms.- Support for platforms that don’t have or require libc. The
stdAPI surface is already designed to accomodate this, but not the implementation.
- Support for platforms that don’t have or require libc. The
- Reduced maintenance burden for ports. Porting std today requires touching too many parts of the libraries, and those parts must be maintaned by the std maintainers. In general, day-to-day maintenance should not require dealing with platform-specific code, especially for lesser-maintained ports.
- Rust developers should be aware when they use non-portable interfaces, so that they can avoid them or at least plan for them.
- Most of Rust's crate ecosystem should be usable on any platform with ease.
- @acfoltzer
- @alfriadox
- @bossmc
- @Ericson2314
- @jethrogb (all things SGX)
- @le-jzr
- @pierzchalski
- @ratmice
- @retep998 (all things Windows)
- @theJPster
- @Tom-Phinney
You can usually find the members of the portability WG on the #rust-portability channel (server: irc.mozilla.org). Most of us use our GH usernames as our IRC nicknames.