The intention is to support this by allowing users to specify their own conversion function for converting data types that are non-scalar into a scalar type of their choosing, to facilitate sorting these types. This is needed because tr-sort sorts by calculating item positions based on their value, not by comparing items with eachother.
It's quite likely that conversion functions for some data types may need access to the whole set being sorted, or some other universal set of possible values depending on each application, so consideration should be made for supporting this too in the design.
The intention is to support this by allowing users to specify their own conversion function for converting data types that are non-scalar into a scalar type of their choosing, to facilitate sorting these types. This is needed because tr-sort sorts by calculating item positions based on their value, not by comparing items with eachother.
It's quite likely that conversion functions for some data types may need access to the whole set being sorted, or some other universal set of possible values depending on each application, so consideration should be made for supporting this too in the design.