Mailing-List: contact notifications-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
From: paulk-asert <git@git.apache.org>
To: notifications@groovy.apache.org
Reply-To: notifications@groovy.apache.org
References: <git-pr-439-groovy@git.apache.org>
In-Reply-To: <git-pr-439-groovy@git.apache.org>
Subject: [GitHub] groovy pull request #439: WIP Add groovy-macro docs
Content-Type: text/plain
Message-Id: <20161009095733.BF364E0209@git1-us-west.apache.org>
Date: Sun,  9 Oct 2016 09:57:33 +0000 (UTC)
archived-at: Sun, 09 Oct 2016 09:57:35 -0000

Github user paulk-asert commented on a diff in the pull request:

    https://github.com/apache/groovy/pull/439#discussion_r82519042
  
    --- Diff: src/spec/doc/core-metaprogramming.adoc ---
    @@ -2868,6 +3015,90 @@ The difference is that when you use `assertScript`, the code in the `assertScrip
     unit test is executed*. That is to say that this time, the `Subject` class will be compiled with debugging active, and
     the breakpoint is going to be hit.
     
    +===== ASTMatcher
    +
    +Sometimes you may want to make assertions over AST nodes whether to filter those nodes, or to make sure a given
    +transformation has built the expected AST node.
    +
    +**Filtering nodes**
    +
    +For instance if you would like to apply a given transformation only to a specific set of AST nodes, you could
    +use **ASTMatcher** to filter these nodes. The following example shows how to transform a given expression to
    +another. Using **ASTMatcher** it looks for a specific expression `1 + 1` and it transforms it to `3`. That's why
    +I called it the `@Joking` example.
    --- End diff --
    
    I => we


---
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.
---