-
Notifications
You must be signed in to change notification settings - Fork 9
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
Two working implementations #124
Comments
AFAIK we have a working implementation by @martinschroeder: koolkode/async: https://github.com/koolkode/async which each pass all tests by their currently supported loops. |
@bwoebi We need tests for strict types. |
Yeah, that has been changed very recently, will add a test to event-loop-test repo |
Test added \cc @martinschroeder |
@bwoebi There's a typo in your ping. I just tagged https://github.com/async-interop/event-loop/releases/tag/v0.4.0 |
Thanks for letting me know. I removed strict types from the loop implementations and will have a look into version 0.4 of the loop spec today or maybe tomorrow. I had to disable the test case for nested loop signal dispatching for the event extension due to an issiue with epoll. All other test cases are working out fine. My question is: Does the loop implementation still conform to the specification or do i have to remove the entire signal handling support from the event-extension-based loop? |
@martinschroeder I wonder, is there no workaround? a) You could shut the warning up with |
@bwoebi I will have a look into the enable/disable solution tomorrow, sounds like a good idea to me. |
I think working on consumers is as important, if not more, than working on implementations. The best approach from here would be refactoring a collection of async PHP apps to use this event loop. I've got a PHP snake game that uses React which I can try to rewrite - but I am incredibly limited on time at the moment! |
I migrated koolkode/async to event loop API version 0.4 and tagged a new release 0.2.10 that provides the event loop implementation. |
Following the FIG, I think it's good to have two working implementations passing all tests. I think we should have
v0.4.0
and two working implementations, then tagv1.0.0
.The text was updated successfully, but these errors were encountered: