No description
0f453a5568
Instead of a `kind` field containting a `TokenNode` variant, a TokenTree is now an enum with variants of different types (Literal, Op, Term, etc). Note that a TokenTree could be a sequence of TokenTrees if it is a Group variant. Other notes: I'm unsure about the set_span call in Builder::emit_if, but I did not want to throw away the passed in Span. Parsing relies on destructuring references to the values associated with TokenTree enum variants It doesn't seem as easy to compose/chain TokenStreams as it is to collect a Vec<TokenTree> into a TokenStream. There is probably some iterator API I could use instead. See `match_arms` and build.rs Refs #121 |
||
|---|---|---|
| benchmarks | ||
| maud | ||
| maud_extras | ||
| maud_htmlescape | ||
| maud_lints | ||
| maud_macros | ||
| .gitignore | ||
| .travis.yml | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| maud.png | ||
| README.md | ||
| rust-toolchain | ||
maud
Documentation (source) • API reference • Change log
Maud is an HTML template engine for Rust. It's implemented as a macro, html!, which compiles your markup to specialized Rust code. This unique approach makes Maud templates blazing fast, super type-safe, and easy to deploy.
Note that Maud depends on the unstable procedural macro API, and so requires the nightly version of Rust.
For more info on Maud, see the official book.
Stability
As of version 0.11, I am satisfied with the core syntax and semantics of the library. Development at this stage is focused on adding features and fixing bugs.
The underlying procedural macro API is still unstable though, so updating your compiler may break things. Please file an issue when this happens!