-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
explain the types used in the open64 call #71921
Conversation
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
I think this code is shared by all Unix-y targets, while the comment is very macOS-specific? Or at least, the comment only makes sense if you presuppose |
It's not just macOS though... |
I updated the comment, better now? |
Seems good enough to me, it won't do any harm and may help someone in the future. @bors r+ |
📌 Commit fbf791b has been approved by |
Rollup of 6 pull requests Successful merges: - rust-lang#71510 (Btreemap iter intertwined) - rust-lang#71727 (SipHasher with keys initialized to 0 should just use new()) - rust-lang#71889 (Explain our RwLock implementation) - rust-lang#71905 (Add command aliases from Cargo to x.py commands) - rust-lang#71914 (Backport 1.43.1 release notes to master) - rust-lang#71921 (explain the types used in the open64 call) Failed merges: r? @ghost
Fixes #71915, where I learned about this quirk. I don't actually know what I am talking about here. ;)