# SE-0556: Cell, ConstCell, and Volatile

**URL:** <https://forums.swift.org/t/se-0556-cell-constcell-and-volatile/89988>\
**Category:** Proposal Reviews\
**Created:** [October 9, 2026, 10:00pm UTC](https://forums.swift.org/t/se-0556-cell-constcell-and-volatile/89988 "2026-10-09T22:00:51Z")\
**Posts on this page:** 1\
**Showing post:** 46

<div class="post-metadata">

**Author:** ![Nobody1707](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/nobody1707/32/2169_2.png) [@Nobody1707](https://forums.swift.org/u/Nobody1707)\
**Post date:** [November 2, 2026, 10:46pm UTC](https://forums.swift.org/t/se-0556-cell-constcell-and-volatile/89988/46 "2026-11-02T22:46:48Z")

</div>

I was under the impression that `ConstCell`s primary purpose was to represent the contents of a C `T const*` to a potentially non-const value. So that, for instance, a Swift implementation of a C function that takes a `T* dst, T const* src, size_t len` triple can import the parameters as `dst: Span<Cell<T>>, src: Span<ConstCell<T>>` and merely get tearing instead of undefined behavior if someone mutates `src` out from under you. Or to protect you from UB if the function in question is akin to `memmove` and `dst` and `src` overlap.

---

_[View the full topic](https://forums.swift.org/t/se-0556-cell-constcell-and-volatile/89988)._
