Me editing libc headers: RIP to everyone killed by the gods for their hubris but im different. and better. maybe even better than the gods
Félix
🏳️🌈 he/him
🍎 compiler intruder
🦅 memory safety hawk
I am once more astonished to find out that undocumented implementation details of software can change
I hate airports, this was entirely too many airports for 24 hours
TIL that you can use [[clang::always_inline]] on a statement, and that tells clang to try to inline every call in that statement: [[clang::always_inline]] foo(bar()); will ask it to inline both bar and foo
The results are in: I took 23,914 photos in the last 2 weeks
Mohabi only incurs modest overheads on common benchmarks—24.82% on JetStream and 24.43% on Speedometer. The academic “modest” strikes again
Probably preaching to the choir given how much of my esteemed following is AI-h8ing, but:
If I engage with you and you give me an AI response, we are automatically spending an extremely asymmetric amount of effort towards each other. In online spaces, we call that “trolling”
@thephd@pony.social if you allowed “auto x” for a default case, #define bar(X) _Generic(X, auto x: …) could become the least bad way to bind the expansion of a preprocessor macro to a variable inside a single expression

