Issues found while developing and using speculative

Issues are sorted by date from newest to oldest.

Unfixed or unreleased

• Add support for undefining a spec (port of CLJ-2060) (CLJS)
• Unify behavior of shuffle in CLJ and CLJS (CLJ)
• Spec'ed fn doesn't throw when called lazily (CLJ)
• stest/unstrument is called at unexpected time when used in finally block (CLJS)
• Remove useless call to merge (juxt/yada)

Fixed and released

• Instrumenting next gives maximum call stack size exceeded (CLJS)
• Requiring clojure.spec.test.alpha loads clojure.test.check (CLJS)
• Unify namespace for interacting with clojure.test.check (CLJS)
• + can't be instrumented in Planck REPL (Planck)
• Instrumented self-calling multi-arity fn throws maximum call stack exceeded with optimizations advanced (CLJS)
• re-seq is relying on undefined behavior of subs (CLJS)
• unstrument returns symbol of non-instrumented var (CLJS)
• Coal-mine test found use of merge that doesn't conform to spec (4clojure)
• Make clojure.spec.alpha reloadable (CLJS)
• Stack overflow when specing core = (CLJS)
• Self-host: spec check macro compile-time expansion (CLJS)
• stest/with-instrument-disabled prints warning of private use (CLJS)
• Stack overflow calling instrumented variadic fn with zero args (CLJS)
• merge-with being passed seq of lazy-seqs (gf3/secretary)
• Update merge-with to use key / val (CLJS)
• spec fdef triggering for variadic fn (CLJS)
• Can't define nilable spec on undefined pred (CLJS)

Other known issues related to self-spec'ing Clojure

Open

• [spec] :clojure.spec/invalid is not a valid :clojure.spec/any value (CLJ + CLJS)