# \[Second review\] SE-0390: Noncopyable structs and enums

**URL:** <https://forums.swift.org/t/second-review-se-0390-noncopyable-structs-and-enums/63866>\
**Category:** Proposal Reviews\
**Created:** [March 22, 2023, 12:34am UTC](https://forums.swift.org/t/second-review-se-0390-noncopyable-structs-and-enums/63866 "2023-03-22T00:34:33Z")\
**Posts on this page:** 1\
**Showing post:** 105

<div class="post-metadata">

**Author:** ![jeremyabannister](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jeremyabannister/32/10143_2.png) [@jeremyabannister](https://forums.swift.org/u/jeremyabannister)\
**Post date:** [March 28, 2023, 10:41am UTC](https://forums.swift.org/t/second-review-se-0390-noncopyable-structs-and-enums/63866/105 "2023-03-28T10:41:16Z")

</div>

> [@ksluder](#):
>
> As one of the people who’s commented on the potential virality of `move`,

I’m curious about what you mean by “virality of `move`”. Do you mean the ubiquitous usage of these features across programming domains, despite the core team’s stated assumption that noncopyable types are a niche feature intended for only a couple key use cases?

This concept is the reason I’ve been using up space on this thread to voice my opinions despite not being someone who plans to use noncopyable types in the niche way anytime soon. I’m intrigued by the possibility of more common use cases for noncopyable types (for example, I posted [this](https://forums.swift.org/t/noncopyable-structs-and-enums-as-reference-types-not-just-performance-boosters/63949) recently), and I’m worried that the syntax/feature design might be being overly influenced by the assumption that very few people will find it useful.

> [@ksluder](#):
>
> I’d like to clarify that I can see myself explicitly moving an otherwise copyable type far more often than I would write non-copyable types.

This idea interests me a lot. Does this mean that it can make sense to use `consume` on a copyable type? Because it seems possible to me that this would be the actual way to use these new features in order to replace some classes, without actually needing to use types that are themselves noncopyable.

---

_[View the full topic](https://forums.swift.org/t/second-review-se-0390-noncopyable-structs-and-enums/63866)._