curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From madrob <...@git.apache.org>
Subject [GitHub] curator pull request: CURATOR-131 use iterator.remove instead of f...
Date Thu, 31 Jul 2014 21:25:47 GMT
GitHub user madrob opened a pull request:

    https://github.com/apache/curator/pull/29

    CURATOR-131 use iterator.remove instead of foreach

    When iterating over a collection, if we try to remove elements that
    can lead to undefined behaviour. We should use an iterator and its
    remove method to do this safely.

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

    $ git pull https://github.com/madrob/curator CURATOR-131

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

    https://github.com/apache/curator/pull/29.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 #29
    
----
commit e38d1ceda492e097ad9c94bb854838f2b1f7caa9
Author: Mike Drob <mdrob@cloudera.com>
Date:   2014-07-31T21:24:40Z

    CURATOR-131 use iterator.remove instead of foreach
    
    When iterating over a collection, if we try to remove elements that
    can lead to undefined behaviour. We should use an iterator and its
    remove method to do this safely.

----


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

Mime
View raw message