Implement real futures

[brycelelbach]

[reported by blelbach] [Trac time Tue Aug 9 21:04:09 2011] Our current futures, while useful, are not truly futures, because they are not globally accessible. Futures need to be reimplemented as hpx::lcos::barrier-style managed component LCOS - that is to say, they should have GIDs, they should be reference counted, and they should be accessed through a client class.

[brycelelbach]

[comment by blelbach] [Trac time Sun Aug 14 22:01:56 2011] Bumping this to 1.0.0 as Hartmut would like #72 done earlier than 1.0.0, and I don't want to set unrealistic goals for 0.7.0.

[sithhell]

Do we still want/need this?

I'd argue to close this issue and mark it as "won't fix" as futures represent a return type or event which should not be referencable remotely. Furthermore, I think this contradicts with move-only futures.

[hkaiser]

Well, futures are remotely accessible. However, I agree that we should close this as we now have a way to pass futures to remote actions (and to return them).

[sithhell]

Closed. Please reopen and state your reasons if you still need this.