about things
revert: remove project-specific tracking from language notes
-27
-27
languages/ziglang/0.16/io.md
-27
languages/ziglang/0.16/io.md
···
76
76
- other implementations possible (io_uring, kqueue, etc.)
77
77
78
78
the interface is concrete, not generic - same benefits as 0.15's explicit buffer approach.
79
-
80
-
## zat 0.16 migration prep
81
-
82
-
isolated HTTP I/O behind `HttpTransport` in `src/internal/transport.zig`. when 0.16 lands:
83
-
84
-
1. update `transport.zig` to accept `std.Io` parameter
85
-
2. add `initWithIo()` constructors if needed
86
-
3. all resolvers/clients automatically get the change
87
-
88
-
### downstream update points
89
-
90
-
projects importing zat (benefit from transport refactor automatically):
91
-
92
-
| project | files | notes |
93
-
|---------|-------|-------|
94
-
| leaflet-search | `tap.zig`, `extractor.zig` | uses zat for firehose sync |
95
-
| music-atmosphere-feed | `posts.zig`, `api.zig`, `auth.zig`, `filter.zig` | uses zat for atproto integration |
96
-
97
-
### other projects needing 0.16 migration (not zat consumers)
98
-
99
-
| project | files | I/O type |
100
-
|---------|-------|----------|
101
-
| logfire-zig | `exporter.zig` | HTTP client - consider same transport pattern |
102
-
| find-bufo-bot | `bsky.zig`, `stats.zig` | HTTP client + server |
103
-
| prefect-server | uses zap framework | HTTP server (wait for zap update) |
104
-
105
-
note: leaflet-search and music-atmosphere-feed also have direct `std.http` usage beyond zat imports.