Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114810
MIME-Version: 1.0
References: <CAF+90c9zifA=aq=SM8-iP3b0gzHy2uR_zrH8OCF4ECLu6-tWdg@mail.gmail.com>
In-Reply-To: <CAF+90c9zifA=aq=SM8-iP3b0gzHy2uR_zrH8OCF4ECLu6-tWdg@mail.gmail.com>
Date: Thu, 10 Jun 2021 15:14:11 +0200
Message-ID: <CAF+90c-vsAGt_o4EwEM9RrRc1TViwmZnfCrk3JmX9XWeYf77fQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b804c005c4692b64"
Subject: Re: Allow combining arg unpacking and named args
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000b804c005c4692b64
Content-Type: text/plain; charset="UTF-8"

On Tue, May 25, 2021 at 4:18 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> Currently, argument unpacking (...$foo) cannot be combined with named
> arguments (foo: $bar) at all. Both func(...$args, x: $y) and func(x: $y,
> ...$args) are rejected by the compiler.
>
> https://github.com/php/php-src/pull/7009 relaxes this by allowing
> func(...$args, x: $y). The named arguments are required to come last,
> because this automatically enforces the invariant that named arguments must
> be sorted after positional argument.
>
> Are there any concerns with relaxing this restriction?
>

Any further feedback on this?

Nikita

--000000000000b804c005c4692b64--