StephanTLavavej

19 ms·

151.
by StephanTLavavej 12y ago
Yeah, the presentation covered those parts (motivation, and putting the pieces together). C++14 rejects the bad code by providing a deleted overload for const string&&, as covered in the following slides. My slides are already at th
152.
by StephanTLavavej 12y ago
What do you think of my slides? ("STL Features And Implementation Techniques") I try to make them readable by themselves.
153.
by StephanTLavavej 12y ago
The log graph is scarier: https://upload.wikimedia.org/wikipedia/commons/2/2d/Evolutio... (It's easier to recognize a straight line on a log scale, than to distinguish an exponential line on a linea
154.
by StephanTLavavej 12y ago
Die shrinks reduce power consumption. 45nm consumes more power than 28nm.
155.
by StephanTLavavej 12y ago
Both auto& and auto&& produce const T& for a const vector<T>, and T& for a modifiable vector<T>. The difference between them is subtle: auto&& handles Humanity's Eternal Nemesis, vector<bool&g
156.
by StephanTLavavej 12y ago
Traditionally, "ticks" are small, and "tocks" are big. See https://en.wikipedia.org/wiki/Intel_Tick-Tock .
157.
by StephanTLavavej 12y ago
> did it offer a `mutable` opt-in, though? Nope. > would intuitively expect it to be the POLS behavior. If you give me (the implementation) a modifiable range, and I invisibly add constness before giving you back an element, that&#x27
158.
by StephanTLavavej 12y ago
I love const, but I am strongly opposed to adding constness here - as I mentioned, the non-Standard "for each" extension did that, and it caused endless confusion. Note that the lambda precedent is not actually applicable, because
159.
by StephanTLavavej 12y ago
I talked about this some more in http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n399... Q17. Many people have asked for such syntax, but I am wary of adding more complexity to the Core
160.
by StephanTLavavej 12y ago
It took me some time to recognize the problem with range-for (after testing its implementation in VC 2012), and more time to work up the courage to write a Core Language proposal. I also wish next-gen range-for had gotten into C++14, but th