Hey, just to let you know that I’ve added this conversion operator as an opt-in: https://www.fluentcpp.com/2017/11/07/calling-functions-methods-strong-types/.
Thought you might be interested to know!

Yes, I did. Thanks for noticing that Juan, this is now corrected.
Let me know how it goes for you when using strong types, and don’t hesitate if I can do anything to help.

Great, Pawel! Let me know how it goes, and if you’re facing some difficulties I’d be glad if I can help.

Really glad to hear that the blog is helpful to you Todd! Please let me know if there is anything else I can do, in particular topics you’d like me to write about, to make this blog even more useful to you.
Totally in line with you on the topic of strong typing for units. If you have this need in your code you may also want to have a look at Boost Units for comparison, which focuses on units but with different design choices. Robert Ramey’s talk explains its principles very well. And about performance you’ll probably be interested to read Good news: strong types are (mostly) free in C++.
Thanks for your feedback!

Your trick of declaring the parameter type within the template declaration is terrific. I’d never seen that before. It certainly cleans the code up.

Right, inheritance is nice for recycling operators. But on the other side the using syntax is more declarative. Which one to choose? We can have both actually. I’m writing a new post about this, scheduled for the coming weeks (other posts are queuing up!). But in the meantime you can have a look at the implementation on the github project, and let me know what you think. How does that sound? https://github.com/joboccara/namedtype

or I think inheritance for every strong type is the better way,
so we can support many useful function such as +=
=, ++, etc specifically.

operator +(Width, Width )///