Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93076
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.193 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <B0.14.16256.4234A275@pb1.pair.com>
References: <CAH8Mpn=qHqqQsoMusw0WJG2UGiQ7g43_a7gpG=Bcy0LGSpjyUg@mail.gmail.com>
	<18.B0.04700.FD2DC065@pb1.pair.com>
	<CALW=WEDkdEQbOez3xM4yr4Lu3192EXmpoZUq5gDkMDFSmicQPQ@mail.gmail.com>
	<38.90.16256.DC90A275@pb1.pair.com>
	<CANUQDCjSAihdrzCr1Ygt6dWJgPqL4ivzS8uoG8dFVXLxeuA8mg@mail.gmail.com>
	<B0.14.16256.4234A275@pb1.pair.com>
Date: Wed, 4 May 2016 22:56:30 +0300
Message-ID: <CALW=WEBygH380inAkeH8F31i0Ea9gfckoO3fDquJ+p4RUogQQg@mail.gmail.com>
To: Stephen Coakley <me@stephencoakley.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Re: async/await - is future reserved words in PHP 7.x?
From: ua.san.alex@gmail.com ("S.A.N")

> I don't think we should wait, I was just thinking that it might not be ready
> until that time.
>
> Also, if we plan on rewriting streams and I/O to all be async and use libuv
> underneath, that would probably be a BC break unless the existing functions
> just become blocking interfaces for a separate async API. If it was a large
> BC break, it probably would need to wait for PHP 8.
>
> Now that I think about it, that would be our chance to replace stream
> resources with classes...
>
> $file = \php\stream::open("file.txt");
> $bytes = await $file->read(1024);
> $file->close();
>
> Then rewrite fread() and friends to be aliases that block instead of await
> results.

This is a great opportunity to normalize API standard libraries PHP :)

> $bytes = await $file->read(1024);

It is rarely necessary, more often needs

$result = await $db->query($sql);
and
$result = await $noSql->get($key);