Skip to content

Re-measure the branch conventions on 2.1.0 - #915

Merged
Rafael-SOWNet merged 1 commit into
masterfrom
post-914
Aug 12, 2026
Merged

Re-measure the branch conventions on 2.1.0#915
Rafael-SOWNet merged 1 commit into
masterfrom
post-914

Conversation

@Rafael-SOWNet

Copy link
Copy Markdown
Collaborator

SimplificationContract.md §6 said its table of branch choices was "measured on a 2.0.0 build". True, and now incomplete: 2.1.0 changes logarithm behaviour (#902 guards the exponent pull) and abs (#881), so a reader is entitled to ask whether the branch choices moved with them.

All nine are unchanged, measured on a 2.1.0 build: sqrt(-4) is 2i, (-1)^(1/2) is i, ln(-1) is pi*i, i^i is 0.2078..., and the five negative-base powers including the trap the section exists for — (-8)^(1/3) is -2 while (-8)^0.3333333333 is 1 + 1.732i.

The sentence now says to re-measure whenever a release touches a branch, rather than naming one build, since that is what the section is for.

Doc only.

Section 6 said the table was measured on a 2.0.0 build, which was true and is now also
incomplete: 2.1.0 changes logarithm behaviour (#902 guards the exponent pull) and abs (#881), so
a reader is entitled to ask whether the branch choices moved with them. All nine values are
unchanged -- sqrt(-4), (-1)^(1/2), ln(-1), i^i, and the five negative-base powers including the
(-8)^(1/3) against (-8)^0.3333333333 trap.

Re-measuring these whenever a release touches a branch is the point of the section, so the
sentence now says that rather than naming one build.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@Rafael-SOWNet
Rafael-SOWNet merged commit b8cf4dc into master Aug 12, 2026
22 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant