On 23.11.19 03:08, MG wrote:
On 22/11/2019 17:51, Jochen Theodorou wrote:
So strictly spoken none of the calls to m1 and m2 should be supported
here. But this is a problem for the user, as the user is not used to
write 1.0d instead. And it will make a lot of programs cumbersome. But
it would be
Chiming in late here, but the only one I would passionately argue about is
the string <=> numeric conversions. The implicit conversions to / from
String already in Groovy have been responsible for a large proportion of
the impactful bugs that have come out of my complex groovy code. For
example, th
Hello everyone,
That is an interesting example (actually I was not aware that groovy does that)
Am 24.11.2019 um 01:28 schrieb Simon Sadedin :
> Chiming in late here, but the only one I would passionately argue about is
> the string <=> numeric conversions. The implicit conversions to / from St
