Just a thought for user: Be aware of different kinds of limits.

[Spammed]

Regarding docs/blog/posts/quantity-point-bounds.md:

There are boundaries imposed by

• physical laws (e.g. regarding mass),
• conventions of the measurement system (e.g. regarding meridian angles),
• standards and regulations (e.g. regarding noise levels in the workplace)
• and what is experienceable (e.g. regarding the body temperature of living humans)

I would probably start by sticking to the first two kinds, but:
When formulating specific boundaries, one ties one’s (possibly too narrow) view of the world to the ‘quantity’.
The major advantage is that now, one can be alerted if the quantity falls out out of this.

[mpusz]

I am unsure how to interpret this. The library does not plan to enforce any bounds besides the non negativity and maybe some well established geographical constraints. However, it provides the power to users to do what they want.

I am still working on this feature but I hope to be done soon.

[Spammed]

It’s more of a point that users should bear in mind, which doesn’t affect the library’s design.
What prompted me to think of this was the body temperature example.

[mpusz]

Everything depends on a use case. If something is life-threatening, then an exception (e.g., on a sports watch during a workout) might be a good idea.