plsql-parser 0.1.0

PL/SQL parser frontend: ParseBackend trait, token tape, CST, AST types

Coverage
63.52%
155 out of 244 items documented1 out of 67 items with examples
Size
Source code size: 123.62 kB This is the summed size of all the files inside the crates.io package for this release.
Documentation size: 3.59 MB This is the summed size of all files generated by rustdoc for all configured targets
Ø build duration
this release: 15s Average build duration of successful builds.
all releases: 15s Average build duration of successful builds in releases after 2024-10-23.
Links
Homepage
MuhDur/plsql-intelligence
2 0 0
crates.io
Dependencies
Versions
- 0.1.0 (2026-06-28)
Owners

PL/SQL parser frontend.

This crate defines the backend-independent parsing API that all downstream crates consume. No ANTLR-generated types or grammar rule names escape this boundary (R2 / R20).

Design

A [ParseBackend] implementation converts raw source text into a [BackendParseResult] containing the lossless token tape, a CST (concrete syntax tree), and a typed AST (abstract syntax tree).

The public [parse_file] / [parse_with_backend] functions wrap [BackendParseResult] into a [ParseResult] that pairs the output with the originating [FileId].

Lossless contract

The token tape is the source of truth for round-tripping. Every token and trivia element carries a byte-offset span. The AST is a semantic projection — it is NOT required to preserve whitespace or comments.