Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

What is the recommended approach for @ObsoleteCoroutinesApi

See original GitHub issue

Version 0.27.0 marked all channel operators with @ObsoleteCoroutinesApi saying:

This API has serious known flaws and will be replaced with a better alternative in the nearest releases.

My question here is: What is the recommended approach while waiting for the better alternative in the nearest releases?

Should we stop using channel operators? Should we migrate existing code for an alternative technology (like RxJava) in the meantime?

Issue Analytics

State:
Created 5 years ago
Comments:17 (12 by maintainers)

Top GitHub Comments

4reactions

joefernercommented, May 4, 2019

I would really like some guidance on this. Should channels not be used until this is resolved?

3reactions

jcornazcommented, Mar 7, 2019

Cool. I see we are on the same page then.

That seems fine. Is that all the original question was asking

Actually the initial question was already answered and closed for quite a while already. But this last bit was not completely off-topic, since the question was: “What is the recommended approach for @ObsoleteCoroutinesApi”.