trying something a little more adventurous with Rust: yet another version of my dns-trie adventurous because it will need a little bit of unsafe{} to be competitive with the C version

currently trying to work out how to do this in stable rust: there is Vec::from_raw_parts() BUT NOT Vec::into_raw_parts() 😭

hmm actually i want slice::from_raw_parts which avoids having to worry about the compiler implicitly dropping the vec when i don’t want it to

ugh, having moaned at length about if{}else{} being so much more bulky than ?: i will now moan at length about how a missing ; is so much more tricky than a return keyword

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…