rusty_lr_parser 3.62.0

grammar line parser for rusty_lr
Documentation

rusty_lr

crates.io docs.rs

A Bison-like parser generator & compiler frontend for Rust supporting IELR(1), LALR(1) parser tables, with deterministic LR and non-deterministic LR (GLR) parsing.

RustyLR is a parser generator that converts context-free grammars into IELR(1)/LALR(1) tables with deterministic LR and non-deterministic GLR parsing strategies. It supports custom reduce actions in Rust, with beautiful diagnostics. Highly inspired by tools like bison, it uses a similar syntax while integrating seamlessly with Rust's ecosystem. It constructs optimized state machines, ensuring efficient and reliable parsing.

title

Features

  • Custom Reduce Actions: Define custom actions in Rust, allowing you to build custom data structures easily.
  • Automatic Optimization: Reduces parser table size and improves performance by grouping terminals with identical behavior across parser states.
  • Multiple Parsing Strategies: Supports minimal-LR(1), LALR(1) parser tables, and GLR parsing strategy.
  • Detailed Diagnostics: Detects grammar conflicts, verbose conflict resolution stages, and optimization stages.
  • Static & Runtime Conflict Resolution: Provides mechanisms to resolve conflicts at compile time or runtime.
  • Location Tracking: Tracks the location of every token in the parse tree, useful for error reporting and debugging.

Installation & Usage

Add RustyLR to your Cargo.toml:

[dependencies]
rusty_lr = "..."

To work with rusty_lr, you need to generate parser code using one of the following methods:

  • Executable: Use the standalone rustylr executable to generate parser code 
    cargo install rustylr
  • Build script: Enable the build feature and generate parser code during the build process 
    [build-dependencies]
rusty_lr = { version = "...", features = ["build"] }
  • Procedural macros: Use the built-in lr1! macro

Recommendation: Use the rustylr executable. It's faster and provides helpful grammar diagnostics, and commands for debugging state machines directly.

Important: Ensure the version of the generated code targets the same version of rusty_lr in your Cargo.toml. Otherwise, you may encounter build errors.

Using Procedural Macros

Define your grammar using the lr1! macro:

// This defines an `EParser` struct where `E` is the start symbol
pub enum MyToken {
   Num(i32),
   Op(char),
   Whitespace(char),
}

lr1! {
   %userdata i32;              // User data type passed to parser
   %tokentype MyToken;         // Token type; sequence of tokens fed to parser
   %start E;                   // Start symbol; this is the final value of parser

   // Token definitions
   %token num  MyToken::Num(_);
   %token plus MyToken::Op('+');
   %token star MyToken::Op('*');
   %token ws   MyToken::Whitespace(_);

   // Left reduction for '+' and '*'
   // Operator precedence: '*' > '+'
   %left plus;
   %left star;

   // ================= Production Rules =================
   Number(i32)                  // Production rule `Number` holds `i32` value
       : ws* num ws*            // `Number` is one `num` surrounded by zero or more whitespaces
       { 
           // Extract the numeric value from the first token
           if let MyToken::Num(value) = num {
               value
           } else {
               println!("Error at: {:?}", @num); // location of the token
               0
           }
       };

   // Binary operator
   BinOp(MyToken): plus | star ;

   // Expression rules
   E(f32): E BinOp e2=E { 
       match BinOp {
           MyToken::Op('+') => E + e2,  // Handle addition
           MyToken::Op('*') => E * e2,  // Handle multiplication
           _ => {
               println!("Unexpected operator: {:?}", @BinOp); // location of the operator
               0.0 // Default value for unexpected operators
           }
       }
   }
   | E error e2=E {
       println!("Expected '+' or '*' at {:?}", @error); // location of the error token
       0.0
   }
   | Number { Number as f32 }           // Number is `i32`, so cast to `f32`
   ;
}

This defines a simple arithmetic expression parser that can handle expressions like 2 + 3 * 4.

Using Build Script

For complex grammars, you can use a build script to generate the parser. This approach provides more detailed error messages when conflicts occur.

1. Create a grammar file (e.g., src/parser.rs) with the following content:

// Rust code: `use` statements and type definitions
use std::collections::HashMap;

pub enum MyToken {
    Identifier(String),
    Number(i32),
    // ... other token types
}

%% // Grammar definition starts here

%tokentype MyToken;
%start E;

%token id MyToken::Identifier(_);
%token num MyToken::Number(_);

E: id
 | num
 ;

2. Set up build.rs:

// build.rs
use rusty_lr::build;

fn main() {
    println!("cargo::rerun-if-changed=src/parser.rs");

    let output = format!("{}/parser.rs", std::env::var("OUT_DIR").unwrap());
    build::Builder::new()
        .file("src/parser.rs")     // Path to the input grammar file
        .build(&output);           // Path to the generated output file
}

3. Include the generated source code:

include!(concat!(env!("OUT_DIR"), "/parser.rs"));

4. Use the parser in your code:

let parser = parser::EParser::new();        // Create <StartSymbol>Parser instance
let mut context = parser::EContext::new();  // Create <StartSymbol>Context instance
let mut userdata: i32 = 0;

