Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129041
Message-ID: <cc264692-882f-4677-84c3-a9cc8ae6b00e@dennis.birkholz.biz>
Date: Sat, 1 Nov 2025 14:17:04 +0100
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 5
To: internals@lists.php.net
References: <CAMW7n8DiWK6y=76cRTpx+6eGmBgytd2HWs2C-OH5rd8WNLffFA@mail.gmail.com>
 <2441aa9c-41c8-4ce1-b9c0-67136e5f97da@dennis.birkholz.biz>
Content-Language: de-DE
In-Reply-To: <2441aa9c-41c8-4ce1-b9c0-67136e5f97da@dennis.birkholz.biz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: php@dennis.birkholz.biz (Dennis Birkholz)

Hi Edmond,

could you please clarify these two questions? Thanks.

Am 31.10.25 um 11:59 PM schrieb Dennis Birkholz:
> Also I do not really understand why the "cancellation" is an 
> awaitable. If the provided awaitable is itself some infinitely 
> blocking Coroutine (e.g. `while (true) {}`), how can the scheduler run 
> the actual Coroutine and the "cancellation" awaitable to determine 
> whether the Coroutine should be cancelled or not? As long as there is 
> no multithreading, this does not make sense for me.
>
> In addition, what happens if a Coroutine is suspended and is restarted 
> again. Is the cancellation awaitable restarted? Or just continued?

Kind regards
Dennis