Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83315
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.182 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CAPhkiZyH1erPE=Set9dOdtv=ikOB64u1NLnsn12dm5qPcxPOLQ@mail.gmail.com>
References: <CAFMT4No-KBHn6s5MqTV9CAQYHKCMWbiOnAwfPx8Xj=-x5++hHg@mail.gmail.com>
	<CAFMT4NpTHMtfJuqO_RC6c8cv2Zg=JxFBC7pn6RHnrzqCON_r6Q@mail.gmail.com>
	<04db01d04cc1$d9925770$8cb70650$@php.net>
	<CAPhkiZyH1erPE=Set9dOdtv=ikOB64u1NLnsn12dm5qPcxPOLQ@mail.gmail.com>
Date: Fri, 20 Feb 2015 09:00:21 -0700
Message-ID: <CAFMT4NprvaGUV2mHkLf9ZyXm7WBmX4r-shy9vZXyhymMeT5YJw@mail.gmail.com>
To: Andrey Andreev <narf@devilix.net>
Cc: francois@php.net, internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: [RFC] Reserving More Types in PHP 7
From: levim@php.net (Levi Morrison)

On Fri, Feb 20, 2015 at 4:21 AM, Andrey Andreev <narf@devilix.net> wrote:
> On Fri, Feb 20, 2015 at 6:01 AM, Fran=C3=A7ois Laupretre <francois@php.ne=
t> wrote:
>> Add 'resource', 'object', 'scalar', 'mixed', 'numeric'

If someone wants to reserve these I will leave them up to another RFC,
as I suspect they are more controversial than what I have proposed.

>> Remove 'double' (avoid this alias if we decide to encourage 'float' ever=
ywhere)
>>
>> Not sure we'll use Boolean and integer but reserve also.
>>
>> Hope 'null', 'true', and 'false' can technically be used as type hints. =
If not, bad news, especially for null. Love 'int|false' as return type !

This is out of scope for this RFC, but if this RFC passes they would
be reserved which means this *could* be done without BC breaks in the
future.

> I'd rather not reserve 'resource'. Such a hint may be useful in the
> short term, but there already are plans to turn the current resources
> into objects, and with the rise of REST lately it is also an obvious
> base class/interface/trait name.
>
> Agree on 'double' though ... if we want to discourage its usage, we
> might even think of deprecating it.

While deprecating it might be a good course of action, it is out of
scope of this RFC. I personally think that reserving it is a good way
to discourage its use: simply reserve it and then don't use it for
anything. If we decide not to use the aliases if we have scalar types
and the aliases are reserved this would prevent users from making
custom types from the aliases. In my opinion this a Good Thing.