plex icon indicating copy to clipboard operation
plex copied to clipboard

a parser and lexer generator as a Rust procedural macro

Results 18 plex issues
Sort by recently updated
recently updated
newest added

As the grammar gets large, compile times grow a lot. A grammar similar to C but still a *lot* simpler takes about 2 or 3 minutes to compile and it...

Hello I'm currently taking a lecture in the topic of lexical analyzers where we focus on flex. flex has a thing called [Starting Conditions](https://ftp.gnu.org/old-gnu/Manuals/flex-2.5.4/html_mono/flex.html#TOC11) where you can basically set the...

I started seeing these on the newest rust nightly ``` kai@kai-thinkpad ~/d/plex (master)> cargo test Compiling proc-macro2 v1.0.10 Compiling unicode-xid v0.2.0 Compiling bit-vec v0.4.4 Compiling syn v1.0.17 Compiling vec_map v0.6.0...

Suppose I have this lexical syntax for a token: ``` Identifier ::= * Initial ::= a..z Subsequent ::= Initial | ... ``` Here the `Initial` part is used in both...

Hi! I'm not very familiar with Rust, but very excited by your library. Only my problem is I decided to keep on latest stable Rust. Is it very difficult to...

Automated testing is great! It would probably be a good idea to write some.

Hi, If I add a lifetime to my token enum like in the README, I have a hard time compiling the parser. Essentially I get the following error. ``` error[E0106]:...

I needed to pass an interner to the lexer (to avoid calling `.to_owned()` for idents) but there doesn't seem to be a way to add it to the signature without...

error recovery is important for practical parser, is there any plan that plex will support it? for example, when we are failed to parse a statement, we skip remaining tokens...

Thanks for plex! Would it be feasible to support multiple entry points that reuse the same grammar? As an example, I have something like: ``` statement: Statement { expression[e] TokenSemicolon...