You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The crate seems to be missing a non-arch specific implementation, which forces anyone using gxhash to select another hash and use cfg directives to choose between them (obviously releasing non-specialized crates that only work on x86-64 and arm64 is not acceptable).
If the user selecting another hash is desired, then all GxHash types should take the other hash as a generic parameter, for user convenience.
The text was updated successfully, but these errors were encountered:
Yes you're right, it is important to provide a fallback. That's probably the 1st priority. Something can be done in the spirit of what is done for the crate ahash
The crate seems to be missing a non-arch specific implementation, which forces anyone using gxhash to select another hash and use cfg directives to choose between them (obviously releasing non-specialized crates that only work on x86-64 and arm64 is not acceptable).
If the user selecting another hash is desired, then all GxHash types should take the other hash as a generic parameter, for user convenience.
The text was updated successfully, but these errors were encountered: