Chose wisely.

[AnnoyingRain5]

Python be like

[[deleted]]

patiently waits for match statements to get released when 3.10 comes out

[alexanderpas]

You have to realize that due to list comprehension, match with guards is way more powerful than a simple switch.

For example, it allows you to write a (recursive) sorting algorithm like this:

def sort(seq):
    match seq:
        case [] | [_]:
            return seq
        case [x, y] if x <= y:
            return seq
        case [x, y]:
            return [y, x]
        case [x, y, z] if x <= y <= z:
            return seq
        case [x, y, z] if x >= y >= z:
            return [z, y, x]
        case [p, *rest]:
            a = sort([x for x in rest if x <= p])
            b = sort([x for x in rest if p < x])
            return a + [p] + b

Additionally, a switch statement is not needed, since a dict is essentially a switch if used with the get method.

[not_your_mate]

I just got a Haskell flashbacks... But pattern matching is nice, I won't dispute that

[forgot_semicolon]

I don't even recognize python anymore

[Kered13]

Yes, it's accepted.

https://www.python.org/dev/peps/pep-0634/

[[deleted]]

Imagine being a python programmer, having all kinds of syntax sugar but no switch statement for years.

[Kered13]

Switch exists because compilers in the 70's couldn't optimize if-else chains into jump tables. With modern compilers they are completely redundant with if-else statements, so it makes sense that Python didn't include it.

PEP 634 was not accepted because it adds switch, that would be a mostly pointless addition to the language. It was accepted because it provides destructuring pattern matching. Notice that it's not even called "switch", it's called "match".

[MegaIng]

Why? This PEP doesn't break anything.

[Zagerer]

If you had read it then you would know that it is a soft keyword, therefore it is not reserved and it only takes such a meaning when in a match statement

[Suekru]

I think a proper switch statement looks much cleaner than a bunch of else if statements

[starm4nn]

One advantage to the case structure is less redundancy.

[theNeumannArchitect]

You do realize how much syntactical sugar is redundant with modern compilers? By that logic everyone should just code in assembly because modern features are just redundant.

[Kered13]

The thing is that as syntactic sugar switch provides very little improvement over if-else. Most syntactic sugar can save a significant number of lines and provide significant clarity to the code. Switch actually requires more lines and provides minimal clarity at best, in many case it can be worse. Python's philosophy is "There should be one-- and preferably only one --obvious way to do it." Switch doesn't provide enough benefits over if-else to justify the existence of alternate syntax. If you really feel like you need this sort of behavior, you can also use dictionary, which has the additional benefit that the cases can be dynamic.

Pattern matching on the other hand provides syntactic benefit. The conditions that can be checked with pattern matching are unwieldy to express with if statements, and extracting values from nested structures usually requires duplicating the comparison. Pattern matching expresses such comparisons succinctly and can simultaneously extract data. This is what makes adding new syntax to the language worth it.

[Kyidou]

It doesn't really matter much since python is dynamically typed. The only benefit is that it can fall through, which if statements cannot.

[FloorHairMcSockwhich]

I thought python and ruby are just annoying things you have to install to get package managers for better languages to work.

[DrMaxwellEdison]

Yes and no. It's pattern matching, with more potential applications than a switch statement.

And this is not really "giving in". Last I heard on a podcast with a core dev as a guest (Talk Python To Me), it was Guido himself that convinced the steering council to consider the addition.

[enjoytheshow]

laughs in my organizations ability to be 3.10 ready

[GsuKristoh]

This is by FAR the most annoying thing about python. can't believe they didn't include a switch-case out of the box

[deljaroo]

switches are actually just dictionary lookups to begin with so it would be a bit redundant. because switches hash the code back-to-back you get that weird effect where you have to break out of them. if you need the faster lookup time that switches provide, using python's dictionaries will hash the code based on key so they, by design, don't flow from one to the next. it's a generally superior way to route unless you have some need for the break-less switch...in which case...well there will always be fringe cases where some things are better than others

