So I am wondering if it is guaranteed that
t.a == 0andt.b == 1?
This will always be true so long as a comes before b in the class declaration and nothing else calls f() between the initialization of a and b. Class members are initialized in the order they are declared in the class. [class.base.init]/11:
In a non-delegating constructor, initialization proceeds in the following order: […]
- Then, non-static data members are initialized in the order they were declared in the class definition (again regardless of the order of the mem-initializers).
So since a comes before b then when the constructor initializes a it will call f() the first time and then it will call it a second time when it initializes b.
We also know there is a sequence point between member initializer because [class.base.init]/7:
[…]The initialization performed by each mem-initializer constitutes a full-expression. Any expression in a mem-initializer is evaluated as part of the full-expression that performs the initialization.
tells us each initializer is a full expression and each full expression is sequenced: [intro.execution]/14
Every value computation and side effect associated with a full-expression is sequenced before every value computation and side effect associated with the next full-expression to be evaluated.