High-level expression.Systems-level control.
Prismio combines modern static abstraction with explicit systems boundaries: native code, visible mutability, direct foreign calls, specialized generics, and programmer-directed layout where it matters.
Modern types, specialized at compile time
Structs, recursive enums, pattern matching, closures, overloaded methods, bounded generics, traits, associated types, default methods, impl Trait, and explicit dyn Trait objects are part of the shipped language surface.
Generic functions and types are specialized for the concrete programs that use them. Storing or returning a closure is not supported yet.
Async code and ownership-aware concurrency
An async fn returns a Future<T> and await runs it. scope { } and spawn { } start tasks that must finish before the scope ends. Typed blocking Channel<T> values move messages between workers, while c.share() makes endpoint sharing explicit.
A task is still a native OS thread, and await blocks its thread when the task runs elsewhere. There are no mutexes and no work-stealing executor yet.
Layout control for real hot loops
Flat values can live inline inside Vec<T>, and Slice<T> provides bounded views. Experimental soa and aos conversions give explicit structure-of-arrays access through checked DataView<T>. Int<N> and UInt<N> are integers of exactly N bits.
The compiler specializes the element type before choosing its container representation.
Down to the metal
A freestanding build links no C library and no startup files, so a kernel or a boot image can be written in Prismio. std.syscall reaches the kernel directly, linux { }, macos { } and windows { } blocks choose code per target, and sizeOf and offsetOf match C’s layouts.
A freestanding program supplies its own allocator. Modules that need an operating system, such as std.fs and std.process, are not available.
A small, explicit standard surface
Strings, vectors, maps, sets, optionals, results, iterators, files, processes, JSON, ordering, and equality live in ordinary std.* modules, apart from a small built-in core such as Vec’s push and indexing. There is no prelude pulling unused facilities into a program.
Import only the behavior the program intends to carry.