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
If we have the following Rust items, the PV backend will generate ambiguous accessors for them
struct Foo(Vec<u8>); struct Bar(Vec<u8>); fn qux(a: Foo, b: Bar) -> bool{ a.0 == b.0 }
The generated PV shows that the backend generates the same destructor accessor_mwe__0 for both types, which is not supported by ProVerif.
accessor_mwe__0
type mwe__t_Foo. [...] fun mwe__Foo(bitstring) : mwe__t_Foo [data]. reduc forall mwe__0: bitstring; accessor_mwe__0(mwe__Foo(mwe__0)) = mwe__0. type mwe__t_Bar. [...] fun mwe__Bar(bitstring) : mwe__t_Bar [data]. reduc forall mwe__0: bitstring; accessor_mwe__0(mwe__Bar(mwe__0)) = mwe__0. letfun mwe__qux(a : mwe__t_Foo, b : mwe__t_Bar) = core__cmp__f_eq(accessor_mwe__0(a), accessor_mwe__0(b)).
The text was updated successfully, but these errors were encountered:
jschneider-bensch
Successfully merging a pull request may close this issue.
If we have the following Rust items, the PV backend will generate ambiguous accessors for them
The generated PV shows that the backend generates the same destructor
accessor_mwe__0
for both types, which is not supported by ProVerif.The text was updated successfully, but these errors were encountered: