Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83525
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.45 as permitted sender)
Message-ID: <54EA850E.7010301@gmail.com>
Date: Sun, 22 Feb 2015 17:40:30 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Niktia Nefedov <inefedor@gmail.com>, 
 "internals@lists.php.net" <internals@lists.php.net>
References: <op.xudk90d77q1gix@nikita-hp-elitebook-750-g1>
In-Reply-To: <op.xudk90d77q1gix@nikita-hp-elitebook-750-g1>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Allow to use argument unpacking at any place in arguments
 list
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> This makes it impossible to use this feature with some of the ext/std
> functions (array_udiff, array_interect_ukey, etc.) and just feels a bit
> incomplete...

I see how it can be useful with crazy functions like array_udiff, but
these are in tiny minority. What I am concerned about is that besides
those functions - which are weird anyway - code like foo($a, ...$b, $c)
would be completely unmanageable as it would be impossible to know where
$c is actually going. I think the case for weird array functions is
pretty narrow and can be handled in ad-hoc manner without introducing
this construct.

> I'm not sure if this change requires an RFC because this is a pretty
> small, advancement of already existing feature that doesn't contain any

It's a new syntax (yes, looking a lot like an old one, but still new),
so I think it requires an RFC.
-- 
Stas Malyshev
smalyshev@gmail.com