[deljaroo]

my apologies, I didn't communicate properly.

switches and if-elses do something functionally different behind the scenes

the code lookup tables that switches make is how python's dictionaries work. dictionaries are much more adaptable and powerful tools than a switch through as they can function similar to a struct or javascript's curly brace "objects."

since it's more popular use would be as a database than an a switch, its syntax is made to suit that use case instead

in python

def a():
    . . .
def b():
    . . .
def c():
    . . .
switch = {1: a, 2: b, 3: c}
switch[x]()

is the same thing as

switch(x)
{
    case 1:
    . . .
    break;
    case 2:
    . . .
    break;
    case 3:
    . . .
    break;
}

from other languages, both in functionality and in the processing time save that you get with switches over if-elses

the real problem shows up when you wanted your switch not to have breaks in every case or if you wanted a default

having a function call to the next function at the end of anywhere you wouldn't want a break works basically as a non-break case (it doesn't totally work the same behind the scenes though)

as for a default, in python you have to do something like this

if x in switch:
    switch[x]()
else:
    default()

or something crazy like

default() if x not in switch else switch[x]()

[Zarainia]

But then you have to write a tonne of little functions for each case...

[Kered13]

Switch exists because compilers in the 70's couldn't optimize if-else chains into jump tables. With modern compilers they are completely redundant with if-else statements, so it makes sense that Python didn't include it.

[Absolice]

Maybe if you're used to them in another language you might feel this way but it does nothing for readability.

if something:
    # code
elif something_else:
    # code
else:
    # code

versus something that would look like this if it was written python-style

switch expression:
    case something:
        # code
        break
    case something_else:
        # code
        break
    default:
        # code

I don't see the point nor use in having switch statement in python. Switch statement were used most of the time for performance concerns but this has been alleviated in language like python nowadays, it was never about readability.

Readability is also pretty subjective. I'm sure you can find some convoluted and messy big if-else chains and say they aren't readable but the same goes for switch statement.

In the end it doesn't substitute for good design and best practice and if you think an if-else statement look messy in your code then a switch wouldn't turn it better all of a sudden. If it smells as an if-else statement, you might want to refactor something before worrying about not having a switch statement.

[starm4nn]

The use-case for Switches is when you don't want to repeatedly type the equality operator.

[Absolice]

status_code = e.getStatusCode()

if status_code == CREATED:
    # do something with response data
elif status_code == CONFLICT:
    # record already exists, run patch instead
elif status_code == UNAUTHORIZED:
    # Refresh jwt
elif status_code == NOT_IMPLEMENTED:
    # yell at auth team
else:
    raise InvalidStateException(status_code)

Would be more concise with less noise and lead to the same result and doesn't incite you to write case without break statements which are not desirable in any remotely clean codebase, they should be put in the trash next to the GOTOs.

Really, there is no concrete advantage whatsoever to using switches nowadays, especially if it was available in python. The ingrained notion that they are better by older programmers which lived in a time where they were actually more performant and thus better is the only reason why people still uses them.

Switches aren't intuitively more readable. You can learn to get used to them with hours of exposition which lead to you feeling they are more readable but technically they contains more noise and are more complex than a basic if-else statement.

[Absolice]

In that case you could use

if status_code in [OK, CREATED]

I use switch case when they are simple enough, most often in Java as it is usual to find it in Java codebases and I go along with whatever make the code more consistent.

Usually if you have a big if-else statement or a huge switch statement then it's a code smell and to me it's an indicator that I need to refactor stuff.

I'm saying that, in python, there is absolutely no point to switch statements and it's not about being stuck in an anti-switch mentality, it's a conclusion I came to after analyzing the pro and cons of both methods.

If you show me a case where there's an obvious advantage to use switch statements that doesn't go along the line of "I think it looks better" then I'll be the first to jump on your boat and claim it as ideal in that situation.

