Am 12.01.20 um 09:09 schrieb Daniel.Sun:
In Java, `int a = 0; assert a+=1` will fail to compile because expecting
boolean value, but `int a = 0; assert 0 == (a+=1)` is OK, so I think we
forbidden assignments seems not correct...
a long time ago we decided to no allow assignments in certain p
Am 10.01.20 um 16:14 schrieb Daniel.Sun:
Hi Jochen,
> If you want to get the maximum performance then I would suggest to
work
with the guards instead of falling back to a hashed map.
Thanks for your suggestions :-)
After we constructed the following "tree" MH with guards, we
Hi Jochen,
The changed example will run faster than the original one because cache
will always be hit for each argument. Actually we can make run even much
faster, loop more than 100_000 times, e.g. 1_000_000, because the optimize
threshold reaches, the related MH will be linked to the cs.
Am 13.01.20 um 15:49 schrieb Daniel Sun:
Hi Jochen,
The changed example will run faster than the original one because cache
will always be hit for each argument. Actually we can make run even much
faster, loop more than 100_000 times, e.g. 1_000_000, because the optimize
threshold re
Hi,
TL;TR. How would be best to distinguish in Groovy 3 foo.x and
foo.getProperty("x") in a call (at the level of an interceptor for a
mocking system)?
More detailed version.
Working on the Spock adjustment to Groovy 3 I spotted that Groovy 3
started for a property access go.x (go - some GroovyO
The vote has passed with 5 +1 binding votes, one additional +1 vote and no
other votes. I'll proceed with next steps.
Cheers, Paul.
On Sat, Jan 11, 2020 at 1:13 PM Paul King wrote:
>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.4.18 bug fix release!
>
>
The vote has passed with 5 +1 binding votes and no other votes. I'll
proceed with next steps.
Cheers, Paul.
On Sat, Jan 11, 2020 at 1:45 PM Paul King wrote:
>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.5.9 release!
>
> This release includes 30 bug fixes
