nah its great, kitchen sink.

# announcements

[groostav]

nah its great, kitchen sink.

[groostav]

@Shawn I created akotlin discussion post on this, lemmi know what you think:

https://discuss.kotlinlang.org/t/a-good-bad-idea-use-a-constraint-solver-to-proove-when-exhaustiveness/5632

[Shawn]

honestly this is a bit out of my wheelhouse, so I don’t have a whole lot of useful input here 😅

[Shawn]

but considering that the language works pretty well without the inclusion of an SMT solver, and the fact that when defaults to “safely” error if the statement isn’t trivially determinable to be exhaustive, I doubt anyone working on the compiler is going to consider this kind of thing for a long while

[Shawn]

Kotlin’s overall a pretty pragmatic language, and this is decidedly not the most pragmatic option

[Shawn]

at least, perhaps, until someone figures out whether or not boolean satisfiability even has a polynomial time algorithm 😛

[groostav]

hahaha, my thoughts also, but I guess the question I'm trying to get at is when will it become pragmatic?

[groostav]

when jetbrains revenue cracks the 10 Billion mark?

[groostav]

😄

[Shawn]

haha, if computational complexity theory could be solved by throwing money at the problem, Google, Apple, and MS would have already figured out P vs NP a long while ago 😛

[dave08]

You could always else -> throw SomeNeverToBeSeenException("I'll hopfully never see this") even w/o sealed class... 😜