Kotlin Evolution and Enhancement Process (by Kotlin)

KEEP Alternatives

Similar projects and alternatives to KEEP

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better KEEP alternative or higher similarity.

Suggest an alternative to KEEP

Reviews and mentions

Posts with mentions or reviews of KEEP. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-07-29.
  • Effective Kotlin Item 49: Consider using inline value classes | 2021-09-08
    I base my opinions on things that I've read from Mr. Elizarov and from the value classes KEEP:
  • Underused Kotlin features | 2021-09-02
    Be sure to read the full documentation and how value classes in Kotlin relate to Java’s upcoming Project Valhalla.
  • What's the status of KEEP-87 and type class support in kotlin? | 2021-08-25 I'm guessing in 1.7 (or by the pace features are currently getting released, 1.17...) it will get an experimental release.
  • What is the future of Java? | 2021-07-29
    The value classes KEEP itself even raises the point that even once Valhalla is released, its adoption won't be universal at first, and that limiting a major feature like value classes to a specific version of the JVM, or a specific target, doesn't make sense.
  • What have Jetbrains ever done for us?
  • Effective Kotlin Item 46: Avoid member extensions | 2021-07-19
    Incidentally, there's been a feature request, some design discussion, and a proposal about how to add first-class support for multiple receivers.
  • Kotlin/KEEP Context Receivers | 2021-07-07
  • How to Use Result Data Type | 2021-06-14
    In Kotlin 1.5 these limitations were removed from the Result type.
  • Kotlin Team AMA #3: Ask Us Anything | 2021-05-27
    Is there are any progress / plans on compile time dependency injection feature? | 2021-05-27
    We are actively looking a concurrency as an area where Kotlin, as a language, can continue improving developers' lives. What's the problem with concurrency? It is the problem of "shared mutable state" that bites developers. After experimenting with freezing objects in Kotlin/Native we've become disillusioned in attempts to solve this problem by some form of "conditional mutability". We feel that a better solution lies through immutability, which automatically makes concurrency way safer. Out current design thinking in this direction is laid out here: | 2021-05-27
    We have some ideas for future language enhancements in this area. See Meanwhile, if somebody writes a compiler plugin I'm sure it'll be welcomed by the community.
  • Can I get some reasons to use Java instead of Kotlin? | 2021-05-17
    the kotlin devs aren’t dumb, they know this is coming and they welcome it because it means kotlin can have better performance too. Here is the kotlin open source proposal for value classes from the kotlin language lead It addresses the kotlin value types at There’s also a video they released about kotlin value classes recently notes/|Kotlin/KEEPKotlin/KEEP | Added by GitHub (Legacy)
  • Kotlin 1.5 Gets Support for Java 15 Features and a New JVM Compiler
    full pattern matching is actively being worked on
  • The Modern Java Platform - 2021 Edition | 2021-03-17
    pattern matching (also referred to as "full blown pattern matching" by some) would be a big start. there is a KEEP for it too.
  • Wednesday Links - Edition 2021-02-17 | 2021-02-17
    Design Notes on Kotlin Value Classes (~1h read) 💲


Basic KEEP repo stats
20 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
Find remote jobs at our new job board
There are 36 new remote jobs listed recently.
Are you hiring? Post a new remote job listing for free.