Well, rx2 dependencies overhead after proguard is ...
# coroutines
t
Well, rx2 dependencies overhead after proguard is about 2.5k in my project and coroutines is only ~0.5k (even with coroutines-rx2), but the initial question is still actual: why coroutines generates more methods and what to do with it?
g
What to do with what? Do you see any really unnecessary methods that can be optimised? Really, your samples looks not very realistic Also methods count is also about references to other methods, maybe it’s just first usage overhead. And would be interesting to see some real sample to compare
t
@gildor real project results are even worse. First usage overhead - no, I've duplicated blocks of code and counted difference.
I've not checked generated code yet since kotlin->java decomplier doesn't work for me on coroutines.
g
you cannot use decompiler for coroutines, check bytecode
e
Some of the generated methods for coroutines are indeed not strictly necessary. They will be optimized in the finalized version of coroutines that is planned for Kotlin 1.3.