Re: [RFC] Deprecations for PHP 8.6
| From: | Michael Babker | Date: | Thu, 02 Jul 2026 03:19:33 +0000 |
| Subject: | Re: [RFC] Deprecations for PHP 8.6 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131695@lists.php.net to get a copy of this message | ||
> On Wednesday, Jul 01, 2026 at 10:44 PM, Seifeddine Gmati <azjezz@carthage.software
> (mailto:azjezz@carthage.software)> wrote:
>
> And this is what I keep coming back to: why this deprecation in
> particular? The same RFC deprecates several other things, and at least
> one of them is genuinely harder to migrate than
list(), which
> makes
> the focus on list() odd.
>
Because array construction and destructuring are much more widely used than most anything else in
the deprecations RFC, be it with “modern” or “legacy” syntax. And given core functions like
var_export still use the long “legacy” syntax for arrays, it seems like that alone should block
a deprecation proposal until someone finally lands a solution to let it use the other syntax.