I think I am tired.

I almost did a switch-case on a boolean.

Bro get some sleep

Damn, get some 10 hours of sleep...

Out of curiosity:
Why even use switches? For me theyre hard to read and serve no purpose.

@Strazdonis Because having 10 if for an enum is annoying to read to me

@rEaL-jAsE Wh.. why?

Well, switch(true) works, it'll choose the case that is true..

Maybe you can do a switch case on a nullable Boolean.

@Strazdonis gonna need more than 2 hours of sleep...

By design switch performance is O1. If-elif tree performance -- o(n). Switch calculates the exact jump spot and sets eip immediatelly while if-elif does that using sort of a bruteforce.

Also switch cases are quite often easier to read when used properly, because they rely on a constants.

[someone above asked why use switches over ifs]

@Brosyl well, in checkboxes for example. Checked is true, unchecked is false, null is when no choice is made. You need a switch case to check those.

@netikras thanks a lot it is a lot clearer for me now! I've never seen a switch that was easy to read for me though :/

@Brosyl C#. But it appears to exist in Java as well, since version 8. In Typescript as well I think.

@DodgerAkame that's why you use polymorphism instead.

You can do that in some languages (kinda), it’s called pattern matching. Check out Rust!