| 1. | Problem 1 : immutable objects weren t
问题1 ：不可变对象不是不可变的 |
| 2. | Be primitive types or references to immutable objects
必须是原语类型或是对不可变对象的引用。 |
| 3. | Immutable objects , like
）不可变对象（如 |
| 4. | " and others , i extolled the virtues of immutability - immutable objects cannot get into an inconsistent state
” （和其他文章中） ，我赞扬了不可变的优点，不可变对象不能进入不稳定的状态。 |
| 5. | Keyword , and you can freely share and cache references to immutable objects without having to copy or clone them
关键字保证的） ，并且您可以随意共享和缓存对不可变对象的引用，而不必复制或者克隆它们。 |
| 6. | There can be no side effects on immutable objects , and caching a reference to an immutable object is always safe from alias problems
不可变对象上没有副作用，并且缓存不可变对象的引用总是安全的，不会出现别名问题。 |
| 7. | One of the most surprising failings of the jmm is that immutable objects , whose immutability was intended to be guaranteed through use of the
Jmm的其中一个最惊人的缺点是，不可变对象似乎可以改变它们的值（这种对象的不变性旨在通过使用 |
| 8. | The old jmm allowed some surprising and confusing things to happen , such as final fields appearing not to have the value that was set in the constructor thus making supposedly immutable objects not immutable and unexpected results with memory operation reordering
旧的jmm允许一些奇怪而混乱的事情发生，比如final字段看起来没有那种设置在构造函数里的值（这样使得想像上的不可变对象并不是不可变的）和内存操作重新排序的意外结果。 |
| 9. | An object of an immutable sequence type cannot change once it is created . ( if the object contains references to other objects , these other objects may be mutable and may be changed ; however , the collection of objects directly referenced by an immutable object cannot change
一个不可变对象一旦建立其值不可能再改变(如果这个对象包括其它对象的引用,这个被引用的对象可以是可变对象并且其值可以变化;但为该不可变对象所直接引用的对象集合是不能变的 |
| 10. | However , because of potential delays in propagating changes in memory writes from one thread to another , there is a possible race condition that would allow a thread to first see one value for an immutable object , and then at some later time see a different value
但是，因为在将内存写方面的更改从一个线程传播到另一个线程时存在潜在的延迟，所以有可能存在一种竞态条件，即允许一个线程首先看到不可变对象的一个值，一段时间之后看到的是一个不同的值。 |
