Internal and External truncation conditions (original) (raw)
Remi Forax forax at univ-mlv.fr
Sun Feb 10 05:47:39 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/2013 02:42 PM, Doug Lea wrote:
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?
No, throwing an exception when the VM thinks that can it can escape is really slow.
-Doug
Rémi
- 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