AnanasAttack

Correctly using a spinlock: Never when preemption is enabled

You can totally have memory barriers in macros. It doesn't have much to do with the language at all

I always feared sites would do things like this so I clear the clipboard/fill it with garbage after usage

People do whatever they can to "win" on these benchmarks, so the resulting code is often not idiomatic

It seems anything is newsworthy here when it's in Rust

The comment doesn't explain why there even is an offset in the first place. Who put it there and why? I think this should be explained as well

C++ coroutines are stackless

Thread scheduling (or waking up cores) is slow. Because of this, mutexes will look better on dumb benchmarks, as the contending threads keep going to sleep, while the single succesful owner has practically uncontended access

I can't be the only one who finds it cleaner to just use structs with state and pointers to them, than all such macro and typedef hackery

Only stød is unusual. It is written with a superscript glottal stop (ˀ) letter

I've been wondering about the impact of insturction cache misses and potential downsides of executable bloat caused by C++ templates, but have never seen a real case of this being a problem.

How about infringing on a patent for inventing something independently without knowing it?

How is that naive or arrogant?

What do you dislike about edge triggered mode?

You're right: No fun is EVER allowed. Is that a smile on your face? Doesn't look very productive to me, now get back to work.

Not that unusual really. Whenever you hear about new stuff, chances are it's better to look it up on Wikipedia first.

I'd much rather ...

How can you be sure that the NSA is any better than the chinese?

I've seen points like these made before, but never really understood how. Can you give an example of self-modifying code becoming a security issue?

Are there any languages that could actually make use of self modifying code? JIT languages already do this.