-
This is the tracking issue for ideas discussed with @g2p in #35: can the parser expose the raw bytes for all components?
Maybe a possibility is to use something like [nom-locate](https://github.com…
-
Right now our user query parser and our content-disposition parser use lots of raw pointer manipulation. This is obviously a bad idea.
One example of a parser that is designed to be secure is Nom, fr…
-
While doing prep for #1408, I was bothered by the number of nom::character parsers. A problem is that they do just enough that you'd want more out of them which would be more unwieldily. Before doing …
-
### What?
Write a parser that can read lolcode files and create an AST out of it.
### Why?
Parsing stuff is fun and educational. Also lolcode.
### How?
Probably use nom for that.
-
Thank you for the amazing tool!
I would like to use nix-output-monitor for my local deployments, as they make the output nicer and more understandable.
What would the best way forward to send a …
-
**Describe the bug**
I am currently evaluating the pelias tool for geocoding.
And i am trying to import a CSV dataset containing french adresses.
But the import job interrupts while a double-quot…
-
## Prerequisites
- Rust version: `rustc 1.64.0 (a55dd71d5 2022-09-19)`
- nom version: 7.1.1
- nom compilation features used: `alloc` + `std`
## description of issue
I want to parse somethin…
-
This was impossible to figure out. The top-level parser should be forced to have `Clone` on its types, especially `nom`'s default error type.
-
I'm trying to parse Lua source code, which is not UTF-8 (strings are just bags of bytes). `nom` seems to be mostly compatible with `&[u8]`, but I keep finding that random parts of nom randomly fail to…
-
Get the above error at the point I try and parse anything. The module installed ok passing tests. Any hint on what Im doing wrong or might be going wrong?
`perl6 --version`
This is Rakudo version …