mp-units VS termtosvg

It's not the type system you're complaining about, though. It takes a bit of work but you can write types that include units information with no loss of performance.

I recommend using this as reference https://github.com/mpusz/units it probably solves the same or similar problem.

Yep. And there are some libraries to provide strong-type int, depending on what you need: type_safe or even units.

Indeed you cannot. Then again, you couldn't write a library like fmtlib in C in the first place. I mean why do you complain about C++ features which enable you to write libraries you otherwise couldn't? How would you expect to implement equivalent libraries to EVE or mp-units in C alone?

How does it compare with https://github.com/mpusz/units ?

I don't have a book to recommend, but I have a fantastic library: https://github.com/mpusz/units

Good C++ library for that topic is [0]. You can even go further and combine with something like [1] which is super helpful for kalman filters and other stuff where you have heterogeneous units in one vector.

[0] https://github.com/mpusz/units

This seems to be on a progress to standardisation for c++23/26: https://github.com/mpusz/units

Looking at the source, it appears to have been generated by https://github.com/nbedos/termtosvg

https://github.com/nbedos/termtosvg (dead, unknown if usable?)

Yes, it's great! I've used [termtosvg](https://github.com/nbedos/termtosvg) a lot in the past, but it seems it's archived now. :(

Apart from the obvious feels (I love that movie), the big takeaway from this for me is https://github.com/nbedos/termtosvg - makes me think, considering how much I enjoy creating documentation (sort of as a relaxing technique), why the hell haven't I jazzed up my READMEs yet?!