Should be able to encode-to/decode-from JS objects, not just strings

[favila]

Working from intermediate JS objects instead of going all the way down to string would be useful (and probably faster) in structured cloning contexts (indexeddb, web workers, etc). I am eager to create a pull request at least for the cljs side, but I wanted to gauge interest and feasibility.

[favila]

By "JS objects" I of course mean JSON-encodeable (or a least structured-cloneable) JS object/array/primitive trees, not arbitrary objects.

[micha]

You are talking about clj data <--> JS data ready for JSON stringification? Because the #'tailrecursion.cljson/encode and #'tailrecursion.cljson/decode functions do that.

[favila]

Yes you are right, didn't see those. Any reason these are not part of the public API?

[micha]

In the queue for next version. See here: #8.