wirelyre

Results 11 comments of wirelyre

Some progress in minimizing. The project builds if two particular `write_bindings` calls are [removed](https://gist.github.com/wirelyre/207acebeb5cbc081c344e053eae58d34) from [`test_no_warnings/build.rs`](https://github.com/brendanzab/gl-rs/blob/10b1987fb0467f85006b100e8bcaad2cf62c673e/tests/test_no_warnings/build.rs). However, the build fails if either of those two calls are present, *even if...

👍 The context-dependent meaning of `~` is troublesome. In some cases, it can even mean different things in a single rule: ``` double_meaning = { "a" ~ "b" } //...

I have to admit that I'm very excited about this RFC, because I think the discussion could potentially make `pest` syntax more consistent *and* easier to learn. In that spirit:...

The OCaml parsing library [`angstrom`](https://opam.ocaml.org/packages/angstrom/) has a primitive called [`commit`](https://github.com/inhabitedtype/angstrom/blob/9f7268946dc3c5c50aa49786e4f74f29270546f0/lib/angstrom.mli#L355-L365), which could be useful inspiration. `commit` indicates that, outside of the usual success–failure–backtrack strategy, if a parse ever reaches that...

Some more brainstorming: There is also the option of making errors more expressive in general. Parsing doesn't just fail at one spot. There are two parts: the context which led...

This is undecidable in general, I suspect. Along [these lines](https://en.wikipedia.org/wiki/Context-free_grammar#Language_disjointness): Use the alphabet {0, 1}. Take two indexed families of nonempty strings {a₁, ⋯ , aₙ} and {b₁, ⋯ ,...

@dragostis The implication is that, for any fuzzer, there exist grammars which will cause it to run forever but never make a single matching string. And it is not possible...

I was wrong. A 2004 article shows how to convert any well-formed PEG (which doesn't admit the empty string) into another one that doesn't use the "predicate operations" `&` or...

Probably a duplicate of #2613.

I'm confused why there's a `conj` function at all. Wouldn't it make more sense to give `[$@list $items...]` the O(m) guarantee? The notation's already there *and* it's shorter to type...