Re: [RFC] Deprecations for PHP 8.6
| From: | Juliette Reinders Folmer | Date: | Mon, 22 Jun 2026 19:58:47 +0000 |
| Subject: | Re: [RFC] Deprecations for PHP 8.6 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131480@lists.php.net to get a copy of this message | ||
On 22-6-2026 20:41, Osama Aldemeery wrote:
On Mon, Jun 22, 2026 at 6:59 PM Juliette Reinders Folmer <php-internals_nospam@adviesenzo.nl <mailto:php-internals_nospam@adviesenzo.nl>> wrote:On 22-6-2026 15:13, Gina P. Banyard wrote:It is this time of year again where we proposed a list of deprecations to add in PHP 8.6:https://wiki.php.net/rfc/deprecations_php_8_6
Unfortunately none of the proposals contain a proper impact analysis.For the *return-in-finally deprecation*, I did run an impact analysis. I just kept it out of the RFC entry itself, partly to keep the entry short, partly because I'd already shared the core of it in my original pre-RFC message on this list (https://externals.io/message/131393#131393 - which lists all 12 affected sites), and partly because I hadn't gotten around to reposting it in this thread yet. ... The full write-up, with the per-site breakdown and the script to reproduce it, is here: https://github.com/aldemeery/php-rfcs/tree/master/deprecate-return-in-finally Thanks Osama! And yes, I remember you posting those impact analysis results to the list. I believe it would be good to include that summary in the RFC text. Would make your proposal the (positive) exception to the rule ;-) Smile, Juliette