The listed features are also at various stages of development. Please note that this is not an exhaustive list of features we are currently working on. We also ask you to vote for specific solutions, as some of the potential features can be implemented in multiple ways and in some aspects they may contradict one another. We ask you to choose the three features that would bring the most benefit to you, and downvote one that will create more problems for your code. The official Kotlin documentation about contributionīelow, you will find the descriptions of features and the use cases they address.If you’re interested in learning more about the Kotlin design process and your opportunities to contribute to it, take a look at these materials: Webinar with Roman Elizarov and Svetlana Isakova Features that address popular use cases are a lot more likely to be implemented first. The use cases of our users are our brightest beacon in this ocean of choices and trade-offs, helping us navigate and make the right language design decisions. New features bring new functionality, but they can complicate the language and provide an easy opportunity for misuse. That’s why designing new features is always hard. One of the goals of Kotlin, as a pragmatic language, is to stay both concise and versatile at the same time. During the webinar you will be able to ask your questions and discuss the future of the language. You can find the descriptions of all the features and their use cases below. The survey provides an opportunity for you to have your say about the features that should be prioritized in Kotlin. To this end, we’re launching the Kotlin Features Survey, along with a webinar hosted by Roman Elizarov and Svetlana Isakova. We’re planning the next steps for Kotlin’s development and would like to know your opinion about the relative importance of upcoming features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |