But I'm still confused about their implementation. In particular, I assume that once you've placed an implicit parameter that asserts a particular relationship, then you can use variables as if they've automatically been cast properly, e.g. this will compile:

But how does this actually work in the compiler? Is there some magic compiler support for these operators, and if not, what's the underlying mechanism that allows it to infer this sort of relationship from the definition? (Was this mechanism added specifically to allow these operators to work, and how specific is it to these particular operators?) It seems a little magical that you can place an extra implicit parameter like this which somehow changes the compiler's interpretation of a type.

1 Answer
1

There is an implicit method in Predef which can provide a value of type A <:< A for any A

implicit def conforms[A]: A <:< A

When you try to invoke your method, it looks for an implicit value of type T <:< String. The compiler will check to see if conforms[T] is a valid value. Let's say T is Nothing then there will be an implicit value Nothing <:< Nothing in scope which will allow your method call to compile. Due to the way <:< is defined

sealed abstract class <:<[-From, +To]

From is allowed to vary up and To is allowed to vary down. So a Nothing <:< Nothing is still a valid Nothing <:< String since Nothing is a subtype of String. A String <:< String would also be a valid Nothing <:< String since String is a supertype of Nothing (but the compiler seems to always pick just the first type).

You can call methods of String on it because <:< also extends => aka Function1 and serves as an implicit conversion from T to String, which basically ends up doing a safe cast.

=:= is the same thing except it is defined without any variance annotations, so the types must match exactly.

<%< is defined like <:< but the implicit method is a bit different, it adds another parameter to specify a view bound

Thanks! The following is the key to explaining how the compiler lets you call String methods (or whatever): You can call methods of String on it because <:< also extends => aka Function1 and serves as an implicit conversion from T to String, which basically ends up doing a safe cast.
–
Urban VagabondJul 22 '12 at 0:17