public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/114808] Qualified void return type is not diagnosed
Date: Mon, 22 Apr 2024 19:11:54 +0000	[thread overview]
Message-ID: <bug-114808-4-JDeKJzQ9XV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114808-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't see such a sentence in C++17 nor other C++ standards.
All compilers I've tried accept it.
On the other side, e.g. http://eel.is/c++draft/basic.fundamental#15 talks about
functions returning cv void.
Similarly http://eel.is/c++draft/stmt.return#2
And
https://eel.is/c++draft/dcl.fct#14 explicitly says
"The return type shall be a non-array object type, a reference type, or cv
void."
This is something that was earlier said in [expr.call]/3 (e.g. in C++17,
[expr.call]/5 in C++20).

  reply	other threads:[~2024-04-22 19:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 17:02 [Bug c/114808] New: " luigighiron at gmail dot com
2024-04-22 19:11 ` jakub at gcc dot gnu.org [this message]
2024-04-22 19:15 ` [Bug c/114808] " pinskia at gcc dot gnu.org
2024-04-22 19:17 ` jakub at gcc dot gnu.org
2024-04-22 19:34 ` pinskia at gcc dot gnu.org
2024-04-22 19:42 ` luigighiron at gmail dot com
2024-04-22 19:46 ` luigighiron at gmail dot com
2024-04-22 19:54 ` jsm28 at gcc dot gnu.org
2024-04-22 20:11 ` pinskia at gcc dot gnu.org
2024-04-23  1:12 ` luigighiron at gmail dot com
2024-04-23  5:54 ` xry111 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-114808-4-JDeKJzQ9XV@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).