# 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:** 22

<div class="post-metadata">

**Author:** ![Douglas\_Gregor](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/douglas_gregor/32/1362_2.png) [@Douglas\_Gregor](https://forums.swift.org/u/Douglas_Gregor)\
**Post date:** [October 23, 2021, 12:06am UTC](https://forums.swift.org/t/improving-sendable/52377/22 "2021-10-23T00:06:09Z")

</div>

Hi all, I'm about to revise this proposal based on feedback here and more experimentation with enabling `Sendable` checking in apps and seeing where the fallout is. One of the things we tripped over is that the limitations on inference of `Sendable` for `public` types is unfortunate. If I have something like this:

```swift
public struct Point {
  var x, y: Double
}

```

It doesn't get a `Sendable` conformance. We don't infer `Sendable` conformances for public types because we didn't want to make an implicit promise to other modules that the `Sendable` conformance exists, but there is a better model for this: [scoped conformances](https://forums.swift.org/t/scoped-conformances/37159/1). If we could infer the `Sendable` conformance but keep it internal to the module, then we would only need to explicitly write `Sendable` when we want to export that information to clients (and commit to it). It's more in line with, e.g., the synthesized member initializers of structs being `internal`.

I'll write it up as part of "version 2" of this pitch, but... what do you think?

Doug

---

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