FiberManager - addFiberFuture and blockingWait
Summary: This diff has two goals: - To provide an API that allows users to schedule async annotated functors to run on fibers (thereby removing the need to use `init_await` at the top of the stack) - To provide a boilerplate-free entry point into fiber code that should work for a majority of testing/benchmarking interactions with fiber manager. The diff implements two APIs: -addFiberFuture: wrapper around `fiberManager.addTaskFuture`. The differing name is to mainly avoid namespace collisions and avoid confusion with `coro::Task` - blockingWait: Fiber entry point helper Reviewed By: A5he Differential Revision: D22071005 fbshipit-source-id: 24ceea005d32f6e2c84b4599042703207504bd0f
Showing
Please register or sign in to comment