Squants VS NamedType

Scala's squants library is a nice implementation of units-of-measure/dimensional-analysis http://www.squants.com

In particular it uses types for dimensions; whilst units are just constructors. Hence `Meters(2)` and `Microns(7)` have the same type (`Length`).

squants for the “Market” package to use in financial calculations.

take a peek at https://www.squants.com looks like not in your language, but maybe you can apply some same concepts

You might find the Squants library for Scala interesting; it even seems like an apt usage of some oft-questioned language features.

https://github.com/typelevel/squants

This article seems to be targeted towards beginners. From the title, I was expecting it to cover something like https://github.com/joboccara/NamedType, which is a technique I would recommend.

I haven't used this library in particular or this one, but bless the authors and all the others for trying to make it happen… the project I'm now leading uses strongly typed strings for different component addresses, and it saves me to constantly look up the documentation what the functions need – it's beautiful.

I think you are thinking of something like https://github.com/joboccara/namedtype

The basic jist is that if you use strong types, you can dispatch more easily inside the function. Because of how the template function is generically written, I don't need to do any manual calls to the template parameters, it all gets figured out through automatic template deduction. In this example I'm using really simple types, but in a more production system I would use something more along the lines of Jonathan Boccara's NamedType. Here is a great article that explains it pretty well [link].