Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86305
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.178 as permitted sender)
MIME-Version: 1.0
Date: Tue, 19 May 2015 17:28:34 +0200
Message-ID: <CAF+90c8ap8eEt0Bj1jY89AxS58QQ8ExTGGoR-zkRnJgg72UOMQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d041825bcb0ada6051670f6a4
Subject: Soft-reserve "void" class name
From: nikita.ppv@gmail.com (Nikita Popov)

--f46d041825bcb0ada6051670f6a4
Content-Type: text/plain; charset=UTF-8

Hi internals!

For PHP 7 we soft-reserved a number of class names [1] like "numeric", so
that we have the ability to introduce them as typehints in a 7.x release.
"Soft" here means that we only document these names as being reserved and
don't throw an error when they're used.

I'd like to add "void" to this list, so we have the option to introduce a
void return type in PHP 7.x. I've seen some disagreement as to whether this
should be called "void" or "null" - this discussion should be held when an
RFC comes up, however we need to keep both options open until then.
(Currently only "null" is reserved.)

If people think that this requires a vote, I'll open one.

Thanks,
Nikita

[1] https://wiki.php.net/rfc/reserve_even_more_types_in_php_7

--f46d041825bcb0ada6051670f6a4--