On 17 Mar 2016, at 12:38, Christoph Moench-Tegeder wrote:
...
>> Last but not least, please ask about this on the Chromium mailing lists.
>> There must be lots of C++ libraries out there with non-trivial std::pair
>> copy constructors, and they must have some sort of workaround for those.
>
> It'
On 16 Mar 2016, at 22:27, Christoph Moench-Tegeder wrote:
>
> I'm currently working on updating www/chromium to the latest
> version (the 49 versions). Recently (that is, during development
> of version 49) the chromium developers allowed some c++11 features
> to be used.
> Included in those is s
On 16 Mar 2016, at 23:36, Dimitry Andric wrote:
>
> On 16 Mar 2016, at 22:27, Christoph Moench-Tegeder
> wrote:
...
>> Could anyone point me in a direction to resolve this?
...
> Last but not least, please ask about this on the Chromium mailing lists.
> There must be lots of C++ libraries out t
On 18 Mar 2016, at 17:22, Dimitry Andric wrote:
>
> We
> could enable this feature, but then we'd have to bump our libc++
> version, together with all the followup hassle.
There are quite a few ABI-breaking changes in libc++. Some improve standards
compliance and a few improve performance. I’
## Dimitry Andric (d...@freebsd.org):
> In r261801 [1], we turned off the _LIBCPP_TRIVIAL_PAIR_COPY_CTOR option
> in libc++, because it made the ABI incompatible with the version of
> libc++ we had shipped before that time. However, this option makes the
> std::pair copy constructor non-trivial,
Hi,
I'm currently working on updating www/chromium to the latest
version (the 49 versions). Recently (that is, during development
of version 49) the chromium developers allowed some c++11 features
to be used.
Included in those is std::move(), replacing their homegrown
rvalue-reference-generating co
