ConcurrentHashMap/ConcurrentMap/Map.compute (original) (raw)
Doug Lea dl at cs.oswego.edu
Fri Dec 14 16:58:53 PST 2012
- Previous message: ConcurrentHashMap/ConcurrentMap/Map.compute
- Next message: ConcurrentHashMap/ConcurrentMap/Map.compute
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/14/12 19:47, Brian Goetz wrote:
(no MapStreams) I'm left with the usual choices of how to name and/or parameterize them. Probably: forEach{Key,Value,Entry,}Sequentially / forEach{...}InParallel reduce{...}Sequentially / reduce{...}InParallel search{...}Sequentially / search{...}InParallel Seems reasonable. I'd suggest leaving off Sequentially but you'll just ignore that :)
The main reason is caution wrt future APIs by not using the prime real estate of plain "forEach". And it seems OK to do this here in CHM, since it is designed mainly for concurrency+parallelism anyway, so making the choice very explicit is more defensible than elsewhere.
-Doug
- 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