-
Notifications
You must be signed in to change notification settings - Fork 739
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 Interest::PRIORITY #1647
Add Interest::PRIORITY #1647
Conversation
Since this is pretty much, what I proposed here: #1645 (comment)
Unfortunately no, it does not solve it fully. You missed debug-fmt-ing the priority interest. In your case debug printing a priority interest alone does panic. Have a look at my proposal in src/interest.rs lines 186-192. Thank you very much for your work regarding this issue. |
I only saw the example, which had a bug I pointed out, then I got a pr (#1646) with the exact same bug and an unwanted dependency. So, in my free time I tried fix the problem you were having... If you had the solution and a working fix, why not submit that in as a pr? |
Don't get me wrong. As I said already: I am very thankful for your work. Be it:
I am sorry, that you did not see my proposed fix hidden in the comment on the issue. This is my fault. I thought you get notified, if you were commenting on an issue and I add a new comment.
This is because I am really unsure. You are the holy magicans that make this work and keep the code tidy andclean and I am a clueless guy having an issue. At first I was unsure if the problem I saw is really an issue in mio or if it is just me doing something wrong. While investigating the issue, I saw in the history that there actually has been some PRIORITY stuff already, but it was removed. Maybe for a good reason? Before submitting a PR I wanted to know where the problem really is. During our discussion on the issue, it became clear to me, that there really is an issue and I started thinking about how a solution could look like. This then became the code in my proposal. |
Could you please add something like |
Thank you.
That's what pr reviews are for, it's an easy place to see what you're proposing and it's a place for a discussion.
No magicians at work, we're all writing the same code. I'll push a commit with the formatting fix and give you co-author credit. |
82880dc
to
ba1e196
Compare
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.
The code looks good to me now.
But what happened to the Co-authored-by?
Thank you!
ba1e196
to
507ab25
Compare
@poeschel it seems you commit with a different email address than GitHub recognises, what do you prefer I use? |
To trigger Event::is_priority on Linux and Android. In the future we might want to include EV_OOBAND for kqueue, but that seems to be Apple only (FreeBSD and OpenBSD don't implement it at least). Co-authored-by: Lars Pöschel <[email protected]>
Best is, you use |
507ab25
to
d6a3c90
Compare
To trigger Event::is_priority on Linux and Android.
In the future we might want to include EV_OOBAND for kqueue, but that seems to be Apple only (FreeBSD and OpenBSD don't implement it at least).
Closes #1645
Does this solve the problem @poeschel, @Urist-McGit?