# \#async **URL:** https://ziggit.dev/tag/async/123.md [Latest](https://ziggit.dev/latest.md) · [Categories](https://ziggit.dev/categories.md) · [Tags](https://ziggit.dev/tags.md) --- ## [Zio - async I/O framework](https://ziggit.dev/t/zio-async-i-o-framework/12213)
**Author:** [@lalinsky](https://ziggit.dev/u/lalinsky)\ **Replies:** 159\ **Last updated:** [October 19, 2026, 3:31am UTC](https://ziggit.dev/t/zio-async-i-o-framework/12213 "2026-10-19T03:31:56Z")
This an experiment that grew out of my frustration, when working on the NATS client for Zig. It kind of competes with the future std.Io event loop, but I wanted to see what API I could use right now. I’ll probably finish… --- ## [Dusty - HTTP server/client library](https://ziggit.dev/t/dusty-http-server-client-library/12807)
**Author:** [@lalinsky](https://ziggit.dev/u/lalinsky)\ **Replies:** 24\ **Last updated:** [October 7, 2026, 2:59pm UTC](https://ziggit.dev/t/dusty-http-server-client-library/12807 "2026-10-07T14:59:01Z")
As if Zig didn’t already have enough HTTP servers, I’m creating another one. This is very early, but it’s one of the reasons for me working on zio in the first place. I have a server application, where I want to run cust… --- ## [Confusion about releasing a resource from a future](https://ziggit.dev/t/confusion-about-releasing-a-resource-from-a-future/17584)
**Author:** [@Tropid](https://ziggit.dev/u/Tropid)\ **Replies:** 4\ **Last updated:** [September 13, 2026, 12:50am UTC](https://ziggit.dev/t/confusion-about-releasing-a-resource-from-a-future/17584 "2026-09-13T00:50:46Z")
I’m trying to understand how to correctly manage resources when using futures. The following example does not compile: const std = @import("std"); const Io = std.Io; const Allocator = std.mem.Allocator; const ArrayList … --- ## [Communication methods between concurrent tasks, modelling recovery / error handling](https://ziggit.dev/t/communication-methods-between-concurrent-tasks-modelling-recovery-error-handling/17144)
**Author:** [@jeffective](https://ziggit.dev/u/jeffective)\ **Replies:** 1\ **Last updated:** [August 9, 2026, 6:07am UTC](https://ziggit.dev/t/communication-methods-between-concurrent-tasks-modelling-recovery-error-handling/17144 "2026-08-09T06:07:29Z")
Good evening my esteemed colleagues. I am implementing a communication library which requires concurrency to work correctly. The structure of my application could be represented as the following diagram: setup -\> task… --- ## [Linux gpio library for 0.16.0](https://ziggit.dev/t/linux-gpio-library-for-0-16-0/15590)
**Author:** [@cancername](https://ziggit.dev/u/cancername)\ **Replies:** 1\ **Last updated:** [July 28, 2026, 6:22am UTC](https://ziggit.dev/t/linux-gpio-library-for-0-16-0/15590 "2026-07-28T06:22:02Z")
gpio https://codeberg.org/cn-cn-cn/gpio I’ve just updated an existing gpio library to Zig 0.16.0. It was quite fun, and the original API was already to my taste, so little work was required. --- ## [Threadlocal variable for std.Io.async / std.Io.concurrent](https://ziggit.dev/t/threadlocal-variable-for-std-io-async-std-io-concurrent/16454)
**Author:** [@kmnn](https://ziggit.dev/u/kmnn)\ **Replies:** 3\ **Last updated:** [July 2, 2026, 4:38am UTC](https://ziggit.dev/t/threadlocal-variable-for-std-io-async-std-io-concurrent/16454 "2026-07-02T04:38:46Z")
Is there any way to make a global variable that is local to each task created by Io.async and Io.concurrent, similar to threadlocal? For context, I am currently working on a project in which I would need to pass common … --- ## [Canceling awaited Future/Group/etc is impossible?](https://ziggit.dev/t/canceling-awaited-future-group-etc-is-impossible/15466)
**Author:** [@chirp\_chirp](https://ziggit.dev/u/chirp_chirp)\ **Replies:** 3\ **Last updated:** [May 12, 2026, 8:04am UTC](https://ziggit.dev/t/canceling-awaited-future-group-etc-is-impossible/15466 "2026-05-12T08:04:10Z")
I’m trying to use cancelation from the new Io (0.16.0) to shut down background task on unix signal. However, it panics with assertion that awaited future can’t be canceled (at least if it isn’t finished and is still awai… --- ## [Memcached client](https://ziggit.dev/t/memcached-client/14285)
**Author:** [@lalinsky](https://ziggit.dev/u/lalinsky)\ **Replies:** 0\ **Last updated:** [February 11, 2026, 12:14pm UTC](https://ziggit.dev/t/memcached-client/14285 "2026-02-11T12:14:49Z")
I’m continuing to build my networking ecoystem, as I’m hoping to replace all my existing C++ and Go code in AcoustID with Zig. One of the last pieces I needed was a memcached client, capable of consistent hashing, retrie…