It might not be unreasonable for Swift to treat this specific pattern as a special case and promise to evaluate the captures in the original context. But Jordan is right: it would have to be a special case because the semantics today are that the entire expression is evaluated asynchronously.