Fix #1103 - add explicit operator support for ulong on RedisValue #1104
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.
context: #1103
This necessitated a new sentinel value for handling very large (64-bit)
ulong, as we need to encode/decode them differently (obviously, they're not large negative numbers) - but we treat everything up to 63-bit as the previouslong, for simplicity.Adding these operators made some of the other operators ambiguous (from the compiler's perspective), so additional operators were also added to make this work without complaint.
Additionally:
Utf8Parser) were exploited