[GitHub] groovy pull request #514: Adds documentation around 'remove' method Integer/...

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

[GitHub] groovy pull request #514: Adds documentation around 'remove' method Integer/...

aalmiray-3
GitHub user VoltiSubito opened a pull request:

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

    Adds documentation around 'remove' method Integer/Object ambiguity

    I'm decently new to Groovy and was recently caught off-guard by attempting to use the `remove` method on a list of Integers, so I thought I'd try to update the document to add `removeAt` and `removeElement` to that section.

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

    $ git pull https://github.com/VoltiSubito/groovy doc_list_remove_ambiguity

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

    https://github.com/apache/groovy/pull/514.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 #514
   
----
commit 5e2bb0ae1472927b463ade4424ce5a5e6f4ec12c
Author: Jason Schindler <[hidden email]>
Date:   2017-03-19T19:50:40Z

    Adds documentation around 'remove' method Integer/Object ambiguity

----


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

[GitHub] groovy pull request #514: Adds documentation around 'remove' method Integer/...

aalmiray-3
Github user asfgit closed the pull request at:

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


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