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
It seems the update to arbitrary 1.0 requires const generics, which were stabilized only incredibly recently (March of this year). This breaks most distro rustc users as relatively few distros have shipped 1.51 into their normal release channels. The requiring of super recent rustc in a minor-minor version is somewhat surprising, and broke some of our build pipeline.
Is it possible to define the MSRV policy and maybe make the arbitrary feature optional, given its not required unless you want the fuzzer to map the types automagically?
The text was updated successfully, but these errors were encountered:
It seems the update to
arbitrary
1.0 requires const generics, which were stabilized only incredibly recently (March of this year). This breaks most distro rustc users as relatively few distros have shipped 1.51 into their normal release channels. The requiring of super recent rustc in a minor-minor version is somewhat surprising, and broke some of our build pipeline.Is it possible to define the MSRV policy and maybe make the
arbitrary
feature optional, given its not required unless you want the fuzzer to map the types automagically?The text was updated successfully, but these errors were encountered: