Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103046
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.43 as permitted sender)
MIME-Version: 1.0
Sender: nicolas.grekas@gmail.com
Date: Mon, 6 Aug 2018 15:02:34 +0200
Message-ID: <CAOWwgpkmdubYgEmu=opTOx_nBL8xVWNGuo-d_4xotx-5GGMg3Q@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>, Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005a9dd80572c3e557"
Subject: Deprecations for PHP 7.4, preparing named args
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--0000000000005a9dd80572c3e557
Content-Type: text/plain; charset="UTF-8"

Hello,

I was reading https://wiki.php.net/rfc/named_params again. Named args would
be great for 8.x.

Following https://wiki.php.net/rfc/deprecations_php_7_4, would it make
sense to deprecate calling `call_user_func_array` with associative arrays,
so that it can be made to work with named args in 8.0? Another option would
be to deprecate `call_user_func_array` altogether and recommend using the
splat operator instead. WDYT?

The named params RFC also tells about "Signature validation allows changing
parameter names", adding a requirement to keep the same parameter name in
child classes. Should this requirement be added to 7.4 with a deprecation
notice?

Are there other things we should deprecate to make room for named args?

Just throwing the ideas so we don't forget considering them, thanks for
reading.

Nicolas

--0000000000005a9dd80572c3e557--