Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114817
MIME-Version: 1.0
References: <CAF+90c9zifA=aq=SM8-iP3b0gzHy2uR_zrH8OCF4ECLu6-tWdg@mail.gmail.com>
 <CAF+90c-vsAGt_o4EwEM9RrRc1TViwmZnfCrk3JmX9XWeYf77fQ@mail.gmail.com>
In-Reply-To: <CAF+90c-vsAGt_o4EwEM9RrRc1TViwmZnfCrk3JmX9XWeYf77fQ@mail.gmail.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Thu, 10 Jun 2021 09:50:07 -0600
Message-ID: <CAAKU0unN0qTMRP4ua6sXWzvezUG5nqHd-aycuK=5eft6vdmv5A@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Re: Allow combining arg unpacking and named args
From: internals@lists.php.net ("Levi Morrison via internals")

On Thu, Jun 10, 2021 at 7:14 AM Nikita Popov <nikita.ppv@gmail.com> wrote:
>
> 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

No objection. In my head I figured the unpack would come after named
parameters, but it makes sense that an unpack which can contain both
positional and named arguments would come between the positional and
named arguments.