Francesco Nigro 60dbeae438 ARTEMIS-1702 ConcurrentLongHashMap and ConcurrentLongHashSet should avoid volatile set cost on put/remove ... Most of the visibility guarantees of size/capacity fields modifications are already provided through optimistic locking, hence it could be used it instead of volatile set(s) on put/remove, making those methods more efficient.		2018-02-26 17:38:36 -05:00
..
src	ARTEMIS-1702 ConcurrentLongHashMap and ConcurrentLongHashSet should avoid volatile set cost on put/remove	2018-02-26 17:38:36 -05:00
pom.xml	ARTEMIS-1510 refactor Maven poms	2017-11-13 17:03:35 -05:00