Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114007
MIME-Version: 1.0
Date: Fri, 9 Apr 2021 09:23:26 +0200
Message-ID: <CAG9XoMQFF+Anutc92iGFX1bOw-w1TWvwNa-XZeKw1GrGGSbWGg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d599e105bf850a1c"
Subject: Required parameter after optional one
From: benjamin.morel@gmail.com (Benjamin Morel)

--000000000000d599e105bf850a1c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi internals,

I'm wondering why PHP 8 started warning about required parameters declared
after optional ones, when this version is the one that also introduced
named parameters, which can take advantage of this:

```
function test($a =3D 1, $b) {
    echo $a, $b;
}

test(b: 2);
```

> Deprecated: Required parameter $b follows optional parameter $a in
/in/DmhYG on line 3
> 12

https://3v4l.org/DmhYG

If I'm not mistaken, the introduction of this warning (January 2020
<https://externals.io/message/108052>) predates the introduction of named
parameters (May 2020 <https://wiki.php.net/rfc/named_params>), which could
explain why it would have temporarily made sense to introduce this warning.

Shouldn't it be removed now, that it makes IMO full sense with named
parameters to have required and optional parameters at arbitrary positions?

Thank you for your time,

=E2=80=94 Benjamin

--000000000000d599e105bf850a1c--