Hi Evan, By the sounds of it regex should help with this – each match operator being available in an un-overloaded format. Does this API work for you? Chris On 2017-03-10, 05:12, "Evan Laforge" <qdunkan@gmail.com> wrote: That's always been my canonical example about how you can overuse typeclasses to make a simple job into an impenetrable documentation hunt. Long ago I wrapped it in a simple API and have always used that. Much later, pcre-heavy showed up and I just switched my wrapper to use that, since it was still a little too typeclass happy for my taste. On Thu, Mar 9, 2017 at 11:06 AM, Chris Dornan <chris@chrisdornan.com> wrote: > Dear Haskell Cafe, > > With the regex announcement, I wanted to try get other folks' perspective > on what has been happening with the Haskell regular expression libraries. > > I have been in turn impressed at how good the engineering of the Regex > packages while gobsmacked by how difficult the traditional Text.Regex API > is to use. > > In this blog post, > > http://engineers.irisconnect.net/posts/2017-03-07-regex.html > > I rather cheekily speculate that the Haskellers perhaps have been a bit > disdainful of regular expressions (not important in a language capable > of doing proper parsing, etc.). > > What do you think? > > Chris > > > > > _______________________________________________ > Haskell-Cafe mailing list > To (un)subscribe, modify options or view archives go to: > http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe > Only members subscribed via the mailman list are allowed to post.