Playground¶
Every ASCII datatype, every registered code, every refusal, and a declared vocabulary, as the package itself answered them.
Nothing on this page is computed in your browser. The JavaScript extension is a native Node addon,
so a browser cannot load it, and a documentation page may not reimplement what the package does. So
the outputs are generated: scripts/build_docs_playground.js runs the real package over a fixed
corpus and writes assets/playground.json, which is committed and checked for drift in CI; this
page fetches that manifest and renders it. A browser build would need a WebAssembly target of the
node crate that does not exist, and could not carry Parquet or Iceberg, so it is not offered here.
The contract these values prove is on the datatype page; this page is the same contract with every case laid out. To try a value of your own, add it to the corpus in the generator and rerun it:
The ASCII datatypes and the codes¶
This section renders assets/playground.json and needs JavaScript.
Encode: text into storage¶
This section renders assets/playground.json and needs JavaScript.
Decode: storage into text¶
This section renders assets/playground.json and needs JavaScript.
A declared vocabulary¶
This section renders assets/playground.json and needs JavaScript.
A member is the integer its ASCII value packs into - the value's own storage bytes, big-endian - so the code is the same in every process and in every declaration, never a position in some column's vocabulary. The declaration itself rides on the field under one reserved metadata key, so it crosses Arrow, a file, and another runtime beside the datatype's own identity.
Look up a value¶
This section renders assets/playground.json and needs JavaScript.