| commit | 5c9da573d8ec812608e1b21f94997b926586e2dc | |
| author | Thomas Wolf <thomas.wolf@paranor.ch> | |
| Mon, 12 Oct 2015 22:07:33 +0000 (13 00:07 +0200) | ||
| committer | Andrey Loskutov <loskutov@gmx.de> | |
| Tue, 13 Oct 2015 13:25:24 +0000 (13 09:25 -0400) | ||
| tree | bbb8ed5b073dce652b63d74e89d27d21228b48ee | treesnapshot (tar.gz zip) |
| parent | 1852b8c1e825522ebb72f281456707f17eddac8b | commitdiff |
Remove unnecessary AtomicReference instances
Per JLS 17-7[1] "writes to and reads of references are always atomic".
So unless one needs getAndSet or compareAndSet, there's no need to use
AtomicReference.
[1]
https://docs.oracle.com/javase/specs/jls/se7/html/jls-17.html#jls-17.7
Change-Id: I85668337bb9d61f0fd59feb421afe628ab5b3828
Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>
Per JLS 17-7[1] "writes to and reads of references are always atomic".
So unless one needs getAndSet or compareAndSet, there's no need to use
AtomicReference.
[1]
https://docs.oracle.com/javase/specs/jls/se7/html/jls-17.html#jls-17.7
Change-Id: I85668337bb9d61f0fd59feb421afe628ab5b3828
Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>