What's Next
You've covered the core language available in Miri v0.6.0-beta.4. The headline of this release is the
extended standard library: system.fs, system.os and
system.time for capability-scoped access to the outside world, regular expressions in
system.text, a pure-Miri JSON parser in system.json, and Queue and
Stack — together with a closed attribute set, the native miri test runner, and
memory diagnostics that keep the whole library provably leak-free.
Nothing in that library panics, and none of it hands back a sentinel: index_of returns
int? rather than -1, and pop and remove_at return
T? rather than trapping. The absent case is always a value you handle.
The GPU preview from the previous release is unchanged and still current: device-resident
bindings (gpu let / gpu var), forall kernels, on-device reduction,
shared memory, atomics, warp operations, vector types, and interactive gpu frame programs that
compile to the browser via WebGPU — with no shader files and no FFI.
Continue with the GPU Programming guide — it starts from your first kernel and assumes no GPU background — or see the programs running live in the GPU Playground.
Here's what's coming next:
- Future milestones — Trait objects, capture-by-reference closures, async/await and
async gpustreams, channel-based concurrency, and additional GPU backends behind the sameforallsurface, starting with a native SPIR-V / Vulkan path
More resources:
- Explore the test suite for more code examples
- Star the project on GitHub and follow development
- Check the issue tracker for the roadmap
Miri is evolving fast. Trait objects, async, and the native GPU backends are actively being designed. Join us on GitHub to shape the language!