# \#classes

**URL:** https://forums.swift.org/tag/classes/780.md

[Latest](https://forums.swift.org/latest.md) · [Categories](https://forums.swift.org/categories.md) · [Tags](https://forums.swift.org/tags.md)

---

## [Sendable subclassing](https://forums.swift.org/t/sendable-subclassing/90639)

<div class="topic-metadata">

**Author:** [@Nickolas\_Pohilets](https://forums.swift.org/u/Nickolas_Pohilets)\
**Replies:** 0\
**Last updated:** [November 10, 2026, 10:35pm UTC](https://forums.swift.org/t/sendable-subclassing/90639 "2026-11-10T22:35:00Z")

</div>

I just invented a trick that I wanted to share. So, normally you cannot subclass checked Sendable classes: class Base: Sendable { // error: Non-final class \`Base\` cannot conform to the \`Sendable\` protocol. let id: I…

---

## [Noncopyable structs and enums as “reference types”, not just performance boosters?](https://forums.swift.org/t/noncopyable-structs-and-enums-as-reference-types-not-just-performance-boosters/63949)

<div class="topic-metadata">

**Author:** [@jeremyabannister](https://forums.swift.org/u/jeremyabannister)\
**Replies:** 4\
**Last updated:** [March 24, 2023, 6:36pm UTC](https://forums.swift.org/t/noncopyable-structs-and-enums-as-reference-types-not-just-performance-boosters/63949 "2023-03-24T18:36:43Z")

</div>

Up until now I’ve almost exclusively seen the concept of noncopyable types praised for the potential they unlock for highly performant code, but while reading this latest pitch I was intrigued to see the parallels drawn …

---

## [Structures and Classes : Quick Reference Guide](https://forums.swift.org/t/structures-and-classes-quick-reference-guide/62889)

<div class="topic-metadata">

**Author:** [@Marie.B.B](https://forums.swift.org/u/Marie.B.B)\
**Replies:** 9\
**Last updated:** [February 3, 2023, 6:02pm UTC](https://forums.swift.org/t/structures-and-classes-quick-reference-guide/62889 "2023-02-03T18:02:46Z")

</div>

I made a Quick Reference Guide for Structures and Classes. (One Pager.) What thinks? :rainbow::pray::rainbow: