# SE-0475: Transactional Observation of Values

**URL:** <https://forums.swift.org/t/se-0475-transactional-observation-of-values/79224>\
**Category:** Proposal Reviews\
**Created:** [April 11, 2025, 1:56am UTC](https://forums.swift.org/t/se-0475-transactional-observation-of-values/79224 "2025-04-11T01:56:25Z")\
**Posts on this page:** 1\
**Showing post:** 71

<div class="post-metadata">

**Author:** ![John\_McCall](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/john_mccall/32/1351_2.png) [@John\_McCall](https://forums.swift.org/u/John_McCall)\
**Post date:** [June 11, 2025, 7:21pm UTC](https://forums.swift.org/t/se-0475-transactional-observation-of-values/79224/71 "2025-06-11T19:21:17Z")

</div>

> [@KeithBauerANZ](#):
>
> As [discussed in the ProgressReporter thread](https://forums.swift.org/t/review-2nd-sf-0023-progressreporter-progress-reporting-in-swift-concurrency/80284/15), `withObservationTracking` inherently creates a window where _concurrent_ changes are _not_ tracked. Observation really wants to be able to guarantee that `Observable` types are either global-actor-isolated or non-Sendable, which the type system can't represent.

This looks like a real problem in the current implementation, but it isn't inherent to the design and should be fixable.

---

_[View the full topic](https://forums.swift.org/t/se-0475-transactional-observation-of-values/79224)._