Bump version numbers and fix up warnings

[jngls]

• Bump version numbers to latest
• Fix up new warnings

Maybe Controversial

I've updated rust edition = "2024" - what do you think?

[ihciah]

I've updated rust edition = "2024" - what do you think?

I suggest keeping the status quo. For example, smallvec still uses the 2018 version because upgrading directly may break users. We can consider upgrading in the next major version, but this will still cause users to have to increase their MSRV to upgrade.

[jngls]

Cool. Yeah that makes sense. Reverted the edition change back to 2021.

[onbjerg]

Bump @ihciah, any interest in merging the hashbrown bump? Alternatively, an interest in just using HashMap from std given it's essentially hashbrown anyway?

[ihciah]

Sorry for holding this PR for so long.
I pushed some commits yesterday and reviewed it today. The remaining tasks seem to be adding the unsafe {} and SAFETY: explanations. I believe these will help improve code maintainability. If you’re still up for it, feel free to update the PR and I’ll get it merged.

[ihciah]

Alternatively, an interest in just using HashMap from std given it's essentially hashbrown anyway?

@onbjerg Thanks for the ping.

We can switch to std::collections::HashMap, but since the std implementation is already backed by hashbrown, it doesn’t really give us any extra benefit.

More importantly, both this project and hashbrown expose hashbrown::Equivalent, which lets us perform lookups using different key types. That capability is stronger than what the standard library offers, and there’s no indication that std plans to change its API in this area.

So sticking with hashbrown still gives us the flexibility we rely on.

[jngls]

Yeah still up for it. Most likely tomorrow as I have to wind down now. Cheers!