From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Remove instantiations when no concept check
Date: Tue, 10 Nov 2015 13:08:00 -0000 [thread overview]
Message-ID: <20151110130823.GB2937@redhat.com> (raw)
In-Reply-To: <56410CA6.5030803@gmail.com>
On 09/11/15 22:14 +0100, François Dumont wrote:
>Hi
>
> I just committed this trivial cleanup.
>
>2015-11-09 François Dumont <fdumont@gcc.gnu.org>
>
> * include/bits/stl_algo.h
> (partial_sort_copy): Instantiate std::iterator_traits only if concept
> checks.
> (lower_bound): Likewise.
> (upper_bound): Likewise.
> (equal_range): Likewise.
> (binary_search): Likewise.
> * include/bits/stl_heap.h (pop_heap): Likewise.
Thanks! The unused-local-typedefs warnings are quite noisy, so it's
good to get rid of them.
prev parent reply other threads:[~2015-11-10 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 21:14 François Dumont
2015-11-10 13:08 ` Jonathan Wakely [this message]
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=20151110130823.GB2937@redhat.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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: link
Be 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).