public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bill.trost at harmonicinc dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/112796] New: <algorithm> header implicitly includes <concepts> Date: Thu, 30 Nov 2023 23:33:24 +0000 [thread overview] Message-ID: <bug-112796-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112796 Bug ID: 112796 Summary: <algorithm> header implicitly includes <concepts> Product: gcc Version: 12.2.0 URL: https://godbolt.org/z/Pra17xczj Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: bill.trost at harmonicinc dot com Target Milestone: --- Target: x86-64 Created attachment 56739 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56739&action=edit Sample code that incorrectly compiles. The attached code should not compile (and does not compile if you don't include <algorithm>). It should have to #include <concepts>.
next reply other threads:[~2023-11-30 23:33 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 23:33 bill.trost at harmonicinc dot com [this message] 2023-12-01 13:21 ` [Bug libstdc++/112796] " redi at gcc dot gnu.org 2023-12-01 13:28 ` redi 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-112796-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).