Gary Fredericks
Gary Fredericks
The simplest case would be ``` clojure (json/generate-to-stream my-data) ;; returns an input stream ``` Then the input stream could be returned as the response body to the ring adapter...
I don't think this is solvable without the user having to give information to the parser about where the byte arrays are.
I think long would be better if there aren't any performance issues. I assume large enough integers are already returned as longs?
This has been a big pain point for me as well. One option I just thought of is to have another option that can be passed of a `:fallback-encoder` --...
Though now that I look through the implementation I remember that options are passed around as first-class args, and so having an extra option means expanding the signatures everywhere :/
If the signature thing is a big perf deal, maybe an internal dynamic var that gets set once at the top level would be an alternative.
I'll see if I can quickly make a branch with the options-map change.
do you just mean destructuring when you don't actually need all the keys? When I macroexpand a `{:keys [foo bar]}` destructuring the only extra thing I see is a `(seq?...
okay; it ought to be identical to the macroexpanded code, but regardless I will leave it out so we don't have to wonder
Okay I have some code [here](https://github.com/gfredericks/cheshire/tree/options-map) that seems to work except for some bug in the generate-seq code that I don't have time to chase down at the moment. Hopefully...