- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Sun, 28 Apr 2013 23:01:53 +0200
- To: "'Dave Longley'" <dlongley@digitalbazaar.com>
- Cc: "'Linked JSON'" <public-linked-json@w3.org>
On Sunday, April 28, 2013 9:29 PM, Dave Longley wrote: > On 04/28/2013 01:35 PM, Markus Lanthaler wrote: > > > > That's where we agree. IMO a Future isn't a construct to let you > > "call a method in the future" but a placeholder for a return > > value that might not be ready yet when the function returns. > > I'd be just fine with this, but I don't think that's how Futures > actually work. Rather, they have to be understood differently in order > to support certain use cases; you're supposed to be able to attach > handlers, etc. after obtaining the Future (or Promise) object before > indicating that you want it to run. Just out of pure curiosity: What use cases require to attach handlers after obtaining the Future but before indicating to run it? Why is a separate mechanism to execute/run the Future needed? -- Markus Lanthaler @markuslanthaler
Received on Sunday, 28 April 2013 21:02:34 UTC