systems designed with physical level technologies usually rely on mutable objects residing at various levels of an architecture.
采用物理层技术设计的系统通常依赖于驻留在架构不同层次上的可变对象。
when passing references to mutable objects between methods, you need to clearly document under what cases the object's ownership is being transferred.
当在方法之间传递对可变对象的引用时,您需要清楚地文档说明哪些情况下对象的所有权被转移。
lists, specifically, are handy mutable objects that can conveniently even hold multiple values.
明确的讲,列表是一些便利的可变对象,他们甚至可以方便地保留多个值。
typically, this means copying any mutable objects that comprise the internal 「deep structure」 of the object being cloned and replacing the references to these objects with references to the copies.
这通常意味着要复制包含正在被复制对象的内部「深层结构」的所有可变对象,并使用对副本的引用替换对这些对象的引用。
remember that interfering with mutable objects while you are iterating them is not a good idea.
记住,在迭代可变对象的时候修改它们并不是个好主意。