public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davidfromonline at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103783] Ambiguous overload between constrained static member and unconstrained non-static member
Date: Sun, 02 Jan 2022 16:57:22 +0000	[thread overview]
Message-ID: <bug-103783-4-OlQWkcxCr8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103783-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from David Stone <davidfromonline at gmail dot com> ---
Fedor, it looks like that wording was changed to a non-normative note and
expanded in N4868 to say: "There cannot be a static and a non-static member
function with the same name, parameter-type-list, and trailing requires-clause
([over.load]).". https://timsong-cpp.github.io/cppwp/n4868/class.static.mfct#2.
Later versions of the standard (for C++23) removed the sentence entirely.

  parent reply	other threads:[~2022-01-02 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  1:39 [Bug c++/103783] New: " barry.revzin at gmail dot com
2021-12-21  1:50 ` [Bug c++/103783] " pinskia at gcc dot gnu.org
2022-01-02  5:40 ` fchelnokov at gmail dot com
2022-01-02 16:57 ` davidfromonline at gmail dot com [this message]
2022-01-02 19:23 ` davidfromonline at gmail dot com
2022-01-04 18:08 ` ppalka at gcc dot gnu.org
2022-01-10 19:59 ` cvs-commit at gcc dot gnu.org
2022-01-10 21:16 ` cvs-commit at gcc dot gnu.org
2022-01-10 21:17 ` ppalka 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-103783-4-OlQWkcxCr8@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).