docs(twitter): add 2076534605193036043 corpus (NOTimothyLottes X_/G_ macro + assembly-style control flow)

3-post companion to 2063733456144597200 + 2076893128515112995: defines X_ = return, G_ = goto. Moves from C-style {if,while,do,switch,for} to assembly-style {if,goto} so static branch prediction (backward=taken, forward=not_taken) is explicit. Plus exit-with-error now properly drains the background console render thread.
2026-07-26 21:22:36 -04:00
parent 175bce00f3
commit 41be106888
4 changed files with 91 additions and 0 deletions
@@ -0,0 +1,33 @@
+---
+title: "Another quality of life change, exit with error now triggers the background cons"
+author: "NOTimothyLottes"
+handle: "@NOTimothyLottes"
+post_url: "https://x.com/NOTimothyLottes/status/2076534605193036043"
+post_id: "2076534605193036043"
+timestamp: "2026-07-13 05:10:04"
+post_count: 3
+reply_count: 0
+repost_count: 0
+like_count: 3
+view_count: 593
+---
+
+# @NOTimothyLottes — Another quality of life change, exit with error now triggers the background cons
+
+## Post 1 (2026-07-13 02:22:56)
+
+I'll mark this down a more code obfustication for most humans, but for me it's another useful shorthand.
+define X_ return
+define G_(x) goto x
+
+![Media 1](./media/2076492543622107480_1.png)
+
+## Post 2 (2026-07-13 02:33:19) — reply to Post 1
+
+Not been happy with traditional C style {if,while,do,switch,for} so moving to more assembly style {if,goto} instead. This way static branch prediction {backward=taken,forward=not_taken} is more explicit in the code. Prototyping it in the Library loader below
+
+![Media 1](./media/2076495156316864720_1.png)
+
+## Post 3 (2026-07-13 05:10:04) — reply to Post 2
+
+Another quality of life change, exit with error now triggers the background console render thread to actually quit, so it always draws the console, then draws the error code, then exits.
@@ -0,0 +1,58 @@
+{
+  "root_post_id": "2076534605193036043",
+  "posts": [
+    {
+      "post_id": "2076492543622107480",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "I'll mark this down a more code obfustication for most humans, but for me it's another useful shorthand.\ndefine X_ return\ndefine G_(x) goto x",
+      "timestamp": "2026-07-13 02:22:56",
+      "media_urls": [
+        "https://pbs.twimg.com/media/HNEuyadXoAAVxgG?format=png&name=orig"
+      ],
+      "reply_to_id": null,
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 2,
+        "repost_count": 1,
+        "like_count": 13,
+        "view_count": 1898
+      }
+    },
+    {
+      "post_id": "2076495156316864720",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "Not been happy with traditional C style {if,while,do,switch,for} so moving to more assembly style {if,goto} instead. This way static branch prediction {backward=taken,forward=not_taken} is more explicit in the code. Prototyping it in the Library loader below",
+      "timestamp": "2026-07-13 02:33:19",
+      "media_urls": [
+        "https://pbs.twimg.com/media/HNExHNRWIAAimHM?format=png&name=orig"
+      ],
+      "reply_to_id": "2076492543622107480",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 2,
+        "repost_count": 0,
+        "like_count": 8,
+        "view_count": 917
+      }
+    },
+    {
+      "post_id": "2076534605193036043",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "Another quality of life change, exit with error now triggers the background console render thread to actually quit, so it always draws the console, then draws the error code, then exits.",
+      "timestamp": "2026-07-13 05:10:04",
+      "media_urls": [],
+      "reply_to_id": "2076495156316864720",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 0,
+        "repost_count": 0,
+        "like_count": 3,
+        "view_count": 593
+      }
+    }
+  ],
+  "source_url": "https://x.com/NOTimothyLottes/status/2076534605193036043"
+}