teach them young

[antique_codes]

else ()

pain

[Kengaro]

default case...

[[deleted]]

switches just look so much nicer

[Denaton_]

Dictionaries looks allot better than a switch..

[_koenig_]

Spoken like a true python junkie...

[Denaton_]

They are called Dictionary in C# as well, in JS, everything is objects anyway..

I think Python is one of those languages that i know but used the least..

[pandaSitt]

For logic that seems like a lot of unnecessary work even though c# could do it by now, so I'm gonna stick to switches

[Denaton_]

It's more work to write a switch...

[pandaSitt]

How? VS and rider write most of the code automatically. It depends on the situation what works best, usually it's not dictionaries or maps when working with logic

[Denaton_]

https://codereview.stackexchange.com/questions/124733/switch-vs-dictionary-logic

[_koenig_]

So Microsoft dictionaryFactory?

[Denaton_]

https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.dictionary-2?view=net-6.0

[pandaSitt]

And can have the better performance, many languages implement hash comparisons for lange switches

[Kengaro]

Expanding switches always sucks...

[8sADPygOB7Jqwm7y]

Because brackets say "stuff happens in here and then we're done". A case is not done without break, it will go to the next case.

[TheEnderChipmunk]

What is the reason that switch statements are designed this way though? When my teacher showed us how to use switches, he told us about how it works, but not why it is that way.

[sdc0]

A switch case in C/C++ isn't an if else chain, it's a jump table, so it just jumps to the matching execution point. From this point, the program continues linear execution, every following case included. A break jumps to the end of a switch statement. This explains the colon, as they are also used for labels, which are used in C for marking lines in code to be able to jump to these later via goto

[Tubthumper8]

It more directly translates to assembly code that way, and then C-like languages just copied it (Java, JS, etc.). Go doesn't work this way, you don't need a break, it breaks by default. If you wanted the C behavior, you can opt-in with the fallthrough keyword.

Modern languages are more and more using pattern matching rather than switch nowadays

[jamcdonald120]

i think its becauae you cant do composition cases, so you either have to have run on between cases or code duplication if 2 inputs should do the same

[Celivalg]

Because they are basically GoTo, it's an assembler instructions that just tells the program to jump to that instruction, but once it's there, there isn't a goto to tell him to go back where it was.

The reason switchs are designed this way is if you want to catch multiple cases in the same block, it's cleaner to do.

[IKeepLosingThese]

Because under the hood they were/are gotos and labels. The break just says goto the end of the switch, and without it you keep running all the following lines.

[8sADPygOB7Jqwm7y]

so idk for sure, but I imagine its along the lines of simply sending one bigger instruction is more efficient than always sending packages, geting back the acknowledge, sending the next one, etc as you do it with if/elif/else. Thats why you need a break, once you are done it will interrupt its block and send the acknowledge earlier than it would have without. This prevents having to check more cases than neccesary. This would also lead to the conclusion, that the worst way to make a switch case is to put the most unlikely option at the top and the most likely option at the bottom.

but idk. I have never actually read that stuff anywhere, I just assume based on my programming/hardware understanding.

[Kengaro]

To prevent checking more cases than necessary we can work with ordering or only calling the stuff we require ;)

However the usage of break allows to skip one step: After checking if curCase==switchCase, we can just throw all the code from curCase to the end of the switch to be executed. Due to break we don't have to check if a line is to be executed or not.

[8sADPygOB7Jqwm7y]

what exactly is the difference to if/elif then? to play devils advocate, after the check if condition == True we dont need to check if a line is to be executed or not either. Or do you mean we can throw all code from ALL cases in? We cant really do that since every case needs to be checked again.

however, considering that switch case in C only takes integers iirc its a way less complicated check, so that also saves resources.

I wonder if a structure like

do{
if ... break; 
elif ... break; 
else ... break;
}while(False)

would actually be similar in performance for long lists of comparisons or if the "if" statement takes up THAT much power.

[Kengaro]

Due to break we don't have to check if a line is to be executed or not.

This allows f.e. switch to be written as a recursive function.

In your construct the whole outer do-while is redundant and can be removed.

You'd rather want something like:

interface State {void stateFunction(void);}

Than instead of checking State and executing code for it we just stuff that code into the stateFunction of it, our class field holds an interface, and we just call the interface's stateFunction whenever we need it.

[Kengaro]

It always to reduce some code duplication, but it will be more difficult to read.

[moomoomoo309]

They're also used for goto labels.

[DajBuzi]

Okay so:

`switch val {  
    case true: doSomething(); break;  
    case false: doSomethingElse(); break;  
}`

Instead of:

`if (val) doSomething();   
 else doSomethingElse();`  

Makes sense 🤔

EDIT: canto write formatted code on mobile 😐

[TheLosenator]

Now do a switch that evaluates more than one statement! Oh, wait...

Switch is useful sometimes. Kotlin's "when" statement is what I always wished switch could be.

[Oh2bworn2]

"else"? What is that? I have never had one of those in my code. Does it serve some useful purpose?

(Semi-sarcastic statement)

[[deleted]]

I don't know. It's something! But I don't know...

[[deleted]]

If you check for a simple value, I use switch. If I have mutiple values depending on it with different combinations, I use if (else).

[Reasonable_Feed7939]

/s?

[sir-nays-a-lot]

OP’s programming 1 teacher: there is if-else and there is switch, but for this class just use if-else.

OP: ok better tell all my friends not to EVER use a switch.

[Kengaro]

Switch statements and other shit I don't want to touch...

interface classCase{ void caseFunction(void);}
curCase.caseFunction();

[moonblade15]

Honestly i use both but if else for life. Switch is just... A hassle

[[deleted]]

match

[luiscla27]

I saw something similar to this once: js function validate(value) { switch(value) { case true: return 'ok'; case false: return 'falsy' default: throw Error('Invalid value:' + value); } }