More deeply, it doesn’t suffice to guarantee you’re gonna have a well formed unicode sequence! 

It’d need to be grapheme -> text -> text  right?

I’ve def wanted to dig into how to make programming more grapheme oriented for text at some point.  I think swift explcitly does this in their standard libraries ?

On Sun, Jun 27, 2021 at 1:37 AM Ivan Lazar Miljenovic <ivan.miljenovic@gmail.com> wrote:
On Sun, 27 Jun 2021 at 12:44, Andreas Abel <andreas.abel@ifi.lmu.de> wrote:
 > `intersperse :: Char -> Text -> Text`

Yeah, that looks silly indeed.  Should be pruned or marked as spam.

"Spam" is a bit harsh.  And it does indeed have some use (albeit primarily with test suites and quite possibly more efficient ways to do the required task anyway): https://github.com/search?l=Haskell&q=Text.intersperse&type=Code

 

On 2021-06-27 01:33, Andrew Lelechenko wrote:
> I know applications for `intercalate :: Text -> [Text] -> Text`: `unwords`, `unlines`, etc. But what is `intersperse :: Char -> Text -> Text` good for? Am I correct assuming that its sole merit is to mimic `Data.List` API? Note that `Data.List.intersperse` is polymorphic and is exceedingly rarely used for `Char -> String -> String`.
>
> Best regards,
> Andrew
> _______________________________________________
> Libraries mailing list
> Libraries@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
_______________________________________________
Libraries mailing list
Libraries@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries


--
Ivan Lazar Miljenovic
Ivan.Miljenovic@gmail.com
http://IvanMiljenovic.wordpress.com
_______________________________________________
Libraries mailing list
Libraries@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries