# Improving Sendable

**URL:** <https://forums.swift.org/t/improving-sendable/52377>\
**Category:** Pitches\
**Created:** [September 27, 2021, 3:59am UTC](https://forums.swift.org/t/improving-sendable/52377 "2021-09-27T03:59:32Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![Nickolas\_Pohilets](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/nickolas_pohilets/32/10659_2.png) [@Nickolas\_Pohilets](https://forums.swift.org/u/Nickolas_Pohilets)\
**Post date:** [September 28, 2021, 4:56pm UTC](https://forums.swift.org/t/improving-sendable/52377/16 "2021-09-28T16:56:03Z")

</div>

The key path literal you’ve used in the example will be typed as `Sendable`. It takes some effort to get a non-sendable one - it needs to be a subscript key path, capturing a non-Sendable index value.

Even if you get a non-Sendable key path, I think indeed if you don’t leave @MainActor (or any other actor), it should be fine.

But if you want to round-trip it, then indeed it is not possible. But that is not a keypath-specific issue, this is a general limitation of the  
`Sendable`. Safe round-trip requires much more advanced type system features - see [Preventing data races using dependent types](https://forums.swift.org/t/preventing-data-races-using-dependent-types/43231) for example.

---

_[View the full topic](https://forums.swift.org/t/improving-sendable/52377)._
