Louis CAD

Hello, thanks to you @XilinJia, and your work on https://github.com/XilinJia/krdb, we published a fork on Maven Central yesterday, supporting all targets (iOS and macOS included). https://github.com/Infomaniak/realm-kotlin/releases/tag/3.2.8-2

Hello, thanks to https://github.com/XilinJia/krdb, we published a fork on Maven Central yesterday, supporting all targets (iOS and macOS included). https://github.com/Infomaniak/realm-kotlin/releases/tag/3.2.8-2

It's also non-native at all at the moment, which is not good because it breaks integration with OS features. For instance, I use PopClip, an app that shows an actionable...

Interesting problem! I think having `await(…)` take an optional boolean parameter named `consume` (defaulting to `false`) would be less confusing that `consume`, IMHO. It also makes discoverability much easier since...

You can keep backwards compatibility when adding an optional parameter, you just need to keep the old overload with deprecated hidden for binary compatibility, and source compatibility stays since the...

Is that really the case? I was thinking that it was just about it having a parent `Job` or not. Anyway, the default `consume` value could be set to `this...

I get your point, and I agree it'd be strange. The behavior could be set at the "awaitable" creation, so as a parameter to `asDeferred(…)`, `async(…) { … }`, etc....

The code of kotlinx.coroutines is used as a reference for people learning (juniors to seniors!), and leftovers like this one is noise that can cheaply be removed.

Sent a PR (#4466)

Hello, thanks to https://github.com/XilinJia/krdb, we published a fork on Maven Central yesterday, supporting all targets (iOS and macOS included). https://github.com/Infomaniak/realm-kotlin/releases/tag/3.2.8-2