Aaron Piotrowski

I happened to see this myself just the other day on v3 when attempting to schedule a timer in a destructor during shutdown. I think the UvLoop handle was destroyed...

This was done long ago in the v3 branch. Still want to bother to do this for v2?

Perhaps there's an issue in `ext-uv` when calling `exit` inside a watcher callback? Exit handling changed recently to throw an exception internally (not sure which PHP version this happened in).

Ping @bwoebi @jsor @sagebind @WyriHaximus @AndrewCarterUK

@rdlowrey I wouldn't include it in this package, but having a separate package under `async-interop` for a React adapter would be a possibility.

I believe we should go with the scoped version using `execute()`. This is the better way to do things. We shouldn't be burdened by prior practices, especially since it is...

I'm struggling a bit with this same question with Icicle. I'm currently supporting PHP 5.5+ and 7, but with different, incompatible branches because PHP 7 brings so many shiny features...

+1 for 5.5. While I think most would use 7 for new async projects, after further consideration I'd hate to so quickly exclude those who can't upgrade for reasons beyond...

Just be sure I'm understanding this approach, the following lines in a project's *composer.json* ```js "require": { "async-interop/event-loop": "^0.4", "async-interop/event-loop-implementation": "^0.4" } ``` would become ```js "require": { "async-interop/event-loop-api": "^0.4",...

Hi, thanks for reporting this! Does it work fine again if [these lines](https://github.com/amphp/process/blob/509742a0ac6e9253cfd38f10039ddd8768300d57/src/Internal/Posix/PosixRunner.php#L34-L36) are removed from `PosixRunner`? Not sure why that check was added, as `pcntl` isn't strictly required.