Eliminate fuzz/fuzz_nohook redundancy #161
Merged
Conversation
This file contains 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
frewsxcv
reviewed
Jan 11, 2020
| /// panic!("BOOM") | ||
| /// }); | ||
| /// # } | ||
| /// ``` |
There was a problem hiding this comment.
what happened to this doc comment?
There was a problem hiding this comment.
You're right. It looks like I cut a little too much.
I added a comment explaining the difference between fuzz! and fuzz_nohook! (using the preexisting language).
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.
The common elements of the
fuzz!andfuzz_nohook!macros are consolidated into a single macro,__fuzz!. Thefuzz!andfuzz_nohook!macros are accordingly altered to use__fuzz!. Eliminating this redundancy should facilitate maintainability.