Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand "Reduced maintenance burden for ports" goal #14

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Expand "Reduced maintenance burden for ports" goal #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,9 @@ Some concrete goals:

* Support in `std` for non-Unix, non-Windows platforms.
* Support for platforms that don’t have or require libc. The `std` API surface is already designed to accomodate this, but not the implementation.
* 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.
* 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.
* Porting ecosystem crates, and maintaining them, can't always be expected of upstream crates. On the other hand, having a lot of forks fragments the community. We need to find a good middle ground, quite possibly with additional tooling.
* 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.

Expand Down