public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r14-6793] libstdc++: add missing include in ranges_util.h Date: Thu, 21 Dec 2023 21:55:37 +0000 (GMT) [thread overview] Message-ID: <20231221215537.328E03882669@sourceware.org> (raw) https://gcc.gnu.org/g:a6bbaab2732defa0a901c655e6aacf89e7f746a2 commit r14-6793-ga6bbaab2732defa0a901c655e6aacf89e7f746a2 Author: Arsen Arsenović <arsen@aarsen.me> Date: Sun Nov 5 13:54:54 2023 +0100 libstdc++: add missing include in ranges_util.h libstdc++-v3/ChangeLog: * include/bits/ranges_util.h: Add missing <bits/invoke.h> include. Diff: --- libstdc++-v3/include/bits/ranges_util.h | 1 + 1 file changed, 1 insertion(+) diff --git a/libstdc++-v3/include/bits/ranges_util.h b/libstdc++-v3/include/bits/ranges_util.h index 185e46ec7a9..ad61a19dd33 100644 --- a/libstdc++-v3/include/bits/ranges_util.h +++ b/libstdc++-v3/include/bits/ranges_util.h @@ -33,6 +33,7 @@ #if __cplusplus > 201703L # include <bits/ranges_base.h> # include <bits/utility.h> +# include <bits/invoke.h> #ifdef __glibcxx_ranges namespace std _GLIBCXX_VISIBILITY(default)
reply other threads:[~2023-12-21 21:55 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231221215537.328E03882669@sourceware.org \ --to=arsen@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).