-
Notifications
You must be signed in to change notification settings - Fork 645
categories: Add os::linux-apis #2662
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.
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
Conversation
Linux has a large API surface that isn't shared with other members of the Unix/Unix-like family, so having a separate category for it allows crate authors to better distinguish when writing bindings for Linux-specific interfaces. This is consistent with the availability of `os::macos-apis`, as macOS is another member of the Unix/Unix-like family with its own large and discrete API surface.
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @sgrif (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
categories: "mac OS" -> "macOS" This is a tiny nitpick that I noticed while opening #2662: Apple stylizes their operating system without the space, so I figured consistency with their style makes sense.
categories: "mac OS" -> "macOS" This is a tiny nitpick that I noticed while opening #2662: Apple stylizes their operating system without the space, so I figured consistency with their style makes sense.
The team discussed this in today's meeting. r? @JohnTitor |
Sure, I'm happy to! Here are some examples:
|
@woodruffw Thanks! But could you show more examples? I think it'd be ideal that there were 10 or so examples. Because we're reluctant to add new (sub)categories and need the reason that "we definitely should add this category!". |
Sure. I’ll add a more complete list today.
Sent from mobile. Please excuse my brevity.
… On Aug 4, 2020, at 11:57 PM, Yuki Okushi ***@***.***> wrote:
@woodruffw Thanks! But could you show more examples? I think it'd be ideal that there were 10 or so examples. Because we're reluctant to add new (sub)categories and need the reason that "we definitely should add this category!".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Here are some more examples of crates for Linux-specific APIs and subsystems:
|
Thanks a lot! I'll put this on the agenda again at this week's meeting. |
Thanks to you too! I appreciate the background on the review and approval process 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discussed this at today's meeting and we're happy to accept it. Thanks again for working on it! This category will be available since next deploying.
@bors r+ |
📌 Commit b8bf226 has been approved by |
☀️ Test successful - checks-travis |
Thanks again! |
First of all, thank you to the crates.io team! The service and work you provide is invaluable.
I'm opening this PR to propose a new category slug:
os::linux-apis
. My rationale:Linux has a large API surface that isn't shared with other
members of the Unix/Unix-like family, so having a separate
category for it allows crate authors to better distinguish
when writing bindings for Linux-specific interfaces.
This is consistent with the availability of
os::macos-apis
,as macOS is another member of the Unix/Unix-like family with
its own large and discrete API surface.