Documentation channel: v0.0.5 at compiler commit 2c9c7e8. The latest tagged release is v0.0.5; pages identify APIs that are new in v0.0.5.
Implementation status
This website documents Strut v0.0.5 (compiler commit 2c9c7e8), the current release. The previous release was v0.0.4. Installation commands install the latest tagged release, and the table below shows what each recent release provides.
Stable release and development
| Surface | v0.0.4 | v0.0.5 (latest) |
|---|---|---|
| Language, ownership, checked errors, packages, CLI/LSP | Available | Available |
| HTTP server, TLS, SQLite, buffered outbound HTTP | Available | Available; reactor correctness/robustness fixes |
bytes, Base64/Base64url, crypto | Available | Available |
| Outbound HTTP streaming and cancellation | Available | Available |
| Streaming server requests/responses, persistence, helpers, ranges, NDJSON | Available | Available |
| WebSocket server | Available | Available; reactor dispatch/close/403 parity, saturation 503 |
| WebSocket-to-PTY sessions | Certified as application-level composition; no built-in bridge | Same |
| Hardened process ownership and cancellable pipes | Available | Available |
| PTY | Linux, macOS, and Windows ConPTY | Available |
| Windows ConPTY | Available on Windows 10 1809 / Server 2019 or newer | Available |
| Two-way FFI (exports, native -> Strut, callbacks, checked errors, retained callbacks) | Not released | Available |
| C/host embedding API and language consumers (C, C++, Python, Go, Node.js, C#) | Not released | Available |
| Nift interoperability | Not released | Linux-local evidence |
| Explicit weak ownership for native handles and structs containing them | Not available | Available |
Current-main backend capability
| Capability | Runtime/compiler | Website |
|---|---|---|
| Secure random, SHA-256, HMAC-SHA-256, constant-time compare | Yes | Crypto |
| Strict Base64 and unpadded Base64url | Yes | Crypto |
| Outbound arbitrary methods, binary bodies, limits, redirects, custom CA | Yes | HTTP client |
| Outbound streaming upload/download, async, cancellation | Yes | HTTP client |
| Explicit client certificates, proxy options, Unix sockets | No | Documented limitations |
| Strict HTTP server, TLS, streaming, persistence, files, NDJSON | Yes | HTTP server |
| WebSocket server, subprotocols, messages, limits | Yes | WebSockets |
| Concurrent WebSocket read/write and PTY composition | Yes | WebSockets and Pseudo-terminals |
| Process cancellation, Unicode Windows spawn, tree ownership | Yes | Processes |
| PTY read/write, resize, controls, cancellation, cleanup | POSIX and Windows ConPTY | Pseudo-terminals |
| Windows ConPTY | Yes | Native implementation and executable lifecycle certification |
Platform certification
The compiler and generated C++ at 2c9c7e8 are certified on Linux x64 with GCC and Clang, Linux ARM64 with GCC, macOS ARM64 with AppleClang, and Windows x64 with MSVC. The five-platform CI passed on the first attempt, and the independent regression suite is green against the candidate SHA. The reactor HTTP/WebSocket runtime is covered by mandatory CI stages — plain, AddressSanitizer/UndefinedBehaviorSanitizer with leak detection, and ThreadSanitizer. PTY behavior executes on all three operating systems, including Windows ConPTY lifecycle certification, and WebSocket-to-PTY composition is certified as application-level composition.
Current positioning
Current main has concrete building blocks for serious native backend and full-stack work: HTTP/TLS servers, strict request framing, streaming bodies, persistence, NDJSON, outbound HTTP, cancellation, crypto, SQLite, full-duplex server WebSockets, subprocesses, concurrency, cross-platform PTYs, and application-owned WebSocket terminal sessions. These capabilities have focused compiler, protocol, lifecycle, resource, and cross-platform certification. The project does not yet label the complete backend/runtime stack production-grade; broader production certification remains later campaign work.
Still deferred
HTTP/2, ACME/certificate automation, reverse-proxy trust automation, outbound WebSocket clients, WebSocket extensions such as permessage-deflate, a built-in WebSocket-to-PTY bridge or terminal protocol, authentication/session frameworks, and a centralized package registry remain unimplemented or deferred.
