[integer] Ensure that BigUInt has no leading zero words
#116
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 focuses on improving the
BigUIntandBigDecimalimplementations in thedecimojolibrary by enhancing precision, optimizing arithmetic operations, and ensuring consistency in handling zero values. It also includes a minor documentation update. Below is a categorized summary of the most important changes:Zero words:
is_zero()and comparison functions given that there are no leading zero words in BigUInt by design.Bug Fix:
extend_precisionexample inBigDecimalby correcting a missing closing quote.Consistency Improvements:
BigUInt()withBigUInt.ZEROfor clearer intent when representing zero values across multiple functions.Code Simplification and Optimization:
List[UInt32]allocations with directBigUIntinstantiations in arithmetic functions likeadd_slices_simd,subtract_school, andmultiply_slices_school. This reduces unnecessary memory usage and improves performance.API Enhancements:
BigUInt.from_slicefor copying slices of words, replacing manual slice handling inadd_inplace_by_slice. This improves readability and reduces potential errors.Documentation Update:
README.mdfor community engagement.These changes collectively enhance the library's efficiency, maintainability, and usability.