-
Updated
Oct 1, 2020 - Java
json-parser
Here are 860 public repositories matching this topic...
-
Updated
Oct 3, 2020 - Swift
-
Updated
Oct 3, 2020 - C++
https://github.com/simd-everywhere/simde has done their first release ( https://simd-everywhere.github.io/blog/announcements/release/2020/06/21/0.5.0-release.html ) and it seems like something potentially useful for merging code paths. The most likely candidate I imagine is using SIMD code to replace the non-SIMD fallback path, but maybe it'd be worth checking if it can be used to merge ARM and x8
-
Updated
Sep 9, 2020 - Go
-
Updated
Aug 7, 2020 - Go
-
Updated
Sep 23, 2020 - Java
Hey folks, thanks for a pretty bad ass library! I'm seeing a 3-3.3x gain when decoding fairly large JSON payloads (40-50MB) as compared stdlib/json-iterator.
Few things in the generated code that struck me as odd are the allocation sizes for slices/maps:
- Slice is set to size 1 initially, values are appended using
append
- Map does not have a default size specified
Instead of this, I
-
Updated
Sep 5, 2020 - C
-
Updated
Feb 21, 2020 - Elixir
-
Updated
Oct 2, 2020 - Java
-
Updated
Sep 15, 2020 - Go
-
Updated
Sep 2, 2020 - Scala
-
Updated
Sep 15, 2020 - JavaScript
-
Updated
Jun 30, 2020 - Ruby
-
Updated
Sep 21, 2017 - Rust
-
Updated
Feb 18, 2020 - Go
-
Updated
Sep 9, 2020 - Scala
-
Updated
Aug 13, 2020 - Go
-
Updated
Sep 22, 2020 - C
-
Updated
Sep 2, 2020 - C++
-
Updated
Feb 19, 2020 - Python
-
Updated
Oct 1, 2020 - C++
All exceptions in namespace JsonMachine\Exception
should extend one common exception, say JsonMachineException
, so that userland code can catch for only one type and catch anything from this library. Fell free to create pull request and participate :)
Improve this page
Add a description, image, and links to the json-parser topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the json-parser topic, visit your repo's landing page and select "manage topics."
I think we should patch test/CMakeLists.txt to always use
-Wall -Werror
on *nix and the corresponding MSVC flags. It is way too easy to overlook a warning in the CI output as #1797 has shown.@nlohmann Thoughts?