Re: Re: Shouldn't collection zip functions return streams?

Then it has to be "lazy" in the same sense as a non-executed database query 
is lazy. :-)

The border doesn't need to be awkward, it comes naturally when we make a 
distinction between assembling the computation to be run, and executing it.
Mixing them together is the root issue behind sequential vs. parallel vs. 
iterator vs. sequential views vs. parallel views vs. Slick vs. Spark 
implementations of the same thing.

These days I would consider an API that provides 
map/flatMap/filter/groupBy/join/... and talks about how it is 
implemented/executed conceptually wrong. It causes issues without solving 
any.

-- 
You received this message because you are subscribed to the Google Groups "scala-language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.