Repository navigation
Move the read-write law and exactness to the language - #261
Merged
Merged
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
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.
Refs #66.
Moves §4.10 and §6 of
SPECIFICATION.mdinto the language and deletes them there, with the empty heading of section 4 they leave behind. The read-write law stood under "Reads and writes" onBELOCH.mdalready; the paragraph now carries the asymmetry the law encodes and points at ADR 0011 in place of the section. Exactness is a section of its own onBELOCH.md: every geometric decision is exact, the representation of numbers is free, the constructions bound the degree, and the output is the one inexact step. The pointers to §6 on the overview and the constructions page name the section. What §4.10 said about@being retired and about landmark constructions as an interim is history and is not carried over.