Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not find com.badoo.reaktive:coroutines-interop:1.2.2-nmtc #678

Closed
rickytribbia opened this issue Aug 17, 2022 · 4 comments
Closed

Comments

@rickytribbia
Copy link

Is it x.x.x-nmtc still needed to use reaktive coroutines interop with new memory model?

If yes, I notice that 1.2.2-nmtc couldn't be found.

Thank you for your work

@arkivanov
Copy link
Contributor

Indeed, we forgot to publish 1.2.2-nmtc. It's still needed for the new memory model, thanks for raising it. I will prepare the mt-coroutines branch for the release today.

cc/ @CherryPerry

@CherryPerry
Copy link
Collaborator

@arkivanov When 1.7.20 is released I can merge mt-coroutines in the main branch, right?

@arkivanov
Copy link
Contributor

@CherryPerry As mentioned in this comment, they are gradually stopping support of the native-mt coroutines in coroutines v1.6.x, and the support will be stopped completely in coroutines v1.7.0. Indeed, since Kotlin 1.7.20 the new memory model will be enabled by default, and there will be a way to opt-out. Merging mt-coroutines into the main branch would be a massive breaking change for users still on the old memory model for whatever reason.

I've been thinking about merging mt-corotunes into the main branch, and at the same time removing the support of the old memory model in Reaktive v2.0.0. This should boost performance further on all platforms. There is a todo item in #620. I will be working on v2.0.0 soon. Does it sound reasonable?

@CherryPerry
Copy link
Collaborator

Released, should be available soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants