public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r11-4553] libstdc++: Avoid narrowing conversion in subrange constructor
@ 2020-10-29 22:50 Jonathan Wakely
  0 siblings, 0 replies; only message in thread
From: Jonathan Wakely @ 2020-10-29 22:50 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:a55cda891d69b5a238d2e237903829995ca7249c

commit r11-4553-ga55cda891d69b5a238d2e237903829995ca7249c
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Oct 29 22:47:22 2020 +0000

    libstdc++: Avoid narrowing conversion in subrange constructor
    
    libstdc++-v3/ChangeLog:
    
            * include/bits/ranges_util.h (subrange::subrange(R&&)): Use
            direct-initialization instead of list-initialization, so a
            potential narrowing conversion from ranges::size(r) to the
            stored size isn't ill-formed.

Diff:
---
 libstdc++-v3/include/bits/ranges_util.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/include/bits/ranges_util.h b/libstdc++-v3/include/bits/ranges_util.h
index cc50e2ad4e4..416c3346254 100644
--- a/libstdc++-v3/include/bits/ranges_util.h
+++ b/libstdc++-v3/include/bits/ranges_util.h
@@ -247,7 +247,7 @@ namespace ranges
 	  && convertible_to<sentinel_t<_Rng>, _Sent>
 	constexpr
 	subrange(_Rng&& __r) requires _S_store_size && sized_range<_Rng>
-	: subrange{__r, ranges::size(__r)}
+	: subrange(__r, ranges::size(__r))
 	{ }
 
       template<__detail::__not_same_as<subrange> _Rng>


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-10-29 22:50 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-29 22:50 [gcc r11-4553] libstdc++: Avoid narrowing conversion in subrange constructor Jonathan Wakely

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).