ConcurrentHashMap/ConcurrentMap/Map.compute (original) (raw)
Brian Goetz brian.goetz at oracle.com
Fri Dec 14 16:47:34 PST 2012
- Previous message: ConcurrentHashMap/ConcurrentMap/Map.compute
- Next message: ConcurrentHashMap/ConcurrentMap/Map.compute
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Messy (for you) but probably the most option-preserving choice. Any preferences about which form? I omitted seq forms in current version so as to release the par ones without stalling over whether they'd be segregated under something sharing common interface. But now that this option seems out (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 :)
- 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