for example rule's
a and b require that rule c matches too but I want to silence c when matching a but I not in b
Hi there, I'm seeing this strange message when trying to use the & behavior: https://pest.rs/?bin=1bsukd#editor
Is this a pest bug or just a confusing error message?
Is this a pest bug or just a confusing error message?
(and, if i'm doing it wrong, what would be the standard way to exclude a list of specified keywords from the space of identifiers? I feel like that must be a pretty common thing to have to do)
have a rule that matches all identifiers without discrimination, then just pair it as
!keyword ~ raw_ident
If you want to allow identifiers to resemble keywords see
True being a keyword and True_ being a valid identifier then filter a valid keyword by excluding any matches that are followed by another rule such as ASCII_ALPHA | "_"
you may want to silence the
raw_ident rule in that example
Has anyone got an idea on where the issue in pest-parser/pest#402 could be? Is there a way to output a generated parser as a valid Rust file?
I might have time to create a testcase at least though, where should it be?
Hi! I have written a grammar for the R language and while testing it with a real world code file, I noticed that nested if statements make the parser run noticably slow. I'm not surprised that this happens, it feels like exponential complexity growth, but I was wondering whether I could do some improvements to my grammar. I've no previous experience with parsers nor PEGs.
If you'd like to have a look, I've created a bin at https://pest.rs/?bin=10fbo7#editor. You can copy and paste more
while (TRUE) to the end of the file to get a feel for when it starts to become slow. (It takes a lot of nestings! :) )
By the way, pest is pretty awesome, no performance issues whatsoever except for this excessive nesting! Really cool!
Finally
it's matching 2 lines, but not 3
nvm missing '%' in my rules
amazing
Hi. I'm trying to fix #407 on my own, but some tests(75 out of 450) fails with initial clone setup. But travis seems good with latest commit. Did I do something wrong?
I did
git clone github.com/pest-parser/pest --recursive, cargo bootstrap, cargo test with stable-x86_64-pc-windows-gnu toolchain.
@cr0sh : trying here, will tell you asap if it fails the same way (linux)
@cr0sh : worked like a charm here, just a couple tests ignored, no fail.
Is there a plan for releasing a new version?