Core namespace for compiling and decompiling WASM binaries.

Mentions the [BinF library](https://github.com/helins/binf.cljc).

See README.

Soberly defines binary values described in the WASM binary specifications
such as opcodes.

Given WASM items described in Clojure data structures, computes their size in bytes.

This namespace is used before compilation for pre-computing how much memory to allocate
while recomputing indices so they fit in dense lists.

Everything is computed in a map that is being assoc'ed in the `ctx` at `:wasm/write`.

See README for namespace organization and naming scheme.

Provides helpers for working with the intermediary representation (WASM binaries
expressed as Clojure data structures).

Directly relates to the [[helins.wasm.schema]] namespace.

Once again, names ending with the ' character relates to "non-terminal" symbols
from the WASM binary specification and can be found in the registry :as `:wasm/XXX`.

For instance, [[globaltype']] can used for creating a map describing a global variable
as defined by `:wasm/globaltype` in the registry.

See README.

Reading data from a WASM module represented as a BinF view. In other words, decompilation.

Unless one wants to design a custom module parsing environment, ultimately, one should use the `decompile` function
from the `helins.wasm` namespace which does all the job for decompiling a whole WASM module.

See README for namespace organization and naming scheme.

See [[registry]].

Writing a WASM module represented as Clojure data structures to a BinF view.
In other words, compilation.

Unless one wants to design a custom module compilation environment, ultimately, one should use the `compile` function
from the `helins.wasm` namespace which does all the job for compiling a whole WASM module.

For writing sections, things must be prepared with the [[helins.wasm.count]] namespace.

See README for namespace organization and naming scheme.