-
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
Deprecate AIO_LISTIO_MAX #1498
Deprecate AIO_LISTIO_MAX #1498
Conversation
This value can vary at runtime. Applications should instead use sysconf(3) with _SC_AIO_LISTIO_MAX.
r? @gnzlbg (rust_highfive has picked a reviewer for you, use r? to override) |
BTW, POSIX says that this constant shouldn't even be defined on systems (like FreeBSD and Apple) that publish its value through sysconf: |
@bors: r+ |
📌 Commit 1be630f has been approved by |
Deprecate AIO_LISTIO_MAX This value can vary at runtime. Applications should instead use sysconf(3) with _SC_AIO_LISTIO_MAX.
💔 Test failed - status-azure |
Looks like the same libc bug that affects the nightly Rust stdlib. |
@bors: retry
The failure is in azure. |
Deprecate AIO_LISTIO_MAX This value can vary at runtime. Applications should instead use sysconf(3) with _SC_AIO_LISTIO_MAX.
☀️ Test successful - checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, status-azure |
This value can vary at runtime. Applications should instead use
sysconf(3) with _SC_AIO_LISTIO_MAX.