Lifeboat blog

Better way to work around JVM type erasure in Scala pattern matching

This is a bit of functionality that I keep googling up over and over again.

Scala is very complex, and yet the features I love the most are among the simplest pleasure it provides

Scala error message could be quite cryptic, but there is one which I love the most. It is caused by smallest of the errors with the message insanely far from actual cause.

Squeryl is very smart, but some time you want to alter a bit of its logic. Here is one of the methods.

The error "class XXX inherits conflicting members" is almost obvious by the compiler message, but stop just one step short of the full solution.

It is possible to create a generic class, that would have parts of it aware of the actual class of its type argument. Without reflection and linked in compile time. Here is how.

Ever seen "Failed to initialize compiler: object scala.runtime in compiler mirror not found." error? Delete a corrupted JAR file.