Reputation
Next privilege 125 Rep.
Vote down
Badges
2
Impact
0 people reached

  • 0 posts edited
  • 0 helpful flags
  • 14 votes cast
May
27
comment Blocking function call with asynchronous content
@Mawg, std::future is a C++11 feature, but this answer describes futures as a general pattern, not a concrete class that implements that pattern.
Aug
29
comment C++ Commitee Members?
[Commenting here because I can't answer/comment on a closed question.] Since this answer was written C++ has a new public home at isocpp.org and that site has some info on the committee and an incomplete list of WG21 members
Dec
20
comment Does auto make C++ code harder to understand?
@PlasmaHH I disagree, for (auto& item : items) is often still an advantage over explicitly naming the element type
Dec
20
comment Does auto make C++ code harder to understand?
So don't write auto x = GetX();, pick a better name than x that actually tells you what it does in that specific context ... that's often more useful than its type anyway.
Dec
20
comment Does auto make C++ code harder to understand?
@PlasmaHH, not all loops with iterators can be replace with range-based for e.g. if iterators are invalidated in the loop body and so need to be pre-incremented or not incremented at all.
May
20
comment Would “Efficient C++” book be irrelevant now due to compiler improvements?
Maybe not as directly, but Meyers is very concerned about performance (as you'll know if you've seen his talks about cache effects) and his tips almost always lead to clearer, more maintainable and faster code.