Expand description
Polytile at the host boundary (SRD 114 §5.6): build a tile from
template text, from structural JSON text, or from a parsed JSON
value, then compile it with a program via
tile::compile_polydat_with_tiles.
Re-exports§
pub use crate::dsl::compile::compile_polydat_kernel_with_tiles;pub use crate::dsl::compile::compile_polydat_with_tiles;
Structs§
- Span
- A source location for error reporting.
- TileDef
- A tile definition: its header, its raw body, and the parsed template.
- Tile
Options - Per-tile template options (SRD 114 §2.3): the hole delimiters, the directive sigil, and strictness.
Enums§
- Tile
Body Kind - How a tile body was written, so the printer can reproduce it.
- Tile
Piece - One element of a parsed template.
Constants§
- ENCODINGS
- The encodings a tile may declare.
Functions§
- parse_
template - Parse a tile body into pieces under
opts.spanis the tile statement’s position, used for diagnostics. - render_
template - Render pieces back to template text under
opts, the inverse ofparse_templateup to whitespace inside directives. - template_
text_ from_ value - Turn a structural template into template text under
options. The text is what an author would have written in atile ... : jsonblock for the same document. - tile_
from_ json_ text - A tile from a structural template in JSON text (§3). The encoding is
json. - tile_
from_ json_ value - A tile from a structural template a host has already parsed (§3).
The encoding is
json. - tile_
from_ text - A tile from template text a host holds: the body of a
tilestatement without the statement.textmay be multi-line; it is taken exactly, as a heredoc body is.