-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating to hashbrown 0.12.0 #217
Comments
I hesitate to do this too soon because it bumps MSRV to 1.56, and we already have folks complaining about 1.49 (#214).
Yes, that was me. :) AFAIK our current usage already meets those safety conditions anyway, so there shouldn't be any functional difference for us between 0.11 and 0.12, but I welcome you to confirm that independently.
Both of these are conditions where we just cleared the table and then we are reinserting the same or fewer entries. If there's any question whether that's actually true, I suppose we could add a runtime |
Could we reconsider this now that 1.56 is 6 months old? |
Rust 1.56 has now been out for the best part of 8 months now, are there any plans to release a 1.x version that bumps the dependency? |
I had no plans for 1.x, but we can do it -- see #231. |
Would it be possible to update the hashbrown dependency to 0.12.0? We're going through an audit of indexmap and hashbrown, and we noticed that in hashbrown 0.12.0 they marked
RawTable::insert_no_grow
as unsafe: rust-lang/hashbrown#254.I made an attempt at doing an update, but I'm having trouble telling how
erase_indices
andrebuild_hash_table
guarantee that theindices
table has enough space to useinsert_no_grow
. Do you know what maintains these invariants? Or should we just switch those locations to useRawTable::insert
?The text was updated successfully, but these errors were encountered: