Issue #10 resolved

funtion "many" clashes

Anonymous avatarAnonymous created an issue
$ ghci
GHCi, version 7.0.4:  :? for help
Prelude> :m + Control.Applicative Data.Attoparsec
Prelude Control.Applicative Data.Attoparsec> :t many

    Ambiguous occurrence `many'
    It could refer to either `Control.Applicative.many',
                             imported from Control.Applicative
                          or `Data.Attoparsec.many', imported from Data.Attoparsec

Both Control.Applicative.many and Data.Attoparsec.many seem to share a common definition: Their type signatures are identical, and the behavior is also the same. Then GHCi shouldn't be complaining about ambiguity, unless they are unnecessarily defined separately.

As Attoparsec does not ship with all the Alternative convenience funtions (<|>, optional, etc.), Applicative and Attoparsec should be importable at the same time, without any need to qualify the import or hide certain names.

Comments (1)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.