(non-default) Executors and make_ready_future

[drussel]

make_ready_future uses the default executor implicitly, which doesn't matter for the future itself, but does for continuations that don't explicitly specify the executor. It seems like providing an executor argument to make_ready_future would make the API more consistent.

Currently, if you have one or more custom executors, you have to be always sure to pass them when calling .then if you use make_ready_future somewhere (and can't consistently have the continuation use the same executor as the previous).

[fosterbrereton]

Do the comments in issue #65 help out here at all?

[drussel]

Thanks. #65 suggests my understanding is correct, but doesn't address the problem I see (with having to be careful to avoid having the default executor sneak in unexpectedly from make_ready_future).

[FelixPetriconi]

Make the executor an argument to the make_ functions.