Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129769
Precedence: list
MIME-Version: 1.0
Date: Sat, 17 Jan 2026 16:48:12 +0200
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] Context Managers
In-Reply-To: <8cd697c3-5e25-4854-810c-da220da3f6d8@app.fastmail.com>
References: <a087d9fa-112a-4631-9c84-3efae641e0db@app.fastmail.com>
 <905d9879-70ef-4c87-8578-26519c6d4818@app.fastmail.com>
 <acc43a52ff355590ce45ec750420d8a3@bastelstu.be>
 <8cd697c3-5e25-4854-810c-da220da3f6d8@app.fastmail.com>
User-Agent: Roundcube Webmail/1.4.8
Message-ID: <ba4646505bc9046644578881781bbeb1@glaive.pro>
Organization: SIA "Glaive.pro"
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: juris@glaive.pro (Juris Evertovskis)

On 2026-01-15 18:01, Larry Garfield wrote:
> `continue` is really just to mirror what switch does with it.  If the
> consensus is to simply disallow `continue` entirely (which is 
> inconsistent
> with what switch does today), we're OK with that.  I don't feel 
> strongly
> either way, so we're looking for a consensus.
> 

Hey,

I think the benefit of `switch` supporting `continue` is to ensure 
consistency
in the number of breakable/continuable structures. Consider

     foreach ($a as $e) {
         switch ($e) {
             case 0:
                 foreach ($x as $y) {
                     if (!$y) break 3;
                 }
         }
     }

If I need to change `break` to `continue`, I will naturally change 
`break 3` to
`continue 3`. I would suggest sticking to same in context managers — 
have it respected
not because you would ever `continue` to exit it, but to have the onion 
layer numbers
consistent.

BR,
Juris