also looking at this
feat(android): the app-state trio in Zig — ratchet 59 → 56
#184
6 files
+422
-3
| @@ -56,6 +56,7 @@ const zig_sources = [_][]const u8{ | ||
| 56 | 56 | @embedFile("src/bridge_android_screen.zig"), |
| 57 | 57 | @embedFile("src/bridge_android_files.zig"), |
| 58 | 58 | @embedFile("src/bridge_android_locationstore.zig"), |
| 59 | @embedFile("src/bridge_android_appstate.zig"), | |
| 59 | 60 | }; |
| 60 | 61 | |
| 61 | 62 | /// How many spec actions Zig does not serve yet. |
| @@ -89,8 +90,9 @@ const zig_sources = [_][]const u8{ | ||
| 89 | 90 | /// the service that owns them; 61 with the four controls, once Kotlin agreed |
| 90 | 91 | /// to name its own service class; 59 with the network monitoring pair, the |
| 91 | 92 | /// first listener shim — the callback object is the holder's, the work is |
| 92 | /// Zig's. | |
| 93 | const max_not_yet_migrated: usize = 59; | |
| 93 | /// Zig's; 56 with the app-state trio, the first migration where the state | |
| 94 | /// itself moved rather than being worked around. | |
| 95 | const max_not_yet_migrated: usize = 56; | |
| 94 | 96 | |
| 95 | 97 | /// Every `@JavascriptInterface fun <name>(` in the Kotlin bridge. |
| 96 | 98 | /// |