[ 
https://issues.apache.org/jira/browse/GROOVY-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737801#comment-16737801
 ] 

Frederico Costa Galvão commented on GROOVY-8549:
------------------------------------------------

Sorry if this seemed urgent on my side: that is not the case.

This bug doesn't really affect me. All of my projects are on 2.0.8, 2.4.11 and 
2.4.12, so I'm safe (I'll just need to be careful). I found this while catching 
up on the latest alpha changelog, that is all.

I asked only because the PR seemed simple to port (considering the <Number> 
variants on DGM cover most of the scenarios, as you stated), and I couldn't 
find anywhere a statement about 2.4.x EOL.



Thanks for your time on this!

> Compile Static causes getAt to fail
> -----------------------------------
>
>                 Key: GROOVY-8549
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8549
>             Project: Groovy
>          Issue Type: Bug
>          Components: Compiler
>    Affects Versions: 2.4.13, 2.5.0-beta-3, 2.4.14, 3.0.0-alpha-2, 2.4.15
>         Environment: Intellij plus various versions of Groovy; the same 
> problem also occurs in Eclipse-Groovy with the same versions
>            Reporter: Jon Kerridge
>            Assignee: Paul King
>            Priority: Major
>             Fix For: 3.0.0-alpha-4, 2.5.3
>
>
> I can reproduce by adding @CompileStatic to the example I tried previously 
> and can confirm that 2.4.13 is where the regression started. Workaround would 
> be to remove @CompileStatic until we can get a fix in place. If you can raise 
> a bug issue in Jira, that would be great.
> the reproducer following is a shortened version created by Paul King:
> {code}
> import groovy.transform.CompileStatic
>  
> @CompileStatic
> def method() {
>   def list = [0, 1, 2, 3]
>   for (idx in 1..2) {
>     list[idx-1]++
>   }
>   list
> }
>  
> assert method() == [1, 2, 2, 3]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to