Scala could do better on getters and setters by exposing a Java
foo.getBar() as foo.bar.
Similarly it's about to be left behind when Java adds lambdas because Java
lambdas get assigned a type according to the context they're used in,
whereas Scala lambdas get assigned a type based on their arities, parameter
types and return types, so e.g., executor.execute(() -> {
System.out.println("hello world"); }); in Java 8 will be
executor execute new Runnable { override def run() { println("hello world")
} } in Scala, unless you use/write some wrappers converting Scala's () =>
Unit to Runnable.
On Jan 8, 2013 3:32 PM, "clay" <[email protected]> wrote:
> I would also add that if boilerplate code drives you nuts, you may want to
> simply consider Scala. That language really addresses most of the lombok
> issues, and since they don't have to patch it on top of a legacy language,
> they were able to address the issues more elegantly. Scala handles the
> getter/setter issue particularly elegantly.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Java Posse" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/javaposse/-/L33RPtkOi8cJ.
> 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.
>
--
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.
