Re: Concurrent Hash Map javadoc question
Keith Turner <[email protected]>
| Newsgroups | gmane.comp.java.openjdk.general,gmane.comp.java.jsr.166-concurrency |
|---|---|
| Message-ID | <CAGUtCHr-LWsVoA8L2i+PMB7mEkck5iOG6hoaBVuYspdytGUviw@mail.gmail.com> |
On Tue, Sep 17, 2019 at 9:35 PM Martin Buchholz <[email protected]> wrote: > > I think this doc difference is intentional. If that is the case, it would be really nice update the javadoc to make it explicit. > > In case of a retry loop, the value may have changed in the case of computeIfPresent or compute and so the function must be called again with the new value. > > On Tue, Sep 17, 2019 at 4:36 PM Martijn Verburg <[email protected]> wrote: >> >> Hi Keith, >> >> I think this is one for concurrency interest to answer. >> >> Cheers, >> Martijn >> >> >> On Tue, 17 Sep 2019 at 12:48, Keith Turner <[email protected]> wrote: >> >> > The javadoc for ConcurrentHashMap.computeIfAbsent() states the >> > remapping function is applied at most once. The functions >> > computeIfPresent() and compute() do not explicitly state if the >> > remapping functions could possibly be run multiple times. Does anyone >> > know if computeIfPresent() and compute() are guaranteed to only run >> > the remapping functions at most once? If so, should the javadoc be >> > updated? >> > >> > Thanks, >> > >> > Keith >> >