You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/12/24 10:05:00 UTC

[jira] [Commented] (GROOVY-8424) Final variable analysis analyses generated fields

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

Paul King commented on GROOVY-8424:
-----------------------------------

As an example, when using Spock, these variables are analysed:  {{$spock_errorCollector}} and {{$spock_valueRecorder}}. While it's not wrong to analyse them and we could check that AST transformations are doing the correct thing wrt final modifiers, it does slow compilation time a little and reported errors are somewhat confusing to users of the transforms anyway unless they know the internal workings. One possibility would be to keep checking on when a flag, e.g. {{groovy.stc.debug}} is enabled.

> Final variable analysis analyses generated fields
> -------------------------------------------------
>
>                 Key: GROOVY-8424
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8424
>             Project: Groovy
>          Issue Type: Bug
>    Affects Versions: 2.5.x
>            Reporter: Paul King
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)