RFC: FutureDAG
authorJames Sedgwick <jsedgwick@fb.com>
Mon, 18 May 2015 15:42:50 +0000 (08:42 -0700)
committerViswanath Sivakumar <viswanath@fb.com>
Wed, 20 May 2015 17:57:11 +0000 (10:57 -0700)
commitf51b046693ba4e381b19e1f1f4c1e0b8efdbb287
tree986c539b423a891d975f11746b2eca39a89cc17f
parent4ecf6e3f6d120907c0e32059a923d15cd6fcfedc
RFC: FutureDAG

Summary:
See task. Set up a DAG of Future-returning tasks (optionally with executors) and eventually kick them off.
One big question is ownership. Currently the user would be responsible for ensuring that the FutureDAG outlives its own completion. This requirement could go away with shared_from_this magic maybe

Test Plan: unit. I didn't bother to test via() functionality because it's too much work for now - the functionality is trivial. Same for "true-async" dags...

Reviewed By: hans@fb.com

Subscribers: folly-diffs@, jsedgwick, yfeldblum, chalfant

FB internal diff: D2073481

Signature: t1:2073481:1431961131:82a8898502d5308f6ab3cc8cc5b84b016d3998fe
folly/Makefile.am
folly/experimental/FutureDAG.h [new file with mode: 0644]
folly/experimental/test/FutureDAGTest.cpp [new file with mode: 0644]