Using the keyword switch for successive condition testing is a travesty. Switching means taking one of several code paths based on a value. The problem with using a switch syntactic sugar for conditional testing is that the cases are not exclusive:

  switch {
    a > 5:
         ...
    a > 3:
         ...
  }

Here a > 3 is not reachable: it tests a condition that overlaps with a > 5 completely, and a > 5 is earlier.

This form of switch would be useful (and actually live up to the name) if the compiler were required to diagnose against overlapping cases, and also incomplete cases.

  switch {
    a < 3: ...
    a > 5: ...  error: domain of variable "a" not covered in switch without a default: clause
  }

  switch {
    a > 10: ...
    a > 5: ...  error: overlapping cases in switch
  }