Expand description
§What this top-level crate does
This crate provides an abstraction layer over both the interpreter and the compile-time template compiler, allowing to switch between them at will in a project (or more likely: use the hot-reloadable interpreter in development and the high-performance compiler for production).
Currently this crate only supports interpreted mode.
Macros§
- initialise_
template_ manager - On startup, must be called with the identifier of the manager. Note that the manager uses lazy_static! and thus must be initialised without any potential for thread races!
- interpreter_
params - interpreter_
setters - lazy_
static - make_
template_ manager - Makes a template manager. The syntax within the macro resembles a static ref binding so that the effect of the macro is more obvious…
- render_
template_ string
Structs§
Functions§
- is_
hot_ reload_ enabled - new_
template_ manager - INVOKED BY MACRO; don’t use manually (no point).