> I think volatile is not that bad - it means: this is immutable field, > but it can change at any moment because of "external considerations". > As in standard flow, volatile would be a low-level hint for compiler > not to assume that field can be pre-fetched. It's may cause performance penalty.