Promises¶
Liskov, B., & Shrira, L. (1988). Promises: Linguistic Support for Efficient Asynchronous Procedure Calls in Distributed Systems. Proceedings of the SIGPLAN '88 Conference on Programming Language Design and Implementation, 260-267.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Future Or Promise
- In computer science it is the futures and promises of Java, JavaScript, C++, Scala, Python, and Rust;
async/awaitacross modern languages; and reactive streams.This sourceIntroduces promises as first-class placeholders for the results of asynchronous remote procedure calls in distributed systems, with call-streams composing sequences of such calls.
Supported in partVerified against the publisher's abstract
Establishes the origin of the promise construct for asynchronous calls, but says nothing about Java, JavaScript, C++, Scala, Python, Rust, async/await, or reactive streams.
“It describes a new data type called a promise that was designed to support asynchronous calls. Promises allow a caller to run in parallel with a call and to pick up the results of the call, including any exceptions it raises, in a convenient and type-safe manner.”
- In computer science it is the futures and promises of Java, JavaScript, C++, Scala, Python, and Rust;
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:fd6a1c52b1d3 · see in the full table