[Development] QtCS: Notes from Modern C++ session

[Olivier Goffart]

On Friday 12. June 2015 14:42:44 Thiago Macieira wrote:
> On Friday 12 June 2015 18:58:59 Marc Mutz wrote:
> > On Friday 12 June 2015 16:37:15 Thiago Macieira wrote:
> > > On Friday 12 June 2015 12:12:17 Olivier Goffart wrote:
> > > > Which mean using things like std::function, std::unique_ptr, in our
> > > > ABI.
> > > > Should we allow that?
> > > 
> > > The problem is deciding between std::function and std::__1::function.
> > 
> > Is __1 now standard? Or just a placeholder for what Clang's libc++ uses?
> 
> It's what libc++ uses, which is the real problem. For as long as there are
> systems where you can opt into libstdc++ or libc++, we should avoid
> hardcoding one or the other.

We are not hard coding one. The compiler selects one.

Now, that would mean that we break binary compatibility when the user switches 
the standard library. The question is whether we want to support this.

-- 
Olivier 

Woboq - Qt services and support - http://woboq.com - http://code.woboq.org