# Handling a specific kind of over-observing using @Observable

**URL:** <https://forums.swift.org/t/handling-a-specific-kind-of-over-observing-using-observable/89676>\
**Category:** Using Swift\
**Created:** [September 21, 2026, 6:33am UTC](https://forums.swift.org/t/handling-a-specific-kind-of-over-observing-using-observable/89676 "2026-09-21T06:33:04Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![mbrandonw](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mbrandonw/32/349_2.png) [@mbrandonw](https://forums.swift.org/u/mbrandonw)\
**Post date:** [September 21, 2026, 7:35pm UTC](https://forums.swift.org/t/handling-a-specific-kind-of-over-observing-using-observable/89676/7 "2026-09-21T19:35:31Z")

</div>

This came up recently [here](https://forums.swift.org/t/observation-optimizes-away-unnecessary-callbacks-for-equatable-properties-sometimes/89358), and I pointed to a discussion in the review for `@Observable` starting around [here](https://forums.swift.org/t/second-review-se-0395-observability/65261/42) and ending [here](https://forums.swift.org/t/second-review-se-0395-observability/65261/119). The summary is that `@Observable` only minimizes observations when it is reference types all the way down. There is no way to detect a change in a small part of a big value type.

---

_[View the full topic](https://forums.swift.org/t/handling-a-specific-kind-of-over-observing-using-observable/89676)._