Description

This issue was raised when Effect.throttle was updated for Sendability issues: https://github.com/pointfreeco/swift-composable-architecture/pull/3325/files/1ae7e67def1deb8650d79d3bda41f8165243ca7b#r1993347017

From what I can tell, the throttle function requires the Stride to be Sendable, but the most common instances of Stride are not Sendable, so the only way to use the function is to disable the warning/error via @preconcurrency.

Is this an oversight in the implementation? Or is there another form of Stride that is expected to be used here? I haven't been able to find any documentation that would indicate one way or the other.

Checklist

• I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
• If possible, I've reproduced the issue using the main branch of this package.
• This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior

Effect.throttle can be used with StrictConcurrency enabled

Actual behavior

Effect.throttle raises StrictConcurrency warnings/errors because Type 'DispatchQueue.SchedulerTimeType.Stride' does not conform to the 'Sendable' protocol; this is an error in the Swift 6 language mode

Reproducing project

No response

The Composable Architecture version information

1.23.1

Destination operating system

No response

Xcode version information

Xcode 16.4

Swift Compiler version information

swift-driver version: 1.120.5 Apple Swift version 6.1.2 (swiftlang-6.1.2.1.2 clang-1700.0.13.5)
Target: arm64-apple-macosx15.0