groovy

Variables in annotation closures should never be bound to declarations in "enclosing" scopes

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.8.2
  • Fix Version/s: 1.8.3, 1.9-beta-4, 1.7.11
  • Component/s: Compiler
  • Labels:
    None
  • Number of attachments :
    0

Description

For example, in the following code the closure variable is incorrectly bound to the method parameter, resulting in the absence of an (Object, Object) constructur and the presence of an (Object, Object, Reference) constructor for the closure:

@Foo({ value })
def doit(value) {}

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Peter Niederwieser added a comment - - edited

Also see http://groovy.329449.n5.nabble.com/Annotation-closure-not-behaving-as-expected-td4821286.html

Show
Peter Niederwieser added a comment - - edited Also see http://groovy.329449.n5.nabble.com/Annotation-closure-not-behaving-as-expected-td4821286.html
Hide
Permalink
blackdrag blackdrag added a comment -

fixed

Show
blackdrag blackdrag added a comment - fixed

People

  • Assignee:
    blackdrag blackdrag
    Reporter:
    Peter Niederwieser
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: