The original intent was to benefit from the strongly typed uavcan.si namespace but the experience indicates that it makes the types more complex with little actual benefit. I propose replacing the segregated translational/rotational types with generalized types that contain native float32-typed fields instead of referring to the uavcan.si namespace.
pavel-kirienko
commented
1 year ago
The original intent was to benefit from the strongly typed
uavcan.sinamespace but the experience indicates that it makes the types more complex with little actual benefit. I propose replacing the segregated translational/rotational types with generalized types that contain nativefloat32-typed fields instead of referring to theuavcan.sinamespace.This change will not affect wire compatibility.