The GameLisp interpreter.
Runtime owns all of the data required to run GameLisp code: a set of global variables,
a symbol table, a set of registered Rust functions, and much more.
To manipulate the GameLisp runtime, you don't call methods on the
Runtime type directly.
Instead, use the
run method to establish a particular
Runtime as the
"active runtime", then use this crate's global functions and methods to interact with the
If you attempt to execute any GameLisp-related code without an active runtime, it will almost always panic.
It's possible for multiple
Runtimes to coexist. Each runtime is strictly isolated from the
others - they don't share global variables, symbols, and so on. This means that it's possible
to run GameLisp code in isolated
Runtimes on multiple threads without needing any
Runtime with default settings.
To construct a custom
impl !RefUnwindSafe for Runtime
impl !UnwindSafe for Runtime
type Error = Infallible
The type returned in the event of a conversion error.