Hi all,
I finally got around to trying out Project Lombok today. Great stuff!
The more I used it, the more it felt like fluent setters would be a
neat addition, so I thought I'd have a go at implementing a prototype.
I realise you're already looking at doing this as part of @Builder, so
it's just a bit of fun really:
http://github.com/rewbs/lombok/commit/ee60a6c21f48f7f9d8ca02db586e9949ae4888cc
I'm aware of at least 4 things that don't work properly yet in my
prototype (I think 1, 2 & 3 should be pretty easy to resolve, not yet
sure about 4):
1. Adding a fluent setter annotation does not yet result in a warning
if a user-added non-fluent setters already exists, and vice versa.
2. Fluent setters don't yet correctly return parametrized types.
3. No tie-in with @Data yet.
4. While the "fluent" attribute that I added to @Setter can co-exist
with the unnamed AccessLevel attribute when compiling with javac, this
doesn't work with the Eclipse compiler. In other words, the following
compiles with javac but not Eclipse:
@Setter(fluent=true, lombok.AccessLevel.PRIVATE) int foo;
I was really impressed by how simple it was to set up the environment
and start hacking.
By the way, is there a way to run the automated tests against the
Eclipse compiler handlers?
Cheers,
Robin
--
You received this message because you are subscribed to the Google
Groups group for
http://projectlombok.org/
To post to this group, send email to
project...@googlegroups.com
To unsubscribe from this group, send email to
project-lombo...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/project-lombok?hl=en