• h

    Hanno

    1 year ago
    Thanks for sharing the roadmap, it's very exciting whats on the table. I have a question regarding multiple receivers stuff, hope this is the right place to ask. For me as a very interested kotlin power user, i can't see how we went from sth like fun (A, B).foo(bar: Bar) as described in the multi receiver keep to decorators as in the Presentation. There was a lot of discussion by users in https://github.com/Kotlin/KEEP/pull/176 and i don't see any of those go into the direction of a decorators construct. I also try to be open and know that the shown syntax is Not necessarily what i think it is, but the first look of the decorators design looks way more complicated and un-kotliny than the ones from KEEP 176. So is there already any discussion or information about how decorators came up in this context, am i missing any discussions or threads here?
    h
    Zach Klippenstein (he/him) [MOD]
    +2
    4 replies
    Copy to Clipboard
  • Ananiya

    Ananiya

    1 year ago
    Hi all,:blob-thinking-fast: I am bit confused with the term "New complier" does that mean new standalone runtime for kotlin or improving the old once? Really curious to know :blob-hype: kotl.in/roadmap
    Ananiya
    andylamax
    +1
    4 replies
    Copy to Clipboard
  • etolstoy

    etolstoy

    1 year ago
    Hey all! We’ve updated the roadmap:- Roadmap: https://kotl.in/roadmap - What’s changed: https://kotlinlang.org/roadmap.html#whats-changed-since-october-2020 - YT board: https://youtrack.jetbrains.com/agiles/153-1251 We’ll be grateful for your feedback 🙂
    etolstoy
    Javier
    +1
    4 replies
    Copy to Clipboard
  • Kris Wong

    Kris Wong

    1 year ago
    it would be super cool if I didn't get an email notification every time someone votes for an issue
    Kris Wong
    1 replies
    Copy to Clipboard
  • ankushg

    ankushg

    1 year ago
    Maybe I'm alone on this, but it feels weird to mark the new JS IR as stable (or even beta) without supporting some version of exported enum classes at all: https://youtrack.jetbrains.com/issue/KT-37916
    ankushg
    mikehearn
    +1
    4 replies
    Copy to Clipboard
  • s

    serebit

    1 year ago
    We've decided to postpone... [improving] usability of multi-threaded coroutines library for Kotlin/Native
    Why was this postponed? Looking at the results of the multiplatform survey, the top mentioned pain point of multiplatform is the strict memory model of Kotlin/Native and the inability to write concurrent code like in Kotlin/JVM, so it seems odd to me that this would be pushed back.
    s
    Zach Klippenstein (he/him) [MOD]
    +1
    4 replies
    Copy to Clipboard
  • etolstoy

    etolstoy

    1 year ago
    This time we published the roadmap in two formats: table-view in docs and board in YouTrack:1️⃣ Table 2️⃣ Board Which representation is more convenient for you to explore and use?
    etolstoy
    solidogen
    +3
    6 replies
    Copy to Clipboard
  • j

    Joffrey

    1 year ago
    Is there any ETA for the stabilization of the Opt-in mechanism? I had hoped for 1.5 but apprently this is not the case. It always feels strange to opt-in for the
    @OptIn
    🙂
    j
    louiscad
    2 replies
    Copy to Clipboard
  • e

    edenman

    1 year ago
    anybody know if iterating over sealed class subclasses (without using kotlin-reflect) is likely to make it on the roadmap anytime soon? super frustrating https://youtrack.jetbrains.com/issue/KT-25871
    e
    1 replies
    Copy to Clipboard
  • andylamax

    andylamax

    10 months ago
    It hurts when your lovely awaited feature is practically living in postponed section 😢
    andylamax
    s
    +1
    4 replies
    Copy to Clipboard