Jacob Quinn

Can you share the error you're seeing?

I have this pattern that I use when reading from a non-exhausting IO stream: ```julia # Threads.@spawn producer(io, n, outgoing_msgs, incoming_msgs, buflen) function producer(io::IO, n::Int, outgoing_msgs::Channel{Message}=Channel{Message}(n), incoming_msgs::Channel{Message}=Channel{Message}(n), buflen::Int=1024) # Create...

There were a couple of HTTP versions where this was an issue, but it should be fixed on the latest releases of both 1.9.X and 1.10.X series. Can you confirm...

This will be fixed in JSON.jl 1.0 where you can define an intermediate "chooser" definition, since otherwise, there's no way to know if the input should be deserialized as `E`...

This will be supported in the JSON.jl 1.0 release with the introduction of `JSON.lazy(x)` it returns a `LazyValue` that can be used to lazily navigate a json structure and then...

This kind of thing will be supported in the JSON.jl 1.0 release via new `JSON.tokey` and `JSON.fromkey` interface functions for non-string keys. Users will be able to precisely control how...

This should be fixed in the JSON.jl 1.0 release where we ensure `pointer(buf, pos)` is supported by the JSON source, otherwise the input is copied into an appropriate container that...

This will be fixed in the JSON.jl 1.0 release via use of a new `JSON.Object` Dict-like struct that is the default Julia "object" JSON objects are deserialized to. It has...

This will be handled in the JSON.jl 1.0 release by writing detected circular references as `null` and by default, null fields are omitted from output, so we get: ```julia julia>...