telegram-cloud-photo-size-2-5316709178309457116-y.jpg
r
telegram-cloud-photo-size-2-5316709178309457116-y.jpg
👀 1
message has been deleted
K 3
K 2
🙏 2
message has been deleted
c
ah. cant wait for exhaustive when statements!
g
cant wait for exhaustive when statements!
It works even with 1.5.31 with progressive mode
d
I have to admit, I feel like I'm missing some of the excitement about this one. I mean it's only right that the compiler will enforce this, but the IDE has been inspecting it since as long as sealed classes have been a thing, which for me already brings 95% of the practical benefit. I'm missing something... what is it? Safety at CI time?
c
safety at compile time yeah. the IDE only gives you a yellow little squiggle. I've been using the cashapp/exhaustivewhen repo to enforce this. so im looking forward to dropping it.
👍 1