Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129080
Precedence: list
MIME-Version: 1.0
References: <a087d9fa-112a-4631-9c84-3efae641e0db@app.fastmail.com>
In-Reply-To: <a087d9fa-112a-4631-9c84-3efae641e0db@app.fastmail.com>
Date: Wed, 5 Nov 2025 06:29:29 +0000
Message-ID: <CAKxcST9Hp+GYOe8NhkY=2fbgd5hPfn98Hp34SrjdOQd31DaN5A@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Context Managers
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009e5e330642d312f1"
From: dragoonis@gmail.com (Paul Dragoonis)

--0000000000009e5e330642d312f1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 4, 2025, 8:18=E2=80=AFPM Larry Garfield <larry@garfieldtech.com=
> wrote:

> Arnaud and I would like to present another RFC for consideration: Context
> Managers.
>
> https://wiki.php.net/rfc/context-managers
>
> 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. :=
-)
>
> Naturally, Arnaud and I feel that our approach is the better one.  In
> particular, as Arnaud noted in an earlier reply, __destruct() is unreliab=
le
> 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).
>
> 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.
>
> Discuss. :-)
>

Great idea, I'm definitely behind this.

I've also read through all the PR code.

I have a few questions

1. Apart from wrapping zend_resource into ResourceContext, has there been
discussions or ideas to wrap other things ?

2. Are there any scenarios where using with() is a bad idea or has "side
effects"?

3. In the implementation code there is a lot of mention of "list" and
zend_list .. why? Maybe the answer is obvious but I can't see, at first
glance, why we are implementing list under the hood.

Thanks, and great work to both of you!



> --
>   Larry Garfield
>   larry@garfieldtech.com
>

--0000000000009e5e330642d312f1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote gmail_quote_contai=
ner"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 4, 2025, 8:18=E2=80=
=AFPM Larry Garfield &lt;<a href=3D"mailto:larry@garfieldtech.com">larry@ga=
rfieldtech.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Arnau=
d and I would like to present another RFC for consideration: Context Manage=
rs.<br>
<br>
<a href=3D"https://wiki.php.net/rfc/context-managers" rel=3D"noreferrer nor=
eferrer" target=3D"_blank">https://wiki.php.net/rfc/context-managers</a><br=
>
<br>
You&#39;ll probably note that is very similar to the recent proposal from T=
im and Seifeddine.=C2=A0 Both proposals grew out of casual discussion sever=
al months ago; I don&#39;t believe either team was aware that the other was=
 also actively working on such a proposal, so we now have two.=C2=A0 C&#39;=
est la vie. :-)<br>
<br>
Naturally, Arnaud and I feel that our approach is the better one.=C2=A0 In =
particular, as Arnaud noted in an earlier reply, __destruct() is unreliable=
 if timing matters.=C2=A0 It also does not allow differentiating between a =
success or failure exit condition, which for many use cases is absolutely m=
andatory (as shown in the examples in the context manager RFC).<br>
<br>
The Context Manager proposal is a near direct port of Python&#39;s approach=
, which is generally very well thought-out.=C2=A0 However, there are a few =
open questions as listed in the RFC that we are seeking feedback on.<br>
<br>
Discuss. :-)<br></blockquote></div></div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">Great idea, I&#39;m definitely behind this.=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">I&#39;ve also read through all the PR=
 code.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">I have a fe=
w questions</div><div dir=3D"auto"><br></div><div dir=3D"auto">1. Apart fro=
m wrapping zend_resource into ResourceContext, has there been discussions o=
r ideas to wrap other things ?</div><div dir=3D"auto"><br></div><div dir=3D=
"auto">2. Are there any scenarios where using with() is a bad idea or has &=
quot;side effects&quot;?</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>3. In the implementation code there is a lot of mention of &quot;list&quot=
; and zend_list .. why? Maybe the answer is obvious but I can&#39;t see, at=
 first glance, why we are implementing list under the hood.=C2=A0</div><div=
 dir=3D"auto"><br></div><div dir=3D"auto">Thanks, and great work to both of=
 you!=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto"><div class=3D"gmail_quote gmail_quote_container"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<br>
-- <br>
=C2=A0 Larry Garfield<br>
=C2=A0 <a href=3D"mailto:larry@garfieldtech.com" target=3D"_blank" rel=3D"n=
oreferrer">larry@garfieldtech.com</a><br>
</blockquote></div></div></div>

--0000000000009e5e330642d312f1--