public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95564] New: GCC rejects lambda expression with "noexcept(1+1)" Date: Sat, 06 Jun 2020 16:18:58 +0000 [thread overview] Message-ID: <bug-95564-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95564 Bug ID: 95564 Summary: GCC rejects lambda expression with "noexcept(1+1)" Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: haoxintu at gmail dot com Target Milestone: --- This code test.cc int main(){ auto a = [ & ] (...) noexcept(1+1) {}; return 0; } $g++-trunk test.cc test.cc:2:38: error: narrowing conversion of '2' from 'int' to 'bool' [-Wnarrowing] 2 | auto a = [ & ] (...) noexcept(1+1) {}; | GCC fails to compile it, while clang, icc, or msvc accept it.
next reply other threads:[~2020-06-06 16:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-06 16:18 haoxintu at gmail dot com [this message] 2020-06-09 23:04 ` [Bug c++/95564] " mpolacek at gcc dot gnu.org 2021-12-09 6:51 ` 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@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: linkBe 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).