public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jlame646 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109763] GCC accepts invalid program involving decltype(classtype::memberfunction) when used with concepts
Date: Sun, 07 May 2023 11:08:32 +0000	[thread overview]
Message-ID: <bug-109763-4-MfjEbWyqKR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109763-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jason Liam <jlame646 at gmail dot com> ---
(In reply to Andrew Pinski from comment #8)
> Gcc correctly accepts this:
> template <int t> constexpr bool d = true;
> template < typename T >
> concept test = d<T::value>;
> 
> Without a typename as T::value here refers to a value for the non-type
> template argument.

I see. 

-------------------------------

Anyways, for my original example, [temp.constr.normal]:

> The normal form of a concept-id C<A1, A2, ..., An> is the normal form of the constraint-expression
of C, after substituting A1, A2, ..., An for C’s respective template parameters
in the parameter
mappings in each atomic constraint. If any such substitution results in an
invalid type or expression,
the program is ill-formed; no diagnostic is required.

  parent reply	other threads:[~2023-05-07 11:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07  4:16 [Bug c++/109763] New: " jlame646 at gmail dot com
2023-05-07  4:28 ` [Bug c++/109763] " pinskia at gcc dot gnu.org
2023-05-07  4:29 ` pinskia at gcc dot gnu.org
2023-05-07  4:31 ` pinskia at gcc dot gnu.org
2023-05-07  5:43 ` jlame646 at gmail dot com
2023-05-07  5:45 ` jlame646 at gmail dot com
2023-05-07  9:19 ` jlame646 at gmail dot com
2023-05-07 10:43 ` pinskia at gcc dot gnu.org
2023-05-07 10:45 ` pinskia at gcc dot gnu.org
2023-05-07 11:08 ` jlame646 at gmail dot com [this message]
2023-05-08  4:02 ` jlame646 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-109763-4-MfjEbWyqKR@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).