also looking at this
test(ios): check the event channel, the half nothing was checking
#128
4 files
+280
-0
| @@ -67,6 +67,13 @@ | ||
| 67 | 67 | //! equivalent, so nothing ever dispatches that event. Tapping launches or |
| 68 | 68 | //! foregrounds the app and stops there. Pre-existing, identical under the |
| 69 | 69 | //! Swift shim, and outside these two actions' scope. |
| 70 | //! | |
| 71 | //! That paragraph was the only record of it for several phases, which is the | |
| 72 | //! problem with recording a gap in the header of the one module that noticed: | |
| 73 | //! nothing else can see it and nothing re-checks it. `craftShortcut` is now a | |
| 74 | //! row in `ios_conformance_test.zig`'s `dead_subscriptions`, alongside three | |
| 75 | //! more of the same shape found by looking — the build fails if it quietly | |
| 76 | //! gains an emitter, and fails if a fifth appears. Tracked in issue #127. | |
| 70 | 77 | |
| 71 | 78 | const std = ; |
| 72 | 79 | const builtin = ; |