Issues filed for m4rw3r/chomp

View Full Project
Do you use chomp? Leave a review!

Rate of open issues in the last 60 days

chomp open issues (View Closed Issues)
  • almost 2 years Be able to unwrap Input from InputPosition.
  • almost 2 years Accessing numbering::InputPosition::position via map_err
  • about 2 years Reorganize types
  • about 2 years Improving the `buffer` module
  • about 2 years Non `Copy` `Token`s?
  • over 2 years Implement alternative `parse!` macro using compiler plugin
  • over 2 years Provide alternatives preventing overflow and unbounded parsing
  • almost 3 years Applicative parsing
  • almost 3 years Proper parsers tests and examples for using `&str` as a parse source
  • almost 3 years Attoparsec parsers
  • almost 3 years Adapter for Nom
  • almost 3 years TOML example parser
  • almost 3 years ForEach macro/method/function to make it easier to use Stream

chomp closed issues

  • almost 2 years Use std::str::from_utf8_unchecked instead of std::mem::transmute
  • about 2 years Returning the entire slice matched by a chain of parsers
  • about 2 years HTML extract link parser.
  • about 2 years `impl Trait` and making Chomp require nightly
  • about 2 years More comprehensive examples
  • over 2 years Proper `prelude` module
  • over 2 years Make `Input` a trait
  • over 2 years Update bitflags dependency
  • over 2 years How do I examine success/fail?
  • over 2 years Infinite loop?
  • over 2 years Request: readable str error messages
  • over 2 years Is there a way to get current position?
  • over 2 years `or` fails with incomplete even though second parser could have succeeded on the input
  • over 2 years Maybe use quickcheck to simplify some tests
  • over 2 years Remove type parameter default on functions and methods
  • over 2 years run_scanner state can't depend on last token
  • over 2 years what type of argument to supply for i.err()?
  • over 2 years `or` with many branches
  • almost 3 years Size hint for internal iterator used by `many*` and `count`
  • almost 3 years Debug mode (feature) including backtraces in errors
  • almost 3 years FAQ and help for debugging `parse!` macro
  • almost 3 years `parse!`: Support for typehints for generic functions.
  • almost 3 years Use Humpty Dumpty to verify linearity of `Input` and `ParseResult`
  • almost 3 years Parse utilities
  • almost 3 years Maybe move the core of Chomp into an inner crate?
  • almost 3 years `string` can cause parsing to be slow with `verbose_error`
  • almost 3 years `parse!` does not support inline `map`, `map_err` or `bind` for named actions
  • almost 3 years Remove `unwrap*` and `expect` from `ParseResult`, and `Input::new()`
  • almost 3 years Rename `internal` to something more appropriate
  • almost 3 years Split InputModify and ParseResultModify into more specialized traits
  • almost 3 years Streaming utilities and generalized input management
  • almost 3 years Adapter for working with Result and Option
  • almost 3 years EOF and non-finite parsers