Example for demonstrating test failures #3
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
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.
Hacked together a program to make sure tests are running/failing as expected. The code may not be written with best practices. This PR is not intended to be merged.
The program is similar to
examples/usage.rs, but spawns an additional thread that "corrupts the memory" (It gets access to the samememoryvec by taking in a pointer to bypass Rust's concurrency rules. Very unsafe and can cause race condition, but should be fine since the point is to mess with the vector anyways?)Might be worth merging into the codebase in the future, but not a priority. Right now this is mainly for helping with debugging #1 .