RFR 8056249 Improve CompletableFuture resource usage
dl at cs.oswego.edu
Fri Aug 29 13:35:02 UTC 2014
On 08/29/2014 06:01 AM, Paul Sandoz wrote:
> Please review fixes by Doug to j.u.c.CompletableFuture to better control resources for long completion chains (e.g. avoiding stack overflows). This fix resulted in a lot of internal refactoring and clean up. There are also some doc clarifications for certain j.u.c.CompletationStage exception handling methods (which most likely means a CCC is required).
Thanks for doing this!
> Is the following snippet missing from the doc updates to the methods CompletationStage.handle and handleAsync?
While touching up wording, we noticed that this sentence doesn't capture
all the cases that are described in the top-level CompletionStage specs.
So including it seems more confusing than omitting it, and just relying
on the overall specs.
> If the supplied function itself encounters an
> exception, then the returned stage exceptionally completes with this
> exception unless this stage also completed exceptionally.
More information about the core-libs-dev