public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "François Dumont" <frs.dumont@gmail.com>
To: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Deque fiil/copy/move/copy_backward/move_backward/equal overloads
Date: Tue, 16 Jul 2019 17:20:00 -0000	[thread overview]
Message-ID: <2cd43ed9-364b-3705-c167-1eaa1389c388@gmail.com> (raw)
In-Reply-To: <9357e741-9a71-6783-2ce9-24ba8a3939ba@gmail.com>

Ping ?

On 6/19/19 7:32 PM, François Dumont wrote:
> I wanted to implement Debug overloads for those already existing 
> overloads but then realized that those algos could be generalized. 
> This way we will benefit from the memmove replacement when operating 
> with C array or std::array or std::vector iterators.
>
> I might do the same for lexicographical_compare one day.
>
> The ChangeLog below is quite huge so I attached it. I wonder if I 
> could use deque::iterator and deque::const_iterator in place of the 
> _Deque_iterator<> to reduce it ?
>
> Tested under Linux x86_64 normal and debug modes, ok to commit ?
>
> François
>

  parent reply	other threads:[~2019-07-16 16:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 17:32 François Dumont
2019-06-20  8:38 ` Morwenn Ed
2019-06-21  4:43   ` François Dumont
2019-07-16 17:20 ` François Dumont [this message]
2019-07-26  9:13 ` PR 90409 " François Dumont
2019-08-01  9:57   ` Jonathan Wakely
2019-08-01 10:36     ` Daniel Krügler
2019-08-01 11:01       ` Jonathan Wakely
2019-08-01 11:31         ` Daniel Krügler
2019-08-01 12:52           ` Jonathan Wakely
2019-08-01 12:53             ` Jonathan Wakely
2019-08-21 21:18               ` François Dumont
2019-08-26 20:31                 ` François Dumont

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=2cd43ed9-364b-3705-c167-1eaa1389c388@gmail.com \
    --to=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).