Collections & Utilities
Riot’s toolchain story would be weaker if it stopped at builds and commands.
The standard library matters because users also need day-to-day programming surfaces:
- collections
- text and byte helpers
- time and process utilities
- structured data support
- networking building blocks
This page is a map of that territory.
What this page is for
Section titled “What this page is for”Use this page when you are asking:
- does Riot already have a battery for this?
- which area of the standard library should I inspect first?
- is there already a package-level convention around this problem?
It is not the page for exact signatures. It is the page for orientation.
The big buckets
Section titled “The big buckets”The surfaces most users care about first are:
Beyond those, Riot also includes lower-level utility surfaces that become important as packages get more serious.
Why this matters in the product story
Section titled “Why this matters in the product story”Users adopting Riot are often asking whether it is only a shell around other tools or whether it also offers a coherent programming environment.
The standard library is part of the answer to that question.