#Scala trait series

Let’s look at a simple and contrived example.

Classes that implement this trait can be sorted with and can be compared with standard comparison operators (e.g.

See before using this trait for more information about whether to use instead. We can use a Scala Trait as an interface (contract), abstract class, class. A trait for data that have a single, natural ordering. We can also think of the concept as multiple inheritance without some of it’s dangers but with some limitations. Traits and classes can have companion objects (an object with the same name as the class/trait). Scala Traits are somewhat similar to Java 8s interface, but they do more. Or, by looking at traits from a different perspective we can also think of them as classes that can’t have constructor parameters. Traits can be thought of as interfaces in which it’s possible, but not necessary, to provide implementations for all or some of the methods that the interface defines.

#Scala trait series

In this part of the Learning Scala series we’ll look at traits which is one of the features of Scala that appeals the most to me as a C# developer. Scala lets us write short and expressive code, and today were going to look at one of the ways weve leveraged that.