public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-4963] libstdc++: Fix inconsistent noexcept-specific for valarray begin/end Date: Fri, 5 Nov 2021 21:45:54 +0000 (GMT) [thread overview] Message-ID: <20211105214554.C5C7B3857C44@sourceware.org> (raw) https://gcc.gnu.org/g:2b2d97fc545635a0f6aa9c9ee3b017394bc494bf commit r12-4963-g2b2d97fc545635a0f6aa9c9ee3b017394bc494bf Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Nov 5 21:42:20 2021 +0000 libstdc++: Fix inconsistent noexcept-specific for valarray begin/end These declarations should be noexcept after I added it to the definitions in <valarray>. libstdc++-v3/ChangeLog: * include/bits/range_access.h (begin(valarray), end(valarray)): Add noexcept. Diff: --- libstdc++-v3/include/bits/range_access.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/include/bits/range_access.h b/libstdc++-v3/include/bits/range_access.h index 3dec687dd94..5e4c4727ebf 100644 --- a/libstdc++-v3/include/bits/range_access.h +++ b/libstdc++-v3/include/bits/range_access.h @@ -110,10 +110,10 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION template<typename _Tp> class valarray; // These overloads must be declared for cbegin and cend to use them. - template<typename _Tp> _Tp* begin(valarray<_Tp>&); - template<typename _Tp> const _Tp* begin(const valarray<_Tp>&); - template<typename _Tp> _Tp* end(valarray<_Tp>&); - template<typename _Tp> const _Tp* end(const valarray<_Tp>&); + template<typename _Tp> _Tp* begin(valarray<_Tp>&) noexcept; + template<typename _Tp> const _Tp* begin(const valarray<_Tp>&) noexcept; + template<typename _Tp> _Tp* end(valarray<_Tp>&) noexcept; + template<typename _Tp> const _Tp* end(const valarray<_Tp>&) noexcept; /** * @brief Return an iterator pointing to the first element of
reply other threads:[~2021-11-05 21:45 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=20211105214554.C5C7B3857C44@sourceware.org \ --to=redi@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).