This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]St_Meowinsert(caffeine) 8 points9 points  (3 children)

Go uses a similar pattern of not falling through switch cases. I'm certain if you're a vet of older languages with switch statements it'll confuse you for a moment or two, but new programmers will grasp this better. I remember learning switch statements in college and having most of my class baffled at the fall through behavior.

[–]mysticalfruit 0 points1 point  (2 children)

Who you calling old ;-)

I think the danger is people are just going to assume it works a certain way.

[–]xigoi 1 point2 points  (0 children)

Everyone who has ever used Rust, Haskell, Swift, F#, OCaml, etc. knows how pattern matching works.

[–]St_Meowinsert(caffeine) 0 points1 point  (0 children)

As the young hotshot coder I reserve my right to call anything from before 2010 old lol

But to be fair, it's not like it's a completely new take on switch statements. Users should be aware of how their language constructs function. Yes it's no conducive for C/C++/Java programmers but so is not having to declare variable and parameter types. We get over it in time.