reading the Dec 9 LWN, i can't help but think that expressing non-obvious ordering dependencies should be a feature of the language, rather than depending on the right compiler version and a shitload of macros.
for example, saying something like
a then b;
should return the result of b, but guarantee that b's evaluation doesn't begin until a's has completed. C lacks then as a reserved word, so it's available for this use; and a compiler getting it wrong would be just plain buggy, rather than being super-clever and optimising it away.
Follow
@thamesynne This is actually a feature built into a lot of processors at the hardware level!! i don't know why it's not made use of more for things other than multithreaded stuff
-F
