Re: Re: PHP True Async RFC Stage 4

Hello > I am not sure how feasible this is, but would there be a way to split the "async > toggle" of IO operations off to its own PR/RFC? > To me, that is by far the most important part of this RFC as that's the biggest blocker > for wider async adoption, > but I'm not sure how many layers are needed above it to make it possible to toggle in a > safe fashion. Why is this considered the main blocker? (Or maybe I didn’t quite catch the meaning.) After all, this is precisely the part of the RFC that doesn’t actually change the behavior from the user’s perspective inside a coroutine. As for the PRs. There’s no doubt there will be several. I hope the PHP core team will help with the code separation process and advise on the best way to do it, since it’s not a trivial task. As for the toggle switch. If a developer doesn’t use spawn, then why toggle anything at all? And even if they do, there’s still no difference — the code won’t start executing “differently.” --- Best Regards, Ed