88
Avoiding if-else Hell: The Functional Style (lackofimagination.org)
submitted 2 years ago by to c/programming@programming.dev
33 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] -2 points 2 years ago (5 children)

I can't find it right now, but there is some explanation in "Clean Code" why switches shouldn't be used all over the place.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 3 points 2 years ago (3 children)

    Google for "replace conditional with polymorphism".

    Just checked and it is in "Clean Code" - Chaper 17; Section G23 "Prefer Polymorphism to if/else or switch/case".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 2 years ago (1 child)

    This is really terrible advice. Sometimes it's better to do that, but definitely not in the example from this article.

    If anyone says you should always prefer polymorphism to switches they are a bloody idiot.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 2 years ago

    In case you’re wondering about the down votes, many think Clean Code is not a good book. It got a few good advice, but it also got bad advice disguised as good advice.

    I don’t think switch statements should always be avoided. There are cases where polymorphism makes things more difficult to maintain. Saying polymorphism should be used over switch statements is not a good advice.

    Here’s an article going into more detail why we should stop recommending Clean Code: https://qntm.org/clean

  • permalink
  • fedilink
  • source
  • parent