Re: About eliminating ambiguities of method call with closure argument

2020-04-01 Thread Paolo Di Tommaso
Arriving late to this thread, therefore not sure it has already discussed, but have you taken in consideration that changing the method call argument interpretation for the case 1, eg. meth { p -> } it will break all DSL in which the user scripts use this form? Just thinking Gradle for example.

Re: About eliminating ambiguities of method call with closure argument

2020-04-01 Thread Paul King
Groovy 2.5 and earlier don't support this form. But yes, if any Groovy 3 DSLs were created in the last few weeks (or longer if we count betas/RCs) and they used this form, then they would break. Cheers, Paul. On Wed, Apr 1, 2020 at 10:56 PM Paolo Di Tommaso wrote: > Arriving late to this thread

Re: About eliminating ambiguities of method call with closure argument

2020-04-01 Thread Paolo Di Tommaso
I see, then I agree that it's not a big issue. I was confused because I saw that Gradle supports that syntax. Not understanding how they can, then? Cheers, p On Wed, Apr 1, 2020 at 3:30 PM Paul King wrote: > Groovy 2.5 and earlier don't support this form. But yes, if any Groovy 3 > DSLs were