StreamSupport -> Streams?

Brian Goetz brian.goetz at
Thu Jun 20 13:56:48 PDT 2013

Streams was already scheduled to be GC'ed, which would have left only 

The incremental suggestion from Sam was "Now that Streams is being GCed, 
can't we then rename StreamSupport to Streams, where this stuff used to 
live anyway?"

On 6/20/2013 4:55 PM, Joe Bowbeer wrote:
> The StreamSupport name applies to support stuff and the Streams name
> applies to publicly useful stuff. Which stuff remains to be named?
> If it's not publicly useful, doesn't this argue for GC'ing Streams?
> On Jun 20, 2013 1:39 PM, "Brian Goetz" <brian.goetz at
> <mailto:brian.goetz at>> wrote:
>     Now that Streams has no more public members, it was suggested we
>     move the public factories (stream() and parallelStream()) to Streams
>     and garbage-collect StreamSupport.
>     The motivation for the somewhat more ungainly name StreamSupport was
>     to make it clear(er) that these were low-level methods intended for
>     developers of data structures, and mixing them with the
>     for-the-public methods in Streams like concat() was confusing.  But
>     now all the for-the-public methods in Streams are gone.

More information about the lambda-libs-spec-experts mailing list