Re: [PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-26 Thread Patrick Palka
On Tue, 26 Aug 2025, Tomasz Kaminski wrote: > > > On Tue, Aug 26, 2025 at 5:50 PM Patrick Palka wrote: > On Tue, 26 Aug 2025, Jonathan Wakely wrote: > > > On 20/08/25 10:13 +0200, Tomasz Kamiński wrote: > > > This patch refactors the implementation of bind_front and bind_back

Re: [PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-26 Thread Tomasz Kaminski
On Tue, Aug 26, 2025 at 5:50 PM Patrick Palka wrote: > On Tue, 26 Aug 2025, Jonathan Wakely wrote: > > > On 20/08/25 10:13 +0200, Tomasz Kamiński wrote: > > > This patch refactors the implementation of bind_front and bind_back to > > > avoid using std::tuple for argument storage. Instead, bound a

Re: [PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-26 Thread Patrick Palka
On Tue, 26 Aug 2025, Jonathan Wakely wrote: > On 20/08/25 10:13 +0200, Tomasz Kamiński wrote: > > This patch refactors the implementation of bind_front and bind_back to > > avoid using std::tuple for argument storage. Instead, bound arguments are > > now: > > * stored directly if there is only one

Re: [PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-26 Thread Tomasz Kaminski
On Tue, Aug 26, 2025 at 4:30 PM Patrick Palka wrote: > On Tue, 26 Aug 2025, Tomasz Kaminski wrote: > > > > > > > On Tue, Aug 26, 2025 at 3:54 PM Patrick Palka wrote: > > On Wed, 20 Aug 2025, Tomasz Kamiński wrote: > > > > > This patch refactors the implementation of bind_front and >

Re: [PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-26 Thread Jonathan Wakely
On 20/08/25 10:13 +0200, Tomasz Kamiński wrote: This patch refactors the implementation of bind_front and bind_back to avoid using std::tuple for argument storage. Instead, bound arguments are now: * stored directly if there is only one, * within a dedicated _Bound_arg_storage otehrwise. "otehr

Re: [PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-26 Thread Patrick Palka
On Tue, 26 Aug 2025, Tomasz Kaminski wrote: > > > On Tue, Aug 26, 2025 at 3:54 PM Patrick Palka wrote: > On Wed, 20 Aug 2025, Tomasz Kamiński wrote: > > > This patch refactors the implementation of bind_front and bind_back to > > avoid using std::tuple for argument storage. I

Re: [PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-26 Thread Tomasz Kaminski
On Tue, Aug 26, 2025 at 3:54 PM Patrick Palka wrote: > On Wed, 20 Aug 2025, Tomasz Kamiński wrote: > > > This patch refactors the implementation of bind_front and bind_back to > > avoid using std::tuple for argument storage. Instead, bound arguments are > > now: > > * stored directly if there is

Re: [PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-26 Thread Patrick Palka
On Wed, 20 Aug 2025, Tomasz Kamiński wrote: > This patch refactors the implementation of bind_front and bind_back to > avoid using std::tuple for argument storage. Instead, bound arguments are > now: > * stored directly if there is only one, > * within a dedicated _Bound_arg_storage otehrwise. I

[PATCH v2] libstdc++: Refactor bound arguments storage for bind_front/back

2025-08-20 Thread Tomasz Kamiński
This patch refactors the implementation of bind_front and bind_back to avoid using std::tuple for argument storage. Instead, bound arguments are now: * stored directly if there is only one, * within a dedicated _Bound_arg_storage otehrwise. _Bound_arg_storage holds each argument in an _Indexed_bou