4 ms·
I fail to see how a simple switch statement doesn't read just as easily. I mean, sure I have to know the mod 15 trick, but... not exactly hard. function f
by taeric 12y ago
I fail to see how a simple switch statement doesn't read just as easily. I mean, sure I have to know the mod 15 trick, but... not exactly hard.
function fizzBuzz(i) {
switch(i % 15) {
case 0: return "fizbuzz";
case 5:
case 10: return "buzz";
case 3:
case 6:
case 9:
case 12: return "fizz";
default: return i.toString();
}
}
[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15].map(fizzBuzz)
- chrismorgan 12y agoEven that is better in Rust (using the enum from the end): match i % 15 { 0 => FizzBuzz, 5 | 10 => Buzz, 3 | 6 | 9 | 12 => Fizz, _ => Number(i), }
- taeric 12y agoI actually agree it is better. But... my point was that the switch statement was already pretty readable. If there are gains, they feel pretty small in these examples. And to be clear, I like pattern matching. A lot. I just don't feel this really shows it off that well.
- icedog 12y agoWhat do you expect; it's FizzBuzz.
- mattmanser 12y agoOnly because you're expecting the cases to fall through, you're being blinded by your own expectation. Your code is considered bad practice in many languages.