# Noncopyable types in documentation

**URL:** <https://forums.swift.org/t/noncopyable-types-in-documentation/76481>\
**Category:** Swift Documentation Tooling\
**Created:** [December 9, 2024, 12:18pm UTC](https://forums.swift.org/t/noncopyable-types-in-documentation/76481 "2024-12-09T12:18:21Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![vanvoorden](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/vanvoorden/32/33619_2.png) [@vanvoorden](https://forums.swift.org/u/vanvoorden)\
**Post date:** [December 9, 2024, 6:01pm UTC](https://forums.swift.org/t/noncopyable-types-in-documentation/76481/5 "2024-12-09T18:01:37Z")

</div>

> [@Noncopyable Generics in Swift: A Code Walkthrough](https://forums.swift.org/t/noncopyable-generics-in-swift-a-code-walkthrough/70862):
>
> Hi Swift Evolution, For the past few weeks I've been testing out the new generic non-copyable features, by trying to create non-copyable data structures. At the same time, these features are being proposed and reviewed through the Swift evolution process. Non-copyable generics aren't for every-day code – but we've put a lot of care into making them stay out of your way until you need them, and then keeping them usable once you do. They will allow libraries to unlock more performance and safety…

This post from @ben-cohen might also help.

---

_[View the full topic](https://forums.swift.org/t/noncopyable-types-in-documentation/76481)._