23h
awarded Nice Answer
Mar
2
awarded Good Answer
Feb
7
awarded Good Question
Dec
19
awarded Yearling
Dec
11
awarded Yearling
Dec
11
awarded Yearling
Nov
30
awarded Necromancer
Nov
29
reviewed Approve suggested edit on How do I get into 3D Java game development?
Nov
29
reviewed Approve suggested edit on transform.Rotate needs to change axis of rotation
Nov
25
awarded Notable Question
Nov
19
awarded Good Question
Nov
16
awarded Notable Question
Nov
16
awarded Popular Question
Nov
16
awarded Yearling
Nov
16
awarded Nice Question
Nov
15
asked What can I do with a plane ticket that won't be used?
Oct
10
answered If statement with both AND and OR Java
Jul
27
comment Updating immutable map as the side effect of getOrElse
@dk14 Right, that makes sense. I don't care about that, it's what I meant by "Since it's a memoization cache, the values are deterministic, so I don't care which thread gets to update the var first."
Jul
27
comment Updating immutable map as the side effect of getOrElse
Am I reading the JVM memory model wrong? Looks like reference assignments are atomic. "Writes to and reads of references are always atomic, regardless of whether they are implemented as 32-bit or 64-bit values." from docs.oracle.com/javase/specs/jls/se7/html/jls-17.html#jls-17.7
Jul
27
comment Updating immutable map as the side effect of getOrElse
Assuming reassigning the var itself is atomic, and the values I put in the map are deterministic, what kind of problems could I have? Or is reassigning the var not atomic?
1 2 3 4 5