If this request had an implicit Promise in scope, that Promise gets saved away here. This is mainly so that exceptions can properly fail the Promise. If there is no implicit Promise, this will be set to Requester.emptyPromise, which is simply a signal that there isn't really one.
If this request had an implicit Promise in scope, that Promise gets saved away here.
If this request had an implicit Promise in scope, that Promise gets saved away here. This is mainly so that exceptions can properly fail the Promise. If there is no implicit Promise, this will be set to Requester.emptyPromise, which is simply a signal that there isn't really one.
The request "monad". It's actually a bit suspicious, in that it's mutable, but by and large this behaves the way you expect a monad to work. In particular, it works with for comprehensions, allowing you to compose requests much the way you normally do Futures.