Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119675
MIME-Version: 1.0
In-Reply-To: <CAGBsUrfxk-krEeimWMMaJv-8CTOq-uU1=f3f6eA7jbno27BuTA@mail.gmail.com>
References: <CAC_PL4zjupNSx_qx9cESuu5jKRx1uSDiaO2GQyCKMikmAKRr6g@mail.gmail.com>
 <CAGBsUrfxk-krEeimWMMaJv-8CTOq-uU1=f3f6eA7jbno27BuTA@mail.gmail.com>
Date: Thu, 9 Mar 2023 07:53:15 +0500
Message-ID: <CAC_PL4wnJXiRkOJA5J0bQbs8KU4J-um0GNNNvBvC9etxsoaP3g@mail.gmail.com>
To: Kamil Tekiela <tekiela246@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Two Issues regarding Named Parameters; want to
 understand the technicality
From: office.hamzaahmad@gmail.com (Hamza Ahmad)

Hi Kamil,

Thank you for your response. I shall sure create an issue and will
update in this threat.

On 3/9/23, Kamil Tekiela <tekiela246@gmail.com> wrote:
> Hi Hamza,
>
> If you encounter a bug, please create a GitHub issue with reproducible
> steps. Your description of a program crashing is not actionable, as we
> cannot reproduce this error.
>
> Regarding your second point, how do you want this to work? $names is just a
> collection of string parameters. It's not a single parameter so you cannot
> refer to it by name. When you use named parameters with variadic
> parameters, then the names you specified will be used as array keys. So no
> error there, and no warning should be raised. But I don't know what you had
> in mind of how this is supposed to work.
>
> Regards,
> Kamil
>