001/* 002 * Copyright (C) 2007 The Guava Authors 003 * 004 * Licensed under the Apache License, Version 2.0 (the "License"); 005 * you may not use this file except in compliance with the License. 006 * You may obtain a copy of the License at 007 * 008 * http://www.apache.org/licenses/LICENSE-2.0 009 * 010 * Unless required by applicable law or agreed to in writing, software 011 * distributed under the License is distributed on an "AS IS" BASIS, 012 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 013 * See the License for the specific language governing permissions and 014 * limitations under the License. 015 */ 016 017package com.google.common.collect; 018 019import static com.google.common.base.Preconditions.checkNotNull; 020 021import com.google.common.annotations.GwtCompatible; 022import com.google.errorprone.annotations.CanIgnoreReturnValue; 023import com.google.errorprone.annotations.CompatibleWith; 024import com.google.errorprone.annotations.DoNotMock; 025import java.util.Collection; 026import java.util.List; 027import java.util.Map; 028import java.util.Map.Entry; 029import java.util.Set; 030import java.util.function.BiConsumer; 031import org.jspecify.annotations.Nullable; 032 033/** 034 * A collection that maps keys to values, similar to {@link Map}, but in which each key may be 035 * associated with <i>multiple</i> values. You can visualize the contents of a multimap either as a 036 * map from keys to <i>nonempty</i> collections of values: 037 * 038 * <ul> 039 * <li>a → 1, 2 040 * <li>b → 3 041 * </ul> 042 * 043 * ... or as a single "flattened" collection of key-value pairs: 044 * 045 * <ul> 046 * <li>a → 1 047 * <li>a → 2 048 * <li>b → 3 049 * </ul> 050 * 051 * <p><b>Important:</b> although the first interpretation resembles how most multimaps are 052 * <i>implemented</i>, the design of the {@code Multimap} API is based on the <i>second</i> form. 053 * So, using the multimap shown above as an example, the {@link #size} is {@code 3}, not {@code 2}, 054 * and the {@link #values} collection is {@code [1, 2, 3]}, not {@code [[1, 2], [3]]}. For those 055 * times when the first style is more useful, use the multimap's {@link #asMap} view (or create a 056 * {@code Map<K, Collection<V>>} in the first place). 057 * 058 * <h3>Example</h3> 059 * 060 * <p>The following code: 061 * 062 * <pre>{@code 063 * ListMultimap<String, String> multimap = ArrayListMultimap.create(); 064 * for (President pres : US_PRESIDENTS_IN_ORDER) { 065 * multimap.put(pres.firstName(), pres.lastName()); 066 * } 067 * for (String firstName : multimap.keySet()) { 068 * List<String> lastNames = multimap.get(firstName); 069 * out.println(firstName + ": " + lastNames); 070 * } 071 * }</pre> 072 * 073 * ... produces output such as: 074 * 075 * <pre>{@code 076 * Zachary: [Taylor] 077 * John: [Adams, Adams, Tyler, Kennedy] // Remember, Quincy! 078 * George: [Washington, Bush, Bush] 079 * Grover: [Cleveland, Cleveland] // Two, non-consecutive terms, rep'ing NJ! 080 * ... 081 * }</pre> 082 * 083 * <h3>Views</h3> 084 * 085 * <p>Much of the power of the multimap API comes from the <i>view collections</i> it provides. 086 * These always reflect the latest state of the multimap itself. When they support modification, the 087 * changes are <i>write-through</i> (they automatically update the backing multimap). These view 088 * collections are: 089 * 090 * <ul> 091 * <li>{@link #asMap}, mentioned above 092 * <li>{@link #keys}, {@link #keySet}, {@link #values}, {@link #entries}, which are similar to the 093 * corresponding view collections of {@link Map} 094 * <li>and, notably, even the collection returned by {@link #get get(key)} is an active view of 095 * the values corresponding to {@code key} 096 * </ul> 097 * 098 * <p>The collections returned by the {@link #replaceValues replaceValues} and {@link #removeAll 099 * removeAll} methods, which contain values that have just been removed from the multimap, are 100 * naturally <i>not</i> views. 101 * 102 * <h3>Subinterfaces</h3> 103 * 104 * <p>Instead of using the {@code Multimap} interface directly, prefer the subinterfaces {@link 105 * ListMultimap} and {@link SetMultimap}. These take their names from the fact that the collections 106 * they return from {@code get} behave like (and, of course, implement) {@link List} and {@link 107 * Set}, respectively. 108 * 109 * <p>For example, the "presidents" code snippet above used a {@code ListMultimap}; if it had used a 110 * {@code SetMultimap} instead, two presidents would have vanished, and last names might or might 111 * not appear in chronological order. 112 * 113 * <p><b>Warning:</b> instances of type {@code Multimap} may not implement {@link Object#equals} in 114 * the way you expect. Multimaps containing the same key-value pairs, even in the same order, may or 115 * may not be equal and may or may not have the same {@code hashCode}. The recommended subinterfaces 116 * provide much stronger guarantees. 117 * 118 * <h3>Comparison to a map of collections</h3> 119 * 120 * <p>Multimaps are commonly used in places where a {@code Map<K, Collection<V>>} would otherwise 121 * have appeared. The differences include: 122 * 123 * <ul> 124 * <li>There is no need to populate an empty collection before adding an entry with {@link #put 125 * put}. 126 * <li>{@code get} never returns {@code null}, only an empty collection. 127 * <li>A key is contained in the multimap if and only if it maps to at least one value. Any 128 * operation that causes a key to have zero associated values has the effect of 129 * <i>removing</i> that key from the multimap. 130 * <li>The total entry count is available as {@link #size}. 131 * <li>Many complex operations become easier; for example, {@code 132 * Collections.min(multimap.values())} finds the smallest value across all keys. 133 * </ul> 134 * 135 * <h3>Implementations</h3> 136 * 137 * <ul> 138 * <li>{@link ImmutableListMultimap} 139 * <li>{@link ImmutableSetMultimap} 140 * <li>Configure your own mutable multimap with {@link MultimapBuilder} 141 * <li>{@link LinkedListMultimap} (for one unusual kind of mutable {@code Multimap}) 142 * </ul> 143 * 144 * Guava contains a number of other multimap implementations, such as {@link ArrayListMultimap}. In 145 * new code, we recommend using {@link MultimapBuilder} instead: It provides better control of how 146 * keys and values are stored. 147 * 148 * <h3>Other Notes</h3> 149 * 150 * <p>As with {@code Map}, the behavior of a {@code Multimap} is not specified if key objects 151 * already present in the multimap change in a manner that affects {@code equals} comparisons. Use 152 * caution if mutable objects are used as keys in a {@code Multimap}. 153 * 154 * <p>All methods that modify the multimap are optional. The view collections returned by the 155 * multimap may or may not be modifiable. Any modification method that is not supported will throw 156 * {@link UnsupportedOperationException}. 157 * 158 * <p>See the Guava User Guide article on <a href= 159 * "https://github.com/google/guava/wiki/NewCollectionTypesExplained#multimap">{@code Multimap}</a>. 160 * 161 * @author Jared Levy 162 * @since 2.0 163 */ 164@DoNotMock("Use ImmutableMultimap, HashMultimap, or another implementation") 165@GwtCompatible 166public interface Multimap<K extends @Nullable Object, V extends @Nullable Object> { 167 // Query Operations 168 169 /** 170 * Returns the number of key-value pairs in this multimap. 171 * 172 * <p><b>Note:</b> this method does not return the number of <i>distinct keys</i> in the multimap, 173 * which is given by {@code keySet().size()} or {@code asMap().size()}. See the opening section of 174 * the {@link Multimap} class documentation for clarification. 175 */ 176 int size(); 177 178 /** 179 * Returns {@code true} if this multimap contains no key-value pairs. Equivalent to {@code size() 180 * == 0}, but can in some cases be more efficient. 181 */ 182 boolean isEmpty(); 183 184 /** 185 * Returns {@code true} if this multimap contains at least one key-value pair with the key {@code 186 * key}. 187 */ 188 boolean containsKey(@CompatibleWith("K") @Nullable Object key); 189 190 /** 191 * Returns {@code true} if this multimap contains at least one key-value pair with the value 192 * {@code value}. 193 */ 194 boolean containsValue(@CompatibleWith("V") @Nullable Object value); 195 196 /** 197 * Returns {@code true} if this multimap contains at least one key-value pair with the key {@code 198 * key} and the value {@code value}. 199 */ 200 boolean containsEntry( 201 @CompatibleWith("K") @Nullable Object key, @CompatibleWith("V") @Nullable Object value); 202 203 // Modification Operations 204 205 /** 206 * Stores a key-value pair in this multimap. 207 * 208 * <p>Some multimap implementations allow duplicate key-value pairs, in which case {@code put} 209 * always adds a new key-value pair and increases the multimap size by 1. Other implementations 210 * prohibit duplicates, and storing a key-value pair that's already in the multimap has no effect. 211 * 212 * @return {@code true} if the method increased the size of the multimap, or {@code false} if the 213 * multimap already contained the key-value pair and doesn't allow duplicates 214 */ 215 @CanIgnoreReturnValue 216 boolean put(@ParametricNullness K key, @ParametricNullness V value); 217 218 /** 219 * Removes a single key-value pair with the key {@code key} and the value {@code value} from this 220 * multimap, if such exists. If multiple key-value pairs in the multimap fit this description, 221 * which one is removed is unspecified. 222 * 223 * @return {@code true} if the multimap changed 224 */ 225 @CanIgnoreReturnValue 226 boolean remove( 227 @CompatibleWith("K") @Nullable Object key, @CompatibleWith("V") @Nullable Object value); 228 229 // Bulk Operations 230 231 /** 232 * Stores a key-value pair in this multimap for each of {@code values}, all using the same key, 233 * {@code key}. Equivalent to (but expected to be more efficient than): 234 * 235 * <pre>{@code 236 * for (V value : values) { 237 * put(key, value); 238 * } 239 * }</pre> 240 * 241 * <p>In particular, this is a no-op if {@code values} is empty. 242 * 243 * @return {@code true} if the multimap changed 244 */ 245 @CanIgnoreReturnValue 246 boolean putAll(@ParametricNullness K key, Iterable<? extends V> values); 247 248 /** 249 * Stores all key-value pairs of {@code multimap} in this multimap, in the order returned by 250 * {@code multimap.entries()}. 251 * 252 * @return {@code true} if the multimap changed 253 */ 254 @CanIgnoreReturnValue 255 boolean putAll(Multimap<? extends K, ? extends V> multimap); 256 257 /** 258 * Stores a collection of values with the same key, replacing any existing values for that key. 259 * 260 * <p>If {@code values} is empty, this is equivalent to {@link #removeAll(Object) removeAll(key)}. 261 * 262 * @return the collection of replaced values, or an empty collection if no values were previously 263 * associated with the key. The collection <i>may</i> be modifiable, but updating it will have 264 * no effect on the multimap. 265 */ 266 @CanIgnoreReturnValue 267 Collection<V> replaceValues(@ParametricNullness K key, Iterable<? extends V> values); 268 269 /** 270 * Removes all values associated with the key {@code key}. 271 * 272 * <p>Once this method returns, {@code key} will not be mapped to any values, so it will not 273 * appear in {@link #keySet()}, {@link #asMap()}, or any other views. 274 * 275 * @return the values that were removed (possibly empty). The returned collection <i>may</i> be 276 * modifiable, but updating it will have no effect on the multimap. 277 */ 278 @CanIgnoreReturnValue 279 Collection<V> removeAll(@CompatibleWith("K") @Nullable Object key); 280 281 /** Removes all key-value pairs from the multimap, leaving it {@linkplain #isEmpty empty}. */ 282 void clear(); 283 284 // Views 285 286 /** 287 * Returns a view collection of the values associated with {@code key} in this multimap, if any. 288 * Note that when {@code containsKey(key)} is false, this returns an empty collection, not {@code 289 * null}. 290 * 291 * <p>Changes to the returned collection will update the underlying multimap, and vice versa. 292 */ 293 Collection<V> get(@ParametricNullness K key); 294 295 /** 296 * Returns a view collection of all <i>distinct</i> keys contained in this multimap. Note that the 297 * key set contains a key if and only if this multimap maps that key to at least one value. 298 * 299 * <p>Changes to the returned set will update the underlying multimap, and vice versa. However, 300 * <i>adding</i> to the returned set is not possible. 301 */ 302 Set<K> keySet(); 303 304 /** 305 * Returns a view collection containing the key from each key-value pair in this multimap, 306 * <i>without</i> collapsing duplicates. This collection has the same size as this multimap, and 307 * {@code keys().count(k) == get(k).size()} for all {@code k}. 308 * 309 * <p>Changes to the returned multiset will update the underlying multimap, and vice versa. 310 * However, <i>adding</i> to the returned collection is not possible. 311 */ 312 Multiset<K> keys(); 313 314 /** 315 * Returns a view collection containing the <i>value</i> from each key-value pair contained in 316 * this multimap, without collapsing duplicates (so {@code values().size() == size()}). 317 * 318 * <p>Changes to the returned collection will update the underlying multimap, and vice versa. 319 * However, <i>adding</i> to the returned collection is not possible. 320 */ 321 Collection<V> values(); 322 323 /** 324 * Returns a view collection of all key-value pairs contained in this multimap, as {@link Entry} 325 * instances. 326 * 327 * <p>Changes to the returned collection or the entries it contains will update the underlying 328 * multimap, and vice versa. However, <i>adding</i> to the returned collection is not possible. 329 */ 330 Collection<Entry<K, V>> entries(); 331 332 /** 333 * Performs the given action for all key-value pairs contained in this multimap. If an ordering is 334 * specified by the {@code Multimap} implementation, actions will be performed in the order of 335 * iteration of {@link #entries()}. Exceptions thrown by the action are relayed to the caller. 336 * 337 * <p>To loop over all keys and their associated value collections, write {@code 338 * Multimaps.asMap(multimap).forEach((key, valueCollection) -> action())}. 339 * 340 * @since 21.0 341 */ 342 default void forEach(BiConsumer<? super K, ? super V> action) { 343 checkNotNull(action); 344 entries().forEach(entry -> action.accept(entry.getKey(), entry.getValue())); 345 } 346 347 /** 348 * Returns a view of this multimap as a {@code Map} from each distinct key to the nonempty 349 * collection of that key's associated values. Note that {@code this.asMap().get(k)} is equivalent 350 * to {@code this.get(k)} only when {@code k} is a key contained in the multimap; otherwise it 351 * returns {@code null} as opposed to an empty collection. 352 * 353 * <p>Changes to the returned map or the collections that serve as its values will update the 354 * underlying multimap, and vice versa. The map does not support {@code put} or {@code putAll}, 355 * nor do its entries support {@link Entry#setValue setValue}. 356 */ 357 Map<K, Collection<V>> asMap(); 358 359 // Comparison and hashing 360 361 /** 362 * Compares the specified object with this multimap for equality. Two multimaps are equal when 363 * their map views, as returned by {@link #asMap}, are also equal. 364 * 365 * <p>In general, two multimaps with identical key-value mappings may or may not be equal, 366 * depending on the implementation. For example, two {@link SetMultimap} instances with the same 367 * key-value mappings are equal, but equality of two {@link ListMultimap} instances depends on the 368 * ordering of the values for each key. 369 * 370 * <p>A non-empty {@link SetMultimap} cannot be equal to a non-empty {@link ListMultimap}, since 371 * their {@link #asMap} views contain unequal collections as values. However, any two empty 372 * multimaps are equal, because they both have empty {@link #asMap} views. 373 */ 374 @Override 375 boolean equals(@Nullable Object obj); 376 377 /** 378 * Returns the hash code for this multimap. 379 * 380 * <p>The hash code of a multimap is defined as the hash code of the map view, as returned by 381 * {@link Multimap#asMap}. 382 * 383 * <p>In general, two multimaps with identical key-value mappings may or may not have the same 384 * hash codes, depending on the implementation. For example, two {@link SetMultimap} instances 385 * with the same key-value mappings will have the same {@code hashCode}, but the {@code hashCode} 386 * of {@link ListMultimap} instances depends on the ordering of the values for each key. 387 */ 388 @Override 389 int hashCode(); 390}