A Brooks

I'm leaning toward the latter option (the `:warnings` map), for what it's worth. That would let us support warnings that are turned off by default (perhaps because they're alpha) and...

@humorless Yes, that's tricky. I'm not sure there's a great way to do key-value command line arguments. (I found some discussion [here](https://stackoverflow.com/questions/18115674/how-to-format-command-line-argument-key-value-pairs)). Maybe we could use an approach similar to...

> By the way, I somewhat prefer to delay the command line argument design for later PR. I really think that is there really a need to control kaocha to...

A possible refactoring would be a function that outputs using the correct level based on the warning. For example, `(notify warnings :some-key "message")` so we don't have to repeat the...

I read an interesting proposal by Zach Oakes from a few years ago about interactive examples: https://gist.github.com/oakes/8db57ac808bf6ec144d627fd83a89da3. Adding interactivity is too much for the first version, but I think we...

Codox actually has interactive examples that have no expected output: https://github.com/viebel/codox-klipse-theme. Unfortunately, I'm not sure we could use their format easily. More prior art: * https://github.com/Kobold/clj-doc-test works like the similar...

This syntax might be too heavyweight, but we could also introduce a `with-doctests` macro: ```clojure (with-doctests (defn my-sort [s] (sort s)) (sort [4 3 5]) [3 4 5] (sort nil)...

rich-comment-tests takes a slightly different approach: https://github.com/matthewdowney/rich-comment-tests. It also uses `=>` but the example has them on the same line. They already have `clojure.test` integration, so it may work with...

Hyperfiddle also has their own version (which apparently inspired rich-comment-tests): https://github.com/hyperfiddle/rcf

Issue has been fixed in https://github.com/cloverage/cloverage/pull/349 and merged (although not released yet, unfortunately), so no need to keep this open.