I feel that this would register only on the ok-to-have level for me, for
the simple reason, that
1. You do not typically have a lot of utility-classes (or
function-classes) in a project
2. Afaiks all you save is the static keyword before every method,
because if you incorrectly instantiate the class, you basically get
an Object, and no harm is done
I would much rather see features such as final variables without an
explicit type not being of type Object but of the type assigned to them
- or proper named parameters (though I understand that this is alas a
much bigger feature to implement), to get Groovy up to speed in this regard.
Cheers,
mg
On 12.01.2018 01:57, Paul King wrote:
Hi all,
Would there be interest in a @UtilityClass annotation - similar to
lombok's:
https://projectlombok.org/features/experimental/UtilityClass
It is similar to @Category in some ways but with some useful differences.
What do folks think?
Cheers, Paul.
