Talk:Futures and promises

Requested move

 * The following discussion is an archived discussion of the . Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section. 

Future (programming) → Futures and promises (programming) — The scope of the article has been changed to reflect the fact that there is a technical distinction between "futures" and "promises" in several programming languages (although they are very similar and should still be covered by the same article). DavidHopwood 01:23, 22 March 2007 (UTC)

Survey

 * Add  # Support   or   # Oppose   on a new line in the appropriate section followed by a brief explanation, then sign your opinion using ~ .  Please remember that this survey is not a vote, and please provide an explanation for your recommendation.

Survey - in opposition to the move
I added some material to clarify the definition of futures. After doing so, it seems to me that a similar definition of promises is badly needed since the promise concept seems highly ambiguous.--2ndMouse 14:03, 24 March 2007 (UTC)

Discussion

 * Add any additional comments:

Is the "(programming)" disambiguation really needed? Futures and promises is also a redlink, and I suspect that somebody would just move the article there later, because we're not distinguishing futures and promises in programming from some other "futures and promises". -GTBacchus(talk) 02:48, 28 March 2007 (UTC)
 * The above discussion is preserved as an archive of the proposal. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.
 * Even with the additions that 2ndMouse suggests, the article would still cover both futures and promises, and as GTBacchus points out, there is no need for the disambiguating term. Future (programming) has been moved to futures and promises as the result of a move request. Stemonitis 08:06, 28 March 2007 (UTC)

"Promise" term
I really don't believe that the use of the definition of "Promise" is the correct term to be used in this article, but rather "expectations". Humans expect things that are better than was previously presented before, and this is the future of anything. Everything that has been invented and engineered was due to to the fact that people were confronted with a limited problem that involved the expectations of something better. To promise something would imply that a time machine would have already been invented, for example. It is more accurate to say that the belief in the invention of a time machine by now was a possibility, or even an expection, in that era. To promise this would guarantee that it was definitely a reality now. That is if a promise is like anything my loving girlfriend pulls off time and time again. I've had a few drinks in the past few hours, so I hope I make some sense. E-mail me if you have any questions, I'm sure I'd find it entertaining arguing with you. Bring it on nerds. cerulean_flame@yahoo.com


 * Well, since Wikipedia documents, not invents, the issue is a bit moot. They're called "futures" and "promises" in the field, so calling them anything else on Wikipedia will just confuse matters.  (Oh, and where i come from, you can only make promises about the future, and promises can be broken. :)  --Piet Delport 12:47, 10 January 2006 (UTC)

I don't think Burgess's work (Promise Theory) fits in here, and if it can't be merged in this article, the articles cannot *be* merged.Aaronchall (talk) 22:50, 5 January 2016 (UTC)

Java 1.5 Futures
Is there any relation to Future interface in the Java API?


 * Not really. You can think of Java's   as a one-element, one-shot, thread-safe result queue.  It's useful for thread synchronization, but doesn't implement any of the techniques described in this article.  --Piet Delport 10:46, 3 February 2006 (UTC)
 * Yes there is;  implements an "explicit future". The article now describes the difference between this and the implicit futures/promises implemented by most of the other languages mentioned. --DavidHopwood 02:20, 21 March 2007 (UTC)
 * Addendum: As the article mentions, there is a dialect of Java, called Flow Java, which does implement single-assignment and future variables.  The website has a nice paper and presentation about how they are used, and what kind of problems they can solve.  --Piet Delport 09:52, 5 April 2006 (UTC)

Twisted's Deferred
Is this the same as Twisted's deferred object? If not, how does it differ?


 * Not meaningfully.  s are similar to Java 1.5's , discussed above;  the main difference is that they're usually used without threads, and have their results processed by a dual callback/errback chain instead of a polling/blocking caller.  --Piet Delport 23:55, 19 September 2006 (UTC)


 * That's correct, although this feature of Twisted was inspired by promises in E. The differences are mainly due to the fact that Twisted is strictly a library/framework; it doesn't change the Python language. --DavidHopwood 02:24, 21 March 2007 (UTC)

