Questions And Answers

More Tutorials

Scala Handling units


Type aliases

type Meter = Double

This simple approach has serious drawbacks for unit handling as every other type that is a Double will be compatible with it:

type Second = Double
var length: Meter = 3
val duration: Second = 1
length = duration
length = 0d

All of the above compiles, so in this case units can only be used for marking input/output types for the readers of the code (only the intent).

Value classes

case class Meter(meters: Double) extends AnyVal
case class Gram(grams: Double) extends AnyVal

Value classes provide a type-safe way to encode units, even if they require a bit more characters to use them:

var length = Meter(3)
var weight = Gram(4)
//length = weight //type mismatch; found : Gram required: Meter

By extending AnyVals, there is no runtime penalty for using them, on the JVM level, those are regular primitive types (Doubles in this case).

In case you want to automatically generate other units (like Velocity aka MeterPerSecond), this approach is not the best, though there are libraries that can be used in those cases too:

• Squants

• units

• ScalaQuantity


In this page (written and validated by ) you learned about Scala Handling units . What's Next? If you are interested in completing Scala tutorial, your next topic will be learning about: Scala Higher Order Function.

Incorrect info or code snippet? We take very seriously the accuracy of the information provided on our website. We also make sure to test all snippets and examples provided for each section. If you find any incorrect information, please send us an email about the issue:

Share On:

Mockstacks was launched to help beginners learn programming languages; the site is optimized with no Ads as, Ads might slow down the performance. We also don't track any personal information; we also don't collect any kind of data unless the user provided us a corrected information. Almost all examples have been tested. Tutorials, references, and examples are constantly reviewed to avoid errors, but we cannot warrant full correctness of all content. By using, you agree to have read and accepted our terms of use, cookies and privacy policy.