search

TimurMahammadov / google-collections

Automatically exported from code.google.com/p/google-collections
Apache License 2.0
0 stars 0 forks source link

Fail-fast iterator behavior #85

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The non-concurrent JDK collection classes have fail-fast iterators. If the
an iterator's underlying collection is changed by any mechanism besides the
iterator, subsequent iterator methods will throw a
ConcurrentModificationException.

However, some Google Collection classes, such as multimaps & multisets,
yield iterators that aren't fail-fast. Those iterators may or may not throw
a ConcurrentModificationException, depending on the call sequence.

Should we document that the iterators aren't fail-fast?

Should we provide collection wrappers that guarantee that the generated
iterators are fail-fast?

Original issue reported on code.google.com by jared.l....@gmail.com on 17 Jun 2008 at 1:11

GoogleCodeExporter commented 9 years ago 
Since nobody asked for fail-fast behavior, adding new functionality is a low
priority. However, we should decide whether additional documentation is needed.

Original comment by jared.l....@gmail.com on 8 Apr 2009 at 1:12

GoogleCodeExporter commented 9 years ago

Original comment by kevin...@gmail.com on 17 Sep 2009 at 6:02

GoogleCodeExporter commented 9 years ago 
This issue has been moved to the Guava project (keeping the same id number). 
Simply replace 'google-collections' with 'guava-libraries' in your address 
bar and it should take you there.

Original comment by kevinb@google.com on 5 Jan 2010 at 11:09