# 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:** 30

<div class="post-metadata">

**Author:** ![fclout](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/fclout/32/36155_2.png) [@fclout](https://forums.swift.org/u/fclout)\
**Post date:** [October 22, 2026, 1:04am UTC](https://forums.swift.org/t/se-0556-cell-constcell-and-volatile/89988/30 "2026-10-22T01:04:07Z")

</div>

Yes, on the AliasedSpan I asked about exactly what it means for load/store semantics and we would probably have to answer these questions to bring the Sendable conformance back:

> [@\[Pitch\] Aliased Span and Ref types](https://forums.swift.org/t/pitch-aliased-span-and-ref-types/88529/14):
>
> - If the optimizer sees two consecutive loads of the same index, can they be combined?
> - If the optimizer sees two adjacent accesses, can it combine them into one?
> - If the optimizer needs to stash a value it loaded from an Aliased\*, instead of spilling to the stack and reload from there, can it choose to reload from the Aliased\*?

The answers are probably no, yes, extremely no.

---

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