Quote:

full queues SHOULD NOT happen during normal operation

Another Quote:

With queues-implemented-over-mutexes like the ones we’ve written above, the most annoying thing performance-wise is that there is a chance that the OS’s scheduler can force the preemptive context switch right when the thread-being-preempted-is-owning-our-mutex.

Abstract:

After bashing all those Big Name guys for making those over-arching sets of guidelines, it is perfectly logical for me myself to do the same?

Quote:

DON’T use C-style cast, EVER. If you DO need a cast – DO spend time on figuring out which of C++ *_cast<>s you really mean (and maybe, you’ll find a way to avoid that cast at all)

Quote:

over(ab)using C++ features is a different story, we’ll discuss these features below on case-by-case basis

Another Quote:

Compiler will use all its Next-to-Divine Wisdom to show you that it is smarter than you are, and to ignore most of those inline specifications you carefully wrote.

Abstract:

Allocations and related lack of spatial locality can be DAMN EXPENSIVE

Quote:

During the times of Ancient Gamers (also known as times of Atari, ZX Spectrum, and Commodore64), CPUs were running at clock speed of a single-MHz (and one operation usually took several clocks). At the same time, memory run at about the speed comparable to that of CPUs.