open-source-parsers / open-source-parsers/jsoncpp
Need 128bit unsigned. (supported by GCC)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.9k
- Forks
- 2.7k
- Avg merge
- 31m
- Merged PRs (30d)
- 1
Description
Greetings,
Is there a plan to support uint128_t? GCC has native 128bit unsigned integer support via __int128. I can try add it, but will need it to be upstreamed for good reasons. My use case is NETFLOW 9+ protocol can send 16byte length values in fields which I need to process into JSON. An example is IPV6 Address which needs stay in numeric form.
Thank you in advance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named in the issue. Start by locating the existing numeric JSON value and serialization entry points, then assess how GCC __int128 would represent NETFLOW 9+ 16-byte values and IPv6 addresses. Done means the support scope is defined and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100