Начал читать с середины. Про безопасную публикацию

3.5. Safe Publication
So far we have focused on ensuring that an object not be published, such as when it is supposed to be confined to a thread or within another object. Of course, sometimes we do want to share objects across threads, and in this case we must do so safely. Unfortunately, simply storing a reference to an object into a public field, as in Listing 3.14, is not enough to publish that object safely.

Listing 3.13. Caching the Last Result Using a Volatile Reference to an Immutable Holder Object.



}

Listing 3.14. Publishing an Object without Adequate Synchronization. Don't Do this.



You may be surprised at how badly this harmless-looking example could fail. Because of visibility problems, the Holder could appear to another thread to be in an inconsistent state, even though its invariants were properly established by its constructor! This improper publication could allow another thread to observe a partially constructed object.

Возникло пару вопросов по книге.

Что за аннотация @ThreadSafe ?

код(3.13) в главе представлен, но ссылок на него ниоткуда нет. Зачем он тогда представлен?

Сергей Арсеньев,

я понял, эта картинка к другому разделу. Очень странно книга устроена.

раздел 3.5 меня разочаровал. Один пример неправильной публикации и всё. примеров правильной нет. Никаких разборов.