Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126662
Feedback-ID: id5114917:Fastmail
Date: Sat, 08 Mar 2025 22:13:10 +0000
To: internals@lists.php.net
Subject: Re: [PHP-DEV] PHP True Async RFC
User-Agent: K-9 Mail for Android
In-Reply-To: <676e36e4-0b84-4d8c-b3db-2998831cd79d@gmail.com>
References: <CAMW7n8AJckEDzhGv9BdjNhq8zAdCqb4HsVr56vGi+izw50X6Dg@mail.gmail.com>
 <CAMW7n8CM7oBfXCDsKtV4hTFs40UmLCU3183WjYE2exLNqKDWLQ@mail.gmail.com>
 <78a03dd0-fd4a-4f4a-ad8a-37e5704f06fc@app.fastmail.com>
 <CAMW7n8C-Z18MKhyDX2+ofg70cRbwWOk=YWDAZpKtfLZsFVVRng@mail.gmail.com>
 <bb7a9f8f-0422-45e5-b4fc-f5757add92b4@app.fastmail.com>
 <CAMW7n8BnzL7d0bd_Y_jGOmyWegKQpm-FzrVFRCcDe=bNFZpi+A@mail.gmail.com>
 <08c8ad0b-e8f4-46e3-99f0-b80748d40b89@app.fastmail.com>
 <07973EAE-2D83-47A8-8FA0-84286C77C02B@rwec.co.uk>
 <48d66433-3ae9-4895-8361-7c81a0a3670d@app.fastmail.com>
 <be7cb263-93a1-4bd8-9416-ae4d3e0bafe6@rwec.co.uk>
 <dbce8889-016a-4c59-864c-d8fdec895adc@app.fastmail.com>
 <CAM0Ccxh=bydoDEHBAV+Gb1_86HJjwhW06kzEsdRiMh93k1F7oA@mail.gmail.com>
 <8599eb8b-d4a3-4cb8-899a-25b134e0d64d@gmail.com>
 <D73BCCC4-3547-45B4-84AD-A5FD6569D43C@rwec.co.uk>
 <74c4c726-63aa-44e0-84c9-840e13a65a4f@gmail.com>
 <77DC5F50-531D-49E8-8BE2-504A19CB5FFD@rwec.co.uk>
 <676e36e4-0b84-4d8c-b3db-2998831cd79d@gmail.com>
Message-ID: <510B8EF1-9D07-41A8-9EA0-7D99CF7BFC91@rwec.co.uk>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")



On 8 March 2025 21:42:21 GMT, Daniil Gentili <daniil=2Egentili@gmail=2Ecom=
> wrote:
>
>To make an analogy, it's like saying PHP should have an io {} block, that=
 makes sure all file resources opened within (even internally, 10 stack lev=
els deep into 3 libraries, whose instances are all used after the io {} blo=
ck) are closed when exiting=2E

Traditional PHP offers exactly this: the SAPI lifecycle tracks all file ha=
ndles opened within a request, and closes them cleanly before reusing the t=
hread or process for another request=2E Essentially what I'm proposing is a=
 way to implement the same isolation in userland, by marking a checkpoint i=
n the code=2E

As I've said repeatedly, it doesn't necessarily need to be a mandatory res=
triction, it can be a feature to help users write code without having to wo=
rry about *accidentally* leaving a background fiber running=2E=20

Rowan Tommins
[IMSoP]