[
https://issues.apache.org/jira/browse/COLLECTIONS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865716#comment-17865716
]
Gary D. Gregory commented on COLLECTIONS-856:
---------------------------------------------
[~benjaminconfino]
Thank you for your report 😀 Would you like to create a PR on GitHub to update
the documentation?
> Document the interaction between PeekingIterator and FilteredIterator
> ---------------------------------------------------------------------
>
> Key: COLLECTIONS-856
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-856
> Project: Commons Collections
> Issue Type: Improvement
> Components: Iterator
> Affects Versions: 4.5.0-M1
> Reporter: Benjamin Confino
> Priority: Minor
>
> If you have a FilteredIterator, call peek and get an element x. Then
> something modifies the state of that x. Then you call peek again
> FilteredIterator will return x even if x no longer passes the predicate.
> I think this behaviour is correct. I would not expect the the state of an
> iterator to change unless I called a method like next(), and I would not
> expect an exception like ConcurrentModificationException when the collection
> has not changed.
> However its an obscure edge case so it might be worth documenting it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
