Hi internals,
Since there is no more questions for more than one week, I’ve opened the
vote on the spread operator in array expression RFC. The vote lasts two
weeks and it closes at 7-May.
https://wiki.php.net/rfc/spread_operator_for_array#vote
Regards,
CHU Zhaowei
Since there is no more questions for more than one week, I’ve opened the
vote on the spread operator in array expression RFC. The vote lasts two
weeks and it closes at 7-May.
I've hesitantly voted yes. I am unsure about the behavior with
references. This was brought up during discussion, but never really
addressed. It seems that this behavior is the same for array_merge.
It seems acceptable, though I am unsure if it is desirable or not.
Sorry for the one day delay. This RFC has passed with 43 votes in favor and
1 against.
Thanks & Regards,
CHU Zhaowei
Sorry for the one day delay. This RFC has passed with 43 votes in favor and
1 against.Thanks & Regards,
CHU Zhaowei
I've merged the implementation for this RFC yesterday. However, I would
like to propose adding one extra restriction, implemented in
https://github.com/php/php-src/pull/4162.
Currently, the implementation allows writing things like this:
[42 => 0, ...$array]
['a' => 'b', ...$array]
I think that with the current behavior of ..., where string keys are
forbidden and integer keys are reindexed, it would be best to make these
usages illegal as well, at least for the time being. Especially to avoid
tying our hands too much when it comes to adding the [$head, ...$tail] =
syntax in the future.
Nikita