Printing a line is more than formatting text: output can be buffered, writes can fail, and a buffer may need flushing. Zig’s std.Io provides a cross-platform interface for these operations while leaving choices such as buffer storage under the programmer’s control. section 1.6.2 section 3.6
An Io instance gives standard-library code access to operating-system capabilities including file systems, networking, randomness, and time. It also supports asynchronous and concurrent I/O. Asynchronous operations can be independent without actually running concurrently; asynchrony enables concurrency but does not guarantee it. section 3.1.3
A main function accepting std.process.Init can take its suitable default instance from init.io. Different Io implementations have different runtime and platform consequences, so the default is convenient, not the only choice. section 3.1.1 section 5.3.1
Listing 1.2 All your codebase still belong to us
const std = @import("std");
pub fn main(init: std.process.Init) !void { #1
const io = init.io;
const stdout = std.Io.File.stdout(); #2
var stdout_buffer: [1024]u8 = undefined;
var stdout_writer = stdout.writer(io, &stdout_buffer); #3
const writer = &stdout_writer.interface; #3
try writer.print("All your codebase still belong to us!\n", .{}); #4
try writer.flush(); #5
}
This stdout program supplies a 1,024-byte buffer to a file writer, uses its Writer interface, and explicitly propagates errors from printing and flushing. section 1.6.2
Writers also support files, formatting, string building, and networking. For a TCP server, std.Io wraps system calls with cross-platform functions: listen on an address and port, accept connections, then read from and respond to clients. section 1.6.2 section 4.2.2
Implementation choice matters when the default is not a fit. Io.Threaded can use operating-system threads for concurrency; Io.Uring and Io.Evented use an evented runtime for I/O and concurrency. An independently managed implementation also needs cleanup: a library can deinitialize its Io resources when its users are finished. section 5.3.1
