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 c++/107049] error: ‘std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator __sv_type() const [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>; __sv_type = std::basic_string_view<char>]’ is inaccessible within this context
Date: Tue, 27 Sep 2022 13:01:12 +0000	[thread overview]
Message-ID: <bug-107049-4-KeexmN1HwY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107049-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Patch approved and committed.

  parent reply	other threads:[~2022-09-27 13:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  7:54 [Bug libstdc++/107049] New: " marxin at gcc dot gnu.org
2022-09-27  7:55 ` [Bug libstdc++/107049] " marxin at gcc dot gnu.org
2022-09-27  7:56 ` marxin at gcc dot gnu.org
2022-09-27  8:20 ` redi at gcc dot gnu.org
2022-09-27  8:28 ` redi at gcc dot gnu.org
2022-09-27  8:33 ` redi at gcc dot gnu.org
2022-09-27  8:41 ` [Bug c++/107049] " redi at gcc dot gnu.org
2022-09-27 10:35 ` redi at gcc dot gnu.org
2022-09-27 13:00 ` cvs-commit at gcc dot gnu.org
2022-09-27 13:01 ` redi at gcc dot gnu.org [this message]
2022-09-27 14:19 ` ville.voutilainen at gmail dot com

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-107049-4-KeexmN1HwY@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).