public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david.irvine at maidsafe dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56004] New: Possible bug with decltype and access modifer order Date: Wed, 16 Jan 2013 15:13:00 -0000 [thread overview] Message-ID: <bug-56004-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56004 Bug #: 56004 Summary: Possible bug with decltype and access modifer order Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: david.irvine@maidsafe.net Please see this stackoverflow question for an overview. http://stackoverflow.com/questions/14188535/clang-access-modifier-order-and-decltype The issue seems to be that the private members are not visible at compilation to the decltype call. This is a minimum example (from the question). (I am the questioner in this case). This also seems to appear as a 'bug' in gcc but not msvc (12). I am not 100% convinced but cannot find in the standard why this will not work. I hope this helps. #include <future> #include <iostream> #include <thread> #include <vector> template <class T> T &self(T &t) { return t; } template<typename T> struct Dependent { }; template<typename T> class Synchronised : Dependent<T>{ public: explicit Synchronised(T t = T()) : t_(t) {} template<typename Functor> auto operator()(Functor functor) const ->decltype(functor(self(*this).t_)) { //auto operator()(Functor functor) const ->decltype(functor(this->t_)) { std::lock_guard<std::mutex> lock(mutex_); return functor(t_); } private: mutable T t_; mutable std::mutex mutex_; }; int main() { Synchronised<std::string> sync_string("Start\n"); std::vector<std::future<void>> futures; }
next reply other threads:[~2013-01-16 15:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-16 15:13 david.irvine at maidsafe dot net [this message] 2013-01-16 16:20 ` [Bug c++/56004] " redi at gcc dot gnu.org 2013-01-16 16:41 ` david.irvine at maidsafe dot net 2013-01-16 17:31 ` redi at gcc dot gnu.org 2013-01-16 18:17 ` david.irvine at maidsafe dot net 2013-01-16 18:26 ` 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-56004-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).