what about C# TPL
I think C# TPL implements this concept. I wonder why it is ignored in the list of languages implementing the concept [Futures]


 * Added. --David-Sarah Hopwood ⚥ (talk) 02:46, 25 September 2009 (UTC)

Future is associated with a thread or not?
"Futures and delays are well defined in terms of their denotational semantics in the Actor model. These definitions do not require recourse to low level implementation concepts such as threads."

"a future is associated with a specific thread that computes its value. This computation may be started either eagerly when the future is created, or lazily when its value is first needed. A lazy future is similar to a thunk (in the sense of a delayed computation)."

In the first statement it is said the a future does not require do recourse to threads, however, in the second statement it is said that a future is associated with a specific thread. Shouldn't it be associated with a specific computation instead of a thread? —Preceding unsigned comment added by 89.180.107.28 (talk) 14:00, 30 June 2009 (UTC)


 * You are correct: futures (like all Actors) are not associated with a specific thread.  The article has been corrected.  See what you think. --98.210.236.129 (talk) 14:21, 30 June 2009 (UTC)


 * Seems good to me. Thank you for the clarification. —Preceding unsigned comment added by 89.180.107.28 (talk) 15:46, 1 July 2009 (UTC)

Lucid
Does Lucid really support futures in the sense meant here? It supports stream-based dataflow, but that's not the same thing. I don't know enough about the language to be sure, though. --David-Sarah Hopwood ⚥ (talk) 04:57, 25 September 2009 (UTC)

Future vs Promise
"some differences in usage between 'future' and 'promise' are discussed below"

Having trouble finding this discussion —Preceding unsigned comment added by 1.153.45.43 (talk) 19:26, 17 January 2011 (UTC)

There is a discussion of futures versus promises in Actor Model of Computation published in arXiv:1008.1459. 70.137.165.34 (talk) 20:08, 17 January 2011 (UTC)

What is stinging or forcing?
The article says "Obtaining the value of an explicit future can be called "stinging" or "forcing"." but does not explain what these mean or whether there is a difference. — Preceding unsigned comment added by Gvanrossum (talk • contribs) 18:50, 11 January 2012 (UTC)

Should mention jQuery's Deferred / Promise implementation
Possibly the most visible implementation of this concept is the one added to jQuery in version 1.5. There were other JavaScript implementations before it, but jQuery is getting more and more ubiquitous all the time, and of course JavaScript has been ubiquitous for years.

I had never come across this concept outside of jQuery despite my 22 years of programming. &mdash; Hippietrail (talk) 16:31, 8 August 2012 (UTC)

Swift
Under programming languages with built-in futures, Swift is listed, pointing to the Apple programming language. I don't believe Swift includes futures, is this intended to point to the scripting language? Cjhenck (talk) 20:55, 30 September 2015 (UTC)

Version 6 or 7 for ECMAScript?
Regarding promises, sub section History says "... drafts of ECMAScript 7 ...". Whereas ECMAScript, 6th Edition contains "Other new features ... collections (maps, sets and weak maps), promises, number and math enhancements ...".

Which one is correct? --Mortense (talk) 09:47, 5 June 2016 (UTC)


 * It is likely this article that is incorrect, see ES6 — promises, Let’s talk about ECMAScript 2015. --Mortense (talk) 10:13, 5 June 2016 (UTC)

Start out with a definition and a simple example
The article is very difficult to read unless the reader already know what a future is. It should start out with a simple example that is easy to grasp for beginners.nielsle — Preceding unsigned comment added by 89.23.239.99 (talk) 11:58, 10 July 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Futures and promises. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20130112092827/http://gpars.codehaus.org/ to http://gpars.codehaus.org/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 04:05, 9 October 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on Futures and promises. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20090418025331/http://haskell.org/ghc/docs/latest/html/libraries/base/Control-Concurrent-MVar.html to http://www.haskell.org/ghc/docs/latest/html/libraries/base/Control-Concurrent-MVar.html
 * Added archive https://web.archive.org/web/20081011003837/http://www.udanax.com/gold/ to http://www.udanax.com/gold/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 05:18, 6 January 2018 (UTC)