Spec and API review for {Int,Long,Double}SummaryStatistics

Kevin Bourrillion kevinb at google.com
Fri Mar 29 14:42:45 PDT 2013

I should point out:  by "consistent guidelines for <anything>", I surely
have no illusion of finding such a thing spanning the whole JDK or spanning
back before at the earliest 1.5.  Only in the sense of "this is how we do
things now in the areas where we, y'know, JSR-166-types work."

I'll admit to simply *disliking* the get- prefix as being so much chaff,
except where it's paired with set-, but more than that I just want the

On Fri, Mar 29, 2013 at 2:28 PM, Joshua Bloch <josh at bloch.us> wrote:

> Mike,
> On Fri, Mar 29, 2013 at 12:44 PM, Mike Duigou <mike.duigou at oracle.com>wrote:
>> On Mar 29 2013, at 11:01 , Kevin Bourrillion wrote:
>>  Final nit: what's the consistent rule for when exactly this "get"
>> prefix is used?
>> It's generally used to retrieve state with little or no computation or
>> conversion required to produce the result. "as" or "to" imply conversion.
>> Unadorned names usually imply more computation. Across the JDK it's easy to
>> find counter examples to every rule unfortunately.
> Do you have any evidence that this is a rule across the JDK (i.e., that it
> holds in a significant majority of all cases)?  I haven't done a methodical
> study, but it doesn't match my previous assumptions, which are contained in
> *Effective Java*.
>      Josh

Kevin Bourrillion | Java Librarian | Google, Inc. | kevinb at google.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/lambda-libs-spec-experts/attachments/20130329/88ce9ad3/attachment.html 

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