I am sick of the following pattern:
value = map.get(key);
if (value == null) {
value = new Object();
map.put(key, value);
}
This example only scratches the surface of the extra code to be written when you have nested maps to represent a multi-dimensional structure.
I'm sure something somewhere exists to avoid this, but my Googling efforts yielded nothing relevant. Any suggestions?
The
and from Java 8
has
which returns the value mapped to key or inserts the given value and null if no value is mapped for the key.
If you need lazy evaluation of the value there is
You can use MutableMap and
getIfAbsentPut()
from Eclipse Collections which returns the value mapped to the key or inserts the given value and returns the given value if no value is mapped to the key.You can either use a method reference to create a new
Object
:Or you can directly create a new
Object
:In the first example, the object will be created only if there is no value mapped to the key.
In the second example, the object will be created regardless.
Note: I am a contributor to Eclipse Collections.
EDIT : Note that the feature mentioned below is long deprecated, and a CacheBuilder should be used instead.
The Guava library has a "computing map", see MapMaker.makeComputingMap(Function).
If you need the Function several times, extract it into a utility class, and then create the Map like this (where
MyFunctions.NEW_OBJECT
is the static Function instance):Maybe I'm not seeing the whole problem, but how about using inheritance or composition to add this behavior to the Map object?
The problem with this pattern is that you'd have to somehow define the value that should be used in case the
get()
returns null.There certainly are libraries out there and IIRC there are also some newer collections that do that, but unfortunately I don't remember which those were.
However, you could write a utility method yourself, provided you have a standard way of creating the new values. Something like this might work:
Note that you'd either have to throw the reflection exceptions or handle them in the method. Additionally, this requires the
valueClass
to provide a no-argument constructor. Alternatively, you could simply pass the default value that should be used.If in any case you need to get a default data in your map if it's not existing
javadocs