awesome, my favorite two java projects lombok and tomee sitting in a tree:) (soon a git tree whoop!)
On 3 October 2014 09:42, Romain Manni-Bucau <[email protected]> wrote: > About lombok: it is great but our constraints would be: no transitive > dependency on it (delombokization + no usage of some parts), no over usage > (some equals hascode or other lombok impl would break the container) > Mostly lombok doesn't need to be a runtime dependency (it's only used at compile time and it removes references to itself). delombok may be needed for these code checkers and also for javadoc generation (not sure how to set that up in maven). > > On 03/10/2014 01:04, Daniel Kasmeroglu wrote: > >> * The contribution site points out that it's common practice to use > >> final variables and fields. Can someone elaborate on this ? I see that > >> a lot but in open source code but I think there's usually no point in > >> doing that (I can elaborate on that). > If I recall correctly java 8 implicitly assumes final where needed, like auto boxing eg. for accessing parameters from anonymous inner classes - which can make things really confusing when you run into trouble I can imagine. I can see that specifying the intent is important and that blogpost of David Blevins that lamented that the default should be final comes to mind.. Having such a compiler option would be interesting.. mmmm.. wait a minute.. maybe lombok could be used to fix this! eg. implicitly make all parameters final unless they have a @mutable or @nonFinal annotation (should be opt in via lombok configuration) - I know its a crazy idea but I think in the realms of what lombok can do. -- regards ✝ Marius
