for exhaustivness

# getting-started

[ursus]

for exhaustivness

[Shawn]

if callButtonState isn’t just an Int, sure, I guess, but why would this need to be exhaustive? these methods look like they’d return Unit, so the when doesn’t look like it’s assigning anything useful

[ursus]

I see your point, the question was just seeing if its possible

[ursus]

actually its what should happen after a button click, (and yea its enum, just int for speed writing the pseudocode)

[Shawn]

it’s just that I can’t think of a case where you would both need to be exhaustive and have a branch that does nothing and therefore be cool with the fact that the when implicitly returns Any

[Shawn]

you wanna eliminate the {} when Kotlin lets you eliminate the case entirely

[ursus]

but then it will complaing about it not being exhaustive

[Shawn]

?

[ursus]

linter I guess, warning..

[Shawn]

when is only required to be exhaustive when used as an expression

[ursus]

say I have enum { FOO, BAR, NONE } .. when(foo) ..

[ursus]

oh thats your point...

[Shawn]

oh I see, it’s recommended to be exhaustive

[ursus]

..I still get warnings, even I am not returning from when

[Shawn]

that’s a weird thing to have enabled by default

[ursus]

I honestly like it, but that formatting messes up niceness of code for me 😄

[ursus]

but I guess could have noop: Unit function

[Shawn]

you may as well just have case -> Unit

[ursus]

yea, because now when I thing about it, if when is expression I would need to return something anyways, not just Nothing, okay thanks

[Shawn]

I guess technically speaking the JB guys would rather you use an if/else if for this kind of scenario but I still think it’s dumb lol

[ursus]

hh

[ursus]

I wont since I dont have ternary operator lol