public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-4798] contracts: Lowercase {MAYBE,NEVER}_CONTINUE
Date: Mon, 19 Dec 2022 20:08:15 +0000 (GMT)	[thread overview]
Message-ID: <20221219200815.0B6613858D1E@sourceware.org> (raw)

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

commit r13-4798-ga39f454f0faf0734c7d040c9d8523f71be821000
Author: Arsen Arsenović <arsen@aarsen.me>
Date:   Sat Dec 10 10:43:00 2022 +0100

    contracts: Lowercase {MAYBE,NEVER}_CONTINUE
    
    The lowercase constants are more consistent with the standard, and it is
    unlikely that the uppercase versions would've been accepted.
    
    gcc/cp/ChangeLog:
    
            * contracts.cc: Rename references to
            contract_violation_continuation_mode constants to be lowercase.
    
    libstdc++-v3/ChangeLog:
    
            * include/experimental/contract: Lowercase the constants in
            contract_violation_continuation_mode.

Diff:
---
 gcc/cp/contracts.cc                        | 4 ++--
 libstdc++-v3/include/experimental/contract | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/cp/contracts.cc b/gcc/cp/contracts.cc
index 45f52b20392..26316372389 100644
--- a/gcc/cp/contracts.cc
+++ b/gcc/cp/contracts.cc
@@ -41,9 +41,9 @@ along with GCC; see the file COPYING3.  If not see
 	 "v > 0", // comment,
 	 "default", // assertion_level,
 	 "default", // assertion_role,
-	 MAYBE_CONTINUE, // continuation_mode
+	 maybe_continue, // continuation_mode
        });
-       terminate (); // if NEVER_CONTINUE
+       terminate (); // if never_continue
      }
 
    We use an internal type with the same layout as contract_violation rather
diff --git a/libstdc++-v3/include/experimental/contract b/libstdc++-v3/include/experimental/contract
index cf655023da7..a2babed6301 100644
--- a/libstdc++-v3/include/experimental/contract
+++ b/libstdc++-v3/include/experimental/contract
@@ -45,7 +45,7 @@ namespace experimental
 {
   // From P1332
   enum class contract_violation_continuation_mode {
-    NEVER_CONTINUE, MAYBE_CONTINUE
+    never_continue, maybe_continue
   };
 
   class contract_violation {

                 reply	other threads:[~2022-12-19 20:08 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=20221219200815.0B6613858D1E@sourceware.org \
    --to=jason@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).