Closed illia-li closed 1 month ago
Please add the information about what are you fixing in the commit message
@illia-li , @sylwiaszunejko , on some systems int
/uint
is 32 bytes, on some 64, we need considering this on marshal/unmarshal.
And I think this PR is good place to start doing that.
I think we need first to come up with what is the "correct" behavior and then align code to it.
Issue was created: #307 This PR will be closed until a decision is made on the #307 issue.
All
int
likecql types
havenegative
range andpositive
range, butuint
likego types
have onlypositive
range. For example, if cast-1
tinyint
[]byte("\xff")
intouint like
go types
we got255
.In the old marhsal/unmarshal functions (before the starts redesign), this problem was solved in different ways. Now marhsal/unmarshal functions (before the starts redesign), allow the processing with a negative range of the
int
likecql types
for alluint like
go types
. But this can lead to problems due to the differentDB
andGO
representations of the same values .So, my suggest to leave only one way - stop the processing with a negative range of the
int
likecql types
for alluint like
go types
.