Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129613
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] [RFC] Context Managers
Date: Tue, 16 Dec 2025 09:55:39 +0400
Message-ID: <1BB46A91-C7F4-4F9E-A3A8-24B9DFC3DB3A@gmail.com>
References: <d0f8e14b-7e44-45b0-8566-176e30048e1b@app.fastmail.com>
Cc: php internals <internals@lists.php.net>
In-Reply-To: <d0f8e14b-7e44-45b0-8566-176e30048e1b@app.fastmail.com>
To: Larry Garfield <larry@garfieldtech.com>
From: xepozzd@gmail.com (Dmitry Derepko)



> On Dec 16, 2025, at 1:19=E2=80=AFAM, Larry Garfield <larry@garfieldtech.co=
m> wrote:
>=20
> =EF=BB=BFOn Thu, Dec 4, 2025, at 10:46 AM, Larry Garfield wrote:
>>> On Tue, Nov 4, 2025, at 2:13 PM, Larry Garfield wrote:
>>> Arnaud and I would like to present another RFC for consideration:
>>> Context Managers.
>>>=20
>>> https://wiki.php.net/rfc/context-managers
>>>=20
>>> You'll probably note that is very similar to the recent proposal from
>>> Tim and Seifeddine.  Both proposals grew out of casual discussion
>>> several months ago; I don't believe either team was aware that the
>>> other was also actively working on such a proposal, so we now have two.
>>> C'est la vie. :-)
>>>=20
>>> Naturally, Arnaud and I feel that our approach is the better one.  In
>>> particular, as Arnaud noted in an earlier reply, __destruct() is
>>> unreliable if timing matters.  It also does not allow differentiating
>>> between a success or failure exit condition, which for many use cases
>>> is absolutely mandatory (as shown in the examples in the context
>>> manager RFC).
>>>=20
>>> The Context Manager proposal is a near direct port of Python's
>>> approach, which is generally very well thought-out.  However, there are
>>> a few open questions as listed in the RFC that we are seeking feedback
>>> on.
>>>=20
>>> Discuss. :-)
>>=20
>> More updates to Context Managers:
>>=20
>> * We have added "masking" for the context variable, using essentially
>> the same technique as the block scope RFC.
>> * We have added support for `try using`, as a shorthand for when you
>> want to wrap a try-catch-finally around a using statement anyway.
>>=20
>> More details of both are in the RFC.
>>=20
>> As no one seems to have a strong opinion on `continue`, we will most
>> likely proceed with the current approach of matching `switch` behavior.
>>=20
>> There doesn't seem to be much interest in making `using` an expression,
>> which I find unfortunate, but that means we'll probably drop that. =20
>> Fortunately it is probably possible to change in the future if the need
>> arises (the way `throw` was changed).
>>=20
>> --Larry Garfield
>=20
> Since the only feedback on what to use for "as" was that =3D> makes sense,=
 we have changed the RFC to use =3D> instead.  So the new syntax is
>=20
> using (new CM() =3D> $cVar) {
>  // Do stuff here.
> }
>=20
> --Larry Garfield


I=E2=80=99d ask you to get back to =E2=80=9Cuse=E2=80=9D keyword, despite of=
 it=E2=80=99s in use in Laravel or somewhere else.=20
As a developer I cannot even imagine what =E2=80=9Cuse=E2=80=9D could mean i=
n web frameworks context, I hope it could have a better name and at the same=
 time we can advise to use namespaces if you don=E2=80=99t want to get somet=
hing broken after upgrading language.=20
Just my 5 cents.=20


--=20
Best regards,=20
Dmitrii Derepko.=20
@xepozz=