Should ConfirmationDialogState be Sendable?

[jpsim]

ConfirmationDialogState is meant to model state, and if that state is at all accessed from a Sendable context with -strict-concurrency=complete, this will produce a compiler warning that ConfirmationDialogState is not safe to send across contexts like this.

This is a somewhat of a meta-discussion about goals for this project, and the family of pointfreeco packages. Should TCA support writing SwiftUI applications with -strict-concurrency=complete checks enabled without warnings? In our application, ConfirmationDialogState is one of the last pieces that prevents that from happening, so we use @preconcurrency import SwiftUINavigationCore.

[stephencelis]

It definitely should, along with AlertState.

There's an open PR here to address the problem, but isn't passing CI yet: https://github.com/pointfreeco/swiftui-navigation/pull/116

Hopefully soon!

[jpsim]

Great, thanks for sharing.

[mbrandonw]

@jpsim This has now been released in 1.0.1.