Re: [PATCH] libstdc++/ranges: Use perfect forwarding in _Pipe and _Partial ctors

On Thu, 11 Jan 2024 at 16:12, Patrick Palka wrote: > > On Thu, 11 Jan 2024, Jonathan Wakely wrote: > > > On Wed, 10 Jan 2024 at 21:40, Patrick Palka wrote: > > > > > > Tested on x86_64-pc-linux-gnu, does this look OK for trunk? > > > > > > -- >8 -- > > > > > > This avoids redundant moves when

Re: [PATCH] libstdc++/ranges: Use perfect forwarding in _Pipe and _Partial ctors

On Thu, 11 Jan 2024, Jonathan Wakely wrote: > On Wed, 10 Jan 2024 at 21:40, Patrick Palka wrote: > > > > Tested on x86_64-pc-linux-gnu, does this look OK for trunk? > > > > -- >8 -- > > > > This avoids redundant moves when composing and partially applying range > > adaptor objects. > > > > Note

Re: [PATCH] libstdc++/ranges: Use perfect forwarding in _Pipe and _Partial ctors

On Wed, 10 Jan 2024 at 21:40, Patrick Palka wrote: > > Tested on x86_64-pc-linux-gnu, does this look OK for trunk? > > -- >8 -- > > This avoids redundant moves when composing and partially applying range > adaptor objects. > > Note that the new constraints on _Partial's constructor templates are

[PATCH] libstdc++/ranges: Use perfect forwarding in _Pipe and _Partial ctors

Tested on x86_64-pc-linux-gnu, does this look OK for trunk? -- >8 -- This avoids redundant moves when composing and partially applying range adaptor objects. Note that the new constraints on _Partial's constructor templates are needed so that it's not inadvertently chosen over the copy