On 06/06/19 14:36 +0100, Jonathan Wakely wrote:
On 03/06/19 14:23 +0100, Jonathan Wakely wrote:
In previous standards it is undefined for a container and its allocator
to have a different value_type. Libstdc++ has traditionally allowed it
as an extension, automatically rebinding the allocator
On 03/06/19 14:23 +0100, Jonathan Wakely wrote:
In previous standards it is undefined for a container and its allocator
to have a different value_type. Libstdc++ has traditionally allowed it
as an extension, automatically rebinding the allocator to the
container's value_type. Since GCC 8.1 that
On 03/06/19 22:34 +0100, Jonathan Wakely wrote:
On 03/06/19 23:17 +0200, Rainer Orth wrote:
Hi Jonathan,
In previous standards it is undefined for a container and its allocator
to have a different value_type. Libstdc++ has traditionally allowed it
as an extension, automatically rebinding the
On 03/06/19 23:17 +0200, Rainer Orth wrote:
Hi Jonathan,
In previous standards it is undefined for a container and its allocator
to have a different value_type. Libstdc++ has traditionally allowed it
as an extension, automatically rebinding the allocator to the
container's value_type. Since
Hi Jonathan,
> In previous standards it is undefined for a container and its allocator
> to have a different value_type. Libstdc++ has traditionally allowed it
> as an extension, automatically rebinding the allocator to the
> container's value_type. Since GCC 8.1 that extension has been disabled
In previous standards it is undefined for a container and its allocator
to have a different value_type. Libstdc++ has traditionally allowed it
as an extension, automatically rebinding the allocator to the
container's value_type. Since GCC 8.1 that extension has been disabled
for C++11 and later
