you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 2 years ago (7 children)

This doesn’t get rid of the if statements. It hides them.

  • source
  • hideshow 7 child comments
  • [–] 16 points 2 years ago (1 child)

    It doesn't hide. It makes them happen first and, here's the important bit, closes their scope quickly.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 2 years ago

    The scope is irrelevant it’s a single function class as presented. It was a single method that they broke out “to hide the ifs”. Then they just used compiler specialties to remove the word ‘if’ from the assignments. The comparisons are still there and depending on the execution path those constants may not be so constant during runtime.

  • source
  • parent
  • [–] 3 points 2 years ago (4 children)

    It has conditionals not but actual if statements. Not really different in functionality but a more consistent style.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 years ago (3 children)

    They’re still ifs. They’ve just been lambda’d and assigned to constants.

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

    branching ≠ if ≠ conditional

    They're all related but can't just be used interchangeably. "if" is a reserved keyword to indicate a specific syntax is expected. It's not the semantics the author was trying to change, it's the syntax, and the overall point is that you aren't always required to use the specific "if" syntax to write code just like you're not required to use "while" to achieve looping.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 2 years ago (1 child)

    If you decompile that code you won’t get lambdas. You get ifs. Because that is how the hardware is build. Ifs/ands/Ors that is what computing is built on. Everything else is flavor.

  • source
  • parent
  • hideshow 1 child comment