mock-consensus: ⭐ assert that TestNode<C> is Send + Sync
#4470
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
while refactoring the test node, i found that this is an assumption that isn't explicitly upheld, but is often expected by test code. to prevent future changes/additions from breaking these properties, add some compile-time assertions that a `TestNode<()>` is both `Send` and `Sync`.
cratelyn
added
A-mock-consensus
This was referenced May 24, 2024
erwanor
approved these changes
May 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
while refactoring the test node, i found that this is an assumption that isn't explicitly upheld, but is often expected by test code.
to prevent future changes/additions from breaking these properties, add some compile-time assertions that a
TestNode<()>is bothSendandSync.✅ checklist before requesting a review
if this code contains consensus-breaking changes, i have added the
"consensus-breaking" label. otherwise, i declare my belief that there are not
consensus-breaking changes, for the following reason: