æʃliŋ, ring racers purropawgandist: "code, no image description" - 📟🐱 GlitchCat

æʃliŋ, ring racers purropawgandist @aescling@cat.family

code, no image description

i furgot the extent to which printf is not type safe in C

f8ad2ce210eceb01.png

Mar 04, 2026, 22:51 · · · ·

Mar 04, 2026, 22:52

æʃliŋ, ring racers purropawgandist @aescling@cat.family

code

imo, this should be a compile time error, but since C can’t do that, it should at least cause a runtime error

Mar 04, 2026, 22:52

æʃliŋ, ring racers purropawgandist @aescling@cat.family

girls whose intuition was ruined by the video on type safe printf in Idris

Mar 04, 2026, 23:40

alyssa @alyssa@cat.family

code

@aescling they should invent a version of C where you can check for that

Mar 05, 2026, 00:11

aschmitz @aschmitz@lardbucket.org

re: code

@aescling Is there a common ABI where you could even detect that at runtime?

Mar 05, 2026, 00:18

æʃliŋ, ring racers purropawgandist @aescling@cat.family

re: code

@aschmitz purrobably not

Mar 05, 2026, 00:35

alyssa @alyssa@cat.family

re: code

@aschmitz @aescling i think amd64 sysv abi kinda-sorta might allow catching some cases of it? they pass an upper bound on the number of vector registers used through %al for variadic calls.

Sign in to participate in the conversation