Re: async/await - is future reserved words in PHP 7.x?
| From: | Björn Larsson | Date: | Mon, 28 Sep 2015 18:52:01 +0000 |
| Subject: | Re: async/await - is future reserved words in PHP 7.x? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-88531@lists.php.net to get a copy of this message | ||
Den 2015-09-28 kl. 18:53, skrev Levi Morrison:
On Mon, Sep 28, 2015 at 9:17 AM, Thomas Hruska <thruska@cubiclesoft.com> wrote:mentioned as one key area for the future, see: - https://blog.amasty.com/php-7-and-script-languages-future-insights-from-lead-zend-com-developer Hope it materialises some day! Regards //BjörnOn 9/28/2015 1:29 AM, S.A.N wrote: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 reservingAre 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.voidandnullmakes sense. Perhaps there is a massive effort somewhere off-list but I am not aware of any plans on implementing async/await in PHP. In the interview with Dmitry asynchronous behaviour was