Private
Public Access
ed
41be106888
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.
1.3 KiB
1.3 KiB
title, author, handle, post_url, post_id, timestamp, post_count, reply_count, repost_count, like_count, view_count
| title | author | handle | post_url | post_id | timestamp | post_count | reply_count | repost_count | like_count | view_count |
|---|---|---|---|---|---|---|---|---|---|---|
| Another quality of life change, exit with error now triggers the background cons | NOTimothyLottes | @NOTimothyLottes | https://x.com/NOTimothyLottes/status/2076534605193036043 | 2076534605193036043 | 2026-07-13 05:10:04 | 3 | 0 | 0 | 3 | 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.