W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2017

[webrtc-pc] editorial: 4.3.1 Operation "settled" is not defined

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Tue, 09 May 2017 22:07:18 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-227512495-1494367637-sysbot+gh@w3.org>
fippo has just created a new issue for https://github.com/w3c/webrtc-pc:

== editorial: 4.3.1 Operation "settled" is not defined ==
> If subsequent calls are made while the returned promise of a previous call is still not settled, they are added to the queue and executed when all the previous calls have finished executing and their promises have settled.

This is promise terminology (and we don't say in the terminology section where we define that) which is only used in that paragraph and not even in the algorithm description below.

I think the first occurence could be avoided by saying "still pending" ([this](https://github.com/domenic/promises-unwrapping/blob/master/docs/states-and-fates.md) 'defines' "settled" as "not pending"). For the second use I actually prefer "settled" to "fulfilled or rejected"

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1189 using your GitHub account
Received on Tuesday, 9 May 2017 22:07:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:50 UTC