# Support ~Copyable, ~Escapable in simple standard library protocols

**URL:** <https://forums.swift.org/t/support-copyable-escapable-in-simple-standard-library-protocols/83083>\
**Category:** Pitches\
**Created:** [November 7, 2025, 8:26pm UTC](https://forums.swift.org/t/support-copyable-escapable-in-simple-standard-library-protocols/83083 "2025-11-07T20:26:05Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Jumhyn](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jumhyn/32/3891_2.png) [@Jumhyn](https://forums.swift.org/u/Jumhyn)\
**Post date:** [November 8, 2025, 5:18pm UTC](https://forums.swift.org/t/support-copyable-escapable-in-simple-standard-library-protocols/83083/12 "2025-11-08T17:18:10Z")

</div>

Yeah this is similar to what I’d [imagined](https://forums.swift.org/t/the-future-of-serialization-deserialization-apis/78585/163) in the thread about `~Copyable` x `Codable`—in both cases you have an out because you can throw/return `nil`, though in the case of `LosslessStringConvertible` it does feel _slightly_ more against the spirit of the protocol. I don’t know that that rises to the level where it’s worth totally banning at the library level, though!

---

_[View the full topic](https://forums.swift.org/t/support-copyable-escapable-in-simple-standard-library-protocols/83083)._