Mateusz Pusz

How about: ```cpp constexpr auto distance_traveled = norm(isq::displacement); constexpr QuantityOf auto avg_speed(QuantityOf auto d, QuantityOf auto t) { return d / t; } ``` ? We can also consider adding...

Let's describe the elements in the branch here: - `path_length` - length of a rectifiable curve between two of its points - `distance` - shortest path length between two points...

@dwith-ts, thanks for feedback. I was not aware of this. This complicates things a bit, but I think I know how to make it work. Do you also suggest that...

> Just a side note as it has been mentioned twice already: taking the norm of a position vector should / can not be a valid operation. You can only...

> With 'Every radial_distance [vector] is [a scalar] distance.' (or 'Every [position_vector is a scalar] radial_distance is [a scalar] distance.' ?) I have to get along somehow. `radial_distance` is defined...

> Is this definition from an ISO draft? No, I just improvised a bit :wink: The actual definitions are: ### `displacement` - _Definition_: vector quantity between any two points in...

@dwith-ts, I am afraid that, according to the above definitions, we can't disallow taking the magnitude of a position vector.

> The dimension also encodes some sort of information about the affine space as [m/s] is always an indication that we have a quantity and not a quantity_point; => position_vector[m/s]...

In the entire ISO/IEC 80000 series that defines ISQ, you will not find any mention of the affine space abstractions, points, or deltas. I mentioned it even in [the blog...

> For a clean-sheet design I'd go with either something like inversing the relation by using vector and vector which would also be future-proof for non-uniform vectors. But I presume...