On 06/04/2017 14:08, Daniel Fuchs wrote:
The only reason I touched this method is because I noticed the possibility of ConcurrentModificationException if we reached there.
Well - now that I think about it again CME would probably not have happened with the old code either since we broke out of the loop with return just after the modification. But seeing remove() within a foreach loop was just a red flag.... best, -- daniel
