Internal and External truncation conditions (original) (raw)
Doug Lea dl at cs.oswego.edu
Sun Feb 10 05:42:48 PST 2013
- Previous message: Internal and External truncation conditions
- Next message: Internal and External truncation conditions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 02/10/13 08:12, Doug Lea wrote:
Requiring that all Stream bulk computations like reduce continuously check for async cancel status between each per-element operation is unlikely to satisfy anyone at all, yet seems to be the only defensible option if we were to support it.
Actually, we already support it. Any per-element lambda supplied to any Stream method can itself do any kind of async cancel check itself, and throw an exception rather than returning a result.
Case closed?
-Doug
- Previous message: Internal and External truncation conditions
- Next message: Internal and External truncation conditions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the lambda-libs-spec-observers mailing list