Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129245
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DiWK6y=76cRTpx+6eGmBgytd2HWs2C-OH5rd8WNLffFA@mail.gmail.com>
 <CAMW7n8Dp3siTp0NKGc=-8aNg=Mqoxug9Osgn2399P1v4wi3n5Q@mail.gmail.com>
 <6618a91c-5393-4f40-88b5-b5041ee09deb@app.fastmail.com> <12D52EE4-62F4-42AC-A17D-A8F3A19D2433@zort.net>
 <0f37fa44-dd56-4773-be33-f1ba57eddcd5@app.fastmail.com>
In-Reply-To: <0f37fa44-dd56-4773-be33-f1ba57eddcd5@app.fastmail.com>
Date: Sat, 15 Nov 2025 23:43:07 +0200
Message-ID: <CAMW7n8CKNsuae7BsPUZPF_sfbGd4rEDG4aEkNekcajR4K-ukDQ@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 5
To: Rob Landers <rob@bottled.codes>
Cc: John Bafford <jbafford@zort.net>, php internals <internals@lists.php.net>, 
	Jakub Zelenka <bukka@php.net>, Larry Garfield <larry@garfieldtech.com>
Content-Type: text/plain; charset="UTF-8"
From: edmond.ht@gmail.com (Edmond Dantes)

> With property hooks and implicit suspension, event this becomes unsafe:
> A suspension can happen between the read and the write. Another coroutine can mutate the counter in between. The programmer did nothing wrong; it's just a hazard introduced by invisible suspension.

The risk of a variable being modified by different coroutines does not
depend on the transparency model. This effect is possible in both
implementations.
Even if a setter triggers a suspension, it does not affect the logical
execution flow. Therefore, no danger arises.

The difference between the transparent model and the explicit one lies
in other aspects. It seems this discussion took place in March of this
year.