Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91105
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <38.31.07203.2EB94B65@pb1.pair.com>
References: <38.31.07203.2EB94B65@pb1.pair.com>
Date: Mon, 8 Feb 2016 13:34:58 +0700
Message-ID: <CAEZPtU4BxDVO9n+3A6ZC4gqxHrKm6actA3T7LC39Mu4ioPWurg@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC][VOTE] Allow specifying keys in list()
From: pierre.php@gmail.com (Pierre Joye)

On Fri, Feb 5, 2016 at 7:55 PM, 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!

I voted yes as I like some use cases and the obvious syntax.

However I almost voted no because of the examples about usage as a
half backed named argument, covered in future scope. I mentioned it
during the discussion phase but I will vote against this kind of
things as real named arguments support would be by far superior than
that, for the record here :)

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org