Community
Participate
Working Groups
According to https://docs.oracle.com/javase/specs/jls/se7/html/jls-17.html#jls-17.5 For the programm class FinalFieldExample { final int x; int y; static FinalFieldExample f; public FinalFieldExample() { x = 3; y = 4; } static void writer() { f = new FinalFieldExample(); } static void reader() { if (f != null) { int i = f.x; // guaranteed to see 3 int j = f.y; // could see 0 } } } only on a final field the initialization is given to be seen by other threads. While it is not an always an issue the question is if it makes sense to use final where possible anyway. http://www.cs.umd.edu/~pugh/java/memoryModel/jsr-133-faq.html#finalWrong https://stackoverflow.com/questions/22743223/are-final-fields-really-useful-regarding-thread-safety
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.