Re: [RFC] Context Managers
| From: | Rowan Tommins [IMSoP] | Date: | Wed, 05 Nov 2025 23:02:54 +0000 |
| Subject: | Re: [RFC] Context Managers | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-129099@lists.php.net to get a copy of this message | ||
On 05/11/2025 22:37, Larry Garfield wrote:
Nikita's original proposal was indeed to ban continue targeting switch: https://wiki.php.net/rfc/continue_on_switch_deprecation That doesn't mean any targets would get re-numbered, it just means that the case which currently raises a Warning would have thrown an Error. It was talked down to a Warning during discussion: https://externals.io/message/102393 That was partly about backwards compatibility, which doesn't apply here, so I personally think either Warning or Error would be fine. -- Rowan Tommins [IMSoP]breakandcontinueare interesting keywords. (In the "may you live in interesting times" sense.) Sometimes they have the same effect, if a control structure is non-looping. Or they may have different effects in case it is. The main non-looping case isswitch, where for reasons that were before my time the decision was made to deprecatecontinuein favor of just supportingbreak. However, blocking it entirely is a problem, because that would change wherecontinue 2would go (asswitchwould be removed as a "level" that it could go to). It is kind of a mess.