# SE-0390: @noncopyable structs and enums

**URL:** <https://forums.swift.org/t/se-0390-noncopyable-structs-and-enums/63258>\
**Category:** Proposal Reviews\
**Created:** [February 21, 2023, 3:24pm UTC](https://forums.swift.org/t/se-0390-noncopyable-structs-and-enums/63258 "2023-02-21T15:24:21Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![taylorswift](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/taylorswift/32/43413_2.png) [@taylorswift](https://forums.swift.org/u/taylorswift)\
**Post date:** [February 22, 2023, 5:00pm UTC](https://forums.swift.org/t/se-0390-noncopyable-structs-and-enums/63258/23 "2023-02-22T17:00:46Z")

</div>

> [@gwendal.roue](#):
>
> This doesn't prevent the proposal from being evaluated in isolation - as all proposals.

a little off topic now, but this policy is how we ended up with the [SE-0346 nightmare](https://forums.swift.org/t/se-0346-and-library-evolution/56659). in the end i've seen people hiking toolchain requirements to 5.7 across the board to workaround the issue which was exactly the worst case scenario some of us warned about after it was accepted.

i think we would all be a lot better off if swift evolution started taking the package ecosystem's existence into account, the compiler does not exist in a vacuum.

---

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