can i use coroutines inside my use case without co...
# android
r
can i use coroutines inside my use case without compromising my pattern, or being a library should not be used in the use case (leaving it dependent on a library)?
a
I think this one comes down to a matter of opinion, but maybe survey some users and find out if they would be deterred by your library depending on coroutines?
i.e. I would still use one, but you might get some Kotlin haters or people who get hung up on the "experimental" aspect, that they might be afraid to import a library that depends on such a feature.
r
exactly the point, so I came to ask here and see opinions of people who are already using kotlin the longest and may have gone through this same questioning
👍 1