Zach Klippenstein
Zach Klippenstein
Coroutines don't support synchronized blocks but they support the same semantics with `Mutex`.
@swankjesse started a proof-of-concept using NIO's async API in #531, and there's a ton of discussion there. That proposal adds non-blocking variants to only the basic read/write APIs - processing...
Here's an example of a recent 29 failure (from #352): ``` com.squareup.workflow1.ui.tests.ViewTreeIntegrationTest > complex_modal_backstack_with_text_entry[test(AVD) - 10] FAILED Test failed to run to completion. Reason: 'Test run failed to complete. Expected...
And/or the AndroidX paging library
The comment on this issue makes it sound like this should be fixed already, but apparently it is not: https://github.com/Kotlin/kotlinx.coroutines/issues/1625#issuecomment-544917309
Since it affects which exceptions we expose, I would consider this as an API change even though it's technically not.
Not API change, not 1.0 blocker.
It's not really a trick, it's just a convenient place to put a related definition. If we want to make the samples more explicit though, we could just give the...
This isn't an API change, so it doesn't block 1.0.0.
Github Actions doesn't support API 30 yet.