Conditional initialization in Ruby January 26
Exploring Ruby further, I came accross the || operator. It behaves like the boolean or operator in other languages (Java, C++) but with a catch: it returns the value of the last evaluated term. Since evaluation is lazy (from left to right), the last evaluated term is either the first non-false (I'll qualify this later on, bear with me) term or the last term in the expression.
More concretely, the expression d = a || b || c will assign the value of a to d if a is non-false, the value of b if a is false and b is non-false, or the value of c otherwise.
A non-false value in Ruby is anything that's neither nil, nor false. Thus, values such as true, 1, 0, "a", [] are all non-false.
The || operator can be combined with the = operator in a self-assignment statement: a ||= expression, which is a shorthand for a = a || expression.
A statement of that kind is essentially a conditional initializer: if a is nil (i.e., not initialized), initialize it with the value of expression. Otherwise, leave it untouched.
The conditional initialization idiom has at least one interesting usage. Before we get to it, it is important to note that in Ruby every statement returns a value, which means that any statement can be used in place of an expression. For example, one could conceivably do:
(if true then 8 end) + 3
Ok, on to the example now...
It is common to have to keep track of lists of items associated with certain key values. The obvious way to implement that is with a map of keys to lists of values. In Java, the code for adding an element to such structure would typically look like this:
In Ruby, using the conditional initialization idiom, it could be written more compactly as:
The @map[key] ||= [] piece performs the conditional initialization of the list associated with key and the (...) << value part adds the value to the existing or newly created list.
Ok, ok... you might be thinking, while the Java syntax is more verbose, is certainly more readable. That may be true, but in that case you could still write:
Which is still more compact than in Java but in my opinion does not sacrifice readability.
Pretty neat, eh?
More concretely, the expression d = a || b || c will assign the value of a to d if a is non-false, the value of b if a is false and b is non-false, or the value of c otherwise.
A non-false value in Ruby is anything that's neither nil, nor false. Thus, values such as true, 1, 0, "a", [] are all non-false.
The || operator can be combined with the = operator in a self-assignment statement: a ||= expression, which is a shorthand for a = a || expression.
A statement of that kind is essentially a conditional initializer: if a is nil (i.e., not initialized), initialize it with the value of expression. Otherwise, leave it untouched.
The conditional initialization idiom has at least one interesting usage. Before we get to it, it is important to note that in Ruby every statement returns a value, which means that any statement can be used in place of an expression. For example, one could conceivably do:
(if true then 8 end) + 3
Ok, on to the example now...
It is common to have to keep track of lists of items associated with certain key values. The obvious way to implement that is with a map of keys to lists of values. In Java, the code for adding an element to such structure would typically look like this:
void addToList(Object key, Object value)
{
List list = (List) this.map.get(key);
if (list == null) {
list = new ArrayList();
this.map.put(key, list);
}
list.add(value);
}
{
List list = (List) this.map.get(key);
if (list == null) {
list = new ArrayList();
this.map.put(key, list);
}
list.add(value);
}
In Ruby, using the conditional initialization idiom, it could be written more compactly as:
def addToList(key, value)
(@map[key] ||= []) << value
end
(@map[key] ||= []) << value
end
The @map[key] ||= [] piece performs the conditional initialization of the list associated with key and the (...) << value part adds the value to the existing or newly created list.
Ok, ok... you might be thinking, while the Java syntax is more verbose, is certainly more readable. That may be true, but in that case you could still write:
def addToList(key, value)
list = (@map[key] ||= [])
list << value
end
list = (@map[key] ||= [])
list << value
end
Which is still more compact than in Java but in my opinion does not sacrifice readability.
Pretty neat, eh?