https://kotlinlang.org logo
Join Slack
Powered by
How confident are you that no major modifications ...
# arrow
c
How confident are you that no major modifications will happen between 1.2.0-RC and 1.2.0? I'm considering starting the migration, I obviously don't mind small renames or changes (that's what RCs are for) but I'd rather avoid to do other sweeping changes. Or should I just wait?
s
The point of the RC is for everyone to try, and we will only change it if there is a good reason in discussion with the community. Actually, it was done so that if anything that we 
@Deprecated
proofed to be crucial for the community that we could decide to remove 
@Deprecated
so no changes are expected.
It's explained in the release post, and migration guide but I guess we should've been more explicit about it 😅
c
I'm starting the migration tonight, then. I hope it doesn't feel too limiting not to have context receivers.
s
It shouldn't at all, please let us know if you encounter anything.
c
Well, I'm going to want to make everything an extension on Raise and I'm very quickly going to hit the single-receiver rule
s
Ah ye... 😕 I'm really putting all my prayers towards a context receiver announcement at KotlinConf 🤣 I just want to use them everywhere at this point.
c
...I wish, but I'm not counting on it. They've been fairly clear that they're not working on it before 2.0
I assume the keynote will mention them heavily though
s
Yes, I know. I am more hoping on something along the lines, of K2 is coming (soon) and these features will get stabilized first (including context receivers).
c
I really hope context receivers are the next biggest priority after K2. I've never seen so many library authors this hyped by a language feature
p
@simon.vergauwen Don't we have a 6 month release cycle? As of now we can expect any changes related to context receivers only in 2.1 which is more than a year away... Are you really hoping that they skip announced 1.9 and 2.0 with K2 is already around the corner?
c
Honestly, I'd love to (if 2.0 is ready, of course).
s
No, I am not hoping or expecting anything. I am dreaming of an announcement where 
1.9
and 
2.0
could be closer to each-other than 6-months, since 
1.9
brings the last changes and 
2.0
is the turn-off point of the old compiler. Like we could've released 
2.0.0-RC
today alongside 
1.2.0-RC
, the branch is ready 😅 Since we just got 
1.8.20
1.9.0
could land soon-ish, and 
2.1
or 
2.0.1
could bring KMP experimental context receivers at least build in K2. That'd already be awesome. 
2.1
or 
2.2
could then be beta, which in Kotlin terms means stable.
c
could then be beta, which in Kotlin terms means stable.
🤣
One day, contracts will be stable. Not like they're not already in all libraries…
Well, KotlinX.Coroutines' 
TestScope
will be stable in the next release, that's already going to remove a lot of 
OptIn
from my codebases
s
That points in the direction that 1.9/2.0 are closely related. My dreaming can continue 😂
6 Views
Open in Slack
PreviousNext
Powered by