about things
fix: clarify zat downstream vs separate migration concerns
+7
-7
+7
-7
languages/ziglang/0.16/io.md
+7
-7
languages/ziglang/0.16/io.md
···
87
87
88
88
### downstream update points
89
89
90
-
projects importing zat that may need updates when 0.16 drops:
90
+
projects importing zat (benefit from transport refactor automatically):
91
91
92
92
| project | files | notes |
93
93
|---------|-------|-------|
94
94
| leaflet-search | `tap.zig`, `extractor.zig` | uses zat for firehose sync |
95
95
| music-atmosphere-feed | `posts.zig`, `api.zig`, `auth.zig`, `filter.zig` | uses zat for atproto integration |
96
96
97
-
these projects also have their own direct `std.http` usage that will need migration:
97
+
### other projects needing 0.16 migration (not zat consumers)
98
98
99
99
| project | files | I/O type |
100
100
|---------|-------|----------|
101
-
| leaflet-search | `embedder.zig`, `Client.zig`, `server.zig` | HTTP client |
102
-
| music-atmosphere-feed | `server/http.zig` | HTTP server |
103
-
| find-bufo-bot | `bsky.zig`, `main.zig`, `stats.zig` | HTTP client + server |
104
-
| logfire-zig | `exporter.zig` | HTTP client |
105
-
| prefect-server | uses zap framework | HTTP server (zap will need update) |
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.