1 unstable release
0.1.0 | Jul 12, 2023 |
---|
#847 in Programming languages
180 downloads per month
Used in 5 crates
(via air-parser)
21KB
382 lines
miden-parsing
This crate provides additional infrastructure on top of miden-diagnostics for parsing within a compiler frontend.
Features
The following are features provided by this crate:
- An abstraction called
Source
that provides the core operations required by the scanner component of a parser, along with a "standard" implementation calledFileMapSource
which builds on theSourceFile
type provided bymiden-diagnostics
Scanner
, a low-level component intended for consumption from a lexer. At a high level, the scanner operates on the input source to allow a lexer to precisely control what characters in the source are part of the current token, the ability to get a slice associated with the current token, as well as the ability to control advancement of the underlying source stream (i.e. get the current char, pop the current char, peek the next char, etc).Parse<T>
a trait which describes what is needed to parse aT
, and exposes the API for doing soParser<C>
represents a parser with a configuration typeC
that is capable of parsing any compatibleParse
implementation. This parser is designed for use with components provided bymiden-diagnostics
, specificallyCodeMap
andDiagnosticsHandler
. It abstracts away some of the boilerplate involved with common parsing tasks, e.g.parse_file
andparse_string
.
This crate is known to work well with LALRPOP, and only requires that a compiler frontend provide a lexer
and token type specific to the language being parsed. See the examples
folder for a complete end-to-end
demonstration of how to use this crate (and miden-diagnostics
) with LALRPOP for a simple language.
Dependencies
~3–10MB
~100K SLoC