Thanks for pointing this out, PhistucK. Now there's only one entry at
https://www.chromestatus.com/feature/5643236399906816 .

Dan

On Tue, May 31, 2016 at 7:58 AM, PhistucK <[email protected]> wrote:
> So which one should be removed? Can you merge their content in a reasonable
> way and remove one of them?
>
>
> ☆PhistucK
>
> On Tue, May 31, 2016 at 1:29 AM, Caitlin Potter <[email protected]>
> wrote:
>>
>> LGTM1 (just kidding)
>>
>> Sorry for not getting the launch process ball rolling myself months ago,
>> that probably should have happened.
>>
>> On Monday, 9 May 2016 17:11:05 UTC-4, Daniel Ehrenberg wrote:
>>>
>>> Contact emails
>>> [email protected]
>>>
>>> Spec
>>> https://tc39.github.io/ecmascript-asyncawait/
>>>
>>> Summary
>>> Async functions make it easy to write code which needs to "block" on
>>> certain asynchronous events JavaScript.
>>>
>>> Motivation
>>> Async/await does this by providing a simpler and more ergonomic way to
>>> use Promises. To block on a value, use the 'await' keyword. Async/await can
>>> be implemented based on a desugaring to generators, as described in the
>>> following design doc:
>>> https://docs.google.com/document/d/1K38ct2dsxG_9OfmgErvFld4MPDC4Wkr8tPuqmSWu_3Y/edit?usp=sharing
>>>
>>> Interoperability Risk
>>>
>>> None; in development in Firefox, Edge and Safari. All implementations in
>>> progress target correctness with respect to the specification.
>>>
>>>
>>> Compatibility Risk
>>>
>>> The draft specification creates new contextual keywords, but these do not
>>> change the behavior of any existing code and just allow new patterns which
>>> would have previously been syntax errors. Therefore, the compatibility risk
>>> should be minimal.
>>>
>>>
>>> Ongoing technical constraints
>>> None
>>>
>>> Tracking bug
>>> Dev bug: https://bugs.chromium.org/p/v8/issues/detail?id=4483
>>>
>>> Link to entry on the Chrome Platform Status
>>> https://www.chromestatus.com/features/5643236399906816
>>>
>>> Requesting approval to ship?
>>>
>>> No
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to