Corey Farwell

This looks like https://github.com/rust-lang/rust/issues/53945 We may want to add this Rust flag temporarily as a workaround https://github.com/rust-fuzz/honggfuzz-rs/commit/44167fe733ed526305d4462a126ac657179049f7

a temporary fix was merged in https://github.com/rust-fuzz/afl.rs/pull/144 and just published in 0.4.2

I think it's worth bumping our aflplusplus git submodule in the afl.rs repo to the latest version and seeing if the error still persists. We're a few versions behind https://github.com/AFLplusplus/AFLplusplus/blob/stable/docs/Changelog.md

if you're wondering how to change the 0.6 requirement, you can modify this line: https://github.com/tikv/tikv/blob/9a81ea6bb70cba355fc669b4f92eb017b511cf0b/fuzz/fuzzer-afl/Cargo.toml#L16 to: ``` afl = { path = "/path/to/afl.rs" } ```

This seems doable. We just need to add a new CLI flag and add a conditional here: https://github.com/rust-fuzz/afl.rs/blob/2a0471fafe31085f426ce6d70f45b1b3fd364694/src/bin/cargo-afl.rs#L137

https://users.rust-lang.org/t/announcing-afl-rs-0-2-bindings-for-american-fuzzy-lop/13981

Could add a restriction such that `exposed` only works on concrete types defined in the same crate. On a side note, this could also help out the 'num-traits' crate which...

> I can imagine a case where you want to use a struct but you don't like the implementation of a trait provided by the crate. If that implementation was...

@Wopple You can differentiate via: ```rust Trait1::get_val(&s) ``` EDIT: I originally wrote this, but it's wrong: ```rust (s as Trait1).get_val() ```

> clone the above geometry, or create one from scratch e.g. using OGR_G_CreateFromWkt, and you can modify it, and you're responsible for deallocating; you can also pass ownership back to...