Skip to content

Fix typo: s/portibility/portability/ #1010

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

Merged
merged 1 commit into from
Jul 22, 2022
+1 −1
Merged

Fix typo: s/portibility/portability/ #1010

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
2 changes: 1 addition & 1 deletion posts/inside-rust/2022-04-20-libs-aspirations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ without it becoming hugely inconvenient for maintainers, contributors, or users:
- Make it easier to port std to a new platform, possibly allowing the relevant code
to live outside of the `rust-lang/rust` repository for less popular platforms.
- A better way to allow only parts of `std` to be available, depending on the platform.
For example, a `where Platform: Unix` bound, or something like a [`#[cfg]` portibility lint](https://rust-lang.github.io/rfcs/1868-portability-lint.html).
For example, a `where Platform: Unix` bound, or something like a [`#[cfg]` portability lint](https://rust-lang.github.io/rfcs/1868-portability-lint.html).
- A way to allow non-portable functionality to be available when on platforms
that would support it, such as allowing infallible conversion between `u64` and
`usize` in code that declares it only runs on 64-bit platforms.
Expand Down