Skip to content

Commit

Permalink
Reinstate binary integer quadrants (#114).
Browse files Browse the repository at this point in the history
  • Loading branch information
oscbyspro committed Oct 24, 2024
1 parent a60c355 commit 5f13a8e
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,23 @@ The above setup enables optimizations and disables instrumentation that may limi

👨‍💻🛠️🚧🧱🧱🏗️🧱🧱🚧⏳

```
┌───────────┬───────────┐
│ Systems │ Arbitrary │
┌──────────┼───────────┤───────────┤
│ Signed │ B,E,F,S,X │ A,B,F,X │
├──────────┼───────────┤───────────┤
│ Unsigned │ B,E,F,S,Y │ A,B,E,Y │
└──────────┴───────────┴───────────┘
A) ArbitraryInteger: B
B) BinaryInteger: -
E) EdgyInteger: B
F) FiniteInteger: B
S) SystemsInteger: E, F
X) SignedInteger: F
Y) UnsignedInteger: E
```

#### The lossy invariant

Lossy operations are remarkably well-behaved. In the case of binary integers, we use this term specifically to denote truncation. In other words, a lossy binary integer result omits bits beyond its in-memory representation, which means all existing bits are still valid. In practice, types of different sizes agree on the bits that fit in the smaller type. The following example demonstrates this invariant.
Expand Down

0 comments on commit 5f13a8e

Please sign in to comment.