Hi, my name is Tom Smykowski, I'm a staff full-stack engineer. I build and scale SaaS platforms to millions of users, working end-to-end from system architecture to frontend to mobile. On this blog I share what I learn about software engineering, feature evolution, and the future of programming languages.
What This Article Covers
This article delves into three intriguing feature requests that could shape the future of Kotlin beyond version 1.8, potentially appearing in future updates or even a 2.0 major release. It examines ideas such as multicatch statements, public/private property duality, and named decomposition, exploring their potential impact and the discussions surrounding them within the Kotlin community.
Questions This Article Answers
- What are some of the most promising feature requests for future Kotlin releases?
- How could multicatch statements simplify error handling in Kotlin?
- What benefits could dual public/private property types offer developers?
- How might named decomposition enhance the way Kotlin handles data structures?
- What is the process for feature requests to become part of Kotlin's standard library?
Length and Time
A thought-provoking exploration of potential Kotlin advancements. Approximately 7 minutes to read.