On Tue, Oct 05, 2010 at 02:50:14PM -0400, Sterling Clover wrote:
That said, while most of the changes in Text make perfect sense for a character based rather than text based API, and most make sense to move to bytestring, there are the few ones which are pure taste.
Those are, particularly, break vs. breakBy vs. breakSubstring, and find vs. findBy, and span vs. spanBy.
In all those cases, there's an argument that Text makes the "common case" the short one, and this is good. However, break, span, and find are all part of my standard haskell vocabulary. I know their types from Data.List, use them frequently, and think with them. At this point, to change what they mean would lead to a fair amount of frustration and irritation.
On a scan through Data.Text, it seems the only incompatibilities with Data.List are breakBy vs break, findBy vs find, partitionBy vs partition and spanBy vs span. In each of these cases bytestring agrees with Data.List, and I'd agree that text should too.