Michał Muskała

Ah. Thanks. I think such a feature indeed makes sense. I even did some work on implementing it in https://github.com/michalmuskala/jason/pull/3, but ultimately abandoned it before 1.0 due to complexity, but...

As mentioned in #34 if your JSON is line-delimited (and in most "streaming" cases it actually is), the problem is trivial - split on newlines and feed each part separately...

I can't really reproduce. Both of the ways of encoding those codepoints (escaped and not) work just fine for me: ```elixir iex(1)> "\"\\uFE0F\"" "\"\\uFE0F\"" iex(2)> Jason.decode!("\"\\uFE0F\"") "️" iex(3)> "\"\uFE0F\"" iex(4)>...

It's likely that the data you're receiving is not encoded in UTF-8 - Jason only processes JSON data encoded in UTF-8 as defined by latest standards. You could check with...

Given no way of reproducing the issue, I'm going to close this.

Yes, but we can't use `serde` directly - the problem is that it is not pre-emptive, so we can't use it with regular NIFs. It's true we have dirty schedulers,...

The easiest way would be to maintain the parsing stack as a data structure threaded through the functions instead of using recursive calls - this means we can always interrupt,...

I don’t mean it’s not thread safe - it is. Preemptive means we need to be able to pause the execution of the parser/generator at arbitrary moments to yield the...

After 5 years, I finally got around to this. Check out https://github.com/spawnfest/json_native!

Yeah, I broke my website. Working on getting it back up!