sadly, this doesn't seem to support any sort of multithreading. Even something as simple as swap! isn't thread-safe in this implementation. So that kills one of the main reasons to use Clojure in the first place.
Maybe multithreading is just not yet implemented?
> So that kills one of the main reasons to use Clojure in the first place.
I could see ClojureC being very useful for when you want:
* small footprint
* easy C-library interop
* fast start-up time
(BTW, I'd be curious to hear what you think might be the differences in use cases between ClojureC and mjolnir/clojure-metal.)