Closed Amanieu closed 6 months ago
@bors r+
:pushpin: Commit a5eddffcb1f62fffdd74fd379cf1606408c7f288 has been approved by Amanieu
It is now in the queue for this repository.
:hourglass: Testing commit a5eddffcb1f62fffdd74fd379cf1606408c7f288 with merge 6359e49e0b753f052e311ff79a7c9fa7c9281a44...
:sunny: Test successful - checks-actions Approved by: Amanieu Pushing 6359e49e0b753f052e311ff79a7c9fa7c9281a44 to master...
It looks like this issue (different optimizations with latest Rust 1.77+ and / or LLVM?) is now happening much more frequently. The Fedora Linux CI for hashbrown has started to fail quite often due to test failures that would be fixed by this commit.
Since v0.14.4 was yanked due to breaking API changes, this fix never landed in a non-yanked stable release of hashbrown. Would it be possible to backport this onto a v0.14 branch based on v0.14.3 and release it as v0.14.5?
@decathorpe I released v0.14.5
Great, thank you!
Previously, it was possible for an uninitialized element to be dropped if all of the following occurred:
clone_from
was called whereT: !Copy
.clone
implementation ofT
panicked.HashMap
contained an entry.Fixes #510