News for hackers. Stuff that matters.
Re:C++17 is formally approved by jcelerier on Thursday September 07, 2017 @10:37AM (#15192218)
it has to work with unnamed tuples:

const auto [ x, y ] = make_tuple(1, 23);

Re:C++17 is formally approved by dvlsg on Thursday September 07, 2017 @11:05AM (#15192493)
Tuples are ordered though. I don't usually think of structs by the order the properties are declared - I usually think of them by name.

I am, admittedly, not primarily a c++ dev though. Are structs typically ordered data structures in c++?

Re:C++17 is formally approved by nly on Thursday September 07, 2017 @07:32PM (#15196736)
> I don't usually think of structs by the order the properties are declared

In C++ you have to, since it's guaranteed by the language that members are initialized in order of declaration (within the struct). And, like C of course, it also determines memory layout, padding and alignment

> Are structs typically ordered data structures in c++

Yes, and compilers like Clang even let you inspect their memory layout

Re:C++17 is formally approved by jcelerier on Thursday September 07, 2017 @02:32PM (#15194543)
> Tuples are ordered though. I don't usually think of structs by the order the properties are declared - I usually think of them by name.

Think for instance of a 2D point structure. There are tons of implementations, all with different naming conventions ; or sometimes storing them in an array. This allows to just do :

    auto [x, y] = someRandomLibraryPoint();
Re:C++17 is formally approved by 21 on Thursday September 07, 2017 @11:16AM (#15192598)
There is no struct here.

x will be an independent variable which will take the first value from the tuple, and y the second one.

Re:C++17 is formally approved by euyyn on Thursday September 07, 2017 @12:26PM (#15193311)
His point is that it makes sense to destructure in order for tuples, but what makes sense for structs is destructuring by field name.