From b236debd3b05584e8f5091fe35f1e071a2f4385b Mon Sep 17 00:00:00 2001 From: Jonathan Wakely Date: Wed, 28 Sep 2016 19:04:23 +0100 Subject: [PATCH] * include/std/chrono (system_clock): Fix typo in comment. From-SVN: r240589 --- libstdc++-v3/ChangeLog | 2 ++ libstdc++-v3/include/std/chrono | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 3ce95a1c3ea..ee5a63fc45c 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,5 +1,7 @@ 2016-09-28 Jonathan Wakely + * include/std/chrono (system_clock): Fix typo in comment. + * include/experimental/bits/fs_fwd.h (file_time_type): Simplify definition. * src/filesystem/ops.cc (file_time): Take error_code parameter and diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono index f29d8e1adbc..11e7fa298c4 100644 --- a/libstdc++-v3/include/std/chrono +++ b/libstdc++-v3/include/std/chrono @@ -784,7 +784,7 @@ _GLIBCXX_END_NAMESPACE_VERSION // Clocks. // Why nanosecond resolution as the default? - // Why have std::system_clock always count in the higest + // Why have std::system_clock always count in the highest // resolution (ie nanoseconds), even if on some OSes the low 3 // or 9 decimal digits will be always zero? This allows later // implementations to change the system_clock::now() -- 2.30.2