public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95564] GCC rejects lambda expression with "noexcept(1+1)"
Date: Tue, 09 Jun 2020 23:04:15 +0000	[thread overview]
Message-ID: <bug-95564-4-OF6uydW4zR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95564-4@http.gcc.gnu.org/bugzilla/>

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

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

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
There was some discussion on the Core C++ mailing list about whether a
conversion to bool should be narrowing, and though opinions differed, I think
gcc isn't incorrect in rejecting this code.

  reply	other threads:[~2020-06-09 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-06 16:18 [Bug c++/95564] New: " haoxintu at gmail dot com
2020-06-09 23:04 ` mpolacek at gcc dot gnu.org [this message]
2021-12-09  6:51 ` [Bug c++/95564] " pinskia at gcc dot gnu.org
2021-12-16 10:17 ` de34 at live dot cn
2024-01-19 18:47 ` 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-95564-4-OF6uydW4zR@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).