A modern programming language that makes developers happier.

kotlinlang

Here is an artical in witch I am proposing the notion of *const class* and *const capturing lambda*, and why I think it matters: <https://itnext.io/designing-a-kotlin-memory-safe-mode-c76c06317c3e>

I think that kotlin issue tracker or KEEP is much better place to discuss it than a blog

These are a lot more formal, and allow for a lot less of personal considerations.
I do agree that a KEEP is necessary (I'm working on it), but I wanted to expose my thoughts in a more personal and informal way.

I don't believe issue tracker:
- should be used for proposals (this is the role of KEEP)
- is appropriate for 2000 words articles
- is appropriate for sharing

there are many proposals/feature requests on kotlin issue tracker, also many of them created by Kotlin team members

&gt; this is the role of KEEP
KEEP is very formal document that should cover implementation details on every platform, concider backward compatibility etc
So issue tracker is perfect for proposals that not yet on KEEP stage

However, I wanted an article first :slightly_smiling_face:

I must say I wish they added something like `const` / `mut` from the start. This idea however seems like a way towards improving safety.