Swift 6: reconsider @escaping for optional function-type parameters

+1 for it.

I wonder should it be done with relation to [Pitch] Non-Escapable Types and Lifetime Dependency

Seems that enum Either<A, B> and similar types can also keep noescapable closures. This way Optional<T> will be a particular case.

1 Like