Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105121
MIME-Version: 1.0
References: <003a01d4eaf0$c17d6c20$44784460$@jhdxr.com> <etPan.5ca70798.56da8f03.d25@stijnpeeters.nl>
 <07B1B207-1FCE-412F-837A-6956DCCA1F51@gmail.com>
In-Reply-To: <07B1B207-1FCE-412F-837A-6956DCCA1F51@gmail.com>
Date: Sat, 6 Apr 2019 06:36:50 +0100
Message-ID: <CA+kxMuTnBMTMDgfcK7ZqLKei6_+c91xVur6C74nr_EdE4UAf9Q@mail.gmail.com>
To: Claude Pache <claude.pache@gmail.com>
Cc: Stijn Peeters <ik@stijnpeeters.nl>, CHU Zhaowei <me@jhdxr.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Spread Operator in Array Expression v0.2
From: Danack@basereality.com (Dan Ackroyd)

On Fri, 5 Apr 2019 at 09:03, Claude Pache <claude.pache@gmail.com> wrote:
>
> That begs the question: why is this invalid for function calls?

At least in part, because if we ever wanted to add a standard
_toArray() method, like we have __toString(), it would be quite a
massive BC break if we already made it so that PHP automatically
encased a single variable into an array, where an array was expected.

> In fact, I am able to easily hack around the limitation:
>
>     $result = someFunction(...$arr1, ...$arr2, ...[111]); // valid
>
> but the limitation seems just an unnecessary annoyance.

Typing a couple of extra characters, to avoid needing extra magic
behaviour, seems a good trade-off to me.

cheers
Dan
Ack