The PHP internals mailing list is discussing the RFC for deprecations planned in PHP 8.6. Gina P. Banyard announced the annual deprecations RFC, noting each deprecation will be voted on individually and the RFC must be frozen by July 13th. A significant debate emerged around whether the proposals include proper impact analyses. Juliette Reinders Folmer criticized the lack of impact analysis across the ~25 proposals, while Tim Düsterhus argued that deprecations are not breaking changes and that impact analyses based on public code (e.g., Packagist packages) are inherently biased and incomplete. Rowan Tommins sided with Juliette, stating any proposal without impact information would receive an automatic 'No' vote. Osama Aldemeery shared a concrete impact analysis for the 'return-in-finally' deprecation, showing it affects only 12 places across 9 packages (~0.18% of top Composer packages), with 3 being actual latent bugs.
