You are always going to need the Kotlin stdlib bec...
# getting-started
c
You are always going to need the Kotlin stdlib because the compiler will generate call to stdlib just like Java compiler generates calls to java.lang for some cases.
t
yep, I looked at decompiled code and figured that much too.
Intrinsics
was not the only import marked red in decompiled code, I adapted my library
c
Why is it a problem to make kotlin std lib a dependency?
t
I simply thought it could be done without, that somehow stdlib was not needed when kotlin was not directly used. that the
class
file generated by kotlin compiler could be made kotlin agnostic. Knowing it is not possible, there is no problem, I just added stdlib as a dependency to my library
c
I thought you were trying to sneak kotlin into a project without anyone noticing.
😂
t
no no, we already have 2 services completely in kotlin and a third one 50/50. but I did not want pure java services to have to depend on kotlin 🤷‍♂️ otoh, it might help some colleagues seeing that mixing is safe, so that maybe we could slowly start to migrate this java services to kotlin
c
The co-existance is usually not an issue.
j
If adding a library is not a problem, it's all the same when it's byte code.
And if there are constraints about adding a library, they are the same constraints...
👍 1