Discussion: forM for Data.Set

David Feuer david.feuer at gmail.com
Sun Jan 12 23:11:53 UTC 2020

I'm probably around +.25 on traverse and -1 on the rest. I don't want to
clutter up the API too much with different forms of a derived operation
when we don't even have evidence that it'll be used much.

On Thu, Jan 9, 2020, 7:31 PM hasufell at posteo.de <hasufell at posteo.de> wrote:

> This was posted a year ago already, but without many comments:
> https://mail.haskell.org/pipermail/libraries/2019-January/029335.html
> So after cleaning up the PR a bit, adding tests and benchmarks, let's
> give it another go.
> PR is at: https://github.com/haskell/containers/pull/592
> New functions are: forM, mapM, for, traverse
> This follows the other Data.Set exported functions, overwriting Prelude
> ones like foldr etc, so I think that's exactly what we want.
> Cheers,
> Julian Ospald
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20200112/ef2b1b03/attachment.html>

More information about the Libraries mailing list