== Why is this an issue?

A ``++switch++`` and a chain of ``++if++``/``++else if++`` statements is evaluated from top to bottom. At most, only one branch will be executed: the first one with a condition that evaluates to ``++true++``.


Therefore, duplicating a condition automatically leads to dead code. Usually, this is due to a copy/paste error. At best, it's simply dead code and at worst, it's a bug that is likely to induce further bugs as the code is maintained, and obviously it could lead to unexpected behavior.


For a ``++switch++``, the second ``++when++`` will never be executed, rendering it dead code. Worse there is the risk in this situation that future maintenance will be done on the dead case, rather than on the one that's actually used.

=== Noncompliant code example

[source,apex]
----
if (param == 1) {
  openWindow();
} else if (param == 2) {
  closeWindow();
} else if (param == 1) { // Noncompliant
  moveWindowToTheBackground();
}

switch on i {
  when 1 {
    // ...
  }
  when 2 {
    // ...
  }
  when 1 { // Noncompliant
    // ...
  }
  when else {
    // ...
  }
}
----

=== Compliant solution

[source,apex]
----
if (param == 1) {
  openWindow();
} else if (param == 2) {
  closeWindow();
} else if (param == 3) {
  moveWindowToTheBackground();
}

switch on i {
  when 1 {
    // ...
  }
  when 2 {
    // ...
  }
  when else {
    // ...
  }
}
----


ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

include::../message.adoc[]

include::../highlighting.adoc[]

'''
== Comments And Links
(visible only on this page)

include::../comments-and-links.adoc[]

endif::env-github,rspecator-view[]