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
clippy was complaining about the lack of impl Default before i added it to dotat.at/cgi/git/dnstrie.gitβ¦
2
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
1
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
Iiinteresting. Clippy still mentions the submodule name but gets the impl<T>. rust-analyzer's create-default-impl-from-new doesn't insert the submodule name but misses the <T> off the impl.
May 13, 2021 Β· 7:39 PM UTC
1

