Isn't the contract of List requiring to throw an IndexOutOfBoundsException
though, in case index is invalid?
Mauro Molinari
mauro...@tiscali.it
In data 6 Febbraio 2025 18:00:36 OCsite ha scritto:
Eric,
I know of no oficial documentation explaining this (which does not mean
there&#
Il 14/05/20 03:58, Paul King ha scritto:
Time to get in any bug fixes you want for those releases. Please also
let me know if you have any issues with the proposed timeframe.
Is it possible to backport GROOVY-9518 to 2.5.x?
And maybe have a look at GROOVY-9523 and GROOVY-9524?
Thanks,
Mauro
Just my humble opinion on this, after being using Groovy for some ~7 years.
Il 30/04/20 15:05, Jochen Theodorou ha scritto:
* Almost all Java devs I've been talking about groovy in the last
couple of
months think that groovy is a purely dynamically-typed language.
Which in
fact turns them off
Great news, congratulations Eric!
Mauro
Il 26/08/2019 05:37, Daniel.Sun ha scritto:
Hi all,
I'd like to introduce you to Eric Milles, our new Apache Groovy committer!
Some of you may already know Eric for his work on Groovy Eclipse. He is a
very capable developer with the skills we need to hel
Just for curiosity... the Gradle team says that Kotlin DSL support was
introduced because (as you said) IDE support is then available for
editing build scripts.
But if this is the only (or at least the main...) advantage, why not
collaborating on investing into improving Groovy support in IDEs i
Isn't it equivalent to something like this?
|def elem = collection?.first()?: defaultValue||
||def elem = collection?.first()?: defaultSupplier()||
|
Mauro
Il 18/10/2018 17:39, Milles, Eric (TR Technology & Ops) ha scritto:
I see there are the following DGMs for getting first element of
a "co
we need to move forward. Honestly I'd be in favor of only
maintaining 2 branches: 2.5.x and 3.0.x.
WDYT?
Isn't 2.5 still beta? Do you think to stop supporting any stable release?
--
Mauro Molinari
E-mail: mauro...@tiscali.it
Il 09/01/2018 12:51, Guillaume Laforge ha scritto:
((even more so on users@g.a.o actually, so that it's seen by all our
users))
Maybe you or someone else would be so kind to forward it to the users
mailing list, as I'm not a subscriber.
Thanks,
Mauro
Hello all,
I hope this message won't be considered inappropriate, but I would like
to say my personal big "Thank you!" to Eric Milles for the impressive
work he has done to revive the Groovy Eclipse plugin after Pivotal
stopped to support its development.
After more than a year of work, he al
ou also
mean the case in which "this." is implicit, don't you?
In any case, IMHO the @CompileStatic case should behave exactly like
@CompileDynamic, absolutely!
Mauro
Il 24/11/2017 10:16, Jochen Theodorou ha scritto:
Am 24.11.2017 um 09:09 schrieb Mauro Molinari:
Il 24/11/201
Il 24/11/2017 01:46, Jochen Theodorou ha scritto:
In my opinion the test is wrong, but I'd like to hear others about this.
And another point. We seem to have no similar test for dynamic Groovy.
Groovy does use direct field access if the field is available on
"this". But the question here is if
Il 06/10/2017 00:06, Jesper Steen Møller ha scritto:
In other words, IMHO a?.b.c should implicitly mean a?.b?.c or at least
give a warning that the construct doesn't make sense. In either case
??. wouldn't make much sense.
I perfectly agree with this, I always wondered why it was chosen to
re
In my humble personal experience, I confirm I would have find it useful
when properties are involved, i.e.:
foo.property ?= 'defaultValue'
instead of
foo.property = foo.property?: 'defaultValue'
or the lengthy:
def a = foo.property
foo.property = a?: 'defaultValue'
Not to say in case of nested
Hi all,
sorry for this OT, but as someone else already mentioned, I'm receiving
double posts from some of you (not from all, indeed).
Someone suggested to unsubscribe from the incubator mailing list, but I
just tried to send an e-mail to:
dev-unsubscr...@groovy.incubator.apache.org
and a rece
14 matches
Mail list logo
