-
-
Notifications
You must be signed in to change notification settings - Fork 18
Open
Description
What?
Why?
My assumption is, that there is a lot of undefined behavior in this code.
We could talk about fuzzing, porting C code, performance benchmarks and more.
How?
- Create a naive implementation of
strstr
in Rust. - Benchmark it against the existing C version.
- Port the C
strstr
version verbatim to Rust. - Run afl (fuzzing) against it to check for edge-cases.
Thanks for the inspiration @jorgelbg.