Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129618
Precedence: list
MIME-Version: 1.0
Date: Tue, 16 Dec 2025 10:07:05 +0100
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
Cc: PHP Internals <internals@lists.php.net>, Matthew Weier O'Phinney
 <mweierophinney@gmail.com>, Larry Garfield <larry@garfieldtech.com>
Subject: Re: [PHP-DEV] [RFC] Context Managers
In-Reply-To: <D8927CEA-3D00-4ECF-807B-7C2C96C5B582@rwec.co.uk>
References: <CAJp_myV9+kxx-eA+cja-Fu5dJhDZgzhgpBpiZFWqqW-_zrNreQ@mail.gmail.com>
 <70A79513-5503-467E-BC6F-2B0494A3EBB9@benramsey.com>
 <CADK1yXJgPsZJ5+qepDotrMMtRm8TtG95wS7UNpvd8D=Pm-+BOQ@mail.gmail.com>
 <D8927CEA-3D00-4ECF-807B-7C2C96C5B582@rwec.co.uk>
Message-ID: <480eff88ceba74d3274917d6ce2a3c24@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-12-16 09:08, schrieb Rowan Tommins [IMSoP]:
>> I also agree with Matthew but the reversed proposed here looks very 
>> very
>> awkward to me. I think the most natural thing is the “as” but I may 
>> have
>> missed the discussion on why it had to be changed.
>> 
>> Thinking of foreach ($array as $value), an item from the array (left) 
>> is
>> assigned to $value (right).
> 
> 
> This is the way to read the "as" syntax, yes; as I've said in a few 
> places, a Context Manager is like an iterator that goes around once.

That definition doesn't make sense to me. An iterator that only ever 
emits a single value is not actually iterating anything and it would 
never occur me to interpret it like that. As I had also noted in my 
reply https://news-web.php.net/php.internals/129582, it is absolutely 
magic to me that `break;` would target `using()`.

> My favourite among my own suggestions was "using($cValue from new 
> CM())", but Larry didn't like the reversed order. I also suggested 
> 'using(new CM() for $cValue)", but I don't think that's as clear.

FWIW: Using `from` would be somewhat consistent with `yield from`. Using 
`for` would effectively invent another meaning for an existing keyword, 
something that folks disliked for `use()` as the initial block scoping 
keyword.

Best regards
Tim Düsterhus