Bump kotlinx-coroutines-bom from 1.4.2 to 1.4.3-native-mt in /android

[dependabot]

Bumps kotlinx-coroutines-bom from 1.4.2 to 1.4.3-native-mt.

Release notes

Sourced from kotlinx-coroutines-bom's releases.

1.4.3

General changes

• Thread context is properly preserved and restored for coroutines without ThreadContextElement (#985)
• ThreadContextElements are now restored in the opposite order from update (#2195)
• Improved performance of combine with 4 parameters, thanks to @​alexvanyo (#2419)
• Debug agent sanitizer leaves at least one frame with source location (#1437)
• Update Reactor version in kotlinx-coroutines-reactor to 3.4.1, thanks to @​sokomishalov (#2432)
• callsInPlace contract added to ReceiveChannel.consume (#941)
• CoroutineStart.UNDISPATCHED promoted to stable API (#1393)
• Kotlin updated to 1.4.30
• kotlinx.coroutines are now released directly to MavenCentral
• Reduced the size of DispatchedCoroutine by a field
• Internal class TimeSource renamed to SchedulerTimeSource to prevent wildcard import issues (#2537)

Bug fixes

• Fixed the problem that prevented implementation via delegation for Job interface (#2423)
• Fixed incorrect ProGuard rules that allowed shrinking volatile felds (#1564)
• Fixed await/asDeferred for MinimalStage implementations in jdk8 module (#2456)
• Fixed bug when onUndeliveredElement wasn't called for unlimited channels (#2435)
• Fixed a bug when ListenableFuture.isCancelled returned from asListenableFuture could have thrown an exception, thanks to @​vadimsemenov (#2421)
• Coroutine in callbackFlow and produce is properly cancelled when the channel was closed separately (#2506)

Changelog

Sourced from kotlinx-coroutines-bom's changelog.

Change log for kotlinx.coroutines

Version 1.5.0-RC

Channels API

• Major channels API rework (#330, #974). Existing offer, poll, and sendBlocking methods are deprecated, internal receiveCatching and onReceiveCatching removed, receiveOrNull and onReceiveOrNull are completely deprecated. Previously deprecated SendChannel.isFull declaration is removed. Channel operators deprecated with ERROR are now HIDDEN.
• New methods receiveCatching, onReceiveCatching trySend, tryReceive, and trySendBlocking along with the new result type ChannelResult are introduced. They provide better type safety, are less error-prone, and have a consistent future-proof naming scheme. The full rationale behind this change can be found here.
• BroadcastChannel and ConflatedBroadcastChannel are marked as ObsoleteCoroutinesApi in the favor or SharedFlow and StateFlow. The migration scheme can be found in their documentation. These classes will be deprecated in the next major release.
• callbackFlow and channelFlow are promoted to stable API.

Reactive integrations

• All existing API in modules kotlinx-coroutines-rx2, kotlinx-coroutines-rx3, kotlinx-coroutines-reactive, kotlinx-coroutines-reactor, and kotlinx-coroutines-jdk9 were revisited and promoted to stable (#2545).
• publish is no longer allowed to emit null values (#2646).
• Misleading awaitSingleOr* functions on Publisher type are deprecated (#2591).
• MaybeSource.await is deprecated in the favor of awaitSingle, additional lint functions for Mono are added in order to prevent ambiguous Publisher usages (#2628, #1587).
• ContextView support in kotlinx-coroutines-reactor (#2575).
• All reactive builders no longer ignore inner cancellation exceptions preventing their completion (#2262, #2646).
• MaybeSource.collect and Maybe.collect properly finish when they are completed without a value (#2617).
• All exceptions are now consistently handled according to reactive specification, whether they are considered 'fatal' or not by reactive frameworks (#2646).

Other improvements

• Flow.last and Flow.lastOrNull operators (#2246).
• Flow.runningFold operator (#2641).
• CoroutinesTimeout rule for JUnit5 (#2197).
• Internals of Job and AbstractCoroutine was reworked, resulting in smaller code size, less memory footprint, and better performance (#2513, #2512).
• CancellationException from Kotlin standard library is used for cancellation on Koltin/JS and Kotlin/Native (#2638).
• Introduced new DelicateCoroutineApi annotation that warns users about potential target API pitfalls and suggests studying API's documentation first. The only delicate API right now is GlobalScope (#2637).
• Fixed bug introduced in 1.4.3 when kotlinx-coroutines-core.jar triggered IDEA debugger failure (#2619).
• Fixed memory leak of ChildHandlerNode with reusable continuations (#2564).
• Various documentation improvements (#2555, #2589, #2592, #2583, #2437, #2616, #2633, #2560).

Version 1.4.3

General changes

• Thread context is properly preserved and restored for coroutines without ThreadContextElement (#985)
• ThreadContextElements are now restored in the opposite order from update (#2195)
• Improved performance of combine with 4 parameters, thanks to @​alexvanyo (#2419)
• Debug agent sanitizer leaves at least one frame with source location (#1437)
• Update Reactor version in kotlinx-coroutines-reactor to 3.4.1, thanks to @​sokomishalov (#2432)
• callInPlace contract added to ReceiveChannel.consume (#941)
• CoroutineStart.UNDISPATCHED promoted to stable API (#1393)
• Kotlin updated to 1.4.30
• kotlinx.coroutines are now released directly to MavenCentral
• Reduced the size of DispatchedCoroutine by a field
• Internal class TimeSource renamed to SchedulerTimeSource to prevent wildcard import issues (#2537)

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #70.