<div dir="ltr">On Mon, Mar 26, 2012 at 13:12, Ian Lynagh <span dir="ltr"><<a href="mailto:igloo@earth.li">igloo@earth.li</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":tv">Maybe your point is that neither "take" function should be used with<br>
unicode strings, but I don't see how advocating the Text type is going<br>
to help with that.</div></blockquote></div><br>I think we established earlier that the list-like operations on Text are a backward compatibility wart. Either they should go away, or they should be modified to operate on some other level than codepoints. Probably the way the ecosystem should work is that [Char] (or possibly a packed version thereof, sort of like lazy ByteStrings with Word32 instead of Word8 as the fundamental unit) is the codepoint view and Text is the grapheme view; both are necessary at various times, but the grapheme view is the more natural one for text /per se/.<div>
<div><br></div>-- <br>brandon s allbery <a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a><br>wandering unix systems administrator (available) (412) 475-9364 vm/sms<br>
<br>
</div></div>