Is Combine Future's promise thread safe?

Question

rnikander OP

Created Jun ’20

Replies 2

Boosts 0

Participants 3

Do I need to protect against races when calling the promise that completes the Future?

Code Block swiftlet future = Future<Int,Never> { promise in 
		savedPromise = promise
}
// later...
// in thread #1
savedPromise?(1)
// in thread #2
savedPromise?(2)

Answered by Engineer in 617446022

Yes, Future is thread safe.

Escaping parameters like that out of a block might result easily in leaks, but should still work.

Boost

Answer 1

Engineer OP

Apple

Jun ’20

Accepted Answer

Yes, Future is thread safe.

Escaping parameters like that out of a block might result easily in leaks, but should still work.

0

Answer 2

Amo7 OP

Jul ’24

Hello,

Will Future be Sendable ?
Because it is an error in Swift 6 :
Non-sendable type 'Future<Bool, any Error>' exiting main actor-isolated context in call to non-isolated property 'value' cannot cross actor boundary

Thanks

1