Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88530
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.68 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <56095A0C.4070306@cubiclesoft.com>
References: <CALW=WEBPC2N2tzmU1uB_v93YXLa1MA97=0_q7zP0F6G+uRPDNQ@mail.gmail.com>
	<56095A0C.4070306@cubiclesoft.com>
Date: Mon, 28 Sep 2015 10:53:29 -0600
Message-ID: <CAFMT4NqaqVX-KHh9iz_R05wxp2h=aajv5RuQGh2EQVSNHoLGaQ@mail.gmail.com>
To: Thomas Hruska <thruska@cubiclesoft.com>
Cc: "S.A.N" <ua.san.alex@gmail.com>, internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] async/await - is future reserved words in PHP 7.x?
From: levim@php.net (Levi Morrison)

On Mon, Sep 28, 2015 at 9:17 AM, Thomas Hruska <thruska@cubiclesoft.com> wrote:
> On 9/28/2015 1:29 AM, S.A.N wrote:
>>
>> Are there any future plans for - async/await?
>> This need to know now, not to use these words to constants, and class
>> names...
>
>
> async/await is the single greatest addition to modern application
> development in the last 20 years.  Every language needs these features.
> Microsoft completely solved the core problems surrounding multithreaded
> programming with the concepts behind these two keywords.

While not disputing this claim I think PHP should only reserve words
when there are somewhat concrete plans for their use. There have been
talks and draft RFCs for things like void returns and union types with
Foo | null, so reserving `void` and `null` makes sense. Perhaps there
is a massive effort somewhere off-list but I am not aware of any plans
on implementing async/await in PHP.

If you are worried about them becoming reserved then simply do not use
`async` and `await` as method, constant or class names. There ends the
issue (in my opinion).