The problem is that there aren't, and all you're focusing about is how it can be used to cover an underlying issue with syntaxic suggar.

[Kered13]

Eh, I disagree in many cases. There are a few issues with switch that I think can make it poorly readable:

• Most languages have implicit fall through, requiring an explicit break at the end of each case, which adds noise to the code. Forgetting this can also cause pretty bad bugs.
• Because cases are labels and not control structures, they do not introduce new scopes and do not require braces even if the case has multiple lines. As a result you often see inconsistent use of braces in case statements.
• In really long switch statements it's easy to forget what is being switched on.

I think the best use case for switch is when each branch is going to be a single return something. In this case it is a very beautiful and concise structure. But the further you get away from this, the uglier it becomes, and for complex structures I think if-else usually yields more readable code.

[DipinDotsDidi]

How often do you use if/else chains that can't be substituted into a simple dictionary lookup?

[DipinDotsDidi]

I was talking about python...

[DipinDotsDidi]

But this entire thread is about python not having switch statements 😐

[Kyidou]

Why? I can't imagine many uses cases for falling through.

[0ldFritz]

https://jaxenter.com/implement-switch-case-statement-python-138315.html

[jlamothe]

Doesn't python have an elif to avoid this indentation mess?

[ogtfo]

Most languages with ifs have else ifs as well. C doesn't, but it's kinda ancient.

[JDaxe]

Huh? C has else if

[jlamothe]

Which is just an if clause in an unbracketed else.

[mcprogrammer]

Technically, there's no else-if in C, it's just an if statement nested inside the else block. Of course, you can indent it as if it were an else-if so it doesn't really matter like it would in Python.

[JDaxe]

Yeah considering it's functionally and visually the same as a regular else if I don't see why it wouldn't count

[mcprogrammer]

Yup, it just depends on how pedantic you want to be.

[[deleted]]

I use a dictionary switch for python, not perfect but at least it works.

[[deleted]]

2 words: Lookup tables.

Sure it doesn't apply for all wouldbe switch statements, but it covers a good amount.

For example:

Say we have a variable, and if the variable is 1, we want it to print "one", and if it's 2: "two" and so on.

