Fix Dispatchers.Main not being fully initialized on Android and Swing #3101
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.
unitTests.returnDefaultValues=true
is set on Android, thenLooper.getMainLooper()
may returnnull
. The type system ofKotlin is tricked to believe that the method can't ever return
null
, so doesn't check for it anywhere. As a result, despite notbeing fully initialized,
Dispatchers.Main
is considerednon-missing.
the dispatcher successfully initializes nonetheless.
This was not an issue before, as it only surfaced when
Dispatchers.Main
was used. However, nowMain
is the source oftime for delays, so any delay will throw something
incomprehensible if this happens.