Reading about frozen objects in Kotlin/Native 0.7 ...
# language-proposals
e
Reading about frozen objects in Kotlin/Native 0.7 reminded me about Pony’s reference capabilities. Have those been looked at in any capacity to see how they might inspire some future Kotlin features? https://tutorial.ponylang.org/capabilities/reference-capabilities.html
l
@eddie Repost it in #kotlin-native, you'll be more likeley to get attention of the target folks
Also, read the topic before posting in a channel please, I see no use case in your "proposal"
e
Sorry, perhaps I should’ve included a link to the Kotlin/Native 0.7 blog post, which highlighted frozen objects and why they’re useful: https://blog.jetbrains.com/kotlin/2018/04/kotlinnative-v0-7-released-smoother-interop-frozen-objects-optimisations-and-more/
And I posted it here because I brought up Pony’s capabilities and asked how they might influence Kotlin overall in the future, not just the Native backend.