fix: Big Number support for incrementors in redis #149
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.
Big Numbers (mostly seen in token total supply, etc) will cause crashes unless we use
INCRBYFLOAT
.RESP3 lays out how much memory we can use for Big Numbers (64 bits)
You can try the command with and without
INCRBYFLOAT
using a large 64 bit unsigned integer or signed integer to see the difference it makes.