oh, no, that's not safe to eat

I made a flat plush.

I'm thinking of proposing module maps for standardization. It's clear to me that they are the right solution for telling the toolchain which headers should be header units. Since the system headers need them too, it doesn't make sense for each compiler to have their own version.

I wish people weren't so against header units. They are by far the fastest way to get the build perf benefits of modules as they don't require rewriting all your code. It's also equivalent to what Apple, Google, Meta, and Microsoft are using in prod.

LLVM pone wants to make more assumptions about your code.

By @rivibaes.bsky.social

And here I thought canonicalizing -D and -U options would be easy:
godbolt.org/z/3dKW9ro9G

So apparently both file locking and named semaphores are just fundamentally broken in the Unix ecosystem.

apenwarr.ca/log/20101213
membarrier.wordpress.com/2020/07/16/t...

Also Android just doesn't implement named semaphores.

I just want simple, reliable, and portable cross process sync :(

Added some more plush display space.