public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/114438] Missed constraint F2023:c7108
Date: Sat, 23 Mar 2024 20:11:36 +0000	[thread overview]
Message-ID: <bug-114438-4-GuuOesroxo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114438-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from anlauf at gcc dot gnu.org ---
The same text existed in F2018, so it is not new: F2018:C7103 and Note 1.

Either every compiler developer team misunderstood that clause, or we
need an interp, based on the example, to be able to convince all of them.

(I know of developers who do overwrite default constructors, and it currently
works "everywhere", so clarification is important.)

What do you think?

  parent reply	other threads:[~2024-03-23 20:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 23:13 [Bug fortran/114438] New: " kargl at gcc dot gnu.org
2024-03-22 23:14 ` [Bug fortran/114438] " kargl at gcc dot gnu.org
2024-03-23 19:36 ` anlauf at gcc dot gnu.org
2024-03-23 19:56 ` kargl at gcc dot gnu.org
2024-03-23 20:11 ` anlauf at gcc dot gnu.org [this message]
2024-03-23 20:53 ` kargl at gcc dot gnu.org
2024-03-23 21:15 ` kargl at gcc dot gnu.org
2024-03-24  2:49 ` kargl 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-114438-4-GuuOesroxo@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).