You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by endSly <gi...@git.apache.org> on 2016/06/23 10:15:04 UTC
[GitHub] groovy pull request #354: Fix nested calls between @Lazy static properties
GitHub user endSly opened a pull request:
https://github.com/apache/groovy/pull/354
Fix nested calls between @Lazy static properties
Variable expressions lost owner class context cause they are wrapped into the holder class. Now variable initialization is handled by a private static method in the owning class.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/endSly/groovy nested-lazy-calls
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/groovy/pull/354.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #354
----
commit 828f9e31ada1f6a1a764c459a3b877dcd92f7b27
Author: Endika Guti�rrez <en...@ticketbis.com>
Date: 2016-06-23T07:22:47Z
Added tests for nested lazy properties
commit ef12fd447dba3d0a3a88e9b638529e9ddfa437af
Author: Endika Guti�rrez <en...@ticketbis.com>
Date: 2016-06-23T09:35:36Z
Fixed nested calls between @Lazy static properties
Variable expressions lost owner class context when they are wrapped into
the holder class. Now variable initialization is handled by a private static
method in the owning class.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] groovy pull request #354: GROOVY-7872 Fix nested calls between @Lazy static ...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/groovy/pull/354
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---