Shatter behaves differently in v5 and v6

It seems that the shatter component returns curve segments in a different order between the last Rhino 5 version of Grasshopper and Rhino 6. Consider this definition: (6.8 KB)

See below the outputs in Rhino 5 (left) and Rhino 6 (right):

Sounds like a petty request, I know, but when you are trying to update an infrastructure with thousands of Grasshopper models to Rhino 6, it’s a retro-compatibility issue that could be problematic.

@DavidRutten any idea whether backwards compatibility can be achieved in this case? Is this a GH-level breaking change? Since there is no directly equivalent functionality in Rhino, I can’t really test it there.

Thanks for any insight about this!