Issue #178 - Extending support to full uint64_t/int64_t range and unsigned type (updated) #193
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
nlohmann
added a commit
that referenced
this pull request
Jan 26, 2016
Issue #178 - Extending support to full uint64_t/int64_t range and unsigned type (updated)
|
Thanks so much!!! |
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 pull request is based on pull request #183 and has been created because that pull request was accidentally made from the master branch and that was creating difficulties in managing my fork. Please refer to pull request #183 for details of discussions prior to the creation of this pull request.
Additionally, some changes from #183 have been split off to enable them to be applied independently (in particular to version 1.0.1).