Java中的Map如果在遍历过程中要删除元素,除非通过迭代器自己的remove()方法,否则就会导致抛出ConcurrentModificationException异常。JDK文档中是这么描述的:
The iterators returned by all of this class's "collection view methods" are fail-fast: if the map isstructurally modified at any time after the iterator is created, in any way except through the iterator's own remove method, the iterator will throw a ConcurrentModificationException. Thus, in the face of concurrent modification, the iterator fails quickly and cleanly, rather than risking arbitrary, non-deterministic behavior at an undetermined time in the future.
iterators是fail-fast的,如果这个集合(存在特定的某些集合,比如HashMap)在iterator创建之后在结构上又改变了(通 过任何方式除了iterator本身的remove方法),iterator就会抛ConcurrentModificationException。因 此,在使用过程中又面临同时被修改,iterator就会以又快速又干净地fail来应对,而不是在将来某个不确定的时间冒面临随机又不确定的表现之风险。这么做的原因是为了保证迭代器能够尽快感知到Map的“结构性修改“,从而避免不同视图下不一致现象。Map的所有遍历方式,底层都是用了迭代器。
下面代码展示了遍历Map时删除元素的正确方式和错误方式。