-
Notifications
You must be signed in to change notification settings - Fork 675
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 epoll_create1 #410
Add epoll_create1 #410
Conversation
Changes look good to me. I don't see any negative impact for mio here. So, r=me once you're comfortable @fiveop. EDIT: I missed the minor, good interface change. Probably worth testing mio with this before merging and prepping changes there if required. |
I added readers for |
Seems fine to me. There's a bit of possible "conventions" work on the flags and stuff, but that can wait. We should perhaps let @carllerche weigh in. Also I imagine |
He had his chance :) But seriously, after having tested adapting mio code to the change, I don't really see a problem. I would like to have it merged after we have a new dev version. |
Oh I missed that he was pinged already. In that case, @homu r+ |
📌 Commit 584794d has been approved by |
@homu r- |
Can we at least export EPOLL_CLOEXEC here, or add it as a single-element flags type for the second arg to |
Naming will get complicated from conventions view as there are all the |
I opted for I tried to use But that's for another PR! |
Looks good to me. Since we recently cut a release, this is probably a pretty good time to get the change in so we can integrate mio changes into upstream in preparation. @homu r+ |
📌 Commit 2b0c991 has been approved by |
⚡ Test exempted - status |
Add epoll_create1 In order to get @kubo39's PR #384 forward, I cleaned up the commit history a bit and added `EpollEvent` back. Since this module is used by mio, maybe @carllerche could comment on these changes.
In order to get @kubo39's PR #384 forward, I cleaned up the commit history a bit and added
EpollEvent
back.Since this module is used by mio, maybe @carllerche could comment on these changes.