Chris Rink

Thought of while working on #671

https://docs.cider.mx/cider/indent_spec.html

I think in order to do this, we'll need to have some reader function which provide comments as part of the concrete syntax tree.

https://github.com/kkinnear/zprint feels like a nice option too.

I'm not entirely against the idea. The main reason I used `make`/Makefile before is because it was a convenient tool that every Linux/MacOS device has installed by default (thus requiring...

https://technomancy.us/143

Updated list: ``` *' *agent* *allow-unresolved-vars* *clojure-version* *command-line-args* *compile-files* *compile-path* *default-data-reader-fn* *file* *flush-on-newline* *fn-loader* *math-context* *print-namespace-maps* *read-eval* *reader-resolver* *source-path* *suppress-read* *unchecked-math* *use-context-classloader* *verbose-defrecords* *warn-on-reflection* +' -' ->ArrayChunk ->Vec ->VecNode ->VecSeq...

I think we should throw an error when building a `defrecord` with invalid field names.

Let us go with `basilisp.edn` then. When this is added, we should note that the contents of such a file is as yet unspecified.

In working on #643 I investigated a few different options for trying to thread the line number corresponding to the `(are ...)` form into the generated `(is ...)` assertions, but...