Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Explain in the README that
Divdefaults to 16 decimal places viaDivisionPrecision, and showDivRoundfor choosing precision per operation. Clarify decimal places versus significant digits, halfway rounding, and why rounding afterward cannot restore discarded digits.Addresses #338. This documents existing behavior without changing arithmetic or defaults.
Validation: extracted and ran the example; checked exact division, positive/negative halfway rounding and precision loss through the public API.
go test ./...,go build ./...,go vet ./..., and golangci-lint 2.14.0 pass on Go 1.27.1.AI assistance was used to prepare and verify the documentation.