Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85107
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.217.176 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <CA+kxMuSJmWGQrVwr5Wjeyq7sqShxbvvd3sQXxpWNuPjU0V7ODw@mail.gmail.com>
References: <CAESVnVoL90DRhehrXVk9EpC2SxDNBu2-o-J69+F9s-GY2K3pRQ@mail.gmail.com>
	<CA+kxMuSJmWGQrVwr5Wjeyq7sqShxbvvd3sQXxpWNuPjU0V7ODw@mail.gmail.com>
Date: Mon, 16 Mar 2015 19:49:31 -0400
Message-ID: <CAESVnVpm1BnSyU1MCpBnBXp_NpBEfxUZ86gbfxDGOrv2CxkvhA@mail.gmail.com>
To: Dan Ackroyd <danack@basereality.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [VOTE] Reserve even more type hints
From: pollita@php.net (Sara Golemon)

On Mon, Mar 16, 2015 at 7:37 PM, Dan Ackroyd <danack@basereality.com> wrote:
> On 16 March 2015 at 06:44, Sara Golemon <pollita@php.net> wrote:
>> The voting period for the "Even More" type hints reservation RFC is now open.
>>
>
> There's been a little bit of traffic on the list in the past few days;
> I don't think your RFC has received enough cogent discussion.
>
I can't force people to talk about something.  Especially something so
minor while the war-of-the-century is being waged.

> In particular the keywords 'Resource' and 'mixed' seem to have limited
> need to be reserved. I don't believe there has been any suggestion
> that either of these would actually be used as types for PHP 7.x. So
> making them be unusable seems to be a large BC hit for no gain for
> people who currently have classes that use them
>
To be clear, this RFC is about declaring these names as reserved, not
about actually /using/ them.  There's no language in the RFC about
actually throwing errors or other code-breaking behavior.  Therefore,
even should all of them pass, it does *NOT* mean that your code using
these names suddenly stops working on PHP7.  It means that you have
been warned that using the names of intrinsics is a bad idea, and that
the language reserves the /right/ to make doing so an error at some
point in the future.

> Can anyone please make a strong argument for why 'resource' and
> 'mixed' should be reserved, if we currently have no plans to use them?
>
In the case of "resource", because it refers to a real type in PHP's
type system.  Using that intrinsic as an arbitrary label is a bad
idea.  It'd be like putting your project's code in the PHP namespace.
There's nothing in the language preventing you from doing so, but it's
a bad idea.  Formalizing that it's a bad idea is what this RFC does.

As far as "mixed"... I don't have a strong reason for it.  TBQH, I'm
not strongly in favor of all of these supplemental types. but they're
included for completeness, and presented as individual voting options
for flexibility.

-Sara