ekmett/parsers

Issues

• Applicative Permutation?

  #87 opened 2 years ago by Zemyla
  0

• notFollowedBy is a no-op for attoparsec and yoctoparsec, say

  #85 opened 3 years ago by tscholak
  5

• Move notFollowedBy to LookAheadParsing?

  #76 opened 6 years ago by acertain
  2

• Parsing with source locations

  #84 opened 4 years ago by robrix
  1

• double and scientific don't parse negatives

  #81 opened 4 years ago by imuli
  1

• Is there suppose to be two nested `token` calls here?

  #83 opened 4 years ago by twhitehead
  0

• Dead link in package description

  #78 opened 5 years ago by hesiod
  0

• Incorrect implementation of someSpace for Unlined in Text.Parser.Token.

  #77 opened 5 years ago by alexandervandenbroucke
  0

• Building tests via cabal fails when adding dependencies hspec and trifecta

  #73 opened 6 years ago by freeman42x
  4

• No instance for (Text.Parser.Combinators.Parsing Parser) arising from a use of `unexpected'

  #72 opened 6 years ago by freeman42x
  1

• Runtime crash caused by permutation parsing with Optimization flag

  #16 opened 6 years ago by konn
  3

• Feature request: instances for more parsing libraries

  #57 opened 6 years ago by polux
  3

• Feature Request: case-insensitive string match

  #32 opened 10 years ago by aycanirican
  5

• Intermittent QuickCheck test failures

  #68 opened 7 years ago by RyanGlScott
  2

• Approximate matching combinators (missing?)

  #58 opened 8 years ago by alexanderkjeldaas
  1

• `natural` parser parses 0

  #56 opened 7 years ago by simonyangme
  3

• T.P.Expression should be able to handle chained postfix operators

  #26 opened 10 years ago by MostAwesomeDude
  3

• new parsers not on hackage..

  #63 opened 8 years ago by mimi1vx
  5

• buildExpressionParser Error Messages

  #62 opened 8 years ago by Chobbes
  0

• Test run failure

  #47 opened 9 years ago by snoyberg
  1

• Provide token parsers that return Scientific values instead of Doubles

  #33 opened 9 years ago by patrickt
  1

• Package description insufficient

  #43 opened 9 years ago by nomeata
  0

• Wrong example

  #45 opened 9 years ago by wdanilo
  1

• Parsing an out-of-range character literal throws an exception

  #48 opened 9 years ago by Melvar
  1

• parsers on hackage does not allow does not allow attoparsec 0.12

  #40 opened 10 years ago by onsails
  7

• parsers 0.11.0.2 doesn't compile

  #39 opened 10 years ago by peti
  2

• Compilation errors with latest updates (attoparsec?)

  #37 opened 10 years ago by nslo
  8

• Widen deps to allow use of new attoparsec

  #36 opened 10 years ago by bos
  1

• Add flag description

  #27 opened 10 years ago
  2

• Text.Parser.Char.lower documentation excludes lowercase Unicode characters outside of ASCII

  #29 opened 10 years ago by shlevy
  1

• Generalize highlighting

  #25 opened 11 years ago by pthariensflame
  7

• Expression parser just doesn't work at all

  #24 opened 11 years ago by konn
  7

• Instances for ReadP?

  #17 opened 11 years ago by ekmett
  0

• commaSep1 does not parse one-or-more, it parses zero-or-more

  #10 opened 11 years ago by ocharles
  1

• attoparsec doesn't support lookAhead

  #4 opened 11 years ago by ekmett
  1

• Allow overlap between prefix and term in buildExpressionParser?

  #5 opened 12 years ago by nwf
  1

• Suggestion for a different interface for permutations.

  #1 opened 12 years ago by sjoerdvisscher
  2

• Remove or move the MonadPlus constraint.

  #2 opened 12 years ago by sjoerdvisscher
  2