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