Kolos Foltányi

One would indeed expect to receive the last element when using throttle. A very common use case for example is to throttle a sequence of progress values where receiving the...

Yes, while the PR addresses issues in cases where the sequence finishes (by returning nil), but as @tarbaiev-smg said, we can still await for the next element longer than interval...

@FranzBusch Here is one I think matches my example: ```swift validate { "-a-b-c-d-e-f-----h-i-j-k-|" $0.inputs[0].throttle(for: .steps(3), clock: $0.clock, latest: true) "-a---c---e---f---h---j---|" } ``` actual: `-a---c---e-------h---j---|`

Hey @Juhnkerg! Have you tried setting `options: [.allowUserInteraction]` parameter on the `UIView.animate()` call? I'm afraid achieving this is more complex, will let you know if I have any ideas.

@Juhnkerg what I have found is that user interaction works during the pop animation, but not during push which is weird... What I would try is to implement the non-interactive...

Can you pls provide a Mockable and a SwiftSyntax version?

Will fix this tomorrow, thanks!

Thanks for the issue! This is very strange... It seems like the stored type is `HTTPCookie` but at the time of mocking, it is already bridged to `NSHTTPCookie`. Also, why...

@MaelRB Thanks for checking the changes! This seems like a Swift bug similar to: https://github.com/swiftlang/swift/issues/82222 Will do some investigation and report it if needed. I’d also like to note that...

Found this reported in: https://github.com/swiftlang/swift/issues/83610 Let's wait for some feedback on the issue.