Re: [PATCH 4/4] libstdc++: Rearrange some range adaptors' data members

2020-09-28 Thread Jonathan Wakely via Gcc-patches
On 28/09/20 09:11 -0400, Patrick Palka via Libstdc++ wrote: On Mon, 28 Sep 2020, Jonathan Wakely wrote: On 28/09/20 00:48 -0400, Patrick Palka via Libstdc++ wrote: > Since the standard range adaptors are specified to derive from the empty > class view_base, making their first data member store

Re: [PATCH 4/4] libstdc++: Rearrange some range adaptors' data members

2020-09-28 Thread Patrick Palka via Gcc-patches
On Mon, 28 Sep 2020, Jonathan Wakely wrote: > On 28/09/20 00:48 -0400, Patrick Palka via Libstdc++ wrote: > > Since the standard range adaptors are specified to derive from the empty > > class view_base, making their first data member store the underlying > > view is suboptimal, for if the underly

Re: [PATCH 4/4] libstdc++: Rearrange some range adaptors' data members

2020-09-28 Thread Jonathan Wakely via Gcc-patches
On 28/09/20 00:48 -0400, Patrick Palka via Libstdc++ wrote: Since the standard range adaptors are specified to derive from the empty class view_base, making their first data member store the underlying view is suboptimal, for if the underlying view also derives from view_base then the two view_ba

[PATCH 4/4] libstdc++: Rearrange some range adaptors' data members

2020-09-27 Thread Patrick Palka via Gcc-patches
Since the standard range adaptors are specified to derive from the empty class view_base, making their first data member store the underlying view is suboptimal, for if the underlying view also derives from view_base then the two view_base subobjects will be adjacent, thus preventing the compiler f