Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100210
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <e38924a1-174d-457f-7363-79b40a1cc704@telia.com>
References: <CAH0Uv3G-nti+xRp39qkfJ38qLfj+9ty1SsODSpo8iRO8XQnFtw@mail.gmail.com>
 <CAESVnVq0APVDtwNV40B3q=iwpKRKbLNr8Ht+A+Vz8HsViqokSg@mail.gmail.com>
 <CANrtkQGdM4t=je8TYFP+=nPxptkb1X2w8OR=QTRTAvftN+-kNw@mail.gmail.com>
 <CAH0Uv3HQK5wjcd_-9GynMw34H78ZTv09q9bc=yZ10JBbeT=VOA@mail.gmail.com>
 <A3.98.34801.67DED895@pb1.pair.com> <CAH0Uv3Emi4x_wNFxvG6BU1+ZJ9D-i7Td2Z5yHszLYbtpwTE_cg@mail.gmail.com>
 <e38924a1-174d-457f-7363-79b40a1cc704@telia.com>
Date: Mon, 14 Aug 2017 13:34:32 +0200
Message-ID: <CADyq6sL9MRq19roFgmQu4_0Mty_AKAAs4c6Sw4XZabQpCM_W1Q@mail.gmail.com>
To: =?UTF-8?Q?Bj=C3=B6rn_Larsson?= <bjorn.x.larsson@telia.com>
Cc: Andreas Hennings <andreas@dqxtech.net>, Andreas Treichel <gmblar@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a1148f9702562c20556b50d15"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Allow default value in list() syntax
From: ocramius@gmail.com (Marco Pivetta)

--001a1148f9702562c20556b50d15
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

 > that doesn't clutter the language.

It actually does: now we have an expression-alike node that is lazy and
only evaluated when there's no default value. That's a lot of added
semantics for such an edge case feature.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

On Mon, Aug 14, 2017 at 11:35 AM, Bj=C3=B6rn Larsson <bjorn.x.larsson@telia=
.com>
wrote:

> Den 2017-08-12 kl. 02:37, skrev Andreas Hennings:
>
> This is true, I remember having done it in the past.
>>
>> I still think it would be nice and feel natural to have the default
>> values directly built into the list construct.
>>
>> It would be a bit faster, because it does not have to allocate a new
>> temporary array.
>>
>> Whether this difference matters depends on the case.
>> In my own philosophy, every code that I write to be reusable, could at
>> some point be used in a situation where it is repeated a lot, and thus
>> has a performance impact. So for my taste, it does matter.
>>
>> This said, I understand it not having the greatest priority.
>>
>>
>>
>> On Fri, Aug 11, 2017 at 7:46 PM, Andreas Treichel <gmblar@gmail.com>
>> wrote:
>>
>>> You can merge the result with default values like this:
>>>
>>> [$foo, $bar, $foobar] =3D explode(':', 'foo:bar') + [23, 42, 1337];
>>> var_dump($foo, $bar, $foobar);
>>>
>>>
>>>
>>> --
>>> PHP Internals - PHP Runtime Development Mailing List
>>> To unsubscribe, visit: http://www.php.net/unsub.php
>>>
>>> One could argue that:
> [$foo, $bar, $foobar =3D 1337] =3D explode(':', 'foo:bar');
>
> is more readable. I find it a small but nice addition
> that doesn't clutter the language.
>
> r//Bj=C3=B6rn
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a1148f9702562c20556b50d15--