Private
Public Access
36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
← [Back to Twitter thread index](../README.md)
|
|
|
|
---
|
|
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
|
|
|
|
|
|
|
|
## 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
|
|
|
|
|
|
|
|
## 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.
|