Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91095
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.45 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <38.31.07203.2EB94B65@pb1.pair.com>
References: <38.31.07203.2EB94B65@pb1.pair.com>
Date: Fri, 5 Feb 2016 20:58:00 -0700
Message-ID: <CAFMT4NqwTruax5_OO0B1DxJ9aHFeZ7sb3B_Agc1UT5Whnb_-Ng@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC][VOTE] Allow specifying keys in list()
From: levim@php.net (Levi Morrison)

On Fri, Feb 5, 2016 at 5:55 AM, Andrea Faulds <ajf@ajf.me> wrote:
> Hi everyone,
>
> It's been more than two weeks since I first proposed this RFC, and there's
> no outstanding issues preventing moving towards a vote. There's not yet a
> language specification patch, but that can be done later.
>
> So, I'm opening the vote on this RFC today, 2016-02-05, and it'll close the
> Sunday after next, 2016-02-14. The vote requires a 2/3 majority as it's a
> language change.
>
> The RFC page is here: https://wiki.php.net/rfc/list_keys
>
> Happy voting!
> --
> Andrea Faulds
> https://ajf.me/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php

I wanted to chime in since I voted no. I'm not strongly opposed to
this behavior but I do have concerns about the key behavior that was
changed. In an example in the RFC:

    list($foo => $bar) = $array;

I don't think this really makes sense. `$foo` is being evaluated and
its value is used to look up the key in `$array`, but `$bar` is being
assigned to even though it's a similar place as `$foo`.

I don't think I've really expressed well what I am trying to convey
but I think this RFC would be much better *without* this change, so
I've voted no.