Closed GoogleCodeExporter closed 9 years ago
Thanks for bringing this up. We should definitely review the Javadoc to make
sure
we're mentioning thread-safety when appropriate.
Since the Multimap implementation classes like HashMultimap already document
that
they're not threadsafe, the factory methods like Multimaps.newHashMultimap
don't need
to repeat that fact. However, the Multimaps methods newMultimap(),
newListMultimap(),
newSetMultimap(), newSortedSetMultimap(), and forMap() should document
thread-safety,
as should Multisets.forSet().
Original comment by jared.l....@gmail.com
on 16 Jun 2008 at 4:42
Original comment by jared.l....@gmail.com
on 16 Jun 2008 at 4:47
Original comment by jared.l....@gmail.com
on 16 Jun 2008 at 4:48
Fair enough with the concrete classes. I brought it up specifically for the
Standard** classes as they are package
private and not mentioned on the factory methods.
Original comment by jed.wesl...@gmail.com
on 17 Jun 2008 at 9:21
The Javadoc of those methods now describes the thread-safety of the generated
multimap or multiset. The revised Javadoc will be in the next Google
Collections release.
Original comment by jared.l....@gmail.com
on 7 Jul 2008 at 6:03
Original issue reported on code.google.com by
jed.wesl...@gmail.com
on 15 Jun 2008 at 3:58