What would be the reason behind only allowing publ...
# announcements
j
What would be the reason behind only allowing public constructors on inline classes?
k
Because you wouldn't be able to truly restrict Java code from "instantiating" the class.
j
But that seems similar to internal visibility which is public in the java side
And we still don't have the good thing in Kotlin side
k
True, keep in mind that inline classes are experimental and subject to change. The KEEP calls them "current limitations": https://github.com/Kotlin/KEEP/blob/master/proposals/inline-classes.md#current-limitations
j
I forgot about the KEEP, thanks I'm gonna read through it