earlier replies
yay πŸ€ͺ AddressSanitizer: double-free
1
aaaah when i overwrite myself, rust drops my old value, but instead i wanted rust to forget about it
1
1
1
fuzzer goes brrrrrrrrrrrrrrrrrrrrrrrrrr
1
they should rename libfuzzer to lovefuzzer except that might have the wrong implications wrt furries
1
1
β€œwarning: unsafe function's docs miss `# Safety` section” yes yes @dsilverstone already said that good grief
1
2
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
2
If you can construct a minimal example of it being wrong, please file a bug. The clippy people will appreciate it.
1
hmm the warning doesn't trigger on the obvious simple example play.rust-lang.org/?version=… πŸ€·β€β™‚οΈ
1
When you're otherwise done, point me at your codebase and I'll see if I can dig something out :D
1
clippy was complaining about the lack of impl Default before i added it to dotat.at/cgi/git/dnstrie.git…
2
Replying to @fanf
Hmm, I get paste.rs/TsS which suggests that the problem was already likely fixed. What toolchain are you using? I'm on 1.52.1

May 13, 2021 Β· 7:12 PM UTC

1
Replying to @dsilverstone
i just updated from 1.52.0 to 1.52.1 and the mistake is still there ah nightly has impl<T> rather than bare impl, but it still has the wrong item path
1
oh and actually your paste shows both bugs: if you copy clippy’s suggestion into the code in place of my impl Default, it won’t compile
2
more replies