On Mon, Jun 29, 2026 at 2:38 PM Seifeddine Gmati <[email protected]> wrote:
> On Mon, 29 Jun 2026 at 18:52, Rowan Tommins [IMSoP] > <[email protected]> wrote: > > > > On 29/06/2026 17:37, Seifeddine Gmati wrote: > > > Hello Internals, > > > > > > I have updated the RFC to include a deprecation proposal for the > > > `list()` construct. > > > > > > ref: > https://wiki.php.net/rfc/deprecations_php_8_6#deprecate_the_list_construct > > > > > > I don't think it makes sense to deprecate list() if we're not > > deprecating array() - they're exact counterparts, and both replaced by > > the [] syntax. Indeed, [] as a replacement for array() dates to PHP 5.4, > > but as a replacement for list() was only added in PHP 7.1. > > I'm actually in favor of deprecating `array()` too, and I raised this > on the #php-internals Discord channel. Are you crazy? That would invalidate at least three quarters of the WordPress core code base and almost all of it's plugins, not to mention THOUSANDS of tutorials on stack overflow. And whether you like it or not about 40-60% of PHP sites use WordPress, depending on who you ask. That would almost certainly cause that community to either refuse to upgrade, leading to the problem the Python community faced with 2 & 3, or cause them to fork PHP. To be clear, I find it ugly as Hell too, and I'd love to see the end of the @ error suppression operator, but there are things that simply cannot be done.
