Re: Movable initializer lists (C++ N4166)

2015-05-06 Thread David Krauss
> On 2015–05–04, at 12:00 AM, David Krauss wrote: > > Besides that, are some machines overloaded? If I need to use POWER, will > there be a learning curve or brittleness as on Darwin? To avoid trial and > error whilst wading into the process, I’m just asking for some personal > confirmation o

Re: Movable initializer lists (C++ N4166)

2015-05-03 Thread David Krauss
> On 2015–05–03, at 11:27 PM, Marc Glisse wrote: > > On Sun, 3 May 2015, David Krauss wrote: > >> (Yes, I know that a “compile farm” exists. It appears to be obsolete; >> perhaps someone could vouch for it?) > > What gave you that impression? It doesn't have a lot of variety, but it has > pe

Re: Movable initializer lists (C++ N4166)

2015-05-03 Thread Marc Glisse
On Sun, 3 May 2015, David Krauss wrote: (Yes, I know that a “compile farm” exists. It appears to be obsolete; perhaps someone could vouch for it?) What gave you that impression? It doesn't have a lot of variety, but it has perfectly usable x86(_64) systems, and some very impressive POWER on

Movable initializer lists (C++ N4166)

2015-05-03 Thread David Krauss
Hi all, A couple months ago I created a patch for movable initializer lists, as proposed in N4166. (A few additional details appeared during implementation, which I can document if anyone asks.) Reference: http://open-std.org/JTC1/SC22/WG21/docs/papers/2014/n4166.pdf As I was in the final stag