Boost C++ Libraries: Ticket #11697: Boost.Container: Wrong initialization order in tuple copy-constructor

component changed; owner set

Wed, 30 Sep 2015 14:44:29 GMT

owner set to Ion Gaztañaga
component None → container

Wed, 30 Sep 2015 15:05:10 GMT

Second try (now with the code embedded in a code block):

   // Construct tuple from another tuple.
   template<typename... VValues>
   tuple(const tuple<VValues...>& other)
      // : m_head(other.head()), inherited(other.tail())
      : inherited(other.tail()), m_head(other.head())
   {}

status changed; resolution set

Ion Gaztañaga — Wed, 30 Sep 2015 20:40:36 GMT

status new → closed
resolution → fixed

Thanks for the report. Inherited will always be constructed first, as the initialization order is fixed by the language despite the initialization list. In any case, it's misleading and it should be corrected. Fixed in commit:

https://github.com/boostorg/container/commit/79274e4aae91c563be1e49046bdf98b589d35294

Thu, 01 Oct 2015 12:46:30 GMT

The code was not wrong, I should have been clearer in my wording. The "problem" is that our compiler (ARMCC) reports a warning in this case. Thanks for silencing it! :-)