iOS: Never queue application-level events #3905
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Events like
resumed
,new_events
,about_to_wait
, and so on will never happen as a result of programmer action, so we'll never need to queue those. This allows us to remove the need for the oldEvent
struct in the iOS backend.Furthermore, we can now remove
InUserCallback
, since that state is already stored insideEventHandler
.I've tried to otherwise keep the semantics as close to the original by calling
handle_nonuser_events(mtm, [])
, which flushes pending events.