-
Notifications
You must be signed in to change notification settings - Fork 164
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
Update to hashbrown 0.11 (MSRV 1.49) #181
Conversation
I've left this as a draft because I'm not keen on such a recent MSRV. Technically, |
MSRV aside, it looks like performance has generally improved:
|
Oh that's a big improvement. And this is the hashbrown with the compile-time improvements too, I assume (The rust-lang/rust/pull/77566 issue) |
Yes I agree with you about waiting with the update. Since rustc uses us, I guess they might want that we update, though. With that thought, we can't wait too long. |
Maybe so, but |
Rustc switched to hashbrown 0.11 some time ago, btw. |
FWIW, my own primary concern for MSRV is for RHEL, but we just released RHEL 8.4.0 with Rust 1.49! So I would be OK with bumping this now, if there are no other objections. |
I wish we could be less agressive about raising the MSRV. Our problem is that hashbrown is a core dependency, and they have already bumped. |
Is there perhaps a time-based policy you'd be comfortable with? e.g. For Rayon we chose to stay at least 1 year old for MSRV, and we haven't heard any complaints since we started that a couple years ago. Rust 1.49 was released on New Year's Eve, 2020-12-31, so it's now 5 months old. |
one alternative if you want want to raise MSRV is to allow both versions of hashbrown via |
Yes that's a good idea - can the distributions work with that? Cargo isn't "nice" about combining dependency ranges, so for most users that change would be exactly the same as the change in the PR as it is at present. But if distributions (like debian stable) can work with it, it is worthwhile to use a range like that. |
@cuviper We could just go with having desired-required time limits. Let's say 1 year is desired, but we still go with this change now, because we just have to follow hashbrown (our major upstream), so we put a "required" limit on that, which is less than 1 year, for example a few releases. |
Let's merge this now, current Rust version is 1.53. |
OK, I'll merge and publish it! |
Thanks for doing it! |
No description provided.