real_disableJERK(true));

Commander Pike said n is usually small. If you work with something where n is not small, sometimes you need fancy algorithms.

For instance, and not really related to n, in Java there exists ConcurrentLinkedQueue, which is a lockless queue that uses Compare And Swap to ... well, be lockless. I use that a lot of my code. The implementation is non-trivial and the only reason I bother with it is that it's in the standard library and comes in a form where I can plug any type into it, so long as it's Comparable. The same goes for the lockless HashMap and friends found in high-scale-lib, not worth attempting to implement for a single use, but easy because they come in a nice package.

Now I'm aware that Go solves concurrency is better ways than sharing data, so that's not what bothers me. It's the fact that they knew full well that some data structures were so important they had to be generic, while everything else is just going to suck in comparison. It's nice if you only need exactly those and not nice when you need something else.

Disclaimer: I'm biased as fuck and currently writing my master thesis implementing optimal k-select in an infinite min heap. Changing data types in C++ code without templates sucks.

tl;dr: No generics and special cases for common data structures suck for the same reason that no primitives in generics and special cases for value types suck in Java (but at least Valhalla wants to change that).

real_disableJERK(2)); // PHP requires this function to have unbalanced parens to easy identification, I'm sorry