IMO, it would be more readable to just use ifs most of the times. But switch-case fallthrough is indeed, interesting behaviour
this post was submitted on 16 Feb 2024
6 points (68.8% liked)
C Sharp
1526 readers
31 users here now
A community about the C# programming language
Getting started
Useful resources
- C# documentation
- C# Language Reference
- C# Programming Guide
- C# Coding Conventions
- .NET Framework Reference Source Code
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
founded 1 year ago
MODERATORS
Agreed, multiple if statements are much more readable, in my opinion. I generally think switch statements are always just a little too ugly unless their dead simple.
Switch expressions, on the other hand, are gorgeous code (as long as you don't use expression-bodied cases). I am always looking for chances to use switch expressions. So concise
When the if/else is large I'm in the dictionary of functions boat.
That doesn't sound very effective though.
It works for older platforms that only run CF 3.5
Is CF still a thing? But anyway, if it works, it works :)
Why post a stack exchange from 2008?
Because it is about a not-very-well-known feature of the language. Why would it matter that it's old? I don't think I have ever seen this in use in production code.
An explanation like that at the start would have been helpful. I was reading the page and just didn't understand. Was thinking at first it was to raise awareness of an unanswered question. Couldn't figure it out so I asked.