> I'd much rather have a closure proposal where a method that takes a > closure that has tennant's correspondence principle is strictly > enforced by the compiler to keep the closure stack-safe. In other > words, legal operations are: > > 1. Running the closure, > 2. Grabbing info off of the closure object (running its toString or > some such) > 3. passing it on to another method that accepts closures.
Wouldn't you lose the ability to parallelize? I might want to find an element in a collection that satisfies a certain predicate. The "first" thread to find one gets to return its findings, the others are ignored. With kind regards Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
