also looking at this
feat(android): the first listener shim, and network monitoring on it — 61 → 59
#183
5 files
+246
-13
| @@ -87,8 +87,10 @@ const zig_sources = [_][]const u8{ | ||
| 87 | 87 | /// 67 with downloadFile and saveFile, neither of which needed the main thread |
| 88 | 88 | /// at all; 65 with the recording store's two reads, whose writers stay with |
| 89 | 89 | /// the service that owns them; 61 with the four controls, once Kotlin agreed |
| 90 | /// to name its own service class. | |
| 91 | const max_not_yet_migrated: usize = 61; | |
| 90 | /// to name its own service class; 59 with the network monitoring pair, the | |
| 91 | /// first listener shim — the callback object is the holder's, the work is | |
| 92 | /// Zig's. | |
| 93 | const max_not_yet_migrated: usize = 59; | |
| 92 | 94 | |
| 93 | 95 | /// Every `@JavascriptInterface fun <name>(` in the Kotlin bridge. |
| 94 | 96 | /// |