Post #3921088
2026-05-19 17:00 UTC
@SRAZKVT@tech.lgbt well, you get into interesting library design philosophy questions there
a well-designed library interface for any feature shouldn't leave the user needing to think about how its macros expand any more than they usually should think about what lies behind a function call boundary - which is a non-zero amount of the time but it is comparatively very low
(obviously anything built with #include INCREMENT failed hard at the first hurdle but ygwim)
@eniko@mastodon.gamedev.place
Replies (1)
-
@erisceleste@tech.lgbt 2026-05-19 17:03
@SRAZKVT@tech.lgbt on a personal level (and i don't think i can say this with the safety-critical hat anywhere near me lol) i do think that if you're not extending the syntax, you're not writing with the full language syntactic abstractions are one of your tools for expression if your high-level logic expresses things like allocation modes you should feel safe expressing your intent with blocks like no_gc { /* statements */ } or summat the ideal of any API is composability obviously, many C interfaces (of all kinds) fail dramatically at it @eniko@mastodon.gamedev.place