Re: PHP True Async RFC Stage 4
| From: | Aleksander Machniak | Date: | Wed, 22 Oct 2025 11:16:29 +0000 |
| Subject: | Re: PHP True Async RFC Stage 4 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-128900@lists.php.net to get a copy of this message | ||
On 5.10.2025 07:23, Edmond Dantes wrote:
https://wiki.php.net/rfc/true_asyncThe RFC is not easy to process. Here's some ideas. - The glossary in "Overview" is good, but probably incomplete. The examples there, with no description, do not help much and could be removed, imo. - "Collable by design" and "Coroutine lifetime" sections should become subsections of "Coroutine" or placed after it. - the "Scheduler and Reactor" section does not explain much over what's in the glossary. - the "Critical section" section should not be a main section, "Cancellation policy" probably either. - the "Basic usage" section in the "Suspension" section is useless. - don't use "suspend keyword" and "await keyword", they are functions. One question. Seems like we don't really need delay() function. Why not add an argument to the suspend() function? I think it would make the code easier to understand, considering seeing suspend(1000) versus delay(1000). -- Aleksander Machniak Kolab Groupware Developer [https://kolab.org] Roundcube Webmail Developer [https://roundcube.net] ---------------------------------------------------- PGP: 19359DC1 # Blog: https://kolabian.wordpress.com