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

Remove redundant async tests, do some cleanup #120

Merged
merged 5 commits into from
May 30, 2024
Merged

Remove redundant async tests, do some cleanup #120

merged 5 commits into from
May 30, 2024

Conversation

dbrgn
Copy link
Owner

@dbrgn dbrgn commented May 26, 2024

Some cleanup commits. The async simplification was discussed here: #119 (review) @asasine do you want to take a look at this PR?

Note: The delay async tests were not removed, since in the delay module, the async impl doesn't just call through to the sync impl.

dbrgn added 5 commits May 26, 2024 23:05
Remove previous async tests and replace them with a single test that
tests all four trait methods.

The reasoning is that – given that the async trait impls always call the
synchronous variant – the repeated async tests don't really bring much
added value. A single test that ensures that async is working should be
sufficient, and simplifies maintenance.
Remove previous async tests and replace them with a single test that
tests all four trait methods.

The reasoning is that – given that the async trait impls always call the
synchronous variant – the repeated async tests don't really bring much
added value. A single test that ensures that async is working should be
sufficient, and simplifies maintenance.
@dbrgn dbrgn self-assigned this May 26, 2024
@dbrgn dbrgn changed the title Various cleanup tasks Remove redundant async tests, do some ocleanup May 26, 2024
@dbrgn dbrgn changed the title Remove redundant async tests, do some ocleanup Remove redundant async tests, do some cleanup May 26, 2024
Copy link
Contributor

@asasine asasine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

From the perspective of the test, there's no way to know that the impl is async-over-sync, so it would be great to come up with a way to actually run through the same test body for both, but I agree with your earlier point that of probably doesn't warrant the complexity.

@dbrgn dbrgn merged commit d1e353c into main May 30, 2024
3 checks passed
@dbrgn dbrgn deleted the cleanup branch May 30, 2024 19:21
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

Successfully merging this pull request may close these issues.

2 participants