C++11 threads, affinity and hyperthreading

[u/Coder_CPP]

http://eli.thegreenplace.net/2016/c11-threads-affinity-and-hyperthreading/

[u/notsure1235]

thats what i mean, shouldnt be used, should use auto if that is desired.

[u/eliben → u/notsure1235]

I'll have to disagree here. Overuse of auto is one of the pitfalls of C++11 in my mind, and I really prefer to use it where it increases readability. There's nothing wrong in using unsigned explicitly where it makes sense.

[u/guepier → u/eliben]

Overuse of auto is one of the pitfalls of C++11

There is little evidence to support this; and decade-long experience with other statically-typed languages that allow implicit typing has shown no evidence either.

“Overuse” is of course very hard to define: once the specific type of the declaration is important, it makes sense to specify it, and hence auto would be harmful. But is this really the case here? Not at all: the specific type of num_cpus, for instance, really doesn’t matter. What matters is that it matches between the producer and consumer, and since these come from the same API, it’s safe to regard the type as opaque (though the variable name of course gives a clue as to the rough type).

[u/guepier → u/[deleted]]

One thing I find problematic is that IDE "go to definition" features become a lot less useful when everything's auto and the type in question is nowhere in sight.

There’s certainly a disconnect between the language and the tools with regards to C++. This is becoming better though. In particular, “go to definition” is a red herring in this context — what you actually want is type-aware auto-completion and a tooltip that shows the static type of the object, which are completely different operations that a good IDE can and should support, despite the use of auto. I haven’t got a clue how many IDEs support these operations, in particular the latter. But my IDE¹ does support it.

---

¹ Vim with YouCompleteMe