mp-units VS macroquad

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

See the macroquad docs for full details on building a WASM game.

Any opinion on ggez? I don't like how everything in macroquad is global state https://github.com/not-fl3/macroquad/issues/333

I prefer examples like the ones in Macroquad: https://github.com/not-fl3/macroquad/tree/master/examples. I'm not against advanced examples, but the priority should be extremely clear, minimal, self contained ones.

There were even discussions about deprecating static mut. Even if you think you got it right, there are too many things that might go wrong, like aliasing. For example, macroquad needs a complete rewrite because of their static mut.

It's based on macroquad and you can play the wasm version here: https://unvirtual.github.io/yinsh-rs/

The reality is that I have used unsafe that is also unsound out of convenience because fixing it is a papercut too many. And this tends to be common! I know enough to spot unsoundness in other projects (sometimes even early). But not enough to be confident in my own abilities to write sound unsafe code. Why? Because it's really flipping hard, that's why!

Given that you are making a game, you might want to consider using a game framework such as https://github.com/not-fl3/macroquad/.Macroquad has full support for WASM, and will allow you to render your game both locally and in the browser via WASM depending on how you compile it.