public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94025] Expected-to-fail compilation goes through by not detecting mutable-specifier on lambda Date: Tue, 14 Apr 2020 20:16:56 +0000 [thread overview] Message-ID: <bug-94025-4-YbDom4mBvg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94025-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94025 Daniel Krügler <daniel.kruegler at googlemail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.kruegler@googlemail. | |com --- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> --- In my opinion, this issue does not demonstrate a bug, but is based on an incomplete analysis of what is going on here. 1) It is correct, that the lambda function call operator is non-const in this case. The result is that the function call operator of the lambda expression will *not* be called in the shown example. 2) We have here a lambda expression without any capture. This means that the standard requires the existence of an *additional* conversion function to a pointer to function ([expr.prim.lambda.closure] p7 quoted from N4849). And [expr.prim.lambda.closure] p11 says: "The conversion function [..] is public, constexpr, non-virtual, non-explicit, const, and has a non-throwing exception specification (14.5)." So effectively a second function call resolution is in affect here, selecting the conversion function (which is a const member function as specified above) to function pointer as the only viable candidate (If both were viable, the conversion function would be less preferred) via the surrogate call function ([over.call.object]). That explains IMO why the code is well-formed. If you would try to mimic that with a user-defined class type, it would look similar to the following one: struct Lambda { using f_t = void(); f_t operator(); // "mutable" using fptr_t = f_t*; operator fptr_t() const; }; Note that I use here the very rarely used syntax to declare (but not define) a member function using a typedef for a function type to show the involved function types more precisely. The example would become invalid once you introduce a capture, because in this case there would be no conversion function anymore. I'm surprised that the Visual Studio compiler (I tested 2019) rejects the original example, this looks like a bug to me, especially since that compiler also handles the call resolution for the above defined Lambda type correctly. I plan to report an issue for that compiler.
next parent reply other threads:[~2020-04-14 20:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-94025-4@http.gcc.gnu.org/bugzilla/> 2020-04-14 20:16 ` daniel.kruegler at googlemail dot com [this message] 2020-04-18 18:25 ` daniel.kruegler at googlemail dot com
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-94025-4-YbDom4mBvg@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).