4 ms·
The C++ standard library continued this culture of "making names unreasonably short and/or adding modifiers that are anything but obvious", e.g. rdbuf, setf, se
by blattimwind 8y ago
The C++ standard library continued this culture of "making names unreasonably short and/or adding modifiers that are anything but obvious", e.g. rdbuf, setf, seekg/p, tellg/p, beg (instead of begin[ing]), ends etc.
- garaetjjte 8y agoI prefer that instead of boost-like std::chrono::time_point<std::chrono::high_resolution_clock>
- blattimwind 8y agostd::datetime::timepoint<std::datetime::highres> ? Assuming you'd want to keep a separate datetime namespace. Neither ::highres nor ::high_resolution_clock really is a descriptive name though, because it doesn't really describe what it means. What is a "high resolution clock" here? Does it mean µs resolution? Nanoseconds (as some "newer" Linux APIs support)? What about accuracy? "chrono" is one of these "sounds cool but is kind of a weird word to use" things.