public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-2622] libstdc++: Fix comments in tests to match code
Date: Mon, 12 Sep 2022 11:04:03 +0000 (GMT)	[thread overview]
Message-ID: <20220912110403.B24403858CDA@sourceware.org> (raw)

https://gcc.gnu.org/g:c092d894265f3db590585804c30c1ae3cb7b3773

commit r13-2622-gc092d894265f3db590585804c30c1ae3cb7b3773
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Sep 12 12:02:29 2022 +0100

    libstdc++: Fix comments in tests to match code
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/19_diagnostics/error_code/cons/lwg3629.cc: Fix
            comments.
            * testsuite/19_diagnostics/error_condition/cons/lwg3629.cc:
            Likewise.

Diff:
---
 libstdc++-v3/testsuite/19_diagnostics/error_code/cons/lwg3629.cc      | 4 ++--
 libstdc++-v3/testsuite/19_diagnostics/error_condition/cons/lwg3629.cc | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/libstdc++-v3/testsuite/19_diagnostics/error_code/cons/lwg3629.cc b/libstdc++-v3/testsuite/19_diagnostics/error_code/cons/lwg3629.cc
index b1e0b7f0c81..70fa5e80503 100644
--- a/libstdc++-v3/testsuite/19_diagnostics/error_code/cons/lwg3629.cc
+++ b/libstdc++-v3/testsuite/19_diagnostics/error_code/cons/lwg3629.cc
@@ -39,10 +39,10 @@ template<> struct std::is_error_code_enum<user::E3> : std::true_type { };
 // ::make_error_code(E1) should not be found by name lookup.
 std::error_code e1( user::E1{} ); // { dg-error "here" }
 
-// std::make_error_code(errc) should not be found by name lookup.
+// std::make_error_code(future_errc) should not be found by name lookup.
 std::error_code e2( user::E2{} ); // { dg-error "here" }
 
-// std::make_error_code(future_errc) should not be found by name lookup.
+// std::make_error_code(errc) should not be found by name lookup.
 std::error_code e3( user::E3{} ); // { dg-error "here" }
 
 // { dg-error "use of deleted function" "" { target *-*-* } 0 }
diff --git a/libstdc++-v3/testsuite/19_diagnostics/error_condition/cons/lwg3629.cc b/libstdc++-v3/testsuite/19_diagnostics/error_condition/cons/lwg3629.cc
index e34b53de8a1..562a99aee3b 100644
--- a/libstdc++-v3/testsuite/19_diagnostics/error_condition/cons/lwg3629.cc
+++ b/libstdc++-v3/testsuite/19_diagnostics/error_condition/cons/lwg3629.cc
@@ -39,10 +39,10 @@ template<> struct std::is_error_condition_enum<user::E3> : std::true_type { };
 // ::make_error_condition(E1) should not be found by name lookup.
 std::error_condition e1( user::E1{} ); // { dg-error "here" }
 
-// std::make_error_condition(errc) should not be found by name lookup.
+// std::make_error_condition(future_errc) should not be found by name lookup.
 std::error_condition e2( user::E2{} ); // { dg-error "here" }
 
-// std::make_error_condition(future_errc) should not be found by name lookup.
+// std::make_error_condition(errc) should not be found by name lookup.
 std::error_condition e3( user::E3{} ); // { dg-error "here" }
 
 // { dg-error "use of deleted function" "" { target *-*-* } 0 }

                 reply	other threads:[~2022-09-12 11:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220912110403.B24403858CDA@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).