-
Notifications
You must be signed in to change notification settings - Fork 6
add a sed fuzzer #72
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
base: main
Are you sure you want to change the base?
add a sed fuzzer #72
Conversation
} | ||
"d" => { | ||
// Delete: [addr]d | ||
if rng.random_bool(0.3) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider having generate_address
create 0, 1, or 2 addresses.
}; | ||
|
||
// Compare results | ||
compare_result( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep in mind that the POSIX standard leaves the result of many behaviors undefined. (There are five mentions in the standard.) We need to be careful to avoid these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think the de-facto standard is the GNU impl :)
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #72 +/- ##
=====================================
Coverage 0.00% 0.00%
=====================================
Files 12 12
Lines 2632 2632
Branches 225 225
=====================================
Misses 2632 2632
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
far from perfect
Currently:
but found:
#71