Lines Matching refs:be
26 - Promises can be cancelled.
37 why the promise cannot be fulfilled.
98 Promises can be chained one after the other. Each then in the chain is a new
101 subsequent promises in the chain to only be fulfilled when the returned promise
102 has been fulfilled. The next promise in the chain will be invoked with the
240 can be obtained by calling the `getReason` method of the exception.
270 When unwrapping a promise, the resolved value of the promise will be waited
273 wait function will be the value delivered to promise B.
334 the parent most ancestor that has not yet been resolved will also be
336 be cancelled.
354 A fulfilled promise can be created to represent a promise that has been
371 A rejected promise can be created to represent a promise that has been
416 task queue will be automatically run to ensure that the blocking promise and
419 you do not run the task queue, then promises will not be resolved.
437 *TODO*: Perhaps adding a `futureTick()` on each tick would be faster?
485 consumers of the promise cannot modify the value that will be eventually
489 iteratively is that you need to be able for one promise to reach into the state
508 …ting between global and local copies of the package. The function API will be removed in 2.0.0. A …
537 … send an email to security@tidelift.com. All security vulnerabilities will be promptly addressed. …