Re: STC: strictness of number and string type checking

2019-11-25 Thread MG
Are we discussing different things here ? I understood the question to be about number literals  ("GROOVY-8488: STC: floating-point _literals_ no longer accepted as args to method with double parameter"), not variables of number type. I am only arguing for literals to be conveniently groovy, not

Re: STC: strictness of number and string type checking

2019-11-25 Thread MG
I don't see a consistency problem if this would go, but besides that, just ask yourself: 1. How many times do I have a situation like that ? 2. How often do I not want to control the exact format of the resulting string representation of the number in case ? 3. In that remaining cases, how in

Re: STC: strictness of number and string type checking

2019-11-25 Thread Jochen Theodorou
On 25.11.19 14:21, MG wrote: Are we discussing different things here ? I understood the question to be about number literals  ("GROOVY-8488: STC: floating-point _literals_ no longer accepted as args to method with double parameter"), not variables of number type. I am only arguing for literals to