Re: "non-missable" events, or multi-promises

On Tue, Sep 22, 2015 at 4:50 PM, Zibi Braniecki wrote: > This sort of repeatable-promise, would reduce it to: > 1) Set the repeatable promise on the target > > Sounds like it would make much easier to write async code without logic for > preventing race conditions.

"non-missable" events, or multi-promises

There seem to be an interesting section in Promises doc from 2001 about multi-state promises - https://www.w3.org/2001/tag/doc/promises-guide#state-transitions One of the things that we are working on is a spec for loading localization resources into HTML, which resembles the example from this

Re: "non-missable" events, or multi-promises

On Tuesday, September 22, 2015 at 3:02:21 AM UTC-7, smaug wrote: > That document is from 2015 ;) Oh. Fun! > The example in that chapter is "This property should return the same promise > every time it is retrieved, until the image moves backward from the > loaded state into the unloaded state.

Re: "non-missable" events, or multi-promises

On 09/22/2015 09:49 AM, Zibi Braniecki wrote: There seem to be an interesting section in Promises doc from 2001 about multi-state promises - https://www.w3.org/2001/tag/doc/promises-guide#state-transitions That document is from 2015 ;) One of the things that we are working on is a spec