ConcurrentHashMap/ConcurrentMap/Map.compute (original) (raw)
Remi Forax forax at univ-mlv.fr
Fri Dec 7 08:28:25 PST 2012
- Previous message: ConcurrentHashMap/ConcurrentMap/Map.compute
- Next message: ConcurrentHashMap/ConcurrentMap/Map.compute
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/07/2012 05:16 PM, Doug Lea wrote:
On 12/07/12 09:51, Doug Lea wrote:
Basic idea: defaults for function-accepting Map methods are solely in terms of the 4 CM methods, which are in turn non-atomic for non-CM.... See update at: http://gee.cs.oswego.edu/dl/wwwtmp/apis/Map.html These probably now take more effort for users to understand, but otherwise seem pretty good to me. Any complaints?
I just don't like compute, the verb is too generic, update/updateValue is perhaps better.
(I reordered some of the decls so that they would flow a little better for the 5% (if that) of users who ever read the Javadocs sequentially.) -Doug
Rémi
- Previous message: ConcurrentHashMap/ConcurrentMap/Map.compute
- Next message: ConcurrentHashMap/ConcurrentMap/Map.compute
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the lambda-libs-spec-experts mailing list