-
Hi there,
I was trying to use nom-recursive to pass path expressions like "expr.field.field.field". I couldn't get it working, so I tried making a minimal change to the example program and ran into…
-
Currently, the `pest` parser generates an AST, which is actually a HashMap of `NodeIndex` chains.
The `NodeIndex` is calculated in the process of parsing.
```let node_index = graph.add_node(MyNo…
-
Right now, `nom` has distinct types for complete and streaming parsers.
Problems with this
- Requires duplicate module hierarchies (#1414 would move them around)
- Can't provide convenience imple…
-
It could be really helpful to implement a full example using a simple language like JSON or toml.
https://github.com/Geal/nom/blob/master/examples/json.rs
Originally suggested by @Geal.
-
vimwiki appears to use an older version of `nom` that has a future-incompat warning. I see this when building cobalt.
If open to alternatives to `nom`, I can offer my biased opinion that [winnow](…
-
As far as I can tell, some nom parsers (like `re_find!`) aren't generic enough, and must accept `&str` input. This means you can't pass them a `LocatedSpan`.
It would be nice if there were a functi…
-
*placeholder for now, there is no plan*
some ideas for now:
- naming issues: some combinators still have unclear names, a major version is a good occasion to clean them out
- integrating bitvec
…
-
One of the common use cases of streams are streamable parsers.
I recently started porting my parser in js to streams, and started looking into streamable parsers in Rust. It seems that both nom and…
-
# I'll let you find a nice crate name :)
## Description
(original idea from @jtanguy)
This is a library, written in Rust, compiled to webasm (so it can be called from Javascript code),
that …
-
## Prerequisites
- Rust version : `rustc 1.62.1 (e092d0b6b 2022-07-16)`
- nom version : `7.1.1`
- nom compilation features used: none
## The problem
Sometimes, a custom input type is necess…