Mailing-List: contact notifications-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
Date: Wed, 1 Feb 2017 23:19:07 +0000 (UTC)
From: "Paul King (JIRA)" <jira@apache.org>
To: notifications@groovy.apache.org
Message-ID: <JIRA.13005704.1474156732000.12234.1485991147004@Atlassian.JIRA>
In-Reply-To: <JIRA.13005704.1474156732000@Atlassian.JIRA>
References: <JIRA.13005704.1474156732000@Atlassian.JIRA> <JIRA.13005704.1474156732767@jira-lw-us.apache.org>
Subject: [jira] [Closed] (GROOVY-7942) @Lazy transform creates unneeded
 getter/setter for backing store field
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Feb 2017 23:19:16 -0000


     [ https://issues.apache.org/jira/browse/GROOVY-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King closed GROOVY-7942.
-----------------------------

> @Lazy transform creates unneeded getter/setter for backing store field
> ----------------------------------------------------------------------
>
>                 Key: GROOVY-7942
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7942
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Paul King
>            Assignee: Paul King
>             Fix For: 2.4.8
>
>
> The following code:
> {code}
> @Lazy String foo
> {code}
> creates an appropriate {{getFoo}} getter method and a private {{$foo}} backing field but in renaming the fieldNode to have the dollar prefix, it doesn't remove the corresponding entry in the ClassNode's properties list. This results in some spurious {{get$Foo}} and {{set$Foo}} methods being created in later compilation phases. On the one hand these could be regarded as some backdoor semi-internal way to get access to the backing field but in reality using those methods would violate the contract that {{@Lazy}} is trying to provide..


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)