Quantcast

[GitHub] groovy pull request #498: GROOVY-8088: For @MapConstructor and @TupleConstru...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] groovy pull request #498: GROOVY-8088: For @MapConstructor and @TupleConstru...

danielsun1106
GitHub user paulk-asert opened a pull request:

    https://github.com/apache/groovy/pull/498

    GROOVY-8088: For @MapConstructor and @TupleConstructor we should prov…

    …ide a default undefined value for better Java compatibility

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/paulk-asert/groovy groovy8088

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/groovy/pull/498.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 #498
   
----
commit 42a692c742daa4be61c26f29cd855bbbfa03105d
Author: paulk <[hidden email]>
Date:   2017-02-15T07:28:30Z

    GROOVY-8088: For @MapConstructor and @TupleConstructor we should provide a default undefined value for better Java compatibility

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] groovy pull request #498: GROOVY-8088: For @MapConstructor and @TupleConstru...

danielsun1106
Github user asfgit closed the pull request at:

    https://github.com/apache/groovy/pull/498


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Loading...