public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99493] New: Address of template parameter object is not a valid template argument Date: Tue, 09 Mar 2021 18:20:25 +0000 [thread overview] Message-ID: <bug-99493-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99493 Bug ID: 99493 Summary: Address of template parameter object is not a valid template argument Product: gcc Version: 11.0 URL: https://godbolt.org/z/9zYo8f Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: johelegp at gmail dot com CC: johelegp at gmail dot com Target Milestone: --- See https://godbolt.org/z/9zYo8f. ```C++ struct owner{int m;}; struct view{const int*m;constexpr view(const owner&o):m{&o.m}{}}; template<view V>struct constant{}; template<owner O>constexpr constant<O>v{}; [[maybe_unused]] constexpr auto a=v<owner{}>; ``` https://timsong-cpp.github.io/cppwp/n4861/temp.param#8 defines template parameter object. https://timsong-cpp.github.io/cppwp/n4861/temp.arg.nontype#2 makes the template parameter object a constant expression. https://timsong-cpp.github.io/cppwp/n4861/temp.arg.nontype#3 lists restrictions, which excludes taking the address of a template parameter object.
next reply other threads:[~2021-03-09 18:20 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-09 18:20 johelegp at gmail dot com [this message] 2021-03-15 5:02 ` [Bug c++/99493] " johelegp at gmail dot com 2021-03-15 18:44 ` johelegp at gmail dot com 2022-01-19 2:43 ` pinskia at gcc dot gnu.org 2022-01-19 2:46 ` pinskia at gcc dot gnu.org 2024-01-17 18:02 ` cvs-commit at gcc dot gnu.org 2024-01-18 15:53 ` cvs-commit at gcc dot gnu.org 2024-01-18 15:54 ` ppalka at gcc dot gnu.org 2024-01-18 15:55 ` johelegp at gmail 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-99493-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).