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++/95596] string literal wrong overload resolution (char* vs std::string) Date: Tue, 09 Jun 2020 13:43:33 +0000 [thread overview] Message-ID: <bug-95596-4-Xsw6YGJN5Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95596-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95596 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2020-06-09 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Confirmed. Even with -std=c++14 -pedantic-errors we still choose the wrong overload (and then give an error that the conversion is not allowed). There seems to be no way to disable the conversion from string literals to char* that has been deprecated for years.
next prev parent reply other threads:[~2020-06-09 13:43 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-09 3:05 [Bug c++/95596] New: " bzsurr at protonmail dot com 2020-06-09 7:17 ` [Bug c++/95596] " bzsurr at protonmail dot com 2020-06-09 13:43 ` redi at gcc dot gnu.org [this message] 2020-06-09 13:45 ` redi at gcc dot gnu.org 2020-06-10 19:30 ` mpolacek at gcc dot gnu.org 2020-07-22 14:05 ` redi at gcc dot gnu.org 2020-07-22 14:06 ` redi at gcc dot gnu.org 2022-02-14 20:11 ` pinskia at gcc dot gnu.org 2023-05-27 17:58 ` pinskia 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-95596-4-Xsw6YGJN5Z@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).