You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
This test asserts that neither the "hit" or "miss" counts are affected by two Cache.putIfAbsent() operations
The spec lists this however (page 131):
operation
Puts
Removals
Hits
Misses
boolean putIfAbsent(K key, V value)
Yes
No
Yes
Yes
I am of the opinion that the first putIfAbsent() would count as both a "put" and a "miss", and the second call would record a "hit" in the cache statistics
The text was updated successfully, but these errors were encountered:
timeck
added a commit
to timeck/jsr107tck
that referenced
this issue
Nov 22, 2014
This test asserts that neither the "hit" or "miss" counts are affected by two
Cache.putIfAbsent()
operationsThe spec lists this however (page 131):
I am of the opinion that the first
putIfAbsent()
would count as both a "put" and a "miss", and the second call would record a "hit" in the cache statisticsThe text was updated successfully, but these errors were encountered: