On 10/1/14, 1:59 PM, David Dorwin wrote:
Rejection also has the advantage of providing an exception, which can provide information (reason and message) to differentiate between potentially multiple causes. This is not possible when resolving with null. Providing such information would likely make development and debugging easier.
If you were designing a sync API, would not the same arguments apply? So you'd want to throw different kinds of exceptions to indicate "not supported"?
-Boris
