VOID Language roadmap.
A clear direction.

A working language and native runtime.

The compiler uses C++20 and LLVM 19.1.7, with one shared JIT/AOT pipeline for native execution and object output. Static types, value structs, managed objects, collections, generics, structural interfaces, results and pattern matching are part of the working language.

The runtime supports tracing garbage collection, deterministic resource cleanup, cooperative async/await, structured task groups and a restricted value-transfer subset for bounded native workers. These are distinct mechanisms with their own lifetime and safety boundaries.

Trusted, statically linked native bindings and compatible function replacement exist within explicit host integration. General native-library loading and automatic save-triggered reload are separate future goals.

Make everyday development better.

Current priorities include compiler optimization, readable diagnostics, usability, compatibility and the build, testing and distribution infrastructure needed for dependable development.

The compiler-owned language server now implements completion, hover, signature help, definitions and references, document/workspace symbols, guarded rename and conservative formatting. VS Code, Neovim and Vim integrations have local Linux execution evidence; Vim rename remains disabled. VSCodium execution, new Windows/macOS editor combinations and clean-machine readiness remain unverified, and hosted cross-platform acceptance is pending.

Local implementation and checks do not establish a public release or general platform certification. There are no public compiler or editor builds available here yet.

A broader ecosystem. A smoother flow.

Longer-term goals include a useful standard library, package management and discovery, and broader native-library integration through typed VOID wrappers.

Automatic file watching and compatible save-triggered function replacement aim to improve live development without forcing restarts. A more complete editor experience and broader verified portability remain part of that direction. These goals are not claims of currently available packages, commands or releases.