Bob Weinand
Bob Weinand
I don't think we need to specify wrong types. It makes sense to explicitly specify negative integers being unspecified. (A zero interval for timers is pretty straightforward … it gets...
Looks like we should also include 0 here, the underlying loop backends don't seem to be able to handle that well.
@kelunik Hmm, doesn't make much sense to have it completely unspecified - I think we should specify that they MUST throw a \Throwable|\Exception (but not what type of Throwable exactly...
@joshdifabio That's not an inherently bad idea, but it will have quite a footprint (e.g. extra function call) [also, not all functions receive args, so we'd have some functions directly...
AFAIK we have a working implementation by @martinschroeder: koolkode/async: https://github.com/koolkode/async And our own, amp/loop: https://github.com/amphp/loop which each pass all tests by their currently supported loops.
Yeah, that has been changed very recently, will add a test to event-loop-test repo
Test added \cc @martinschroeder
@martinschroeder I wonder, is there no workaround? a) You could shut the warning up with `@` and enable/disable the signal watchers when Driver::run() is entered/left (so that always the signal...
Note that I've fixed the building on windows for php-uv.
I wouldn't prefer Brotli by default if it has significant overhead.