Re: Limit Debug mode impact: overload __niter_base

2018-07-03 Thread Jonathan Wakely
On 03/07/18 07:47 +0200, François Dumont wrote: Here is the updated patch.     * include/bits/stl_algobase.h (__niter_wrap): New.     (__copy_move_a2(_II, _II, _OI)): Use latter.     (__copy_move_backward_a2(_BI1, _BI1, _BI2)): Likewise.     (fill_n(_OI, _Size, const _Tp&)): Likewise.    

Re: Limit Debug mode impact: overload __niter_base

2018-07-02 Thread François Dumont
Here is the updated patch.     * include/bits/stl_algobase.h (__niter_wrap): New.     (__copy_move_a2(_II, _II, _OI)): Use latter.     (__copy_move_backward_a2(_BI1, _BI1, _BI2)): Likewise.     (fill_n(_OI, _Size, const _Tp&)): Likewise.     (equal(_II1, _II1, _II2)): Use

Re: Limit Debug mode impact: overload __niter_base

2018-07-02 Thread Jonathan Wakely
On 01/07/18 21:20 +0200, François Dumont wrote:     Here is a new proposal between yours and mine.     It is still adding a function to wrap what __niter_base unwrap, I called it __nwrap_iter for this reason. But it takes advantage of Since "niter" refers to __normal_iterator I think a name

Re: Limit Debug mode impact: overload __niter_base

2018-07-01 Thread François Dumont
    Here is a new proposal between yours and mine.     It is still adding a function to wrap what __niter_base unwrap, I called it __nwrap_iter for this reason. But it takes advantage of knowing that __niter_base will only unwrap random access iterator to use an expression to that will do the

Re: Limit Debug mode impact: overload __niter_base

2018-06-27 Thread François Dumont
On 27/06/2018 22:02, Jonathan Wakely wrote: On 27/06/18 21:25 +0200, François Dumont wrote: On 27/06/2018 02:13, Jonathan Wakely wrote: On 26/06/18 17:03 +0100, Jonathan Wakely wrote: On 18/06/18 23:01 +0200, François Dumont wrote: Hi     I abandon the idea of providing Debug algos, it

Re: Limit Debug mode impact: overload __niter_base

2018-06-27 Thread Jonathan Wakely
On 27/06/18 21:25 +0200, François Dumont wrote: On 27/06/2018 02:13, Jonathan Wakely wrote: On 26/06/18 17:03 +0100, Jonathan Wakely wrote: On 18/06/18 23:01 +0200, François Dumont wrote: Hi     I abandon the idea of providing Debug algos, it would be too much code to add and maintain.

Re: Limit Debug mode impact: overload __niter_base

2018-06-27 Thread François Dumont
On 27/06/2018 02:13, Jonathan Wakely wrote: On 26/06/18 17:03 +0100, Jonathan Wakely wrote: On 18/06/18 23:01 +0200, François Dumont wrote: Hi     I abandon the idea of providing Debug algos, it would be too much code to add and maintain. However I haven't quit on reducing Debug mode

Re: Limit Debug mode impact: overload __niter_base

2018-06-27 Thread Jonathan Wakely
On 27/06/18 21:03 +0200, François Dumont wrote: On 26/06/2018 18:03, Jonathan Wakely wrote: On 18/06/18 23:01 +0200, François Dumont wrote: Hi     I abandon the idea of providing Debug algos, it would be too much code to add and maintain. However I haven't quit on reducing Debug mode

Re: Limit Debug mode impact: overload __niter_base

2018-06-27 Thread François Dumont
On 26/06/2018 18:03, Jonathan Wakely wrote: On 18/06/18 23:01 +0200, François Dumont wrote: Hi     I abandon the idea of providing Debug algos, it would be too much code to add and maintain. However I haven't quit on reducing Debug mode performance impact.     So this patch make use of the

Re: Limit Debug mode impact: overload __niter_base

2018-06-26 Thread Jonathan Wakely
On 26/06/18 17:03 +0100, Jonathan Wakely wrote: On 18/06/18 23:01 +0200, François Dumont wrote: Hi     I abandon the idea of providing Debug algos, it would be too much code to add and maintain. However I haven't quit on reducing Debug mode performance impact.     So this patch make use of

Re: Limit Debug mode impact: overload __niter_base

2018-06-26 Thread Jonathan Wakely
On 18/06/18 23:01 +0200, François Dumont wrote: Hi     I abandon the idea of providing Debug algos, it would be too much code to add and maintain. However I haven't quit on reducing Debug mode performance impact.     So this patch make use of the existing std::__niter_base to get rid of

Limit Debug mode impact: overload __niter_base

2018-06-18 Thread François Dumont
Hi     I abandon the idea of providing Debug algos, it would be too much code to add and maintain. However I haven't quit on reducing Debug mode performance impact.     So this patch make use of the existing std::__niter_base to get rid of the debug layer around