P3
The term "thread safe" is used both in the Java Language Specification (e.g. in 17.5 final Field Semantics) and in the Java SE documentation but is not formally defined.
From the annotation `@ThreadSafe` (which is not a part of Java SE), there is a tentative definition:
"No sequences of accesses (reads and writes to public fields, calls to public methods) may put the object into an invalid state, regardless of the interleaving of those actions by the runtime, and without requiring any additional synchronization or coordination on the part of the caller."
The above is based on code developed by Brian Goetz and Tim Peierls and concepts published in 'Java Concurrency in Practice' by Brian Goetz, Tim Peierls, Joshua Bloch, Joseph Bowbeer, David Holmes and Doug Lea.
I think the term should be formally defined. Preferably in the JLS.
From the annotation `@ThreadSafe` (which is not a part of Java SE), there is a tentative definition:
"No sequences of accesses (reads and writes to public fields, calls to public methods) may put the object into an invalid state, regardless of the interleaving of those actions by the runtime, and without requiring any additional synchronization or coordination on the part of the caller."
The above is based on code developed by Brian Goetz and Tim Peierls and concepts published in 'Java Concurrency in Practice' by Brian Goetz, Tim Peierls, Joshua Bloch, Joseph Bowbeer, David Holmes and Doug Lea.
I think the term should be formally defined. Preferably in the JLS.