mapM_ for bytestring

Edward Kmett ekmett at
Sun Sep 1 23:42:12 CEST 2013

Personally, I would support its inclusion.

It is an annoying repetition -- but then so is the entire bytestring API --
so there is no real point in just randomly omitting this one combinator.


On Sun, Sep 1, 2013 at 6:58 AM, Artyom Kazak <yom at> wrote:

> Would this be an appropriate place to propose adding mapM_ (and then
> possibly mapM) to bytestring library?
> Was it suggested before? If yes, why was it rejected?
> ______________________________**_________________
> Libraries mailing list
> Libraries at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Libraries mailing list