MIssing MultimapMaker / expand functionality for MapMaker #142
Comments
|
Original comment posted by kevinb9n on 2009-09-17 at 05:57 PM (No comment entered for this change.) Labels: |
|
Original comment posted by kevinb9n on 2009-09-17 at 06:02 PM (No comment entered for this change.) Labels: |
|
Original comment posted by kevinb@google.com on 2010-07-30 at 03:53 AM (No comment entered for this change.) Labels: - |
|
Original comment posted by fry@google.com on 2011-01-26 at 09:56 PM (No comment entered for this change.) Status: |
|
Original comment posted by kevinb@google.com on 2011-07-13 at 06:18 PM (No comment entered for this change.) Status: |
|
Original comment posted by fry@google.com on 2011-12-10 at 03:37 PM (No comment entered for this change.) Labels: |
|
Original comment posted by fry@google.com on 2012-02-16 at 07:17 PM (No comment entered for this change.) Status: |
|
Original comment posted by wasserman.louis on 2012-02-23 at 07:21 PM Based on the migration to Cache, and the now-reduced role of MapMaker, is there still interest in a MultimapMaker...or do people want to demand MultiCache? |
|
Original comment posted by fry@google.com on 2012-02-23 at 07:41 PM The request in this issue would be satisfied by adding .makeMultimap() which sounds reasonable to me. I don't think we want MultiCache. |
|
Original comment posted by wasserman.louis on 2012-02-23 at 08:03 PM (I agree that we don't want MultiCache.) I suspect, however, that the current Multimap implementation would choke on weakly referenced value collections. This may require some work...? |
|
Original comment posted by kevinb@google.com on 2012-02-24 at 09:13 PM Yes, it would take a lot of work; also, the Maps produced are concurrent, but designing a good concurrent multimap is difficult without making a lot of assumptions about usage patterns that we don't have much basis for. |
|
Original comment posted by kevinb@google.com on 2012-05-30 at 07:43 PM (No comment entered for this change.) Labels: - |
|
Original comment posted by kevinb@google.com on 2012-06-22 at 06:16 PM (No comment entered for this change.) Status: |
|
Original comment posted by kevinb@google.com on 2013-03-12 at 06:25 PM We don't feel this is an area we will be looking into in the foreseeable future. Status: |
gissuebot
added
migrated
type=addition
Original issue created by heroldsilversurfer on 2009-04-10 at 10:10 PM
currently i use MapMaker to create short-lived caches within a hibernate
session, like
MapMaker().weakKeys().makeMap();
the whole point of Multimaps are to get rid of constructs like the one above.
if possible a .makeMultimap() Method should create a Mutable Multimap with
the given features, or alternatively, a new MultimapMaker() class that
mimics the MapMaker. such a builder should have identical semantics.
see also:
http://stackoverflow.com/questions/737060/create-weak-multimap-with-google-collections
The text was updated successfully, but these errors were encountered: