DependencyValue keypath does not conform to sendable

[BrentMifsud]

In the process of swapping out cleanse for swift-dependencies (now that cleanse is archived).

I've been running into this sensibility warning quite a bit while using swift-dependencies.

Has anyone else run into this? Any workarounds?

[mbrandonw]

Hi @BrentMifsud, this is just a bug in Swift <6 and will be fixed once Xcode 16 is officially released. For now you can ignore the warning.

[BrentMifsud]

Hi @BrentMifsud, this is just a bug in Swift <6 and will be fixed once Xcode 16 is officially released. For now you can ignore the warning.

Good to know no action required on my end.

Thanks again for putting this library together. So far, it's been dead simple to work with. Love how it's almost identical to the SwiftUI environment.

Random side question:

Any plans to roll out your own @Entry macro equivalent? For DependencyValues?

[mbrandonw]

Any plans to roll out your own @Entry macro equivalent? For DependencyValues?

There is a PR for part of this (#257) but we're honestly not sure it carries its weight. You can read the discussion here, and please do chime in if you have some ideas to share.

[BrentMifsud]

Seems like this warning still exists in Xcode 16.

[stephencelis]

@BrentMifsud You must either be in Swift 6 language mode (which is still not the default and you must opt into it), or you must enable the InferSendableFromCaptures upcoming feature from your project's build settings or package's Swift settings.

[mnddm]

Hello!
I'm trying to follow the Meet the Composable Architecture tutorials and faced with a similar issue. When I added @Dependency(\.continuousClock) var clock and tried to use it as a timer, I got the error:

Capture of 'self' with non-sendable type 'CounterFeature' in a @Sendable closure

I have Xcode 16 with Swift 6 enabled for my project. I also have a local Swift Package (similar to isowords project structure) where I try to place all my code and the Package also has Swift 6.0 enabled. Enabling the InferSendableFromCaptures option (in Build Settings or in Package settings) doesn't help, moreover it even raises another error that I'm already using Swift 6.0 with this feature.

I believe conforming the CounterFeature to Sendable protocol is wrong way. Am I missing something, could you please help?

Thank you.

[BrentMifsud]

Hello!

I'm trying to follow the Meet the Composable Architecture tutorials and faced with a similar issue. When I added @Dependency(\.continuousClock) var clock and tried to use it as a timer, I got the error:

Capture of 'self' with non-sendable type 'CounterFeature' in a @Sendable closure

I have Xcode 16 with Swift 6 enabled for my project. I also have a local Swift Package (similar to isowords project structure) where I try to place all my code and the Package also has Swift 6.0 enabled. Enabling the InferSendableFromCaptures option (in Build Settings or in Package settings) doesn't help, moreover it even raises another error that I'm already using Swift 6.0 with this feature.

I believe conforming the CounterFeature to Sendable protocol is wrong way. Am I missing something, could you please help?

Thank you.

I think maybe the swift 6 language mode might have some issues.

I tried turning it on, and despite all the concurrency warnings I still have, I was able to build and compile without any issues.

[stephencelis]

Conforming CounterFeature to Sendable is just fine! It will actually infer it for you for types that aren't exported publicly from the module. So if you remove public from this feature, it should build without the explicit conformance, but also explicitly adding the conformance is exactly what you should do when the type is public.