Brandon Williams

Hi @funct7, this should be fixed with the latest release, 1.9.3, and so I am going to close this for now. Let us know if there are any other problems.

Hey @lukeredpath, just wanted to let you know we haven't forgotten about this. We've made a few small changes and hope to merge it tomorrow, but we may make a...

Hi @alexcho617, thanks for the PR, but I don't think this quite the right fix. I just opened https://github.com/pointfreeco/swift-composable-architecture/pull/3085 to fix a bunch of references in the docs, including this...

Hi @dr-star, see [this](https://github.com/pointfreeco/swift-snapshot-testing/issues/400#issuecomment-765060051) reply on how you can accomplish this. And since this isn't really an issue with the library, and instead more of a feature request (which is...

Hi @IgorRosocha, this was fixed in 0.42.0. Have you tried that? Also there has been many releases since then, so we recommend updating to the newest.

Oh sorry, I saw your first mention of 0.41 and thought that is what you were using. Are you able to share a sample project that reproduces the error so...

Hey @yuanhang, thanks for exploring this! We haven't had time to look over it yet, but hopefully in the next few days.

Hi @Thomvis, thanks for the detailed report! Unless I'm missing something, this does behave how I would expect. You are concatenating the effects, and so the `.cancel(id:)` effect doesn't even...

Just to drive home the difference between Combine and Swift concurrency, the following effect will operate how you want: ```swift return .merge( .task { false } .eraseToEffect() .cancellable(id: 1), .cancel(id:...

> I would expect the task to start, but be cancelled almost immediately while it's awaiting the `Task.sleep`. If I delay the `.cancel` by 1 ms it works as intended....