public inbox for
help / color / mirror / Atom feed
From: Jonathan Wakely <>
Subject: [gcc r13-1977] libstdc++: Add feature test macro for <experimental/scope>
Date: Fri,  5 Aug 2022 14:18:44 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

commit r13-1977-g58a644cfdee53275e3d07eff0c2126dc88b87aef
Author: Jonathan Wakely <>
Date:   Fri Aug 5 15:17:20 2022 +0100

    libstdc++: Add feature test macro for <experimental/scope>
            * include/experimental/scope (__cpp_lib_experimental_scope):
            * testsuite/experimental/scopeguard/ Check macro.

 libstdc++-v3/include/experimental/scope                     | 2 ++
 libstdc++-v3/testsuite/experimental/scopeguard/ | 6 ++++++
 2 files changed, 8 insertions(+)

diff --git a/libstdc++-v3/include/experimental/scope b/libstdc++-v3/include/experimental/scope
index 37a57b38af7..208fadc513e 100644
--- a/libstdc++-v3/include/experimental/scope
+++ b/libstdc++-v3/include/experimental/scope
@@ -43,6 +43,8 @@ namespace std _GLIBCXX_VISIBILITY(default)
 namespace experimental::inline fundamentals_v3
+#define __cpp_lib_experimental_scope 201902
   template<typename _Tp, typename _Up>
     concept __not_same_as = !same_as<_Tp, _Up>;
diff --git a/libstdc++-v3/testsuite/experimental/scopeguard/ b/libstdc++-v3/testsuite/experimental/scopeguard/
index 7690572ab19..fe9d6ee7cfc 100644
--- a/libstdc++-v3/testsuite/experimental/scopeguard/
+++ b/libstdc++-v3/testsuite/experimental/scopeguard/
@@ -4,6 +4,12 @@
 #include <experimental/scope>
 #include <testsuite_hooks.h>
+#ifndef __cpp_lib_experimental_scope
+# error Feature-test macro is not defined.
+#elif __cpp_lib_experimental_scope < 201902
+# error Feature-test macro has bad value.
 using std::experimental::unique_resource;

                 reply	other threads:[~2022-08-05 14:18 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:

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

  git send-email \ \ \ \ \

* 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).