Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105076
MIME-Version: 1.0
References: <003a01d4eaf0$c17d6c20$44784460$@jhdxr.com>
In-Reply-To: <003a01d4eaf0$c17d6c20$44784460$@jhdxr.com>
Date: Thu, 4 Apr 2019 17:57:43 +0200
Message-ID: <CABdc3WoxnecidPmob+nJVJ49u8vzconJiU64hv-vx9XJAbFciQ@mail.gmail.com>
To: CHU Zhaowei <me@jhdxr.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f4e54c0585b66ea1"
Subject: Re: [PHP-DEV] [RFC] Spread Operator in Array Expression v0.2
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Brzuchalski?=)

--000000000000f4e54c0585b66ea1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi CHU Zhaowei,

Where can I find first RFC version? Revisited RFCs AFAIK should be served
under different name.

Personally I liked key preserve behavior. Without it use of spread operator
I array expression would have minor use. But this is my personal feeling
about only.

I think I'm missing something in RFC. Usage in key preserved array
expression is not covered and the RFC doesn't describe how it would behave.

Thanks for the efforts on it

BR,
--
Micha=C5=82

czw., 4 kwi 2019, 16:15 u=C5=BCytkownik CHU Zhaowei <me@jhdxr.com> napisa=
=C5=82:

> Hi internals,
>
> Thanks for the people who joined the discussion of my [RFC: Spread
> Operator in Array Expression](
> https://wiki.php.net/rfc/spread_operator_for_array). The biggest change
> is I have dropped the support for string keys in v0.2 as suggested by C=
=C3=B4me,
> to make the behavior of spread operator consistent. I have also added Q&A
> to explain the questions I received.
>
> Thanks & best regards,
> CHU Zhaowei
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--000000000000f4e54c0585b66ea1--