for token in tokens {
    match context.feed(&parser, token, &mut userdata) {
        Ok(_) => {}
        Err(e) => {
            eprintln!("Parse error: {}", e);
            return;
        }
    }
}

// Get the final parsed result
let result: i32 = context.accept(&parser).unwrap();

Using the rustylr Executable

crates.io

cargo install rustylr
rustylr input_grammar.rs output_parser.rs

See the Executable Documentation for more details.

Generated Code Structure

The generated code will include several structs and enums:

  • <Start>Parser: A struct that holds the parser table. (LR docs) (GLR docs)
  • <Start>Context: A struct that maintains the current parsing state and symbol values. (LR docs) (GLR docs)
  • <Start>State: A type representing a parser state and its associated table.
  • <Start>Rule: A type representing a production rule. (docs)
  • <Start>NonTerminals: An enum representing all non-terminal symbols in the grammar. (docs)

Working with Context

You can also get contextual information from the <Start>Context struct:

let mut context = <Start>Context::new();

// ... parsing ...

context.expected_token();    // Get expected (terminal, non-terminal) symbols for current state
context.can_feed(&term);     // Check if a terminal symbol can be fed
context.trace();             // Get all `%trace` non-terminals currently being parsed
println!("{}", context.backtrace()); // Print backtrace of the parser state
println!("{}", context);     // Print tree structure of the parser state (`tree` feature)

The Feed Method

The generated code includes a feed method that processes tokens:

context.feed(&parser, term, &mut userdata); // Feed a terminal symbol and update the state machine
context.feed_location(&parser, term, &mut userdata, term_location); // Feed a terminal symbol with location tracking

This method returns Ok(()) if the token was successfully parsed, or an Err if there was an error.

Note: The actual method signatures differ slightly when building a GLR parser.

GLR Parsing

RustyLR offers built-in support for Generalized LR (GLR) parsing, enabling it to handle ambiguous or nondeterministic grammars that traditional LR(1) or LALR(1) parsers cannot process. See GLR.md for details.

Error Handling and Conflict Resolution

RustyLR provides multiple mechanisms for handling semantic errors and resolving conflicts during parsing:

  • Panic Mode Error Recovery: Use the error token for panic-mode error recovery
  • Operator Precedence: Set precedence with %left, %right, %precedence for terminals
  • Reduce Rule Priority: Set priority with %dprec for production rules
  • Runtime Errors: Return Err from reduce actions to handle semantic errors

See SYNTAX.md - Resolving Conflicts for detailed information.

Location Tracking

Track the location of tokens and non-terminals for better error reporting and debugging:

Expr: exp1=Expr '+' exp2=Expr {
    println!("Location of exp1: {:?}", @exp1);
    println!("Location of exp2: {:?}", @exp2);
    println!("Location of this expression: {:?}", @$); // @$ is the location of the non-terminal itself
    exp1 + exp2
}
| Expr error Expr {
    println!("Error at: {:?}", @error); // @error is the location of the error token
    0 // Return a default value
}

See SYNTAX.md - Location Tracking for detailed information.

Examples

Cargo Features

  • build: Enables build script tools for generating parsers at compile time.
  • tree: Enables automatic syntax tree construction for debugging purposes. Makes Context implement Display for pretty-printing.

Grammar Syntax

RustyLR's grammar syntax is inspired by traditional Yacc/Bison formats. See SYNTAX.md for detailed grammar definition syntax.

Contributing

Contributions are welcome! Please feel free to open an issue or submit a pull request.

Project Structure

This project is organized as a Cargo workspace with the following crates:

  • rusty_lr/: The main end-user library that provides the public API. This is what users add to their Cargo.toml.
  • rusty_lr_core/: Core parsing engine containing the fundamental data structures, algorithms, and runtime components for both deterministic (src/parser/deterministic) and non-deterministic (src/parser/nondeterministic) parsing.
  • rusty_lr_parser/: The main code generation engine that parses RustyLR's grammar syntax, builds parser tables, and generates the actual parser code. This is the core of the parser generation process.
  • rusty_lr_derive/: Procedural macro interface that wraps rusty_lr_parser to provide the lr1! macro for inline grammar definitions.
  • rusty_lr_buildscript/: Build script interface that wraps rusty_lr_parser for generating parser code at compile time when using the build feature.
  • rusty_lr_executable/: Standalone rustylr executable for command-line parser generation.
  • scripts/: Development and testing scripts

The crates have the following dependency relationships:

  • rusty_lr depends on rusty_lr_core, rusty_lr_derive, and rusty_lr_buildscript (optional)
  • rusty_lr_derive and rusty_lr_buildscript depend on rusty_lr_parser
  • rusty_lr_parser depends on rusty_lr_core
  • rusty_lr_executable depends on rusty_lr_buildscript

About the Versioning

RustyLR consists of two big parts:

  • executable (rustylr), the code generator
  • runtime (rusty_lr), the main library

Since the cargo automatically uses the latest patch in major.minor.patch version of a crate, we increase the patch number only if the generated code is compatible with the runtime. That is, for any user who is not using buildscript or proc-macro, and using the executable-generated code itself, any code change that could make compile errors with the previous generated code will result in a minor version bump.

License

This project is dual-licensed under either of the following licenses, at your option: