I am writin a lib a

Question

I am writin a lib <https github com jasync sql jasync sql> and just started to use coroutines internal not in exposed api Since this is new I am not using experimental packages I wonder how this affects lib users They will not be able to use it if they are using experimental coroutines

oshai · Answer

I asked in forum but didn t get an answer

oshai · Answer

And this holds me from merging it

gildor · Answer

If you use release coroutines your user cannot compile with your library using 1 2 compiler

gildor · Answer

If you use experimental ones that it can used from 1 2 and 1 3

oshai · Answer

ok from that sentence I thought experimental will not be available in 1 3 `Note that release of kotlinx coroutines will drop all the deprecated declarations from experimental 0 x releases`

oshai · Answer

it appears here <https blog jetbrains com kotlin 2018 09 kotlin 1 3 rc is here migrate your coroutines >

oshai · Answer

so since the usage of coroutines is optional in my lib at the moment I thought to use provide scope so that people will have to provide new coroutines to use it

oshai · Answer

Isn t it makes sense to release an 0 x version with the non experimental packages then I can enfore a version higher than that

gildor · Answer

This sentece about kotlinX coroutines

gildor · Answer

kotlinx coroutines library of course not compatible but stdlib part is backward compatible

gildor · Answer

So if you use kotlinx coroutines you cannot support old and new

oshai · Answer

Yes I am using `kotlinx coroutines` so what s my best option the optional dependency I described above with the new version to save me from migrating later

gildor · Answer

~kotlinx coroutines for 1 2 and 1 3 are binary incompatible~

gildor · Answer

Actually just understand that you can use it

gildor · Answer

not sure why do you need optional dependency

gildor · Answer

Kotlinx coroutines for 1 3 use another package

gildor · Answer

so probably will work

oshai · Answer

to use it with experimental package

gildor · Answer

yes

gildor · Answer

version for 1 2

gildor · Answer

Version for 1 3 cannot be used by 1 2 consumer

oshai · Answer

and do you think version for 1 2 can be used by 1 3 consumer

gildor · Answer

Yes it should be possilbe you can easily check it just create a new 1 3 project and use kotlinx coroutines eap13 version

gildor · Answer

But consumer will have 2 version of kotlinx coroutines in classpath

gildor · Answer

can you just support 2 branches witn new and old coroutines

gildor · Answer

Anyway if you do not expose experimental coroutines as API it should be transparent for consumer

oshai · Answer

`But consumer will have 2 version of kotlinx coroutines in classpath` I don t think that is possible if kotlinx coroutines have the same artifact id + group id

gildor · Answer

hah

gildor · Answer

yeah you right

oshai · Answer

< elizarov> am I missing something here are there any other alternatives for library developers

gildor · Answer

In my library I just have 2 branches one for 1 2 and one for 1 3

oshai · Answer

ok thanks

elizarov · Answer

That is the way to go With Kotlin 1 3 release around the corner it will be over soon

oshai · Answer

I wonder which corner this is around if it will be released in October then I will wait and keep myself safe from having to maintain branches