To address, jgraham's point, let's go back to just use "Run ..." style
phrasing.
I agree that we shouldn't mislead readers that task queuing is always
necessary. Moreover, I think algorithm may be allowed to be done either
synchronously or asynchronously for some cases. Maybe we could add
"possibl
On 1/14/14 10:44 AM, Domenic Denicola wrote:
So maybe we need slightly better phrasing; help appreciated.
Maybe the right way to spec this is to simply use two algorithms...
Algorithm A has some steps, then says to perform B asynchronously and
returns a promise. B has a bunch of steps that e
On 1/14/14 10:44 AM, Domenic Denicola wrote:
I do want to clarify that I want to avoid explicitly queuing needless tasks,
which then themselves go and perform asynchronous actions. Instead, just
perform the asynchronous action, and use the promise microtask queue to the
deliver the results.
From: Boris Zbarsky
> On 1/14/14 9:22 AM, Domenic Denicola wrote:
>> Do you think it would be improved by nesting step 5 under "These steps will
>> be run asynchronously"?
>
> Yes. Otherwise if there is another method that allows synchronously checking
> whether a bookmark has been added I wou
On 1/14/14 9:22 AM, Domenic Denicola wrote:
Do you think it would be improved by nesting step 5 under "These steps will be run
asynchronously"?
Yes. Otherwise if there is another method that allows synchronously
checking whether a bookmark has been added I would expect such a method
to retu
I like your way of phrasing it, because it does not explicitly queue a needless
task. But I am not sure how generally it applies. What did you think of the
addBookmark example?
https://github.com/domenic/promises-unwrapping/blob/master/docs/writing-specifications-with-promises.md#addbookmark--
Nice writing! Both the shorthand phrases and guidance look very useful for
writing Promise based specs.
I have only one comment on this section.
https://github.com/domenic/promises-unwrapping/blob/master/docs/writing-specifications-with-promises.md#maintain-a-normal-control-flow
I agree with your
FYI. (If you want to followup, please reply on www-tag @ w3.org)
Original Message
Subject:Guidance on the usage of promises for API developers
Resent-Date:Mon, 13 Jan 2014 22:50:19 +
Resent-From:
Date: Mon, 13 Jan 2014 22:49:30 +
From: ext Domenic Den
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24268
Morrita Hajime changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24288
Hayato Ito changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
10 matches
Mail list logo
