Streams -- philosophy (original) (raw)
Brian Goetz brian.goetz at oracle.com
Mon Dec 31 09:09:34 PST 2012
- Previous message: Streams -- philosophy
- Next message: Streams -- philosophy
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On that, I think Stream should not have the method iterator() and splitterator() public, but Streams should have two static methods to expose an Iterator and a Spliterator. just to not shut down the idea to find a better abstraction between the release of 9.
I presume you mean something like:
class Streams { public static Iterator iterator(Stream) public static Spliterator spliterator(Stream)
But, static methods would have to work in terms of the public methods on Stream, so that they could work on any stream, not just our own. Meaning there must be some public way to get at the underlying data in the Stream interface. So I think it boils down to the same thing?
- Previous message: Streams -- philosophy
- Next message: Streams -- philosophy
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the lambda-libs-spec-experts mailing list