REPL
Riot does not expose a full top-level REPL workflow yet, but the page belongs in the toolchain now.
That is intentional.
Why keep a placeholder
Section titled “Why keep a placeholder”A serious language toolchain eventually wants an interactive story for:
- exploration
- examples
- debugging
- trying APIs without scaffolding a whole binary first
Even before the feature exists, the docs should reserve that conceptual space.
What a Riot REPL should eventually do
Section titled “What a Riot REPL should eventually do”At minimum, a good Riot-aware REPL would:
- understand the workspace context
- load package code in a predictable way
- let users experiment without losing the package-oriented mental model
That is different from a generic OCaml shell. The value would be that the REPL understands Riot’s workspace and package story.
Until that exists, treat this page as a marker for product direction rather than a finished workflow.