Initializer parameter evaluation order

[nmgswift]

Does Swift guarantee parameter evaluation order in an initializer? For example:

struct Foo {
  let bar: String
  let baz: Int
}
let test = Foo(bar: doSomethingAndReturnString(), baz: doSomethingAndReturnInt())

Will doSomethingAndReturnString() always be called before doSomethingAndReturnInt(), or could compiler optimizations change evaluation order? And, either way, is this behavior documented anywhere?

[Jumhyn (Frederick Kellison-Linn)]

Recent relevant post: Confusing evaluation order - #13 by dabrahams

[nmgswift]

Thanks for the link! However, this seems to be a post more about functions called within functions, rather than functions called as arguments to parameters.

I was aware of this reply here:

Confusing evaluation order

Swift uses a strict left-to-right evaluation order in most situations. In this case, that causes the value of whole to be copied before the other arguments to describe are evaluated. We’ve considered (CC @Andrew_Trick) changing the evaluation of this so that self is not evaluated by copy but instead by immutable borrow, which in this case would cause this code to not compile due to an exclusivity error when the variable is modified while being immutably borrowed.

but the "in most situations" makes me wonder if the parameters example I gave is included. Additionally, it is an older post, so I'm not sure how accurate the answer is to Swift today.