Should hashlink no longer depend on hashbrown?

[Zizico2]

The SwissTable implementation in hashbrown as been merged to std. rust-lang/rust#58623
Should the dependency be kept or should this use the std version?

[rusty-snake]

The default hasher of std and the hashbrown crate are still different:

The default hashing algorithm is currently SipHash 1-3

The default hashing algorithm is currently AHash

So hashbrown::HashMap is still faster than std::collections::HashMap. However type HashMap<K, V> = std::collections::HashMap<K, V, ahash::RandomState> should have the same performance as hashbrown::HashMap IIUC.

[PsiACE]

love this idea

[Dushistov]

Two versions of hashbrown seems overkill.

[kyren]

Unfortunately, the raw table API is not stabilized in std, which is the only real reason that this crate depends directly on hashbrown. Ideally, hashbrown would be completely unnecessary.

Once the raw table API is stabilized, this crate can easily shift over to use the HashMap types directly from std.