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

Adding fuzzers for unsafe code. #11

Merged
merged 1 commit into from
Jun 24, 2022
Merged

Adding fuzzers for unsafe code. #11

merged 1 commit into from
Jun 24, 2022

Conversation

adetaylor
Copy link
Contributor

I wanted to make sure that there weren't sneaky ways UTF sequences could mess with the byte-based iteration. No problems found!

@ssokolow
Copy link

It's good to see someone is concerned about it. I'm migrating a project from Python's shlex and, being the #![forbid(unsafe_code)] type on what I write and not needing maximum throughput, I've been contemplating offering up a PR to add a paranoid feature flag that switches out the use of unsafe entirely if I can't come up with a way to refactor things to just avoid having to choose.

@fenhl fenhl merged commit 6064b48 into comex:master Jun 24, 2022
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.

3 participants