3 ms·
And barrier instructions/semantics are used by many architectures to flush/partition pipelines. AFAICT this one doesn't do that. Too bad they couldn't qualify
by wyldfire 6y ago
And barrier instructions/semantics are used by many architectures to flush/partition pipelines. AFAICT this one doesn't do that.
Too bad they couldn't qualify it somewhere further down below std::. Something like std::thread::barrier or similar might be easier to understand.
- kazinator 6y agoHowever, the barrier metaphor is correct. The counter reaches a certain level (the barrier potential, get it?) upon which the object triggers.
- hn_go_brrrrr 6y agoUnfortunately, nested namespaces can have some surprising and unintended consequences. You might find https://abseil.io/tips/130 https://abseil.io/tips/130 interesting. Given the author was until very recently the chair of the C++ LEWG, I imagine he's had some influence on how what namespaces new types ended up in.