Re: Formatting numbers without precision loss

[bil til <biltil52@...>]

> I’m running into the following issue (minimal example of a problem in a JSONschema validator):
>
> local maximum = 9007199254740991
Isn't this very obvious that something like this will happen at larger
float numbers? This is typical restriction for float.

Check e. g. Online-converter Float -> hex, then you should see the
problem more clearly (you do not define very well in your post, which
bit resolution you use for your floating point calcualations, this
depends strongly on your machine...).

Due to this, for "counting values" like time or large encoder values,
it is often advisable to use int's.