-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Drop tick() from LoopInterface #72
Conversation
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.
Yes 👍
This has been discussed plenty of times already and we have yet to come up with a use case that actually needs the tick()
method. Removing this makes perfect sense, it avoids plenty of issues related to it, reduces implementation complexity and perceived external complexity (smaller public API).
I'd like to hear from @WyriHaximus about this because IIRC he's using |
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.
@jsor Glad to see this horrible hack go 👍 . I use it in one lib, but don't really recommend it, and really would prefer not to use and have it at all.
Since this a BC break, i'd like to have also @cboden's approval here. |
References: #52 (comment), async-interop/event-loop#9
For the tests, i've added a helper function to
TestCase
.Closes #52