Repository navigation
Specify the accuracy-class evaluation contract in PM 1004 - #18
Merged
Merged
Conversation
Replace the platform-precision clause with the accuracy model: values carry accuracy classes (exact integers and rationals, limited floats and guard-digit decimals, limited contaminating exact); boundaries are the operations that would discard exactness; the caller chooses the mode - approximate (default, every boundary crossed and reported), strict (never crosses, defers with the residual expression), or strict with declared guard digits (BigDecimal to the declared precision). Results are objects carrying the value, the boundary records and the unevaluated expressions; exact vectors are byte-identical across runtimes.
3 of 5 tasks
4 tasks
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
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.
Summary
Implements the agreed evaluation-accuracy design in the spec: values carry accuracy classes (exact integers and rationals; limited floats with undeclared accuracy; limited guard-digit decimals; limited contaminates exact), boundaries are the operations that would discard exactness, and the caller chooses the mode at the entry point:
Evaluation returns a result object (value, ordered boundary records, unevaluated expressions); exact vectors are byte-identical across runtimes. Companion implementation PR lands in plurimath/plurimath.
Test plan
ruby scripts/validate-register.rb— VALIDATION OK (6 documents)metanorma compileof pm-1004 — new clauses render (Accuracy classes / Boundaries / Modes / Results)