Applicative and parsec3

Edward Kmett ekmett at gmail.com
Thu Jan 27 19:59:16 CET 2011


I for one would love to see the (<|>) in Parsec go away and be replaced with
use (and if need-be, possible re-export) of (<|>) from Control.Applicative.

-Edward Kmett

On Thu, Jan 27, 2011 at 1:16 AM, Kazu Yamamoto <kazu at iij.ad.jp> wrote:

> Hello,
>
> I'm using parsec3 with the applicative style. Since the functions in
> Control.Applicative and parsec3 conflicts, I need to use the "hiding"
> keyword as follows:
>
>        import Control.Applicative hiding (many,optional,(<|>))
>        import Text.Parsec
>
> This is inconvenient for me. I would like to use them as follows:
>
>        import Control.Applicative
>        import Text.Parsec
>
> Christian, the maintainer of parsec3, told me that it is possible to
> use the functions of Control.Applicative in parsec3 instead of
> implementing its own functions. But (<|>) of parsec3 is "infixr 1"
> while that of Control.Applicative is "infixl 3".  This may be an
> issue.
>
> Any ideas to solve this issue?
>
> --Kazu
>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20110127/e41c7a48/attachment.htm>


More information about the Libraries mailing list