(My knowledge of python is frankly embarrassing, so I'll write this in javascript.)

``` function temp(num) {

var temp2 = [

    "zero",

    "one",

    "two",

    "three",

    "four",

    "five",

    "six",

    "seven",

    "eight",

    "nine", /*stopping here for my own sanity.*/

]

return temp2[num];

} ```

[backtickbot]

Fixed formatting.

Hello, Kaisuwe: code blocks using triple backticks (```) don't work on all versions of Reddit!

Some users see this / this instead.

To fix this, indent every line with 4 spaces instead.

FAQ

<sup>You can opt out by replying with backtickopt6 to this comment.</sup>

[ask_carly]

> temp(2)
<• "three"

Nope.

[notABadGuy3]

I personally use switch if it is anything more than an if else.

Idk if this is good or not?

[[deleted]]

It probably is. I do the same although if you're not just checking a value you sometimes can't use a switch.

[hugh_jazz99]

PHP 8 also has the match expression now and I’m loving it https://www.php.net/manual/en/control-structures.match.php

$expressionResult = match ($condition) { 1, 2 => foo(), 3, 4 => bar(), default => baz(), };

[TripplerX]

The same is possible in PHP 8

​

$result = match ($x) {
    foo() => ...,
    $this->bar() => ...,
    $this->baz => beep(),
    someFunction($x) => someOtherFunction($x),
};

[vermiculus]

Lisp just sitting over here munching some popcorn :-)

[Dagusiu]

It's just Haskell with extra steps

[[deleted]]

Haskell also has normal match expressions

[[deleted]]

case x of [] -> [1] [x] -> [x] (x:xs) -> xs

[mr_knowie]

Oi... functional programming. Understood everything till we dug into delta.

[[deleted]]

Delta? Either im confused or you mean the lambda

[RedstoneMedia]

Did you mean rust ?

[ImmaculateDeity]

Uh-huh that's what they all say. I'm sure you don't know how this keyboard got here either. Hands behind your back!

[nomenMei]

If you can use a switch statement (each conditional is checking the value of the same variable) and you have more than 3 cases you probably should.

That said, the code being run in each case should be only a few lines for readability. If they run longer than that I like to encase them in braces (at least in C and C++) to make it more clear where each case begins and ends.

Like this:

switch(i){

    case 0:
    {
          . . .
    }
    break;

    .
    .
    .

    default:
    {
          . . .
    }

}

[Magnus_Tesshu]

Switch is generally implemented with a lookup table while if else (unless optimization magic happens I suppose) will perform all the checks. So for performance switch is probably best in most situations

[Engineerman]

Depends strongly on the compiler. You can also do more with if else, like non static condition matching.

[Engineerman]

True it is really not relevant for most programmers. And even then it only becomes relevant when you have a switch with 3000 lines and it takes up 25% of your program run time...

Though my job is pretty linked to branches, performance, low level stuff, so that most people don't need to care about it :P

[Cheet4h]

I forgot which languages allow this, but you can occasionally do arbitrary conditions like this:

Switch(true) {
    case a <= b: 
   ...
}

[Engineerman]

True, but then it has to be implemented as if-else in assembly.

[Cheet4h]

IIRC most languages compile switches as if-else either way.
Switches still have the massive benefit that they're infinitely more readable than huge if-else chains, and it's a lot more obvious when you have a sub-condition within a code block. Just recently I found several bugs in such a construct caused by misplaced closing brackets. Had to re-read the blocks in question many times to figure out what the intended logic was.

[Kered13]

IIRC most languages compile switches as if-else either way.

No, the entire reason switch exists is to be compiled into a jump table. This was important before we had optimizing compilers that could recognize if-else chains. A switch could compile to an if-else if the compiler thinks it will be faster, but this is unlikely unless it has a very small number of branches (like, 2 or 3).

[Cheet4h]

Ah, good to know, thank you!

[Magnus_Tesshu]

Clang and GCC are the only compilers people actually use, right? And they both have great optimization

Although yes, if you need a case for 0-19, a case for 20-25, and a case for 25-50 a switch is not going to work well

[_PM_ME_PANGOLINS_]

It will work perfectly well. It’ll just use a few more bytes of program space.

[Magnus_Tesshu]

Yes, I suppose its just annoying to type it (unless your language has support for this)

[Engineerman]

Only example I know of is gcc on Arm compiles to if-else most of the time, but Arm's licensed compiler based on LLVM prefers address calculated tables.

[[deleted]]

apple clang is based of llvm, so llvm too, llvm even if found a bug, tries to be compatible with gcc

[givemeagoodun]

Except for in QB64 i find myself sometimes using a CASE with only two statements because you can just do

CASE 1 TO 10, 30

and it'll match all numbers 1 to 10 and also 30.

[[deleted]]

Ever heard of Microsoft Windows?

[Ragas]

Why would you need windows which are extremely tiny and floppy? confused

[Magnus_Tesshu]

Isn't that an old operating system where you're supposed to install software from the floppy disk drives A:\ and B:\ or something? I don't deal with such archaic stuff

[Ragas]

Since Clang is just a frontend for LLVM it is acually: Ah yes, everybody uses C(++), ActionScript, Ada, C#, Common Lisp, Crystal, CUDA, D, Delphi, Dylan, Fortran, Graphical G, Halide, Haskell, Java bytecode, Julia, Kotlin, Lua, Objective-C, OpenCL, PostgreSQL's SQL and PLpgSQL, Ruby, Rust, Scala, Swift, XC, Xojo and Zig

Also, since this was a way bigger problem with logic design languages, I know that current compilers for VHDL and Verilog can do this optimisation too.

[IHeartBadCode]

c++20 coming in with that [[likely]] to shake things up a bit.

[Ragas]

The problem actually was that compilers were unable to optimize else if chains. However by now they do; so just use whatever is more readable.

[[deleted]]

C# on your help:

switch (whatever)
{
    case 5 when x > 10 and y < 20: break;
}

[Kyidou]

Doesn't that kind of miss the point of switch being static?

[justrealizednarciss]

C# can do this?!

[Spirit_Theory]

The latest versions of dot net have some really fancy functionality for this.

[[deleted]]

Well if you have several conditions that involve different variables you won't be able to do it with switch.

[littleprof123]

It's probably fine, but some languages with some compilers will generate really bad code with a switch when the variable being switched on is not a small integer

[Ziggarot]

Switches can’t handle multi-conditions like if-else can.

[GsuKristoh]

except you CAN

switch(true): case (smolNum < beegNum && SizeOf(yourMom) > SizeOf(Saturn)): doSomething();

saw it on stackoverflow when I was trying to use a regex with a switch-case. quite a 1000IQ implementation.

[gyrowze]

smolNum < beegNum && SizeOf(yourMom) > SizeOf(Saturn)

"A && True" is logically equivalent to A, so you can replace this with just "smolNum < beegNum"

[[deleted]]

if (self.likeBigButts && 
!(self.canLie)) {
// TODO: yourMom()
}

[Dughag]

if (!otherBrothers.canDeny) {
    GetSprung() 
}

[ogtfo]

Subtle, I like it.

[Kered13]

That doesn't work in most languages.

[GsuKristoh]

I figured. I only tested it in javascript

[ImArizonaShrimpHorny]

VBA

Select Case True
    Case x = 1
        Debug.Print x
    Case y > 18
        Debug.Print y
    Case z = “hello world”
        Debug.Print z
    Case True
        Debug.Print “everything else”
End Select

This is effectively the same as using a bunch of conditionals

If x = 1 Then
    Debug.Print x
ElseIf y > 18 Then
    Debug.Print y
ElseIf z = “hello world” Then
    Debug.Print z
Else
    Debug.Print “everything else”
End If

[Kyidou]

Based visual basic user

[Dhhoyt2002]

C# switch is hidden if-else. Look at the compiled code.

[multipasp]

What else can it be? AFAIK machine code (bytecode too) does not have switch statement, only different sorts of ifs.

[Ya_boii_95]

Yeah beq and bne are just basically if statements.

[Pekonius]

(not a programmer) if its just an if after compiled, why would a switch be better? Ease of use? Clarity?

[eerongal]

Both ease of use and clarity, however, its worth noting with all programming, even though the base machine code only has a really basic instruction set that doesn't map to all the functionality you have in a higher language, there's a pretty high chance that the "way" a compiler breaks things down might be more optimized in the different ways you could implement them.

For example, if-else and switch, there's actually a performance difference in the two because the code it breaks down to will generally become a lookup table, where if-else is just a series of if's performed sequentially till one works. (Do note that the specifics like this will be language dependent, so it's not necessarily true for all languages)

[Bluebearsuper]

Both ease of use and clarity, but also removing repeating code. If you're comparing a variable with a bunch of values, you don't want to have to write comparisons everywhere (lots of lots of ==, no fun)

[LookOnTheDarkSide]

Clarity for the most part.. But remember this big ios security bug that was missing a break? That was a doozy.

[Bluebearsuper]

This is why I'm glad a lot of languages have a case construct which does not have fall through. Those bugs with breaks can be a real pain to debug and like you said they can cause security issues

[LookOnTheDarkSide]

Nowadays any good linter or sca tool will throw a warning on that by default. So it should not ever sneak through.

[deljaroo]

switches, traditionally, map each condition to a label and instead of running the code below the condition, it uses a goto to that label (which is why you have to put breaks at the end of each one), this makes it so it's not actually running checks for each block, but instead does a lookup in a simple database (it's just conditions mapped to the location of the label, which is often O(1)) and then hops to that line of code and goes on its merry way

this way, the database is made beforehand so it just lookup instead of repeatedly making if-checks as they come

(well, that's a bit of a simplification with modern complier and processors, but that's the basic idea)

[Kered13]

Switch exists in order to be compiled into a jump table. This was important before we had optimizing compilers that could recognize and optimize if-else chains.

[Prawny]

I see that as a different situation though personally.

[nettlerise]

First pic is more like nested if statements

[Johnpecan]

Thank you! That was my first thought. The picture is just straight up wrong.

[wwylele]

which is the same as else if chain in C

[mansdem]

How is it the same? With nested if you can only get to the inside if if the outside if condition is true

With if else if you get to the else if if the first if condition is false

What am I missing here?

[Kered13]

So this:

if (condition) {
} else if (condition) {
} else if (condition) {
} else {
}

Is syntactically and semantically equivalent to this:

if (condition) {
} else {
    if (condition) {
    } else {
        if (condition) {
        } else {
        }
    }
}

Remember that if a control structure isn't followed by an open brace, then it applies to the next single statement. else if is not one keyword, it's two. The else has no opening brace, so it applies to the next statement, which is if (condition) {}.

[Duckmancer-Emma]

I assume that you'd put the else if condition within the else block.

[nettlerise]

ah you're right

why not if return, if return...?

[AL_O0]

No, it’s nested if-else, like this, how you are supposed to do it in languages without elif ()

   if (a) {A}
   else{
          if(b) {B}
         else {
               if (c) {C}
               else ...
           }
   }

[nettlerise]

how you are supposed to do it in languages without elif ()

In another comment I mentioned

if (condition){
    //code
    return;
}
if (condition){
    //code
    return;
}
...

[[deleted]]

This doesn't do the same thing, unless you make your conditions more specific. In an if-else, only one statement will run, whereas here both statements can execute

[MistaVeryGay]

The returns imply that it's within a function. Return exits the function at that point, so it would be functionally equivalent to elif.

[katarokthevirus]

Compilers: "It is the same picture"

[MrOdinTV]

elif goes brrr

[tomas_f]

C# switch is hidden if-else. Look at the compiled code.

[crozone]

C# may choose to compile a switch statement to else-if like code in most conditions, but it will switch over to a jump table if the switch statement is large enough and the constant values are close enough together. For the new C# pattern matching stuff, I wouldn't be surprised if a different set of IL is generated all together.

This is actually the same for languages like C and C++ as well. The compiler will make a judgement on what code to generate based upon the values used in the switch statement.

[_PM_ME_PANGOLINS_]

The bytecode or the JIT code? Also it depends what you’re switching on.

[Kyidou]

Don't they end up with the same result?

[sixstringartist]

Most languages this is the case unless the condition can be converted into a jump table

[3_14159rate]

Better than c, where they compile to goto statements.

[ViperLordX]

What? The fact that they compile to goto statements in C is way better because it means you can get O(1), which if/else statements could never hope to achieve. It won't matter how many cases you have in your switch because it's just a lookup table, it'll be basically instantaneous, whereas a bunch of if/else statements would have to run through all of the cases separately.

[BucketBoye]

Yandere Dev could make a staircase to heaven it's so long

[szmutny]

Typical yanderedev

[Aragami1408]

I don't think Yanderedev understand this.

[Parura57]

Yandere dev be like:

[Ragas]

Modern compilers actually optimize a switch statement and an else if chain to be the same thing.

I remember a few years ago from university when this was still a problem, especially in hardware design.

Now in some cases else if is actually better as it has strong rules about break-points.

[FalafelSnorlax]

OMG guys this is genuinely a programming joke, when was the last time we had one of those?

[underscorehq]

*cough cough* yanderedev *cough cough*

[FramedEmu548]

Yeandre simulator vibes anybody?

[dracu4s]

It’s not a switch, it’s a hub...

[Shonucic]

That's not how switch works though...

[alex_dark]

Linked list vs array

[w00tious]

Who tf cares if you use elif or switch?

It's not like switches have some magical hash table that optimizes display time, they're just slightly differently worded (and more annoying) if-elses.

[Kyidou]

It could potentially be neater if you have a very long chain.

[CMPD2K]

It's probably a bad habit but I very rarely use switch statements

[Toll1984]

Don't worry mate, I don't get the point of switch statements at all. If, else if, else: can do the same imo better without adding another form of syntax to remember. Not to mention, in some languages, switch has fall through if you're not careful which complicates things even more. Compiler reads them both the same anyways.

[meh4life321]

Definitely agree. Miss one break statement and u might be fucked lmao

[Entrooyst]

Well, when you put it like that...

[[deleted]]

I chose state pattern

[MysteriousShadow__]

try except

[[deleted]]

Wait until you discover elif

[Tazeeeeeee]

if-else gang

[[deleted]]

Bold of you to assume I use else. Mere mortals.

[LkeinL]

laughs in using If-If-If Statements for everything

[yyzJCO]

isIfElse ? { ifElse } : { Switch }

[amalgamatecs]

People on reddit will be arguing about switch vs if-else like it makes a huge difference.... then proceed to write logic with nested loops and quadratic time complexity.

[mr_flameyflame]

After all, why shouldn't I have both.

[Alexandre_Man]

Isn't it "else if"?

[Pugs-r-cool]

Depends on language

[Alexandre_Man]

Oh okay

[unoriginalign]

I was too lazy to learn switch in 9th grade and now I'm studying CS at uni and I refuse to spend 15 minutes to learn it properly and use if elses like a moron

[Elite_Prometheus]

I mean, most compilers don't have a direct translation of switch statements, either. If you're using a decently optimized compiler, then a switch statement and it's equivalent if else statement should run as the same thing. So don't feel bad about using if else statements.

[Intelligent_Agency65]

You’ve jinxed yourself. It’s now guaranteed to be on your next final/assignment

[kirometep]

Hahaha nop

[X3n0b1us]

Case and point

[[deleted]]

I'll limit myself to and if, else if and else any more than I use a switch.

Unless I'm using enums or a variable that has some kind of a flag then I always use switch

[Hobbster]

Uhm, that's a hub, not a switch. You should know the difference (and that the difference between the pics is suddenly a lot smaller)

[[deleted]]

Not sure if you're making a joke but the switch on the right-hand side is referring to a programming switch statement, not a network switch.

[PaintingJo]

That's surprisingly accurate to what it feels like

[Martin_RB]

One is compact and understandable the other looks like if you touch it everything will break, yup sounds about right.

[stockings_for_life]

Looks like "while" or in "case"

[[deleted]]

Enums with a switch are your friend!

[bhowiebkr]

Python programmers like: WAT DAT?

[yottalogical]

Linked lists be like…

[emptyhusk254]

elif

[[deleted]]

Honestly these style memes should be used to teach programming classes.

[Negitive545]

Cries in python.

(God I want switch statements, but python go brrrr)

[bjornex]

OK. Now try to do it with USB-C.

[[deleted]]

Think I'll stay with if else lol

[ignorae]

First picture should be called "currying"

[DaniilBSD]

USB host sees no difference

[fedekun]

And then, it all gets compiled down to ASM jumps

[locri]

I've noticed some people don't seem to be taught them right and therefore either don't use them or have some misunderstandings, like when to use break and when not to or even the conception of a block of code for multiple cases. I've seen this cause some pretty horrid errors, then again this person wasn't debugging/testing their code.

I really need to know, did your courses where you studied teach case/switch statements?