Although this is acceptable for c++, i think this is seems like not good to limit a shift direction and number of bits. So here should be just one Shift operation with -max,+max shift range and ability to rotate bits by other operation.
Sorry, i didn't understand this report description. Is the bug is in the fact that overlay text for the same corner are stacked at the same vertex position?
It seems you check demo file with experimental node in release build. Can you check if there is no such issue in daily build?
Wonder is this type only a temporal solution for smooth move to float3 normals? Or int16_2 will be forever even then normals will be humane?
Oh, did not know what constexpr in a namespace implice static by default/!
Mainly because duplication of the code in such simple case\
Well, i did not mean to make it shared, only simplify in way like:
do_something_with_segements(Curves, Extra_Points, ...) -> do_something_with_segments(segments, addinition).
Too bad that more complexity and less safety are chosen in favor of faster debug build\
Hope if all this code complexity can be avoided by
In case you'd like to improve this section of the code would be good to avoid void do_something() in favor of T something_from(a) or something_convert_to(in, out), .. .
Its better to use abstract term (like groups and group_i) rather then mix geometrical terms (like curve) in to generic (abstract) function like compress_intervals (etc how curves are related intervals?...).
intervals_by_curve.index_range().drop_front(1)