We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The theory is that Verus is checking your code for both 32-bit and 64-bit architectures, no matter which machine you're running on.
However, assumptions about your platform can leak into Verus's assumptions:
proof fn test<const X: usize>() ensures 0 <= X <= usize::MAX, { } proof fn ensure_is_64_bit() ensures usize::MAX == 0xffff_ffff_ffff_ffff, { test::<0xffff_ffff_ffff>(); }
The text was updated successfully, but these errors were encountered:
@tjhance we should coordinate a fix for this that also addresses the const-eval related issues (from 1.79).
Sorry, something went wrong.
No branches or pull requests
The theory is that Verus is checking your code for both 32-bit and 64-bit architectures, no matter which machine you're running on.
However, assumptions about your platform can leak into Verus's assumptions:
The text was updated successfully, but these errors were encountered: