On Mon, Oct 29, 2012 at 7:35 AM, Simon Ochsenreither < [email protected]> wrote:
> > In my opinion, foo.bar(baz) should always invoke a method on type Foo, > not "the compiler figures out whether Foo has such a method and if not > rewrites it to some static invocation of an extension method in scope > FooExtension.bar(foo, > baz)". > That's a fair concern. I haven't made up my mind yet, but I remember that when the industry started shifting toward OO, there was concern that when you read C code that says "foo(a, b)", you knew exactly what method was being invoked but that when you saw C++' "a.foo(b)", you had no idea what method was going to be called. Defender methods might follow the same path in the end and just become something that we are used to parse. > -- Cédric -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
