[Accepted with revision] SE-0395: Observability

[vanvoorden (Rick van Voorden)]

@scanon

It's also really important to be clear that having done one now does not preclude doing the other in the future. Observable is an new feature, and as with all features in Swift we expect it to continue to grow and develop in the years to come, and encourage the community to help provide examples to guide that growth.

I actually brought this up to a few engineers from Apple at the SwiftUI summit these last two days. Because the withObservationTracking that accepts willSet and didSet are @_spi(SwiftUI) (for now)… it's not completely clear what a "evolution" looks like to then just remove that spi and launch this as a legit "public" API. Would that be something that would need an internal SwiftUI approval? Would the community just make that decision to approve and then SwiftUI just has to go along with what the community wants?

The consensus I heard seems to be that yes the decision to launch willSet and didSet should be driven by the open-source evolution review and approval process.

I'm not personally blocked on willSet and didSet… but I know a lot of engineers are blocked on migrating from Combine and launching this to public would help those engineers move to Observable without all the workarounds.