also looking at this
feat(android): the motion pair, and org.json's numbers — ratchet 54 → 52
#187
7 files
+577
-3
| @@ -58,6 +58,7 @@ const zig_sources = [_][]const u8{ | ||
| 58 | 58 | @embedFile("src/bridge_android_locationstore.zig"), |
| 59 | 59 | @embedFile("src/bridge_android_appstate.zig"), |
| 60 | 60 | @embedFile("src/bridge_android_bluetooth.zig"), |
| 61 | @embedFile("src/bridge_android_motion.zig"), | |
| 61 | 62 | }; |
| 62 | 63 | |
| 63 | 64 | /// How many spec actions Zig does not serve yet. |
| @@ -93,8 +94,8 @@ const zig_sources = [_][]const u8{ | ||
| 93 | 94 | /// first listener shim — the callback object is the holder's, the work is |
| 94 | 95 | /// Zig's; 56 with the app-state trio, the first migration where the state |
| 95 | 96 | /// itself moved rather than being worked around; 54 with the Bluetooth scan |
| 96 | /// pair. | |
| 97 | const max_not_yet_migrated: usize = 54; | |
| 97 | /// pair; 52 with the motion pair, once org.json agreed to print the floats. | |
| 98 | const max_not_yet_migrated: usize = 52; | |
| 98 | 99 | |
| 99 | 100 | /// Every `@JavascriptInterface fun <name>(` in the Kotlin bridge. |
| 100 | 101 | /// |