public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69836] compilation error with constexpr in template types with redeclared methods
Date: Tue, 07 Dec 2021 19:14:21 +0000	[thread overview]
Message-ID: <bug-69836-4-JCrj9uHlZq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-69836-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> I wonder if this is just invalid code but no diagnostic required as state
> changes inside the scope of TemplateObject.

That is it needs to be reinterpret it after the parsing and needs to same
inside the scope itself. Like types of the same name should stay the same if
used inside the class.

Like:

typedef int t;
class y
{
  typedef t u;
  typedef float t;
};
Which GCC only handles currently:
<source>:5:17: error: declaration of 'typedef float y::t' changes meaning of
't' [-fpermissive]
    5 |   typedef float t;
      |                 ^
<source>:1:13: note: 't' declared here as 'typedef int t'
    1 | typedef int t;
      |             ^

  parent reply	other threads:[~2021-12-07 19:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-69836-4@http.gcc.gnu.org/bugzilla/>
2021-12-07 19:01 ` pinskia at gcc dot gnu.org
2021-12-07 19:14 ` pinskia at gcc dot gnu.org [this message]
2023-02-01 20:21 ` jason at gcc dot gnu.org
2023-02-01 20:38 ` jason at gcc dot gnu.org
2023-04-26 21:16 ` cvs-commit at gcc dot gnu.org
2023-05-03  4:37 ` jason 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-69836-4-JCrj9uHlZq@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).