Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we actually need coEvery and coVerify names? #106

Open
dalewking opened this issue Apr 30, 2024 · 0 comments
Open

Do we actually need coEvery and coVerify names? #106

dalewking opened this issue Apr 30, 2024 · 0 comments

Comments

@dalewking
Copy link

It seems to me that it would be possible to just have every and verify and through overloads or internally it would be possible to handle the distinction without requiring the user to decide whether they need the co version.

There is nothing preventing you from saying coEvery for something is not suspending and it will fail because it will save it as a blocking stub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant