Repository navigation
GH-35067: [JavaScript] toString for signed BigNums - #35067
Conversation
BigNumsBigNums
|
|
|
|
BigNumsBigNums
|
|
BigNumsBigNums
|
|
trxcllnt
left a comment
There was a problem hiding this comment.
Looks good to me, thanks @aljazerzen!
9a226cd to
7fe2dd5
Compare
|
I've spent a little time trying to get tests to pass, but something strange is happening: the It may be a problem with how these prototypes are assigning to each other, but that is beyond me. |
|
@aljazerzen 99% sure closure is mangling too aggressively, and we need to do |
Co-authored-by: Paul Taylor <178183+trxcllnt@users.noreply.github.com>
|
One review is fine. We can merge this. |
|
Great. Please go ahead, as I don't have the permissions. |
|
Thank you. I had to get back to my computer to use the merge script. |
|
Benchmark runs are scheduled for baseline = 080a74c and contender = a1403d4. a1403d4 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
|
['Python', 'R'] benchmarks have high level of regressions. |
) ### What changes are included in this PR? Closes apache#22932 Basically, signed negative numbers were displayed as very large positive numbers. ### Are these changes tested? Yes, I've also added tests for `bn.ts` (BigNum) that was not tested before. ### Are there any user-facing changes? Negative numbers stored in BigNum will now be displayed as negative numbers instead of very large positive numbers. Note that this change also affects decimals, because they are stored in BigNum as signed numbers. Decimals still don't convert to string correctly, because inserting the decimal dot is not implemented. Ref #28804. * Closes: apache#35067 Lead-authored-by: Aljaž Mur Eržen <aljaz.erzen@gmail.com> Co-authored-by: Aljaž Mur Eržen <aljazerzen@users.noreply.github.com> Co-authored-by: Paul Taylor <178183+trxcllnt@users.noreply.github.com> Signed-off-by: Dominik Moritz <domoritz@gmail.com>
) ### What changes are included in this PR? Closes apache#22932 Basically, signed negative numbers were displayed as very large positive numbers. ### Are these changes tested? Yes, I've also added tests for `bn.ts` (BigNum) that was not tested before. ### Are there any user-facing changes? Negative numbers stored in BigNum will now be displayed as negative numbers instead of very large positive numbers. Note that this change also affects decimals, because they are stored in BigNum as signed numbers. Decimals still don't convert to string correctly, because inserting the decimal dot is not implemented. Ref #28804. * Closes: apache#35067 Lead-authored-by: Aljaž Mur Eržen <aljaz.erzen@gmail.com> Co-authored-by: Aljaž Mur Eržen <aljazerzen@users.noreply.github.com> Co-authored-by: Paul Taylor <178183+trxcllnt@users.noreply.github.com> Signed-off-by: Dominik Moritz <domoritz@gmail.com>
What changes are included in this PR?
Closes #22932
Basically, signed negative numbers were displayed as very large positive numbers.
Are these changes tested?
Yes, I've also added tests for
bn.ts(BigNum) that was not tested before.Are there any user-facing changes?
Negative numbers stored in BigNum will now be displayed as negative numbers instead of very large positive numbers.
Note that this change also affects decimals, because they are stored in BigNum as signed numbers. Decimals still don't convert to string correctly, because inserting the decimal dot is not implemented. Ref apache/arrow-js#100.
BigNums #35067BigNums #35067