public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/101482] New: The resolution of #32907 is too restricted Date: Sat, 17 Jul 2021 03:10:36 +0000 [thread overview] Message-ID: <bug-101482-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101482 Bug ID: 101482 Summary: The resolution of #32907 is too restricted Product: gcc Version: 11.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: de34 at live dot cn Target Milestone: --- The resolution of bug #32907 is restricted to a few specializations (basic_string<CharT>, where bool(__is_char<CharT>::value) is true). It seems that the resolution should be generalized to all specializations of basic_string (by removing the legacy operator== overload and SFINAE in the new overload, which is already done by libc++ and msvc stl). IMO the generalized resolution can also be applied to operator== for __versa_string.
next reply other threads:[~2021-07-17 3:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-17 3:10 de34 at live dot cn [this message] 2022-06-16 6:07 ` [Bug libstdc++/101482] " de34 at live dot cn 2022-06-16 9:47 ` [Bug libstdc++/101482] operator== for basic_string and __versa_string should check sizes first redi at gcc dot gnu.org 2022-06-16 19:20 ` cvs-commit at gcc dot gnu.org 2022-06-16 19:22 ` redi 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-101482-4@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: linkBe 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).