JEP proposed to target JDK 22: 461: Stream Gatherers (Preview)

[Daniel Schmid]

And another thing I realized after writing that E-Mail, the 
"initializer" parameter is called

 > the supplier function for the new gatherer

I am unsure about the name "supplier function". After all, it is already 
named initializer so why not use the name initializer (function) instead 
of supplier function?


Am 21.11.2023 um 10:35 schrieb Viktor Klang:
> Thanks for the feedback -- I agree that could be improved.
> I'll address this in the PR/CSR shortly.
>
> Cheers,
> √
>
> *
> *
> *Viktor Klang*
> Software Architect, Java Platform Group
> Oracle
>
>
> ------------------------------------------------------------------------
> *From:* jdk-dev on behalf of Daniel Schmid
> *Sent:* Tuesday, November 21, 2023 10:31
> *To:* jdk-dev at openjdk.org; Mark Reinhold
> *Subject:* Re: JEP proposed to target JDK 22: 461: Stream Gatherers 
> (Preview)
>
> When reading the type parameters of the
> "Gatherer.of"/"Gatherer.ofSequential" methods, I realized that the type
> parameter for the intermediate state is documted as
>
>  > the type of initializer for the new gatherer
>
> While not being wrong, it looks a bit confusing to me as it refers to
> the intermediate state which is also used by the integrator, that type
> parameter is not exclusive to the initializer.
>
> Is there a reason it is not called
>
>  > the type of intermediate state for the new gatherer
>
> or something similar?
>
> Am 20.11.2023 um 17:17 schrieb Mark Reinhold:
> > The following JEP is proposed to target JDK 22:
> >
> >    461: Stream Gatherers (Preview)
> > https://openjdk.org/jeps/461 <https://openjdk.org/jeps/461>
> >
> >    Summary: Enhance the Stream API to support custom intermediate
> >    operations.  This will allow stream pipelines to transform data 
> in ways
> >    that are not easily achievable with the existing built-in 
> intermediate
> >    operations.  This is a preview API.
> >
> > Feedback on this proposal from JDK Project Committers and Reviewers [1]
> > is more than welcome, as are reasoned objections. If no such objections
> > are raised by 20:00 UTC on Wednesday, 29 November, or if they’re raised
> > and then satisfactorily answered, then per the JEP 2.0 process proposal
> > [2] I’ll target this JEP to JDK 22.
> >
> > - Mark
> >
> >
> > [1] https://openjdk.org/census#jdk <https://openjdk.org/census#jdk>
> > [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html 
> <https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jdk-dev/attachments/20231121/903a5c00/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4490 bytes
Desc: Kryptografische S/MIME-Signatur
URL: <https://mail.openjdk.org/pipermail/jdk-dev/attachments/20231121/903a5c00/smime.p7s>