public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113366] g++.dg/cpp2a/concepts-pr67774.C FAIL
Date: Sat, 13 Jan 2024 11:32:17 +0000	[thread overview]
Message-ID: <bug-113366-4-dBN9tRsyI3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113366-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113366

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Odd.

We get the type/value mismatch from here:

        template<typename _Tp>
          using __maybe_const_t
            = __conditional_t<__format::__formattable_with<_Tp, _Context>,
                              const _Tp, _Tp>;


Where the boolean condition is:

  template<typename _Tp, typename _Context,
           typename _Formatter
             = typename _Context::template formatter_type<remove_const_t<_Tp>>,
           typename _ParseContext
             = basic_format_parse_context<typename _Context::char_type>>
    concept __formattable_with
      = semiregular<_Formatter>
          && requires (const _Formatter __cf, _Tp&& __t, _Context __fc)
    {
      { __cf.format(__t, __fc) } -> same_as<typename _Context::iterator>;
    };


That seems like a valid concept. Is something in the -fconcepts-ts code
tripping up?

  reply	other threads:[~2024-01-13 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13  0:33 [Bug testsuite/113366] New: " mpolacek at gcc dot gnu.org
2024-01-13 11:32 ` redi at gcc dot gnu.org [this message]
2024-01-13 11:40 ` [Bug testsuite/113366] " redi at gcc dot gnu.org
2024-01-13 11:48 ` redi at gcc dot gnu.org
2024-01-15 17:18 ` cvs-commit at gcc dot gnu.org
2024-01-18 21:03 ` cvs-commit at gcc dot gnu.org

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=bug-113366-4-dBN9tRsyI3@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).