Fix mem::uninitialized UB warning#100
Conversation
Gankra
left a comment
There was a problem hiding this comment.
woah yeah, weird whack code
|
Any chance of a release with this fix? The crate is still fairly widely used, and with rust-lang/rust#71274 we are turning the UB here into a panic, which breaks the released version of this crate. |
|
Done. |
|
@Gankra looks like something went wrong? I cannot see a new version at https://crates.io/crates/linked-hash-map. |
|
whoops sorry, fixed |
|
Awesome, thanks. :) |
|
@Gankra is there any plan on yanking the older (unsound) versions? This crate has many reverse dependencies yanking the older ones would ensure that they obtain a sound version of this crate instead of bumping the minimum dependency to 0.5.3 |
|
@Gankra a friendly reminder - it'd be great to yank the previous version as I've been bitten by this as well when using the toml_edit crate and had to scan the backtrace and dig a bit to find that I should bump this transitive dependency to 0.5.3. Pretty please 🙇 (if not that's fine too ofc, just let us know 🙂) |
|
FWIW, |
There is a long-fixed issue[1] that we hit on this upgrade. Honestly I'm surprised that dependabot didn't upgrade us on this. [1]: contain-rs/linked-hash-map#100
There is a long-fixed issue[1] that we hit on this upgrade. Honestly I'm surprised that dependabot didn't upgrade us on this. [1]: contain-rs/linked-hash-map#100
This commit requires linked-hash-map to include contain-rs/linked-hash-map#100 When linked-hash-map is on v0.5.2, ttl_cache can panic due to the UB checks implemented in Rust 1.48: rust-lang/rust#66151
Scary-looking warning fixable as far as I can tell with one-line patch