summaryrefslogtreecommitdiff
path: root/exercises
diff options
context:
space:
mode:
authorChris Boesch <chrboesch@noreply.codeberg.org>2026-04-01 22:28:37 +0200
committerChris Boesch <chrboesch@noreply.codeberg.org>2026-04-01 22:28:37 +0200
commit77d3b684cb467ad4e06c211518e2d2d1c7346ad1 (patch)
tree697873e26443481847ff61cea5e0ff0187d9e8c8 /exercises
parent3056a2b5442f2f1ec58db3f3493109064ad2a2a5 (diff)
revival of the async-io functions
Diffstat (limited to 'exercises')
-rw-r--r--exercises/084_async.zig78
-rw-r--r--exercises/085_async2.zig56
2 files changed, 72 insertions, 62 deletions
diff --git a/exercises/084_async.zig b/exercises/084_async.zig
index 56c9969..48bda2b 100644
--- a/exercises/084_async.zig
+++ b/exercises/084_async.zig
@@ -1,58 +1,48 @@
//
-// Six Facts:
+// In previous versions of Zig, async/await used special keywords
+// like 'suspend', 'resume', and 'async' that operated on stackframes
+// directly. Those keywords no longer exist!
//
-// 1. The memory space allocated to your program for the
-// invocation of a function and all of its data is called a
-// "stack frame".
+// Zig 0.16 replaced them with a unified I/O interface: std.Io.
+// This interface uses a VTable pattern - a struct of function pointers -
+// to abstract over different concurrency backends:
//
-// 2. The 'return' keyword "pops" the current function
-// invocation's frame off of the stack (it is no longer needed)
-// and returns control to the place where the function was
-// called.
+// * Threaded - classic thread-pool based I/O
+// * Uring - Linux io_uring
+// * Kqueue - BSD/macOS
+// * Dispatch - macOS Grand Central Dispatch
//
-// fn foo() void {
-// return; // Pop the frame and return control
-// }
-//
-// 3. Like 'return', the 'suspend' keyword returns control to the
-// place where the function was called BUT the function
-// invocation's frame remains so that it can regain control again
-// at a later time. Functions which do this are "async"
-// functions.
-//
-// fn fooThatSuspends() void {
-// suspend {} // return control, but leave the frame alone
-// }
+// The Io struct itself is tiny:
//
-// 4. To call any function in async context and get a reference
-// to its frame for later use, use the 'async' keyword:
+// const Io = struct {
+// userdata: ?*anyopaque, // opaque state of the backend
+// vtable: *const VTable, // table of function pointers
+// };
//
-// var foo_frame = async fooThatSuspends();
+// Your code receives an Io value and calls methods on it.
+// The backend is chosen at initialization time - your code doesn't
+// need to know which one it is!
//
-// 5. If you call an async function without the 'async' keyword,
-// the function FROM WHICH you called the async function itself
-// becomes async! In this example, the bar() function is now
-// async because it calls fooThatSuspends(), which is async.
+// In Zig 0.16, main() receives a std.process.Init struct to opt
+// into I/O and concurrency support:
//
-// fn bar() void {
-// fooThatSuspends();
+// pub fn main(init: std.process.Init) !void {
+// const io = init.io;
+// // ... use io ...
// }
//
-// 6. The main() function cannot be async!
+// Let's start simple. Fix the main function to extract the Io
+// interface from init, then use it to get the current time.
//
-// Given facts 3 and 4, how do we fix this program (broken by facts
-// 5 and 6)?
-//
-const print = @import("std").debug.print;
+const std = @import("std");
-pub fn main() void {
- // Additional Hint: you can assign things to '_' when you
- // don't intend to do anything with them.
- foo();
-}
+pub fn main(init: std.process.Init) !void {
+ const io = init.???;
+
+ // Get the current wall-clock time using the Io interface.
+ // Hint: Timestamp.now() takes an Io and a Clock type (.real = wall clock).
+ const timestamp = std.Io.Timestamp.now(io, .real);
-fn foo() void {
- print("foo() A\n", .{});
- suspend {}
- print("foo() B\n", .{});
+ // Print the timestamp in seconds since the Unix epoch.
+ std.debug.print("Current time: {}s since epoch\n", .{timestamp.toSeconds()});
}
diff --git a/exercises/085_async2.zig b/exercises/085_async2.zig
index 036aefa..1f1c4c8 100644
--- a/exercises/085_async2.zig
+++ b/exercises/085_async2.zig
@@ -1,28 +1,48 @@
//
-// So, 'suspend' returns control to the place from which it was
-// called (the "call site"). How do we give control back to the
-// suspended function?
+// Now that we know how to get an Io value, let's use it for
+// asynchronous execution!
//
-// For that, we have a new keyword called 'resume' which takes an
-// async function invocation's frame and returns control to it.
+// io.async() launches a function and returns a Future. The result
+// won't necessarily be available until you call .await() on it:
//
-// fn fooThatSuspends() void {
-// suspend {}
-// }
+// var future = io.async(someFunction, .{ arg1, arg2 });
+// // ... do other work here ...
+// const result = future.await(io);
//
-// var foo_frame = async fooThatSuspends();
-// resume foo_frame;
+// The function *may* run immediately or on another thread -
+// your code doesn't need to care! That's the beauty of the
+// Io abstraction. (In the Threaded backend, if no thread is
+// available, the function runs synchronously right away and
+// .await() just returns the already-computed result.)
//
-// See if you can make this program print "Hello async!".
+// io.async() returns a Future(T) where T is the return type
+// of the function you passed in. Future has two key methods:
//
-const print = @import("std").debug.print;
+// .await(io) - block until the result is ready, return it
+// .cancel(io) - request cancellation, then return the result
+//
+// Fix this program so that computeAnswer runs asynchronously
+// and its result is properly awaited.
+//
+const std = @import("std");
+
+pub fn main(init: std.process.Init) !void {
+ const io = init.io;
+
+ // Launch computeAnswer asynchronously.
+ // io.async() takes a function and a tuple of its arguments.
+ var future = io.async(computeAnswer, .{ 6, 7 });
+
+ // Meanwhile, print something to show we're not blocked.
+ std.debug.print("Computing... ", .{});
+
+ // Now collect the result. What method on Future gives us
+ // the value, blocking if it isn't ready yet?
+ const answer = future.???(io);
-pub fn main() void {
- var foo_frame = async foo();
+ std.debug.print("The answer is: {}\n", .{answer});
}
-fn foo() void {
- print("Hello ", .{});
- suspend {}
- print("async!\n", .{});
+fn computeAnswer(a: u32, b: u32) u32 {
+ return a * b;
}