I want a canonical tuple format so that calling Doublet/components() instead of Doublet/ascending() and Doublet/descending() makes sense. All other objects destructure their contents by calling components(), and I want this to be consistent across the board. A recent change also made the 2nd and 3rd method easy to conflate with BinaryInteger/ascending(Bit) and BinaryInteger/descending(Bit). This project always view binary integers in ascending order, so (low:high:) makes the most sense to keep.
I want a canonical tuple format so that calling Doublet/components() instead of Doublet/ascending() and Doublet/descending() makes sense. All other objects destructure their contents by calling components(), and I want this to be consistent across the board. A recent change also made the 2nd and 3rd method easy to conflate with BinaryInteger/ascending(Bit) and BinaryInteger/descending(Bit). This project always view binary integers in ascending order, so (low:high:) makes the most sense to keep.