Crate elly_host 

What every Elly embedder wants and elly-core does not have to know about: the official file-system module resolver (FsResolver), the IO capability modules (io), and running a program’s __main against them (Io::run). See docs/done/2026-10-02_elly-host.md.

Everything that touches the outside world goes through Sys, so a host without a real OS (the wasm playground) can supply its own. StdSys is the one std implementation, for native targets and wasm32-wasip1.

Structs

FsResolver

Io

The built capability, plus the one thing about it a runner has to recognize.

StdSys

Sys over the standard library.

Enums

Run

How running a program’s __main against IO ended.

Stream

Which standard stream a write goes to.

Constants

PATH_VAR

The environment variable holding the search path for a non-relative spec, separated as PATH is on the platform.

Traits

Sys

The system surface a host offers Elly: output, module sources, the environment and the way out. The resolver and IO reach the outside world only through this.

Functions

io

Build IO over sys for a program invoked with args (the arguments after the script).

is_relative_spec

Does spec ask to be resolved against the base directory? Only the two explicit prefixes do; a bare foo/bar is a search-path spec, so which tier answers is visible in the source rather than depending on what happens to exist on disk.

search_path

The directories in ELLY_PATH, in order.