Jacob Quinn
Jacob Quinn
The current version of JSON still has the behavior of parsing Ints as ints and floats as floats by default. "infinity" and "nan" are inherently IEEE concepts, hence with `allownan=true`,...
Yes, just a documentation issue.
I don't think this is a good idea to vendor: * The Base Ryu code is still evolving/maturing; there have been at least [6 PRs](https://github.com/JuliaLang/julia/pulls?q=is%3Apr+%22ryu%22) this year massaging the code...
> The point of vendoring this code is that `Base.Ryu` is free to evolve without breaking JSON.jl Base is already free to evolve? I know package eval is run to...
It was fixed via https://github.com/JuliaServices/StructUtils.jl/pull/22
Duplicate of #935
Hmmmm......I really like how short and sweet it is. Maybe AwsCommon. I have a couple of packages coming like AwsIO, AwsHTTP, etc. Doing all caps AWS just feels like way...
Sorry I forgot about this. Let's ping @fredrikekre, @StefanKarpinski, @KristofferC, and @Octogonapus to get their opinions. Namely, I have a suite of packages I'd like to register, mirroring the aws-c-X...
(also thanks for the quick review/feedback @goerz!)
@Octogonapus and I have come up w/ a new plan outlined in [this slack thread](https://julialang.slack.com/archives/C03R6JMQYUX/p1709951326201449) where we'll implement LibAwsCommon, LibAwsIO, LibAwsHTTP etc libraries. This PR can be closed.