[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: move constructors likely a requirement
From: |
Carlo De Falco |
Subject: |
Re: move constructors likely a requirement |
Date: |
Thu, 5 Sep 2019 11:59:40 +0000 |
> Il giorno 4 set 2019, alle ore 20:14, John W. Eaton <address@hidden> ha
> scritto:
>
> If I understand correctly, -Wpessimizing-move is supposed to be implied when
> compiling C++ code with GCC and using -Wall.
If I understand correctly, copy elision is mandated by the standard only since
c++14, while we are using c++11.
Could it be possible that gcc and clang have different criteria to decide
whether to make the optimization?
c.
- Re: move constructors likely a requirement, (continued)
- Re: move constructors likely a requirement, John W. Eaton, 2019/09/04
- Re: move constructors likely a requirement, Carlo De Falco, 2019/09/05
- Re: move constructors likely a requirement, John W. Eaton, 2019/09/05
- Re: move constructors likely a requirement, Carlo De Falco, 2019/09/05
- Re: move constructors likely a requirement, John W. Eaton, 2019/09/05
- Re: move constructors likely a requirement, Carlo de Falco, 2019/09/05
- Re: move constructors likely a requirement, Carlo de Falco, 2019/09/05
- Re: move constructors likely a requirement, kingcrimson, 2019/09/06
- Re: move constructors likely a requirement, kingcrimson, 2019/09/06
- Re: move constructors likely a requirement, Carlo De Falco, 2019/09/06
- Re: move constructors likely a requirement,
Carlo De Falco <=
- Re: move constructors likely a requirement, John W. Eaton, 2019/09/05
- Re: move constructors likely a requirement, Carlo De Falco, 2019/09/05
- Re: move constructors likely a requirement, Carlo De Falco, 2019/09/05
- Re: move constructors likely a requirement, Carlo De Falco, 2019/09/05