Stream

Joe Bowbeer joe.bowbeer at gmail.com
Sun Jan 13 10:44:57 PST 2013


I'm starting to take the survey and I'm running into name/API changes that
haven't appeared yet in a binary snapshot (e.g., b72).  I can't comment
effectively on these until I've used them in running code.  (I'll add this
comment to the survey as well, but I thought it would be good to point this
out, esp. w.r.t. deadlines.)


On Sun, Jan 13, 2013 at 8:51 AM, Brian Goetz <brian.goetz at oracle.com> wrote:

> I forgot the all-important aspect of this: a deadline.  Thanks to Remi and
> Tim for jumping on this already.
>
> Let's aim to get all responses in by midnight Monday of some unnamed time
> zone.  I'll then collate the responses and relay to the list.
>
>
>
>
> On 1/11/2013 6:02 PM, Brian Goetz wrote:
>
>> I've done a pass through the repo and marked almost all the classes
>> package-private.  There are only a handful of public classes now.  I'm
>> going to do a set of surveys that cover all the public methods of all
>> the public classes.  This is the first one, and it's on Stream.  EG
>> members will be receiving their surveys directly from SurveyMonkey.  If
>> you don't get one within a few hours, let me know.
>>
>> There are not really any questions; there is a free-response box for
>> every method or group of related methods in Stream.
>>
>> You are encouraged to write comments on:
>>   - the suitability of the method
>>   - the specific details of its arguments
>>   - generics nits
>>   - naming nits
>>   - semantic wonderings
>>   - anything else you might have to say
>>
>> Writing nothing in the box will be interpreted as "I think this method
>> is great as is."
>>
>> Specifically, the Collector (reducer) API is still a work in progress,
>> so there will be another opportunity to give final feedback on that (but
>> feel free to give feedback here too.)
>>
>>


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