Note: I'm posing this question to answer it myself, but other answers are welcome.
Consider the following simple method:
def add[T](x: T, y: T)(implicit num: Numeric[T]) = num.plus(x,y)
I can rewrite this using a context bound as follows
def add[T: Numeric](x: T, y: T) = ??.plus(x,y)
but how do I get an instance of the Numeric[T]
type so that I can invoke the plus
method?
Using the implicitly method
The most common and general approach is to use the implicitly method, defined in Predef:
Obviously, this is somewhat verbose and requires repeating the name of the type class.
Referencing the evidence parameter (don't!)
Another alternative is to use the name of the implicit evidence parameter automatically generated by the compiler:
It's surprising that this technique is even legal, and it should not be relied upon in practice since the name of the evidence parameter could change.
Context of a Higher Kind (introducing the
context
method)Instead, one can use a beefed-up version of the
implicitly
method. Note that the implicitly method is defined asThis method simply relies on the compiler to insert an implicit object of the correct type from the surrounding scope into the method call, and then returns it. We can do a bit better:
This allows us to define our
add
method asThe
context
method type parametersNumeric
andT
are inferred from the scope! Unfortunately, there are circumstances in which thiscontext
method will not work. When a type parameter has multiple context bounds or there are multiple parameters with different context bounds, for example. We can resolve the latter problem with a slightly more complex version:This version requires us to specify the type parameter every time, but handles multiple type parameters.
This answer describes another approach that results in more-readable, self-documenting client code.
Motivation
The
context
method that I described previously is a very general solution that works with any type class, without any additional effort. However, it may be undesirable for two reasons:The
context
method cannot be used when the type parameter has multiple context bounds, since the compiler has no way to determine which context bound is intended.The reference to the generic
context
method harms readability of the client code.Type-class-specific methods
Using a method that is tied to the desired type class makes client code much more readable. This is the approach used in the standard library for the Manifest type class:
Generalizing this approach
The main drawback of using type-class-specific methods is that an additional method must be defined for every type class. We can ease this process with the following definitions:
Then a new type-class-specific implicitly-style method can be defined, for any type class:
Finally, client code can use the Implicitly as follows:
At least since Scala 2.9 you can do the following: