Work handed to the main thread from any other thread.
Pages and views live on the main thread, and so do bound methods and window events. A plugin's threads give their results to them through this package: an HTTP response, a WebSocket message, a changed file. The fetch, websocket, watch, updater and terminal plugins depend on it.
The package is plugins/mainthread (module mainthread). It depends on
nothing, not even myzig.
const mainthread = @import("mainthread");
const Job = struct {
window: *myzig.Window,
result: []u8,
fn run(ctx: ?*anyopaque) callconv(.c) void {
const job: *Job = @ptrCast(@alignCast(ctx));
// On the main thread: emit an event, change a view's state, ...
_ = job;
}
};
try mainthread.init(); // once, on the main thread (plugins' services do it when created)
if (!mainthread.post(job, Job.run)) {
// Not queued (no init, or out of memory): the caller still owns `job`.
}init()prepares the queue. Calling it again does nothing.post(ctx, func)runsfunc(ctx)on the main thread, soon.- It is safe from any thread.
- Jobs run in the order they were posted.
funcis amainthread.Func:*const fn (?*anyopaque) callconv(.c) void.
runUntil(&done)runs the queue until an atomic flag is set. It is for tests and tools without an event loop of their own, on the main thread only.
It is the main thread's own queue on each platform, so nothing polls:
| platform | queue |
|---|---|
| macOS | libdispatch's main queue (dispatch_async_f) |
| Linux | GLib's default context (g_idle_add), which GTK's loop runs |
| Windows | a message-only window (PostMessageW), which the app's message loop runs |
In browsers (wasm32-wasi) there is no other thread, and the package does
not compile there.
Inside myzig, work reaches the main thread through myzig.App.after (a
timer) and, on macOS, objc.dispatchMain. See the
architecture guide for the threading model.
cd plugins/mainthread
zig build test # on this machine
zig build check -Dtarget=x86_64-linux-gnu # type-check another platform