If it were exact 1:1 equivalent, generating Rust code operating on a raw buffer with no bounds checks, then no. However, existing parsers in Rust take advantag

If it were exact 1:1 equivalent, generating Rust code operating on a raw buffer with no bounds checks, then no. However, existing parsers in Rust take advantage of its macros and type system to provide more guarantees at compile time, so perhaps a different approach would not allow the logic error that lead to the bug.