>
>
>
>
> Is this not the whole point of releasing versioned binaries? It just
> means a couple of extra steps when I upgrade. First, change the
> coordinates (group + version instead of just the version) and a quick
> refactor of my imports. Every modern IDE makes this easy.
>
>
> This is not m
On 30.03.2017 20:58, Miro Bezjak wrote:
[...]
So if we are talking about JDK9 modules them I'm with Jason and the rest
of you. Sure, breaking backwards compatibility is a sensible thing to do
in that case.
and I wish I would know how to solve all the problems. Right now it
seems like Groovy wi
Hi,
To simplify initialization of my production Money object in tests I've written
an extension module to use explicit coercion:
> Money tenDolars = 10.0 as Money //works fine, but could be shorter
It works fine, but it's Groovy so I would like to achieve more :).
My idea is to be able t
>
> Is this not the whole point of releasing versioned binaries? It just
>> means a couple of extra steps when I upgrade. First, change the
>> coordinates (group + version instead of just the version) and a quick
>> refactor of my imports. Every modern IDE makes this easy.
>>
>>
>> This is not m
Dnia Piątek, 31 Marca 2017 16:02 Marcin Zajączkowski napisał(a)
> Hi,
>
> To simplify initialization of my production Money object in tests I've
> written an extension module to use explicit coercion:
>
> > Money tenDolars = 10.0 as Money //works fine, but could be shorter
>
> It works fi
Yes, the only "native" mechanism I know to do coertion in Groovy (without
applying metaprogramming) is to overwrite the asType method and apply it
explicitly.
For me creating an AST transform it's a very cool idea. Maybe, we could
come up with a library having a configuration file with predefined
