On Sep 28, 2015 11:53 PM, "Levi Morrison" <le...@php.net> wrote: > > On Mon, Sep 28, 2015 at 9:17 AM, Thomas Hruska <thru...@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).
This model totally failed for us in the past. And given that these keywords will be used for anything related to async APIs, let reserve them and put our users on the safe side already.
