java的同步包装器,java – 迭代同步包装器是否安全？

我决定深入研究源代码并注意到

Collections.synchronizedList(List)的实现方式如下：

public static List synchronizedList(List list) {

return (list instanceof RandomAccess ?

new SynchronizedRandomAccessList(list) :

new SynchronizedList(list));

}

static class SynchronizedList

extends SynchronizedCollection

implements List {

private static final long serialVersionUID = -7754090372962971524L;

final List list;

SynchronizedList(List list) {

super(list);

this.list = list;

}

SynchronizedList(List list, Object mutex) {

super(list, mutex);

this.list = list;

}

public boolean More ...equals(Object o) {

synchronized(mutex) {return list.equals(o);}

}

//ommited

public void add(int index, E element) {

synchronized(mutex) {list.add(index, element);}

}

public E remove(int index) {

synchronized(mutex) {return list.remove(index);}

}

//rest is ommited

}

可以看出,该类使用私有锁对象来提供线程安全性.但是the documentation允许我们使用锁定工厂方法返回的对象来迭代它.

It is imperative that the user manually synchronize on the returned

list when iterating over it:

因此,我们使用不同的锁来迭代和修改列表(添加,删除等).

为什么它被认为是安全的？