# ValueSemantic protocol

**URL:** <https://forums.swift.org/t/valuesemantic-protocol/41686>\
**Category:** Discussion\
**Created:** [November 2, 2020, 3:53am UTC](https://forums.swift.org/t/valuesemantic-protocol/41686 "2020-11-02T03:53:26Z")\
**Posts on this page:** 1\
**Showing post:** 62

<div class="post-metadata">

**Author:** ![anandabits](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/anandabits/32/355_2.png) [@anandabits](https://forums.swift.org/u/anandabits)\
**Post date:** [November 5, 2020, 10:34pm UTC](https://forums.swift.org/t/valuesemantic-protocol/41686/62 "2020-11-05T22:34:14Z")

</div>

> [@dabrahams](#):
>
> I believe what I wrote accommodates such types without the need for any exceptions. If you see something in the document that makes you think otherwise, please explain.

I believe so as well. I’m think your definition is a great start! Thank you for putting the effort into laying it out so clearly and for including pragmatic conventions.

If the community adopts this definition and we move ahead with a proposal to bring support into the language what do you think we do with function types? Would we do something similar to what @Chris_Lattner3 suggested [here](https://forums.swift.org/t/pitch-protocol-based-actor-isolation/41677/43) for `ActorSendable`?

> [@xwu](#):
>
> it'd be not very useful to argue whether `Never` has value semantics.

I would argue that it should conform. Not having this conformance would break the use of `Never` as a bottom type for APIs that are constrained to `ValueSemantic`. I have written lots of generic code that uses `Never` in this way and would use `ValueSemantic`.

---

_[View the full topic](https://forums.swift.org/t/valuesemantic-protocol/41686)._
