Add Support for Unsigned Integer Elements, Enhance JSON Encoding/Decoding Robustness, and Replace sprintf with Safer snprintf
#526
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update adds support for handling and accurately encoding/decoding unsigned integer elements in JSON, ensures compatibility with large values, replaces
sprintfwith the safersnprintffunction, and extends the test suite to cover edge cases for integers, unsigned integers, and floating point numbers.However, it does not address the suboptimal implementation where a single function handles both float and double types, which ideally need separate functions for better precision and clarity.