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

Surfacev0.0.4v0.0.5 (latest)
Language, ownership, checked errors, packages, CLI/LSPAvailableAvailable
HTTP server, TLS, SQLite, buffered outbound HTTPAvailableAvailable; reactor correctness/robustness fixes
bytes, Base64/Base64url, cryptoAvailableAvailable
Outbound HTTP streaming and cancellationAvailableAvailable
Streaming server requests/responses, persistence, helpers, ranges, NDJSONAvailableAvailable
WebSocket serverAvailableAvailable; reactor dispatch/close/403 parity, saturation 503
WebSocket-to-PTY sessionsCertified as application-level composition; no built-in bridgeSame
Hardened process ownership and cancellable pipesAvailableAvailable
PTYLinux, macOS, and Windows ConPTYAvailable
Windows ConPTYAvailable on Windows 10 1809 / Server 2019 or newerAvailable
Two-way FFI (exports, native -> Strut, callbacks, checked errors, retained callbacks)Not releasedAvailable
C/host embedding API and language consumers (C, C++, Python, Go, Node.js, C#)Not releasedAvailable
Nift interoperabilityNot releasedLinux-local evidence
Explicit weak ownership for native handles and structs containing themNot availableAvailable

Current-main backend capability

CapabilityRuntime/compilerWebsite
Secure random, SHA-256, HMAC-SHA-256, constant-time compareYesCrypto
Strict Base64 and unpadded Base64urlYesCrypto
Outbound arbitrary methods, binary bodies, limits, redirects, custom CAYesHTTP client
Outbound streaming upload/download, async, cancellationYesHTTP client
Explicit client certificates, proxy options, Unix socketsNoDocumented limitations
Strict HTTP server, TLS, streaming, persistence, files, NDJSONYesHTTP server
WebSocket server, subprotocols, messages, limitsYesWebSockets
Concurrent WebSocket read/write and PTY compositionYesWebSockets and Pseudo-terminals
Process cancellation, Unicode Windows spawn, tree ownershipYesProcesses
PTY read/write, resize, controls, cancellation, cleanupPOSIX and Windows ConPTYPseudo-terminals
Windows ConPTYYesNative 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.