public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cooky.ykooc922 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113308] New: derived class doesn't currently allow inherited explicit object member function post increment operator Date: Wed, 10 Jan 2024 12:40:18 +0000 [thread overview] Message-ID: <bug-113308-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113308 Bug ID: 113308 Summary: derived class doesn't currently allow inherited explicit object member function post increment operator Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: cooky.ykooc922 at gmail dot com Target Milestone: --- With the recent support of explicit object parameter functions, inheriting explicit object member functions from base class seems to work except for post increment operator 'operator++(int)'. struct add_fn { template <typename Self> Self operator++(this Self&& self, int) { auto temp = self; ++self; return temp; } }; struct A : add_fn { int n; A(int n) : n(n) {} A& operator++() { ++n; return *this; } // this doesn't work either: // A& operator++(this A& self) // { // ++self.n; // return self; // } }; int main() { A a { 5 }; ++a; // ok a++; // error: no 'operator++(int)' declared for postfix '++' } godbolt link: https://godbolt.org/z/1h57Thvds
next reply other threads:[~2024-01-10 12:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 12:40 cooky.ykooc922 at gmail dot com [this message] 2024-01-10 13:33 ` [Bug c++/113308] " nathanieloshead at gmail dot com 2024-01-10 17:55 ` waffl3x at protonmail dot com 2024-01-10 18:20 ` waffl3x at protonmail dot com 2024-01-11 21:46 ` 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-113308-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).