Problem with method references

Stephen Colebourne scolebourne at
Fri Jan 14 04:41:07 PST 2011

On 14 January 2011 11:59, John Nilsson <john at> wrote:
> On Fri, Jan 14, 2011 at 11:54 AM, Stephen Colebourne
> <scolebourne at> wrote:
>> On 14 January 2011 09:58, Peter Levart <peter.levart at> wrote:
>>> I don't know if we should allways reject #methodName in static context. Only if it refers to instance method. If it refers to static method, it should be a shourtcut for:
>>> ClassName#methodName
>>> analogous to static method invocation.
>> I would say that references to a static method should require the
>> class name. Its clearer that way.
> Doesn't this argument also apply to calls to static methods? Either in
> scope or imported?
> In the name of consistency the rules should probably be the same for
> references as for calls.

Sadly, you're probably correct.


More information about the lambda-dev mailing list