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 recent update to foldhash as the default hasher for map in v0.8.6 introduces a dependency on std::time within foldhash. This poses a problem for targets like zkvm, where time is not available, leading to errors.
This change effectively breaks compatibility with zkvm and potentially other targets lacking std::time. Projects relying on Alloy and targeting these platforms will no longer work successfully.
The text was updated successfully, but these errors were encountered:
I've removed the default in #771, but this is also the default hasher for Hashbrown, so consider opening an issue/PR in foldhash to extend disabling the time query cfg
I've reverted #771 but gated the default hasher to not include target_os = "zkvm" in #777. I would still recommend making the fix in foldhash since you would encounter this in any hashbrown 0.15 usage.
Component
primitives
What version of Alloy are you on?
alloy-primitives v0.8.6
Operating System
None
Describe the bug
The recent update to
foldhash
as the default hasher for map inv0.8.6
introduces a dependency onstd::time
withinfoldhash
. This poses a problem for targets likezkvm
, where time is not available, leading to errors.This change effectively breaks compatibility with
zkvm
and potentially other targets lackingstd::time
. Projects relying on Alloy and targeting these platforms will no longer work successfully.The text was updated successfully, but these errors were encountered: