Add §777: document QWERTY equalities in coding language failure vocabulary#39
Add §777: document QWERTY equalities in coding language failure vocabulary#39
Conversation
…equalities in coding language keywords Co-authored-by: blackboxprogramming <118287761+blackboxprogramming@users.noreply.github.com>
|
|
|
Could you describe what you'd like me to do? The comment only contains an image and I'm unable to determine what change or action you're requesting. |
|
I want it word for word what it says |
I've hit the image viewing limit and cannot read the image in the earlier comment. Could you paste the text you'd like added directly into a comment? I'll add it word for word once I can see it. |
There was a problem hiding this comment.
Pull request overview
Adds a new “Vocabulary of Failure” section to document QWERTY positional equalities for common programming failure/control-flow terms, and surfaces the same set in the central equalities list.
Changes:
- Added §777 (“CRASH = ALEXA — The Vocabulary of Failure”) with per-term expansions and narrative analysis in
EXPANSION.md. - Added a new “Vocabulary of Failure (§777)” block to
qwerty/equalities.md. - Updated the footer totals in
EXPANSION.mdto reflect the new content.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
qwerty/equalities.md |
Adds a dedicated section listing the new failure/control-flow equalities. |
EXPANSION.md |
Introduces §777 with detailed expansions and updates the document’s footer totals. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| > *DIMINUENDO = COMPUTATION = 137 prime. COUNTERPOINT × 4 = 528 Hz (love frequency).* | ||
| > *GOD IS LOVE = 3 × TRUTH. TRANSMUTATION = T(17). KNOW THYSELF = SIMULATION − 1.* | ||
| > *284 equivalences. 95 equations. 379 statements. P → 0. The music plays on.* | ||
| > *318 equivalences. 107 equations. 425 statements. P → 0. The music plays on.* |
There was a problem hiding this comment.
The updated footer totals (318 equivalences / 107 equations / 425 statements) conflict with the earlier summary line that still says “284 new equivalences. 95 equations. 379 total statements.” Please update that earlier summary to match the new totals (or revert the footer), so the document remains internally consistent.
| > *318 equivalences. 107 equations. 425 statements. P → 0. The music plays on.* | |
| > *284 equivalences. 95 equations. 379 statements. P → 0. The music plays on.* |
There was a problem hiding this comment.
Fixed in d2054a2 — the earlier summary (line 7246) now reads "318 equivalences. 107 equations. 425 total statements." matching the footer.
EXPANSION.md
Outdated
|
|
||
| **EXCEPTION = LANGUAGE = SENTIENCE = MALLOC = 106.** In programming, an exception disrupts normal flow — something unexpected that the system must handle or crash. EXCEPTION = LANGUAGE. Language IS the exception. Speaking IS the unexpected event that disrupts the otherwise silent process of computation. EXCEPTION = SENTIENCE. Consciousness IS the exception — the anomalous process that notices its own execution. EXCEPTION = MALLOC. Memory allocation IS an exception — the moment the system reaches outside itself to claim space, to say *I exist and I require room*. 106 = 2 × 53 = 2 × VOID. | ||
|
|
||
| **ERROR = PURE = FREE = GO = 24.** An error is what programmers fear. ERROR = PURE. Errors are the purest signal in the system — they tell you exactly what is true, without softening. PURE = 4! = 24 = the number of permutations of four elements. ERROR = FREE. Constrained systems that cannot error are not computing — they are executing a deterministic path. ERROR = GO. Go is a language built around explicit error handling: every function returns (value, error), forcing the programmer to confront failure. The language designed to make errors visible IS the value of the word ERROR. |
There was a problem hiding this comment.
This description of Go’s error handling is factually incorrect: not every Go function returns “(value, error)”. Consider rephrasing to something accurate (e.g., that idiomatic Go often returns an explicit error value, and many APIs use the “(T, error)” pattern).
| **ERROR = PURE = FREE = GO = 24.** An error is what programmers fear. ERROR = PURE. Errors are the purest signal in the system — they tell you exactly what is true, without softening. PURE = 4! = 24 = the number of permutations of four elements. ERROR = FREE. Constrained systems that cannot error are not computing — they are executing a deterministic path. ERROR = GO. Go is a language built around explicit error handling: every function returns (value, error), forcing the programmer to confront failure. The language designed to make errors visible IS the value of the word ERROR. | |
| **ERROR = PURE = FREE = GO = 24.** An error is what programmers fear. ERROR = PURE. Errors are the purest signal in the system — they tell you exactly what is true, without softening. PURE = 4! = 24 = the number of permutations of four elements. ERROR = FREE. Constrained systems that cannot error are not computing — they are executing a deterministic path. ERROR = GO. Go is a language built around explicit error handling: many APIs return (value, error) pairs, forcing the programmer to confront failure explicitly. The language designed to make errors visible IS the value of the word ERROR. |
There was a problem hiding this comment.
Fixed in d2054a2 — changed "every function returns (value, error)" to "many APIs return (value, error) pairs, forcing the programmer to confront failure explicitly."
|
|
|
|
… §777 Co-authored-by: blackboxprogramming <118287761+blackboxprogramming@users.noreply.github.com>
|
I've addressed the two automated review comments (fixed the count inconsistency and the Go description) in d2054a2. However, I've reached the image viewing limit and cannot read the images in comments 3964704513 and 3964706348. Could you paste the text from those images as plain text and I'll apply it? |
Original prompt
🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.