Yes, the rationale is covered in Annex C (informative) Compatibility specifically [diff.dcl]p10 (emphasis mine): Affected subclause: [dcl.init.aggr] Change: In C++, designated initialization support is restricted compared to the corresponding functionality in C. In C++, designators for non-static data members must be specified in declaration order, designators for array elements and nested designators are not supported, … Read more
Designated initialisers come in two flavours: 1) It provides a quick way of initialising specific elements in an array: int foo[10] = { [3] = 1, [5] = 2 }; will set all elements to foo to 0, other than index 3 which will be set to 1 and index 5 which will be set … Read more
I’m not sure you can do it in C++. For the stuff that you need to initialize using designated initializers, you can put those separately in a .c file compiled as C99, e.g.: // In common header file typedef union my_union { int i; float f; } my_union; extern const my_union g_var; // In file … Read more
According to the C++ 20 Standard (9.3.1 Aggregates. p. #3) (3.1) — If the initializer list is a designated-initializer-list, the aggregate shall be of class type, the identifier in each designator shall name a direct non-static data member of the class, and the explicitly initialized elements of the aggregate are the elements that are, or … Read more
I used: convenience init() { self.init(nibName:nil, bundle:nil) } Some people suggested: convenience init(){ self.init() } But this gives you an infinite loop.
init(texture: SKTexture!, color: UIColor!, size: CGSize) is the only designated initializer in the SKSpriteNode class, the rest are all convenience initializers, so you can’t call super on them. Change your code to this: class Creature: SKSpriteNode { var isAlive:Bool = false { didSet { self.hidden = !isAlive } } var livingNeighbours:Int = 0 init() { … Read more
This is a C99 feature that allows you to set specific fields of the struct by name in an initializer. Before this, the initializer needed to contain just the values, for all fields, in order — which still works, of course. So for the following struct: struct demo_s { int first; int second; int third; … Read more