-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add renameat2
and change their flags' type to c_uint
#2116
Conversation
Co-Authored-By: Jörg Thalheim <github@thalheim.io> Co-Authored-By: Philipp Gesang <phg@phi-gamma.net>
r? @Amanieu (rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ |
📌 Commit b90fda7 has been approved by |
☀️ Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13 |
The type change causes a build failure for openat (tailhook/openat#35). Should this have gone through a deprecation period per the breaking change policy? |
Thanks for merging this! |
Workaround tailhook#35 AKA rust-lang/libc#2116 Unfortunately since we made this libc::c_int in our public API, we can't easily change it right now. Closes: tailhook#35
@bgilbert I'd consider it as bugfix since |
Well, it can be a bugfix and still be a breaking change. 🙂 But meanwhile, openat has been updated with a workaround in tailhook/openat#36. |
Taking over #1508. This changes the type of some flags but it should've been
c_uint
.Closes #1508