actually when to ; and when not to ; in Rust is still in that category of annoying trivia where i understand the rules but i have not yet programmed my fingers to play along irritating 🤓

ugh i want my std::ops::Index::index() method to return Option<&T> not &Option<T> my data structure either stores T or not, the option is implicit, and i can’t return a ref to something that doesn’ exist

it’s a data structure so it needs a fuzzer and a test oracle i’ve written a BmpVec for small bitmap-compressed vectors now i’m writing a BlimpVec which is not compressed and doesn’t have unsafe code

while i’m getting this fuzzer going, i would be very grateful if any rustaceans could express an opinion on my unsafe code - the important functions are from_cooked_parts() and as_cooked_parts() dotat.at/cgi/git/dnstrie.git…

yay 🤪 AddressSanitizer: double-free

aaaah when i overwrite myself, rust drops my old value, but instead i wanted rust to forget about it

fuzzer goes brrrrrrrrrrrrrrrrrrrrrrrrrr

they should rename libfuzzer to lovefuzzer except that might have the wrong implications wrt furries

“warning: unsafe function's docs miss `# Safety` section” yes yes @dsilverstone already said that good grief

ooh a bug in clippy warning: you should consider adding a `Default` implementation for `bmpvec::BmpVec<T>` help: try this impl Default for bmpvec::BmpVec<T> { dear clippy, i think you want impl<T> there, and also i don’t want the bmpvec prefix inside mod bmpvec