Hi there, > On 16 May 2020, at 2:41, Paul King <pa...@asert.com.au> wrote: > I'd suggest creating an issue for this. We might be able to improve Groovy or > if not we should assess whether the current doco around safe indexing > explains possible interactions well enough.
GROOVY-9561 <https://issues.apache.org/jira/browse/GROOVY-9561> Aside of that, it seems mails sent by me during the week-end did not make it to the maillist at all for some reason? Weird. Anyway, perhaps a bit at the important side, I've been bitten in my tender parts pretty hard by the breaking change of the push/pop behaviour, which far as I understand happened in 2.5.0 to make Groovy more similar to Java (which I can't see as a reasonable goal, given the Groovy's very reason for existence is the Java intrinsic... well, let's say inconvenience :)) The thing is mentioned in the breaking changes in a rather offhand way as “same linkedlist code different behavior between groovy and java”, which I did not pursue, for I never share a list in a code in both the languages. Alas it breaks pure Groovy code too, and in an ugly way (like e.g., “def list=[];list.push(1); list.push(2); assert list.last()==2”) and thus in my opinion should be reformulated in the release notes to something more apt like e.g., “the push/pop behaviour was changed to add/remove from the head of the list instead of its tail as it used to be before”. Another small issue is that it seems the newest compiler does not recongise the --indy switch at all and aborts compilation seeing it. I understand indy does not make sense for 4+ anymore, but for project and buildchain backward compatibility it should recognise the switch and just emit a warning that the switch is ignored. I don't really think these issues are worth a ticket; if you think otherwise, let me please know and I'll gladly add them. Thanks a lot, OC
