oh man - it looks like in order to update my kotlin version in my multiplatform project, any deps I am using that support K/N also need to be built with the latest?
👌 4
Kris Wong
11/18/2019, 8:01 PM
I can understand that, but it's going to be quite limiting in practice
a
Andy Gibel
11/18/2019, 8:04 PM
ran into the same issue
s
Sam
11/18/2019, 8:12 PM
It has mostly been an issue when trying out EAP versions for me. Admittedly I've tried to keep the amount of external dependencies low in my project.
k
Kris Wong
11/18/2019, 8:18 PM
yeah dependencies are pretty tough right now, for the most part. just concerned about the future.
k
kpgalligan
11/18/2019, 8:24 PM
Major versions tend to get deployments quick. EAP is tough. I wouldn’t worry about the future too much. This is frustrating if you’re used to the JVM, but as I understood it, Swift had similar issues with versions.
k
Kris Wong
11/18/2019, 8:26 PM
yes, between versions with breaking changes
e
evant
11/18/2019, 8:28 PM
for a library developer this is really not great, as for java clients you don't want to update your dep as there's no reason to force them onto a newer version of kotlin if not necessary, but for native you do want to bump so that they can use it on the latest version.