Comment made by: mfikes
The copy in CLJS-2209.patch looks great to me. I really like how the material related to non-evaluation or evaluation of test constants is grouped into the middle paragraph.
For reference here is what the docstring looks like with the patch applied:
`
cljs.user=> (doc case)
cljs.core/case
([e & clauses])
Macro
Takes an expression, and a set of clauses.
Each clause can take the form of either:
test-constant result-expr
(test-constant1 ... test-constantN) result-expr
If the expression is equal to a test-constant, the corresponding
result-expr is returned. A single default expression can follow the
clauses, and its value will be returned if no clause matches. If no
default expression is provided and no clause matches, an Error is thrown.
The test-constants are not evaluated. They must be compile-time
literals, and need not be quoted. The only exception to this holds for
the use of test-constants that are symbols resolving to constant Vars
(Vars with ^:const metadata). In this case, the constant's value is inlined.
Please note that this behavior differs from Clojure, which will not inline
the value.
Unlike cond and condp, case does a constant-time dispatch, the
clauses are not considered sequentially. All manner of constant
expressions are acceptable in case, including numbers, strings,
symbols, keywords, and (ClojureScript) composites thereof. Note that since
lists are used to group multiple constants that map to the same
expression, a vector can be used to match a list if needed. The
test-constants need not be all of the same type.
nil
`
